QuickBooks Online Tags Not in API? 3 Workarounds That Work

Introduction

QuickBooks Online Tags have historically helped businesses categorize transactions for reporting.

However, developers building integrations often encounter a significant limitation: the standard QuickBooks Online Accounting API does not provide supported endpoints for managing legacy Tags or retrieving their transaction associations.

This creates problems when businesses want to sync event-level classifications with Salesforce, build Power BI financial dashboards, or maintain custom reporting dimensions across accounting and operational systems.

There is also an important product change to consider. QuickBooks Online has been transitioning away from legacy Tags in certain markets, while Intuit has introduced newer Custom Fields API capabilities for eligible integrations.

In this guide, we explain why legacy QuickBooks Tags cannot be accessed through the standard Accounting API and examine three practical alternatives: Custom Fields, Classes and Locations, and external transaction mapping.

We’ll also explain how to choose the right approach for your integration requirements.

What Are Tags and Tag Groups in QuickBooks Online?

QuickBooks Online Tags were designed to help businesses assign descriptive labels to transactions, including invoices and expenses, without changing their chart of accounts.

A Tag Group organized related labels, such as Charity Gala and Holiday Party under an Events group, allowing users to review activity by category within supported QuickBooks reports.

If you’re wondering how tags work in QuickBooks Online, here’s a simple example:

Let’s say you run a business selling products through your eCommerce store.

Then, you can tag expenses related to different product lines, allowing you to see the profitability of each line without altering your accounting records.

Tags in QuickBooks Online help various industries track and organize transactions.

• E-commerce: Tag different product lines to analyze their profitability.
• Construction: Tag expenses by project to monitor cost overruns.
• Event Planning: Tag transactions for each event to understand event-specific earnings and expenses.
• Healthcare: Tag services provided to track the profitability of each type.
  
  Tag Groups for events.
  

  Note: These screenshots illustrate the legacy QuickBooks Tags interface. Tags availability and functionality may differ depending on the account’s region and current product settings.

Are QuickBooks Online Tags Still Available in 2026?

QuickBooks Online has changed the availability of legacy Tags, making it important to distinguish historical tracking data from features recommended for new integrations.

In the United States, Intuit’s guidance states that Tags became read-only in May 2025, preventing users from assigning new Tags.

Existing tagged data remains accessible during a transition period, with removal scheduled for May 15, 2028.

Regional policies may differ. For example, Intuit’s UK support team has stated that some existing UK customers can continue using Tags without a confirmed removal date.

For businesses developing new QuickBooks integrations, the practical recommendation is to avoid designing new reporting workflows around unsupported legacy Tags API functionality.

Instead, evaluate Custom Fields, Classes, Locations, or an external mapping system based on the data that needs to be retrieved.

The product lifecycle change does not mean that historical Tag assignments can be extracted through the standard QuickBooks Online Accounting API.

Historical reporting and future transaction categorization should be treated as separate requirements.

Intuit’s Tags retirement and migration guidance

The Problem in QuickBooks Online API: No Support for Tags

Consider a business that uses Salesforce for customer relationship management, QuickBooks Online for financial transactions, and Microsoft Power BI for consolidated reporting.

The business organizes events throughout the year and needs to track income and expenses for each event.

Historically, its accounting team used QuickBooks Tags such as Charity Gala and Holiday Party to categorize related transactions.

When the development team attempted to consolidate this information in Power BI, it discovered that the QuickBooks connector could retrieve accounting records but did not provide the legacy Tag assignments associated with each transaction.

Initially, the team considered other BI platforms. However, changing reporting tools would not solve the underlying limitation.

The standard QuickBooks Online Accounting API does not expose legacy Tags and their transaction associations through supported public endpoints.

As a result, the integration could retrieve an invoice’s accounting details but could not automatically determine which legacy event Tag the user had assigned inside QuickBooks.

The solution required a different reporting architecture. Instead of relying on unavailable Tags API data, the integration needed an accessible event identifier stored in an eligible QuickBooks field or maintained in a connected reporting database.

Why QuickBooks Tags Are Not Available Through the API

The QuickBooks Online Accounting API exposes supported accounting objects and their documented fields. However, legacy QuickBooks Tags are not provided as an equivalent public resource for creating, querying, updating, or deleting Tags and their transaction associations.

For example, supported invoices may expose Class and Location references, as well as eligible Custom Field data.

