QuickBooks Tags

The whole point is that they stay out of the ledger

Most tracking mechanisms in QuickBooks change what your financial statements can be sliced by. Tags were built to do the opposite, and that is a feature rather than a shortcoming, provided you wanted it.

Intuit describes the boundary in one sentence: tags monitor "specific areas of your business without affecting your accounting books (General Ledger)". Nothing you tag moves between accounts. No balance changes. A tagged invoice and an untagged invoice post identically.

That makes tags genuinely useful for questions that are not accounting questions. Which trade show produced these sales. Which of three ad campaigns the month's new customers came from. Which jobs a temporary crew worked on. These are operational questions with a financial shape, and answering them by opening new accounts or classes would clutter a chart of accounts permanently for something you care about for six weeks.

The trap is expecting a tag to show up where classes and locations do. Intuit spells out the limit: tags "don't impact your P&L or Balance Sheet reports unless you specifically run a Profit and Loss by Tag report". One dedicated report reads them. Your ordinary Profit and Loss does not. A business that tagged a year of revenue by channel, then asked for a channel breakdown in a standard P&L, is asking the wrong report a reasonable question.

Tags are being withdrawn, and the dates are already in effect

This is the fact that changes what you should do, and it is not a rumour or a deprecation warning. Intuit has published a transition schedule, and the first dates have passed.

On creation, Intuit states: "Beginning May 16, 2025, there will no longer be an option to create tags for reporting. Instead, there is an option to migrate tags to a custom field for tracking and reporting purposes for all QuickBooks Online plans."

On who can still use them: "Customers who have never used tags will no longer see the option to use tags by May 19, 2025", and "Existing users who have used tags can continue to use them until May 19, 2028."

On the end state, which is the sentence worth reading twice: "May 16, 2025 - May 15, 2028 - You can view tags and generate reports for historical transactions. After May 15, 2028, the ability to view tags and generate reports will no longer be available. Tags will be removed from QuickBooks Online and they will disappear from historical transactions."

Read plainly, that last clause says the historical record goes too. This is not a feature being frozen with the old data left readable. If you have years of tagged transactions and the tag is how you identify a cohort, that identification has an expiry date, and the reporting you would use to extract it expires at the same moment.

Two practical consequences follow. If you are choosing a tracking dimension now, do not choose tags. If you already have tags carrying something you care about, the work is to migrate them and to export the historical reporting you would want to keep, rather than to assume it will still be there.

What custom fields do instead, and what changes

Intuit names the replacement rather than leaving a gap: the migration path is from tags to a custom field, offered "for all QuickBooks Online plans".

The mechanical difference worth understanding before you migrate is that a tag and a custom field are shaped differently. A tag is a label you attach, drawn from a flat list you extend as you go. A custom field is a field on the form, and when it is a dropdown it carries a defined set of values. Intuit puts a number on the conversion: you "can add up to 60 existing tags as values to a single custom field dropdown to categorize transactions for review".

Sixty is a real ceiling if your tag list grew organically. A tag list built one campaign at a time over three years is frequently longer than sixty entries, and consolidating it into a dropdown means deciding which distinctions actually earned their place. That is worth doing deliberately rather than discovering at migration time.

The more important continuity question is whether a custom field keeps the property that made tags attractive. It does, in the sense that matters here: a custom field is metadata on the form rather than an accounting dimension, so it still does not move balances. If you need a dimension that does change what your P&L can be sliced by, neither tags nor custom fields were ever the answer, and the choice is between classes, locations and projects.

Which dimension you actually want

Tags sit apart from the other three tracking mechanisms in QuickBooks, and the difference is not granularity but whether the ledger is involved at all.

Classes, locations and projects are accounting dimensions. They change what your financial statements can be broken down by, they come with their own constraints, and choosing between them is a real decision with its own trade-offs. Class tracking and location tracking both require Plus or Advanced.

Tags were the option outside that system: no plan requirement of the same kind, no effect on the ledger, and no place in standard reporting. That combination is exactly right for lightweight operational tracking and exactly wrong for anything you need on a financial statement.

With tags being withdrawn, the practical shape of the decision has simplified. If the thing you are tracking belongs on your P&L, you wanted a class, a location or a project all along, and the entries linked below cover how each behaves and what each costs you. If it does not belong on your P&L, a custom field is the supported way to carry it forward.