Payables: money you are owed
Input credit is yours if the spend was eligible, the document exists and your supplier actually filed. All three can fail, and the third is not in your control.
Taxation Reconciliation
Every other recovery is a conversation. Tax is arithmetic against a statute, which makes it the quietest line on the list and often the fastest to collect. DataTwin reconciles what you booked against what you filed, and both against what your suppliers and customers filed, on the payables side and the receivables side together. Then it ranks what is left by how long you have to act.
Four registers, one difference list
Register against return
Live process
The four things that must agree
DataTwin
Reads all four and names every difference
One difference register
Why this matters A tax difference is not an opinion. Either the ledger and the return agree or they do not, and the counterparty is a statute rather than a negotiation. What is missing is the reconciliation, not the argument.
Read-only to start — we reconcile and evidence; we do not file your returns. Every stage runs on the same engine that powers the DARP Framework and FSCP: acquire, process, govern, report.
Two directions
Most tax work is organised by return rather than by direction, which hides the fact that the payables side and the receivables side leak differently. One loses money you were entitled to. The other creates exposure you have not provided for.
Input credit is yours if the spend was eligible, the document exists and your supplier actually filed. All three can fail, and the third is not in your control.
Output tax is yours to get right. A wrong rate, a wrong place of supply or a credit note that never reversed becomes an assessment, with interest.
Almost every item has a statutory window. Once it closes the money is gone, valid claim or not, so urgency has to rank the findings, not just value.
The reconciliation
Part 1
The books say one thing and the return says another, and nobody can say why without rebuilding both. Doing that once, per registration and per period, turns most tax questions from an investigation into a lookup.
Register
From the ledger up. Purchase and sales registers reconstructed from the transactions themselves, at line level, for every registration and entity you hold.
Return
Period by period. What was filed compared to what the books support, with each difference carrying the invoices behind it rather than a net figure.
Window
Urgency, not just value. Each difference is tagged with the statutory window it sits in, so what is about to expire is ranked above what is merely large.
← Payables side
Input credit fails in two directions at once. Credit is left unclaimed on eligible spend because nobody matched the document, and credit is claimed on spend that was never eligible or against suppliers who never filed. Both are found the same way.
Claimable, unclaimed
Eligible spend where the credit was never taken, including import duty, reverse charge and credits stranded in a period nobody revisited.
Claimed, at risk
Credit taken on blocked or ineligible spend, or against suppliers whose own returns do not show the invoice.
The supplier gap
A valid invoice from a supplier who never filed is a credit at risk. The gap is quantified per supplier so it can be chased while it is still recoverable.
Receivables side →
Output tax rarely goes wrong in the total. It goes wrong on a class of invoices, in one state, or on one product, and it stays wrong for as long as the master data that produced it stays wrong. Re-performing the decision on the invoice is what finds it.
Rate and classification
Rate, classification and treatment tested against the item and customer on each invoice, rather than trusted from the master data behind them.
Place of supply
Inter-state, intra-state and export treatment tested per invoice, since the consequence of getting it wrong is paying twice and reclaiming once.
Credit notes and returns
Credit notes tested against the invoice they reverse and the period they landed in. A reversal in the wrong period is a difference in two returns.
Part 4
Tax your customers withheld is a credit you have to claim, and it fails when the certificate never arrives. Tax you withheld on vendors is a liability you have to deposit at the right rate, and it fails on section, threshold and certificate.
What was withheld from you
Short payments from customers reconciled to the tax they withheld, and the credit claimed rather than left sitting as an unexplained shortfall.
What you withheld
Rate, section and threshold tested per vendor and payment, including thresholds only breached once spend is aggregated across the year.
Certificates and exemptions
Lower-deduction and exemption certificates applied only inside their validity, since an expired certificate silently becomes a short deduction.
What this is not.
We reconcile and evidence. We do not file your returns, and we are not a substitute for your tax advisers. Rules are configured per jurisdiction rather than assumed, so the honest question to ask us early is which of your jurisdictions are already configured and which would be new work. We would rather answer that before a contract than after one.
Part 5
A tax assessment is a reconciliation somebody else has run on your data. If you have run it first, responding is a print rather than a project, and the difference between those two is usually several weeks and a lot of goodwill.
The annual position
The annual reconciliation assembled from the periods as they close, rather than reconstructed in the weeks before it is due.
Evidence, attached
Every difference carries the invoices, documents and filings behind it, so a query is answered from the record rather than from memory.
The same view for the auditor
Your auditor and your tax adviser read the same reconciliation your team does, which removes most of the back and forth.
Prevent
Prevent is not a second build. The checks that reconciled last year are the checks that run on this month’s transactions. That is where a one-off recovery starts compounding.
Rate, classification and place of supply tested on the transaction, before it posts.
Withholding rate, section and threshold applied from the vendor record and the year to date.
Register against return reconciled while the period is still open to correct.
Counterparty filings matched as they appear, so a supplier gap is a same-month chase.
The annual position assembled from periods already agreed, not rebuilt.
What changes
Not a longer list of features. A different distribution of who does what, and when a difference is found.
How tax reconciliation runs today
Downloaded, pasted into a workbook, reconciled by whoever has time
How it runs on DataTwin
Rebuilt from transactions, per registration and period, as the period closes
How tax reconciliation runs today
Found at the annual return, when the supplier has stopped answering
How it runs on DataTwin
Matched as filings appear, so the chase happens while it still works
How tax reconciliation runs today
Trusted from master data until an assessment disagrees
How it runs on DataTwin
Re-performed on the invoice, with the master-data cause identified
How tax reconciliation runs today
Checked per invoice, so aggregated thresholds are missed
How it runs on DataTwin
Tracked across the year per vendor, per section
How tax reconciliation runs today
Chased at year end, when many can no longer be obtained
How it runs on DataTwin
Chased against the period they belong to, with the invoice attached
How tax reconciliation runs today
Findings ranked by value, so expiring items get missed
How it runs on DataTwin
Ranked by remaining window and value together
How tax reconciliation runs today
A project: rebuild the period, find the documents, explain the gap
How it runs on DataTwin
A print: the reconciliation and its evidence already exist
Start here
Everything above is prevention; it stops the next period leaking. It does nothing about the periods already filed, which are sitting in your registers right now, some of them still inside their window. So we start there, read-only, before there is anything to sign.
2min
This is how long it takes to understand how much can be recovered.
Send us the purchase and sales registers, the returns as filed and the counterparty data. We test the full transaction population, not a sample, and come back with what is claimable, what is at risk and how long you have on each. Before any contract.
Credit never taken on eligible spend. Import duty and reverse charge missed. Withholding left.
Credit taken on blocked spend, or against suppliers whose returns never showed the invoice.
Wrong rate, classification or place of supply. Reverse charge never self-assessed. Reversals missed.
Items still inside their window, ranked by the days left rather than by the amount.
The same engine runs tax reconciliation for manufacturing, distribution, retail, pharma and services groups running multiple registrations and entities. Rules are configured per jurisdiction, so ask us early which of yours are covered.