These are different from the legacy Tags users previously assigned through the QuickBooks interface.

The distinction matters when designing integrations:

The availability of a transaction through the API does not imply that every classification visible in the QuickBooks interface is included in its API response.

Developers should therefore evaluate each reporting dimension individually and confirm whether it can be retrieved using documented QuickBooks API operations.

Intuit Developer: Invoice API reference

How to Use QuickBooks Online Tags When the API Doesn’t Support Them

1. Use QuickBooks Custom Fields as Tag Replacements

QuickBooks Custom Fields can provide a practical alternative when a business needs additional identifiers on supported accounting records.

For example, an event-management company could define an Event Code field on eligible transactions and use values such as CHARITY-2026 or HOLIDAY-2026 to associate accounting records with reporting events.

Unlike legacy Tags, supported Custom Fields can be accessed using documented API capabilities, subject to the QuickBooks subscription, transaction type, developer permissions, and API implementation.

Example: Mapping Event Identifiers to QuickBooks Custom Fields

In this example, the integration stores or reads the event identifier through an eligible Custom Field rather than attempting to retrieve a legacy Tag.

Before implementing this approach, the developer must confirm that the selected transaction type supports the field and that the integration has permission to perform the required operation.

Custom Fields API Limitations Developers Should Understand

QuickBooks currently has different Custom Fields capabilities across its legacy REST API and newer GraphQL API.

The legacy REST implementation exposes a limited number of supported string Custom Fields on eligible transactions.

Intuit’s newer Custom Fields GraphQL API supports String, Integer, Date, and List field types with broader functionality for eligible QuickBooks subscriptions.

However, access to the newer API is not automatically included with every developer application.

Intuit Developer Support has identified eligibility requirements under the App Partner Program, including qualifying Silver, Gold, and Platinum partner tiers.

Transaction coverage also depends on the QuickBooks subscription. For example, QuickBooks Online Advanced supports more Custom Fields and a broader set of eligible transactions than Essentials.

Developers should verify their app’s partner tier, available OAuth scopes, target company subscription, transaction coverage, and read/write permissions before choosing Custom Fields as the integration’s reporting model.

Key limitation: Custom Fields are not an automatic API-based way to recover historical legacy Tag assignments, and they do not necessarily reproduce Class-based financial reporting.

Intuit: Custom Fields API
Intuit: Legacy Custom Fields

2. Use Classes Instead of Tags

QuickBooks Classes provide a structured way to categorize financial transactions by department, service line, business unit, or another accounting segment.

Unlike legacy Tags, Classes are represented through documented QuickBooks Online Accounting API functionality.

For supported transactions, developers can work with Class references, including the ClassRef field where applicable.

For example, a professional-services company may use Consulting, Implementation, and Support as its reporting Classes.

An integration can use those classifications to associate eligible financial transactions with the appropriate business segment.

Classes are useful when the business wants its reporting dimensions to align with QuickBooks financial reporting.

However, Classes are not a direct replacement for flexible event or campaign labels.

If Classes are already used for departments, assigning them another purpose may weaken the existing accounting structure.

Key limitation: Class tracking availability and transaction-level behavior depend on the QuickBooks plan and configuration.

When Should You Use Locations Instead of Tags?

QuickBooks Locations are designed to categorize accounting activity by branch, office, store, region, or operational location.

The QuickBooks Online Accounting API represents the Location dimension through supported Department references, including DepartmentRef on eligible transactions.

For example, a retail business may assign New York Store and Chicago Store as Locations, then use those classifications for location-based financial analysis.

Locations can be useful when a business previously used Tags to identify operational branches.

They are less appropriate when the requirement involves temporary events or campaigns unrelated to a business location.

Key limitation: Locations should not be repurposed for unrelated classifications when they already serve an established accounting function.

For broader integration planning, see Satva Solutions’ QuickBooks Integration Guide. For scenarios involving information that is unavailable through supported APIs, review QuickBooks API Limitations with Microsoft Power Automate.

3. Store Tags in an External Database

An external mapping database is a suitable alternative when a business needs additional reporting dimensions that cannot be represented through available QuickBooks Custom Fields, Classes, or Locations.

Instead of attempting to create or retrieve legacy Tags through the Accounting API, the integration maintains separate classification records linked to supported QuickBooks transactions.

This approach can support event-level profitability reporting, campaign attribution, project analysis, and cross-system dashboards.

Example: Linking QuickBooks Transactions to External Event Data

