--- sourceDocument: Brazil Finance and Supply Chain sourceDocumentLink: https://www.servicenow.com/docs/r/source-to-pay-operations Release : - brazil ft:locale : - en-US ft:publication_title : - Brazil Finance and Supply Chain ft:clusterId : - stpop bundleId : - stpop workflow : - Employee --- # Tax Engine Integration # Tax Engine Integration {#ariaid-title1} Release version: Brazil Updated September 10, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Tax Engine Integration The Tax Engine Integration enables ServiceNow Accounts Payable (AP) Operations to connect with external tax engines to validate supplier-provided taxes against system-calculated taxes. This integration supports invoice types including PO, Non-PO, and credit memos, ensuring tax accuracy and compliance through automatic, manual, or scheduled validation. It enhances invoice processing efficiency by enabling straight-through processing when tax matches occur, and provides clear visibility of tax variances at both the invoice header and line levels. Show full answer Show less ## Key Features * **External Tax Engine Integration:** Connects to enterprise tax engines via the integration framework to calculate authoritative tax amounts. * **Intelligent Tax Validation:** Compares supplier tax with system tax using detailed invoice data such as ship-to location, items, services, amounts, jurisdiction, exemptions, and customer tax configurations. * **Granular Tax Comparison:** Performs validation at both the invoice header and individual line item levels for maximum accuracy. * **Configurable Tolerance:** Allows customers to define acceptable variance thresholds; taxes within tolerance are auto-approved. * **Scheduler-Based Recalculation:** Automatically retries tax validation for invoices with errors or updates, maintaining tax accuracy despite temporary integration issues or invoice changes. * **Multiple Validation Modes:** Supports automatic synchronous validation at key invoice processing stages, manual on-demand validation by AP specialists, and scheduled background revalidation. * **Modular Tax Calculation Framework:** A three-tier architecture integrates AP Operations, the Source-to-Pay integration layer, and the external tax engine for scalable, maintainable tax computation and exception handling. ## How It Works When an invoice reaches the accepted state (Non-PO) or completes PO matching, the system triggers tax validation by sending invoice details to the external tax engine. The engine calculates tax based on configured rules and returns the tax amounts, which the system uses to generate tax lines and compare against supplier taxes. If differences exceed configured tolerances, exceptions are raised for manual review; otherwise, invoices proceed to payment. The integration updates tax status and supports recalculation if invoice data changes. ## Benefits for ServiceNow Customers * **Reduced Manual Effort:** Eliminates manual tax line entry through automated calculation and reconciliation. * **Improved Accuracy:** Utilizes authoritative third-party tax logic to ensure correct tax amounts. * **Enhanced Compliance:** Maintains consistent tax validation across multiple jurisdictions and invoice types. * **Faster Invoice Processing:** Increases straight-through processing rates and reduces exceptions. * **Clear Exception Management:** Provides visibility into over-tax and under-tax variances at detailed levels, facilitating quicker resolution. ## Practical Considerations For customers upgrading to the latest version of Accounts Payable Operations, it is important to run the scheduled job **\[APO - close open exception for deactivated exception definition\]** to close legacy invoice exceptions and ensure smooth tax validation workflows. The integration framework relies on configured mapping tables for data exchange and supports manual intervention for failed tax records. Integrate an external tax engine to validate supplier-provided taxes against calculated from external tax engines resulting in accurate, compliant, straight through processing and improving efficiency. The Accounts Payable invoice processing invokes the external tax engine to validate supplier tax (based on ship to, item, service, category, amounts, jurisdiction, exemptions, other tax configuration) against system tax and drive straight through processing for matching outcomes. During invoice data extraction, the tax rate and tax amount will be stored as supplier tax rate and supplier tax amount at both header and invoice line levels. Tax integration is applicable for invoices of type PO, Non-PO and credit memo; supporting automatic, manual, and scheduled tax validation ensuring taxes remain correct even when invoices change or temporary integration issues occur. How system tax is calculated-When invoice data is submitted to the external tax engine, the system receives the calculated tax amounts based on the invoice details and configuration. The system uses this response to automatically generate tax lines. The generated tax lines are then validated against the supplier-provided taxes at the header and line levels. Tax integration is triggered for invoices: * For Non- PO invoices, after the invoice state is changed to accepted state. * For PO invoices, after the PO matching state is completed. {#tax-engine-integration__ul_fvw_m4t_j3c} ## Key capabilities {#tax-engine-integration__section_bft_cqt_j3c} * External tax engine integration- Connects to enterprise tax engines using integration framework. * Intelligent tax calculation- System validates supplier tax against system tax using invoice fields (based on ship to, item, service, amounts, jurisdiction, exemptions, customer tax configuration). * Granular comparison logic- * Line-level and Header-level validation- The extracted values are stored as it is and the system compares tax at the invoice line item and header level for maximum accuracy. * Configurable tolerance-Define acceptable variance thresholds. The system auto-approves tax when the variance is within the configurable tolerance. * Scheduler based re-calculation- The scheduler will automatically reinitiate the tax integration process for invoices with tax status of integration error, or recalculate tax. {#tax-engine-integration__ul_h4l_4qt_j3c} {#tax-engine-integration__ul_jb5_2qt_j3c} ## Benefits of Tax Engine integration {#tax-engine-integration__section_tgt_jxg_m3c} Customers using tax engine integration benefit from: * Reduced manual effort -- Automatic tax calculation and reconciliation removes the need for manual tax line entry. * Improved accuracy -- Taxes are calculated using authoritative third‑party tax logic. * Stronger compliance -- Consistent validation across jurisdictions and invoice types. * Faster invoice processing -- Higher straight‑through processing rates and fewer exceptions. * Clear exception visibility -- Over‑tax and under‑tax variances are surfaced at line and header levels. {#tax-engine-integration__ul_vyy_kxg_m3c} ## Tax calculation framework {#tax-engine-integration__section_clp_rrt_j3c} The tax calculation framework is structured as a modular, three-tier architecture to promote scalability, maintainability, and extensibility. The framework seamlessly integrates Accounts Payable Operations and the external Tax engine, enabling automated and coordinated tax computation. The validation logic is applied at: * Line‑level and Header-level comparison (primary)- Supplier tax and system tax are compared at the invoice line level and header level for maximum accuracy. * Configurable tolerance-Customers can define acceptable variance thresholds. Invoices within tolerance are automatically approved. {#tax-engine-integration__ul_mkd_sqj_m3c}{#tax-engine-integration__table_abq_srt_j3c__entry__2} | Components | Key functions | |-|-| | The Accounts Payable Operations serves as entry point for tax calculation. When an invoice is in PO matching or accepted state in the Accounts Payable Operations, the system determines if tax calculation is required or not. | * If tax calculation is required, then a record is created in the tax staging table \[sn_spend_intg_tax_staging\], and the tax status is set to in progress. For more information on tax status, see [Tax status](https://www.servicenow.com/docs/oDgtyU~8fvLnPhcQJVa0Ig "The tax status field in the invoice record is used to track the current status of tax validation processing throughout the tax integration workflow.") * If tax calculation isn't required, then the invoice processing continues through the regular exception flow and proceeds to payment. {#tax-engine-integration__ul_bbq_srt_j3c} | | The Source-to-Pay integration framework is a processing layer between Accounts Payable Operations and the external tax engine. | * The vendor defines the data mapping required by the external tax engine. * Mapping tables are used during request creation (outbound) and response processing (inbound) between APO attributes and Accounts Payable Operations. * Responses from the tax engine are sent back to the staging table. * Invoice tax status is updated based on the response. * Failed records are processed manually. For more information on the tables, see [Configuration tables and prerequisites for Tax integration](https://www.servicenow.com/docs/ARa8R_6Fu1LTE5rXagmg_g "Use the configuration tables to enable tax integration with third-party tax engines."). {#tax-engine-integration__ul_cbq_srt_j3c} | | The external tax engine computes the tax. | Calculates the tax and returns the response. The response is processed, tax lines are created automatically for the applicable invoice in Accounts Payable Operations. The system triggers exception engine based on the response from tax engine. Tax exception is raised when supplier tax and system tax mismatch in the invoice. Invoice tax status is set to integration error and Accounts Payable specialist investigates the case manually. If the invoice is modified after last execution (change amounts, add lines or adjust tax codes), then the tax is recalculated. The tax processing is re-initiated. Upon successful validation, the invoice processing proceeds to payment. | [Table 1. Components involved in tax calculation framework] {#tax-engine-integration__table_abq_srt_j3c} ## Tax validation modes {#tax-engine-integration__section_bkr_b53_m3c} Tax calculation and validation can be triggered in multiple ways: * Automatic (synchronous)-Runs automatically at key invoice processing milestones * Manual (on-demand)-AP specialists can trigger tax validation during invoice exception review. This is applicable or accessible from the tax exception * Scheduler re-calculation-Background jobs automatically re‑initiate tax validation for invoices that are in progress, or recalculate tax status and integration error status. This ensures taxes stay accurate even if invoice data is updated or external calls fail temporarily. {#tax-engine-integration__ul_gkd_d53_m3c} ## Tax integration workflow {#tax-engine-integration__section_bvx_bst_j3c} A high level workflow of how tax integration works in Accounts Payable Operations is shown below. Note: If you're upgrading from previous version of APO to latest version, you must execute the scheduled job \[APO - close open exception for deactivated exception definition\]. This scheduled job updates the status of invoice exceptions to inactive and closes the corresponding invoice exceptions.