--- title: "Tax" description: "A non-technical ecosystem overview of Tax in RevCent, focused on how Tax records represent tax applied to commerce activity, how Tax connects to Third Party Integrations, Third Party Shops, Sales, Subscription Renewals, Products, Product Sales, Shipping, payments, refunds, and reporting, and how Tax fits into the broader RevCent relationship graph." type: "item" company: "RevCent" canonical: "https://revcent.com/documentation/markdown/ecosystem/item/Tax.md" relationships: - name: "Third Party Integration" url: "https://revcent.com/documentation/markdown/ecosystem/feature/ThirdPartyIntegration.md" - name: "Third Party Shop" url: "https://revcent.com/documentation/markdown/ecosystem/feature/ThirdPartyShop.md" - name: "Sale" url: "https://revcent.com/documentation/markdown/ecosystem/item/Sale.md" - name: "Subscription Renewal" url: "https://revcent.com/documentation/markdown/ecosystem/item/SubscriptionRenewal.md" technical_links: web_app: "https://kb.revcent.com/en/revenue/tax" api: section: "https://revcent.com/docs/api/v2#section-tax" operations: - name: "Get Taxes" operation_id: "GetTaxes" operation: "https://revcent.com/docs/api/v2#operation-GetTaxes" schema: "https://revcent.com/documentation/files/api/operation/GetTaxes.json" - name: "Get A Tax" operation_id: "GetTax" operation: "https://revcent.com/docs/api/v2#operation-GetTax" schema: "https://revcent.com/documentation/files/api/operation/GetTax.json" - name: "Refund A Tax" operation_id: "RefundTax" operation: "https://revcent.com/docs/api/v2#operation-RefundTax" schema: "https://revcent.com/documentation/files/api/operation/RefundTax.json" mcp: overview: "https://revcent.com/documentation/markdown/mcp/operation/OverviewTax.md" operations: - name: "Get Taxes" operation_id: "GetTaxes" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetTaxes.md" available_via_ai: true - name: "Get A Tax" operation_id: "GetTax" markdown: "https://revcent.com/documentation/markdown/mcp/operation/GetTax.md" available_via_ai: true - name: "Refund A Tax" operation_id: "RefundTax" markdown: "https://revcent.com/documentation/markdown/mcp/operation/RefundTax.md" available_via_ai: true bigquery_schema: "https://revcent.com/documentation/files/bigquery/dataset.json" bigquery_tables: - "tax" --- # Tax Tax in RevCent is the item that represents tax recorded on a commerce event. A Tax record is created when tax is applied to an initial Sale, a Subscription Renewal, a Trial expiration payment, a salvage recovery, or another transaction-related commerce flow where tax needs to be represented inside RevCent. In the RevCent ecosystem, Tax is not just an accounting note. It is part of the same relationship graph as Customers, Sales, Product Sales, Products, Shops, Subscription Renewals, Trials, Shipping, payments, refunds, chargebacks, and reporting. Tax helps answer business questions such as: - How much tax was collected on a Sale? - Which shop or campaign generated the tax? - Which Product or Product Sale was the tax connected to? - Was tax collected during the initial checkout, a renewal, or a trial expiration? - Was any tax later refunded? - Which tax provider or tax calculation path was involved? - How does tax affect gross revenue, net revenue, refunds, and customer order history? ## Why Tax Is an Item Tax is an item because each Tax record represents a specific tax occurrence inside the commerce lifecycle. A Tax record is not the same thing as a reusable tax configuration. The distinction is important: - **Tax** is the tax amount recorded on a specific commerce event. - **Tax Profile** is the configuration that helps RevCent determine how tax should be calculated when RevCent is responsible for calculating it. - **Third Party Integration** may represent the connected tax provider used by a Tax Profile. - **Third Party Shop** may represent the storefront that supplied tax during an initial shop checkout. A Tax record is therefore the result of tax being applied. It becomes part of the historical commerce graph. ## Core Purpose The core purpose of Tax in RevCent is to preserve tax context inside the transaction lifecycle. Tax supports: - order totals, - renewal totals, - trial expiration totals, - refund accuracy, - customer support visibility, - shop reconciliation, - tax provider visibility, - accounting review, - gross and net revenue analysis, - product-level reporting, - shop-level reporting, - campaign-level reporting, - subscription and trial reporting. Tax allows RevCent to treat tax as a connected commerce item rather than a detached number. ## Tax in the RevCent Ecosystem Tax sits near the center of the commerce graph because it can attach to many revenue-producing records. A simplified relationship view is: - Customer starts a purchase, renewal, trial expiration, or recovery flow. - RevCent records the related Sale, Subscription Renewal, Trial, Product Sale, Shipping, and payment context. - Tax is recorded when tax applies. - The Tax record remains linked to the surrounding commerce items. - If tax is refunded, refund-related records preserve the tax refund context. - BigQuery makes the tax relationship visible for reporting and analysis. Tax can be connected to: - Customers, - Sales, - Product Sales, - Products, - Product Groups through related Products, - Subscription Renewals, - Subscriptions, - Trials, - Third Party Shops, - Third Party Integrations, - Campaigns, - Shipping, - Transactions, - PayPal Transactions, - Offline Payments, - Checks, - Pending Refunds, - Salvage Transactions, - Chargebacks, - PayPal Disputes, - Fraud Detections, - AI workflows, - API activity, - Metadata, - reporting and analytics. This makes Tax a useful graph node for understanding total order economics. ## Tax vs Tax Profile Tax and Tax Profile should not be confused. A **Tax record** is created when tax is actually recorded on commerce activity. A **Tax Profile** is a reusable configuration that helps determine how RevCent should calculate tax when RevCent is responsible for calculating it. A Tax Profile may use RevCent’s internal ZIP-based tax calculation or a tax-focused Third Party Integration, depending on how the merchant configures tax. Simple distinction: - Tax Profile answers: “How should tax be calculated?” - Tax answers: “What tax was recorded on this commerce event?” Tax Profile setup affects future tax behavior. Tax records preserve historical tax activity. ## How Tax Is Created Tax is created when tax is recorded as part of a transaction-related event. The most common paths are: - tax on an initial Sale, - tax on a Subscription Renewal, - tax on a Trial expiration payment, - tax related to Shipping, - tax connected to a payment record, - tax connected to a refund workflow, - tax connected to a shop-originated order. There are two important sources of tax context: 1. **Shop-supplied tax** from a storefront such as WooCommerce. 2. **RevCent-calculated tax** using Tax Profile configuration. Which path is used depends on where the commerce event originated and who is responsible for calculating tax at that point in the lifecycle. ## Shop-Supplied Tax vs RevCent-Calculated Tax This is one of the most important concepts for understanding Tax in RevCent. For an initial checkout from a Third Party Shop such as WooCommerce, the storefront may already calculate tax during checkout. In that case, RevCent should generally preserve the tax amount supplied by the shop for the initial Sale. For later lifecycle events that happen inside RevCent, such as Subscription Renewals and Trial expiration payments, RevCent may need to calculate tax itself using Tax Profile configuration. This creates a clear model: - Initial WooCommerce or shop checkout tax can come from the shop. - Later RevCent-managed renewal tax can come from RevCent Tax Profiles. - Later RevCent-managed trial expiration tax can come from RevCent Tax Profiles. - Custom stores or API-driven flows may use RevCent tax calculation when external tax is not supplied. This distinction helps avoid duplicate tax calculation, mismatched order totals, refund confusion, and reporting inconsistencies. ## Relationship to Third Party Integrations Third Party Integrations are a feature that can connect RevCent to external providers. For Tax, the most important example is a tax-focused integration, such as a provider that calculates tax for purchases, renewals, or other taxable activity. A Tax Profile may reference a tax-related Third Party Integration when a merchant wants RevCent to use an external tax provider rather than only internal ZIP-based logic. This relationship matters because Tax can be analyzed by tax source: - tax calculated internally, - tax supplied by a shop, - tax calculated through a connected tax provider, - tax connected to a specific campaign or shop, - tax later refunded or adjusted. In the relationship graph, Third Party Integration is the feature that helps connect RevCent to the outside tax calculation system, while Tax is the recorded result inside RevCent commerce data. ## Relationship to Third Party Shops Third Party Shops are storefronts or external shopping carts connected to RevCent. A Third Party Shop can originate a Sale, and that Sale may include tax. For WooCommerce and similar shops, the shop may already know the customer cart, shipping address, product tax behavior, coupons, shipping methods, and checkout tax settings. Because of that, the initial shop checkout may provide the tax amount that RevCent records for the initial Sale. The relationship looks like this: - Third Party Shop receives the customer checkout. - Shop calculates or supplies the initial checkout tax when applicable. - RevCent records the Sale. - Tax becomes connected to the Sale, Product Sales, Customer, Shop, payment records, and reporting. For recurring or delayed lifecycle events, such as Subscription Renewals or Trial expiration payments, the shop is no longer running the original checkout session. RevCent may therefore calculate tax using Tax Profiles. This allows WooCommerce or a custom shop to remain the storefront while RevCent remains the backend commerce engine for renewals, trial expirations, refunds, reporting, and tax relationship visibility. ## Relationship to Sales A Sale is one of the primary places where Tax appears. A Sale represents a customer purchase attempt involving one or more Products. If tax applies to the order, Tax records help preserve that tax context. Tax connected to a Sale can support: - total order review, - customer support, - order reconciliation, - shop reconciliation, - product-level revenue analysis, - refund decisions, - accounting review, - campaign analysis, - reporting by payment type. A Sale can be connected to Tax, Product Sales, Shipping, discounts, payments, refunds, tracking, and metadata. Tax becomes one of the financial components that helps explain the full order economics. ## Relationship to Product Sales Product Sales are the line items inside a Sale. Tax can connect to Product Sales, which is useful because tax often needs to be understood at the item level, not just the order level. Product Sale relationships help answer: - which product generated taxable activity, - how tax was distributed across line items, - which Product Groups generated taxable revenue, - which products had tax refunded, - whether tax is tied to shippable or non-shippable items, - how tax varies across product categories, shops, campaigns, and offers. This is especially important when a Sale contains more than one Product. Without the Product Sale relationship, Tax would only be visible at the order level. With Product Sale visibility, tax can become part of product-level business analysis. ## Relationship to Subscription Renewals Subscription Renewals are recurring billing events. Tax can be connected to Subscription Renewals when a renewal payment requires tax. This matters because the initial Sale and future renewal payments are different events. For example: - The initial Sale may come from WooCommerce and use shop-supplied tax. - The Subscription Renewal may happen later inside RevCent. - The renewal may need a fresh tax calculation. - The resulting Tax record connects to the Subscription Renewal. This helps recurring businesses understand tax across the customer lifecycle, not just at the first checkout. Tax connected to Subscription Renewals can support reporting on: - recurring tax collected, - tax by Subscription Profile, - tax by renewal cycle, - tax by product, - tax by campaign, - tax by shop, - tax refunds on renewals, - tax impact on recurring gross and net revenue. ## Relationship to Trials Trials can also lead to Tax records. A Trial may start with an initial offer and later expire into a paid transaction. When a trial expiration payment occurs, RevCent may need to calculate tax at the time of expiration. This is different from the initial trial Sale. A Trial relationship can look like this: - Product is configured with trial behavior. - Customer starts the trial through a Sale. - Trial remains active until the configured end date. - Trial expiration payment is attempted later. - Tax may be calculated for the expiration payment. - Related payment, shipping, refund, and reporting records connect back to the Trial. This helps businesses analyze trial conversion economics with tax included. ## Relationship to Shipping Tax can be connected to Shipping when shipping is part of the taxable commerce event. Shipping records may be created for shippable Products sold in an initial Sale, a Subscription Renewal, or a Trial expiration flow. Tax and Shipping can be connected because: - some orders include taxable shipping charges, - tax may depend on the customer or shipping address, - refunds may involve Product Sale amounts, Shipping amounts, and Tax amounts, - fulfillment and support teams may need full order context, - BigQuery reporting can show tax alongside shipping and product revenue. This relationship helps merchants understand the complete cost and revenue picture for physical product sales. ## Relationship to Payments Tax can connect to the payment method used for the commerce event. Tax may be associated with: - credit card Transactions, - PayPal Transactions, - Offline Payments, - Checks, - payment activity connected to Subscription Renewals, - payment activity connected to Trial expirations, - payment activity connected to salvage recovery. This matters because refund handling, processor behavior, dispute handling, and payment reconciliation can differ by payment method. Tax does not exist separately from the payment lifecycle. It is part of the same financial graph. ## Relationship to Refunds Refunds are one of the most important reasons Tax needs to be its own item. A customer refund may involve: - Product Sale refund, - Shipping refund, - Tax refund, - full Sale refund, - partial order refund, - refund tied to a Subscription Renewal, - refund tied to PayPal, credit card, offline, or check payment context. Tax refunds need to preserve tax-specific context so reporting can distinguish product revenue refunds from tax refunds. Pending Refunds can connect to Tax when tax is part of a refund action. This helps answer: - was tax refunded, - was the tax refund full or partial, - which order or renewal did the refund belong to, - which product or shipment did it relate to, - which payment method handled the refund, - whether the refund was issued inside RevCent or offsite, - how refunded tax affects reporting. Tax refunds should be viewed as part of a broader refund graph, not as an isolated adjustment. ## Relationship to Chargebacks, Disputes, and Fraud Review Tax can also appear in dispute and risk-related contexts. A Chargeback or PayPal Dispute may involve a Sale that included tax. Fraud Detection may also connect to the original Sale or shop context where tax was recorded. This makes Tax useful for reviewing: - disputed order totals, - tax involved in chargebacks, - tax connected to PayPal disputes, - tax tied to high-risk campaigns or shops, - refund-adjusted tax after disputes, - tax visibility in fraud and support workflows. Tax is not the fraud signal itself, but it is part of the financial context surrounding risk and dispute events. ## Relationship to Campaigns and Customers Tax can be connected to Customers and Campaigns. Customer context helps support teams understand what tax was charged to a specific customer and whether any tax was refunded. Campaign context helps merchants understand how tax appears across acquisition sources, brands, funnels, offers, or business units. This is useful for: - tax by campaign, - tax by customer geography, - tax by shop, - tax by offer type, - tax refunds by customer segment, - tax on subscription-heavy campaigns, - tax on trial-based funnels, - tax on high-volume product lines. ## Relationship to Metadata Metadata can provide extra business context around Tax and related commerce records. Tax may inherit or connect to metadata through the surrounding Sale, Product Sale, Subscription Renewal, Shop, Customer, or payment records. This can help businesses group tax activity by internal concepts such as: - brand, - funnel, - fulfillment type, - marketing source, - tax review status, - accounting batch, - support resolution, - integration source, - custom reporting category. Metadata makes the tax graph more meaningful without changing the underlying Tax item itself. ## Tax and Email Templates Email Templates can use the wider commerce context around Tax, especially when communicating about orders, renewals, refunds, invoices, shipping, or customer support outcomes. Examples of email situations where tax context may matter include: - order confirmation, - refund confirmation, - subscription renewal receipt, - trial expiration payment confirmation, - support follow-up, - invoice-style communication, - internal accounting notification. The Email Template does not replace the Tax item. It can communicate information from the related Sale, Renewal, payment, refund, or customer context. ## Tax and Functions Functions can help automate tax-adjacent workflows. For example, Functions can: - notify an external accounting system after taxable activity, - send tax-related order context to an external service, - enrich internal reporting categories, - add metadata for accounting workflows, - support custom storefront behavior, - help integrate with a non-native third-party tax-related process, - prepare custom data for Email Templates, - help AI Assistants or AI Voice Agents safely retrieve custom context. Functions are especially useful when a merchant wants custom behavior around tax data or wants to integrate with a third-party service that is not available as a native Third Party Integration. ## Tax and AI Assistants AI Assistants can use Tax context to support operational workflows. Examples include: - summarizing tax on a Sale, - reviewing tax-related refund requests, - identifying unusual tax amounts, - preparing internal notes for accounting review, - notifying support when tax appears missing or unexpected, - helping analyze tax in BigQuery reporting, - coordinating tax-related support workflows with Functions or Email Templates. AI Assistants should not provide tax or legal advice. They should explain what RevCent records show and route compliance questions to the merchant’s tax professional or tax provider. ## Tax and AI Voice Agents AI Voice Agents may encounter tax-related customer questions. Examples include: - “Why was I charged tax?” - “Was tax refunded?” - “Why was my renewal taxed?” - “Can I get the tax back?” - “What tax was applied to my order?” A voice workflow can use the related Sale, Tax, Subscription Renewal, Customer, payment, and refund context to answer what RevCent records show. As with AI Assistants, AI Voice Agents should not provide tax or legal advice. Complex tax questions should be escalated to the merchant or tax professional. ## Viewing and Managing Tax Tax can be viewed in the RevCent web app through the Revenue area. The web app helps users inspect Tax records and see related entities such as Sales and Product Sales. The RevCent API and MCP can also support retrieving tax-related information, refunding tax when appropriate, and managing tax-related configuration. In this ecosystem document, those are best understood as management and automation paths rather than as the main subject. The main business idea is that Tax records can be reviewed, connected, refunded, and reported on as part of the broader commerce graph. ## BigQuery Reporting and Relationship Visibility The `tax` BigQuery table makes Tax visible for reporting and relationship analysis. For ecosystem graphing, BigQuery helps show how Tax connects to surrounding commerce activity. Tax reporting can be used to understand: - tax collected over time, - tax by Sale, - tax by Subscription Renewal, - tax by Trial expiration, - tax by Product Sale, - tax by Product, - tax by Product Group through related Product data, - tax by Third Party Shop, - tax by Third Party Integration or tax provider path, - tax by Campaign, - tax by Customer, - tax by payment type, - tax connected to Shipping, - tax connected to Pending Refunds, - tax connected to Chargebacks or disputes, - tax refunds over time, - tax impact on gross and net revenue. BigQuery is important because Tax often needs to be analyzed across many records, not one record at a time. A support user may inspect one Tax record in the web app. A reporting user may use BigQuery to understand tax behavior across the entire business. ## Business Benefits Tax provides several business benefits inside RevCent. It gives merchants visibility into what tax was charged, why it appears in the order graph, and how it relates to the surrounding revenue lifecycle. Key benefits include: - clearer order totals, - better refund accuracy, - better subscription renewal reporting, - better trial conversion reporting, - improved shop reconciliation, - better payment and dispute context, - better product-level analysis, - better campaign-level tax visibility, - better customer support answers, - better accounting review, - better integration visibility, - better AI and automation context. Tax is a small item in a single order, but a major source of business insight across many orders. ## Tax as a Relationship Graph Node In a RevCent relationship graph, Tax helps connect financial activity to operational activity. A Tax node may connect outward to: - Sale, - Product Sale, - Product, - Customer, - Third Party Shop, - Subscription Renewal, - Subscription, - Trial, - Shipping, - Transaction, - PayPal Transaction, - Offline Payment, - Pending Refund, - Chargeback, - Campaign, - Metadata, - Third Party Integration. This graph helps explain not only that tax happened, but where it came from and what it affected. For example: - A Sale explains the purchase event. - A Product Sale explains the line item. - Tax explains the tax portion. - Shipping explains fulfillment cost and delivery context. - Transaction or PayPal Transaction explains payment context. - Pending Refund explains returned tax or related refund activity. - Subscription Renewal explains recurring revenue context. - Third Party Shop explains storefront origin. - Third Party Integration explains external tax provider involvement. - BigQuery makes the full graph reportable. ## Common Ecommerce Use Cases Common Tax use cases include: - reviewing tax charged on a customer order, - reviewing tax on a renewal, - reviewing tax on a trial expiration payment, - reconciling WooCommerce orders with RevCent Sales, - understanding tax by shop, - understanding tax by campaign, - understanding tax by product, - reviewing tax refunds, - investigating tax on disputed orders, - reviewing tax tied to alternate payment methods, - preparing accounting exports or summaries, - helping support explain a customer receipt, - using AI to summarize tax context for a support case. ## Common Mistakes to Avoid Do not treat Tax as a standalone accounting note with no relationships. Do not confuse Tax with Tax Profile. Tax is the recorded item; Tax Profile is configuration. Do not assume initial WooCommerce checkout tax and future renewal tax come from the same calculation source. Do not use RevCent Tax Profiles to recalculate initial shop tax when the shop already supplied tax. Do not forget that Subscription Renewals and Trial expiration payments may need tax handling later, after the original checkout. Do not refund tax without understanding the related Sale, Product Sale, Shipping, payment, and refund context. Do not provide legal or tax compliance advice through AI or support automation. Do not use one-record operational review as a substitute for BigQuery reporting when the goal is reporting, metrics, aggregation, or business analysis. ## AI/MCP Guidance When an AI Assistant, AI Voice Agent, or MCP workflow works with Tax, it should treat Tax as part of a larger commerce graph. Important guidance: - Explain Tax in relation to the Sale, Product Sale, Renewal, Trial, Shop, payment, or refund it belongs to. - Use Tax Profile context only when discussing how RevCent calculates tax for future or recurring flows. - Use Third Party Integration context when tax is calculated through an external tax provider. - Use Third Party Shop context when tax came from a storefront such as WooCommerce. - Use BigQuery for broad tax reporting and trend analysis. - Avoid tax or legal advice. - Escalate compliance questions to the merchant’s tax professional or tax provider. The best AI behavior is to explain what RevCent records show, connect the related ecosystem items, and avoid making compliance judgments. ## Summary Tax in RevCent is the item that records tax applied to commerce activity. It connects initial Sales, Product Sales, Subscription Renewals, Trials, Shipping, payments, refunds, Third Party Shops, Third Party Integrations, Customers, Campaigns, and reporting. Tax Profiles help determine how tax should be calculated when RevCent is responsible for calculation. Third Party Shops may provide tax during initial checkout. Third Party Integrations may support external tax-provider calculation. The `tax` BigQuery table makes Tax visible across the broader relationship graph so businesses can understand tax by sale, product, renewal, shop, campaign, customer, payment type, refund behavior, and lifecycle stage. Tax is most useful when viewed as part of the complete RevCent commerce ecosystem rather than as an isolated amount. --- Document Parent Directory * [Items](https://revcent.com/documentation/markdown/ecosystem/item/index.md) - Non-technical markdown documentation for items within the RevCent ecosystem. An item is an entity that is spawned as a result of a feature or operation conducted within the RevCent ecosystem.