Consider the earlier business using QuickBooks Online, Salesforce, and Power BI. Each event has an identifier maintained in its operational system.

A reporting integration retrieves supported QuickBooks transactions and combines them with event classifications from an external database.

The combination of QuickBooks company ID, transaction type, and transaction ID helps identify the accounting record to which the external classification belongs.

The reporting system can then associate invoice and expense amounts with the appropriate event code, allowing event-level reports without needing direct access to legacy Tags.

Important Integration Considerations

Developers should establish a reliable source for external classification values. This may be an event-management platform, CRM, internal application, or controlled manual process.

They should also account for duplicate records, transaction changes, deleted transactions, synchronization failures, and differences between accounting and operational data.

This method does not retrieve the original QuickBooks Tag value through the Accounting API. It creates and manages an independent reporting relationship.

Key limitation: The integration must maintain and validate the external mappings over time.

Which QuickBooks Tags API Alternative Should You Choose?

The appropriate workaround depends on the reporting requirement, available API permissions, and how the business already uses QuickBooks accounting dimensions.

Custom Fields are often worth evaluating first when the requirement involves a structured identifier on an eligible transaction.

Classes and Locations are better suited to established accounting dimensions.

When existing QuickBooks dimensions are already allocated or the business needs multiple independent classifications, an external mapping architecture may provide greater flexibility.

Whichever approach is selected, developers should test representative transactions before deploying the integration.

How Can Businesses Preserve Historical QuickBooks Tags?

Businesses that previously relied on QuickBooks Tags should preserve important historical reporting information before applicable product access changes take effect.

For US QuickBooks Online accounts, Intuit recommends migrating eligible Tag configurations to Custom Fields or exporting historical Tag reports before the scheduled removal.

However, migrating field definitions does not necessarily recreate every historical reporting relationship.

Unsupported transaction types, including certain bank-deposit scenarios, may require separate reporting exports or another preservation strategy.

Businesses should validate their existing Tag reports, determine which transactions need historical classification, and document how future reporting will use the replacement tracking dimensions.

For a detailed migration process, read our QuickBooks Custom Fields Migration Guide.

Recap

The standard QuickBooks Online Accounting API does not provide supported access to legacy Tags and their transaction associations.

Businesses developing integrations can instead consider eligible Custom Fields, Classes, Locations, or externally maintained transaction mappings.

Custom Fields are suitable for additional supported transaction metadata, Classes and Locations support structured accounting categorization, and external mapping addresses more flexible reporting requirements.

The right choice depends on the QuickBooks subscription, API permissions, existing accounting configuration, and the data required by the connected systems.

Before implementation, validate the selected approach against Intuit’s current API documentation and test it using representative transactions.

FAQs

Are QuickBooks Online Tags available in the API?

No. The standard QuickBooks Online Accounting API does not provide supported endpoints for managing legacy Tags or retrieving their transaction associations. Developers can use eligible Custom Fields, Classes, Locations, or external mapping to address related reporting needs.

Can I use Classes instead of Tags in QuickBooks Online?

Yes, Classes are one of the most practical alternatives to Tags because they are supported by the QuickBooks Online API. They work well for tracking departments, business units, service categories, or cost centers. However, Classes are more structured than Tags, so they may not fit every tagging use case.

Can developers sync QuickBooks Tags with another system?

Developers cannot directly synchronize legacy QuickBooks Tag assignments through the standard Accounting API. They can synchronize supported accounting fields or use an external application to maintain additional classification data linked to QuickBooks transaction identifiers.

When should I build a custom QuickBooks integration for tag-like reporting?

You should consider a custom QuickBooks integration when Classes, Locations, or Custom Fields do not support your reporting needs. This is common when businesses need multi-system reporting, transaction-level categorization, automated mapping rules, or data syncing between QuickBooks and platforms like CRMs, ERPs, marketplaces, or BI tools.

Does QuickBooks Online have a Custom Fields API?

Yes. Intuit provides legacy REST Custom Fields capabilities and a newer GraphQL Custom Fields API. Supported field types, transactions, operations, and developer access depend on the applicable API, QuickBooks subscription, and partner permissions.

Can historical QuickBooks Tag data be retrieved using the API?

The standard QuickBooks Online Accounting API does not provide supported access to historical legacy Tag assignments. Businesses should preserve historical reports and evaluate separate data-migration or mapping methods when reporting continuity is required.