How a Multi-Entity Tax Team Cut Data Prep 70%

A multi-entity U.S. tax team cleaned and mapped ERP data by hand before every filing. Local AI models now classify 90% of transactions and run reconciliation 3x faster.
70%
Less time on tax data preparation
4–8 weeks
Implementation Time
$250K – $500K
Project Cost

the challenge

The client, a multi-entity U.S. enterprise, manages direct and indirect tax across multiple jurisdictions. Its finance and tax data sat in separate ERPs and spreadsheets, and every reporting, provision or compliance cycle started with people extracting, cleaning, standardizing and mapping that data by hand. Book-to-tax reconciliation was slow, classification varied by who did it, and getting consistent, current numbers took far more effort than the tax work itself.

what they built

XIT Solutions deployed Complyia, its finance and tax data platform, for the client. The platform pulls data from the client's ERPs and spreadsheet sources into one data layer, then uses locally hosted language models to interpret financial records, classify transactions into tax categories, map accounts and flag discrepancies. Tax calculations themselves run on rules. Anything the models are unsure about, or anything that looks inconsistent, goes to a tax professional for review, and approved corrections improve later runs. Every classification and calculation traces back to the source record, so the tax team can audit how each number was produced.
The team started with the data and the tax logic, making sure source data, tax categories and calculation rules were correct before training anything. Connectors brought the client's ERP and spreadsheet data into a single layer. On top of it, locally hosted models served through Ollama, including Llama 7B and 10B and Qwen 12B and 24B, handle financial data interpretation, transaction classification, account mapping and discrepancy detection. Running the models locally kept sensitive financial data inside the client's environment. Rules handle the tax calculations, and a review queue sends low-confidence mappings and anomalies to tax professionals, whose approved corrections feed later runs. Results were measured in a controlled before-and-after assessment: the same financial datasets and reconciliation workloads were processed manually and through the platform, and the classifications were checked against tax-expert-reviewed answers. The hardest part was accuracy, since tax rules change by jurisdiction, entity and transaction type.

best fit for

Mid-market and enterprise organizations, tax technology providers and advisory firms managing tax across multiple entities, jurisdictions and financial systems, especially with high transaction volumes in VAT, GST or sales and use tax. It works best where reliable transaction data is available, tax experts and engineers can work together, and the team is willing to standardize existing workflows.
Ai ROLE
Locally hosted language models read financial records, classify transactions into tax categories, map accounts and flag discrepancies. Rules run the tax calculations, and tax professionals review exceptions and approve corrections.

impact

70%

Less time to clean, standardize and map financial data, measured against manual prep on equivalent datasets.

3x

Faster end-to-end book-to-tax reconciliation on equivalent workloads.

90%

Of transaction records classified correctly with no manual touch, checked against tax-expert review.

implementation complexity

High: connectors across multiple ERPs and spreadsheets, locally hosted models, a review loop that learns from approved corrections, and a jurisdiction-aware rules layer.
Rizwan Shaik, XIT Solutions

Rizwan Shaik

Account Executive, GTM Strategy at XIT Solutions
XIT Solutions Inc
Leads AI work at XIT Solutions, where he has spent 20+ years building enterprise systems for the tax technology sector.
Get an intro
Talk to this team
industry
Other
business organization
Finance & Accounting
AI TYpe
Data Synthesis & Reporting
value type
Time Savings

frequently asked questions

How did a multi-entity enterprise cut tax data preparation by 70% with AI?

It brought data from its ERPs and spreadsheets into one layer and used locally hosted language models to classify transactions and map accounts, with rules running the tax math and tax professionals reviewing exceptions. In a controlled before-and-after assessment, data preparation time fell 70%.

What AI models were used for the tax data mapping?

Locally hosted large language models served through Ollama, including Llama 7B and 10B and Qwen 12B and 24B, with LangChain, Pinecone and an AG Grid review interface.

What results did the enterprise tax team see?

70% less time on data preparation, 3x faster book-to-tax reconciliation, and 90% of transaction records classified correctly without manual intervention, validated against tax-expert-reviewed classifications.

How long did the AI tax data platform take to deploy?

First meaningful results came within four to eight weeks.

Who is AI tax data mapping best for?

Mid-market and enterprise organizations, tax technology providers and advisory firms handling high transaction volumes across entities and jurisdictions, especially in VAT, GST or sales and use tax.

Have a similar challenge?

Ask whether this would work for you, or describe what you're trying to solve.
TELL US WHAT YOU'RE EXPLORING