Home › Guides

Reconcile invoices, e-invoice submissions, the ledger and the tax return

Start with the transaction population, not a portal total. A portal may include an invoice from last period, omit a rejected submission and show a credit note separately from its original invoice. Your return can also contain adjustments that have no ordinary sales invoice. Matching two headline totals leaves these differences hidden.

Use this procedure at each close to explain the movement from source transactions to the ledger, external reporting records and the return. The controls are recommended operating practices. Local law determines the reporting population, tax period, deduction rules and correction procedure.

Download the invoice reconciliation worksheet before starting. Assign the controller to own the reconciliation, the integration owner to resolve external reporting failures, and the tax preparer to approve return adjustments. A second reviewer signs off the result.

Set the scope and freeze the evidence

Record the legal entity, registration, reporting obligation, period, currencies and extraction time. State whether you are reconciling sales, purchases or both. Separate authority reporting from customer delivery when those are different services.

Specify the dates each population uses. Keep invoice date, supply or tax-point date, posting date and authority acceptance time as separate fields. An October extraction does not necessarily represent October tax. Include opening unresolved items so an old rejection cannot disappear when the calendar changes.

Save these extracts with their filters and row counts:

• Issued and received document registers, including cancellations and adjustments.
• Relevant general-ledger accounts and tax transaction details.
• Provider or authority records with identifiers, amounts and final or pending states.
• The proposed return and its supporting calculations.

Keep the untouched extracts and do the matching in a working copy. Record any later refresh separately. HMRC's VAT recordkeeping guidance explains the VAT account's role in connecting business records to the return. Use the local equivalent when defining your evidence set. HMRC, VAT Notice 700/21.

Build one identity chain for each document

Join the ERP transaction ID to the legal document number and external identifier. Include issuer identity, document type and direction. An invoice number alone is rarely a safe cross-company key.

Keep the original identifier when an invoice has a credit note or replacement. Do not overwrite the original with the latest UUID. One commercial case can contain several legal documents and several technical attempts.

Match the population in both directions. Find ERP records without external records, then external records without ERP records. Check both counts and amounts. Two missing invoices of equal and opposite value can produce a zero monetary difference while the population is incomplete.

Use the documented status mechanism before classifying an external record. MyInvois tells integrations to follow submission processing using its submission identifier and update the ERP after processing completes. Submission and completed validation are distinct events. LHDN, integration practices.

Classify differences before changing anything

Give each difference one reason, one owner and one required action. Useful reasons include a missing submission, a rejected document, a duplicate, a legitimate period difference, an incorrect amount and a return adjustment.

Distinguish a technical error from a correct tax-period difference. A valid invoice reported late may still belong in the original tax period under the applicable rules. Conversely, an accepted invoice from a previous period may correctly be absent from the current return. Have the tax owner decide the period. Do not move dates merely to make extracts agree.

For each difference, retain the gross amount, taxable base and tax separately. Record the direction of the proposed adjustment. A credit note entered as positive tax can survive a count check and still reverse the result.

Work the document reconciliation

The following example is synthetic. It uses one fictional currency, a fictional 10% tax rate and a single period. All sales are valid for this period independently of external reporting acceptance. The assumed regime allows the reporting repairs described below. These assumptions are not Singapore or UK tax rules.

The sales register contains invoices with net value 10,000 and tax 1,000. It also contains a credit note of minus 1,000 net and minus 100 tax. The ledger therefore has net sales of 9,000 and output tax of 900.

Two current-period invoices are absent from the accepted external population. One has net value 500 and tax 50 and remains pending. Another has net value 300 and tax 30 and was rejected. After including the credit note, accepted current-period records total 8,200 net and 820 tax.

The portal extraction also includes a previous-period invoice accepted during the current month. Its net value is 400 and tax is 40. The unfiltered accepted portal total is therefore 8,600 net and 860 tax.

Resolve the apparent difference in this order:

1. Start with portal totals of 8,600 net and 860 tax.
2. Remove the previous-period record from the current-period comparison, giving 8,200 and 820.
3. Obtain final acceptance for the pending invoice, adding 500 and 50, giving 8,700 and 870.
4. Repair the rejected reporting record through the authorized process. Confirm acceptance for 300 and 30, giving 9,000 and 900.

The previous-period item is a legitimate population difference. The pending and rejected items are reporting exceptions that need resolution. None is a reason to invent an extra sales posting. The final accepted current-period population now agrees with the ledger at 9,000 net and 900 tax.

Keep the original rejection, repair evidence and successful result. A fresh extraction alone would hide why the population changed.

Build the tax-return bridge separately

Continue the fictional example. The purchase register contains net purchases of 6,000 and charged tax of 600. All purchases are posted. The tax owner has approved these explicit assumptions:

• Tax of 10 on one purchase is permanently non-deductible.
• Tax of 20 on another purchase is deductible in the next period under this example's timing rule.
• A separate imported service requires reverse-charge output tax of 40 and permits an equal input credit of 40 in this period. Its expense and supplier payable are already recorded separately.

The 600 is tax shown on supplier documents, not a claim that the deductible-tax ledger must contain 600. Check how your ERP posts blocked tax and deferred tax before comparing its accounts.

The ordinary input claim is 600 minus 10 minus 20, which equals 570. Add the reverse-charge credit of 40 to reach total input tax of 610. Output tax is sales tax of 900 plus reverse-charge tax of 40, which equals 940. Tax payable is 940 minus 610, which equals 330.

A draft return showing output tax of 900 and input tax of 600 would show payable tax of 300. Correcting it increases output by 40 and input by 10 overall. The payable amount increases by 30 to 330. The input movement consists of adding 40, removing 10 and deferring 20.

The approved blocked-tax, timing and reverse-charge treatments are legitimate bridge items. Omitting those treatments from the draft return is an error. Recording a difference as a bridge item does not by itself make the treatment lawful.

Actual return boxes need their own mapping. IRAS provides box-specific instructions and conditions, so do not populate a national form from this fictional output/input summary without checking its instructions. IRAS, completing a GST return.

Resolve failures without hiding the remaining obligation

If a submission outcome is unknown, preserve the attempt and ask the integration owner to establish its state. Do not resubmit solely because the total is short. A second accepted document can create a new exception.

If the return deadline approaches while reporting remains unresolved, escalate both obligations to the tax owner. Record the legally supported filing and correction action. An internal reconciliation must not silently postpone a statutory deadline.

Singapore illustrates why the deadlines need separate attention. Under the GST InvoiceNow requirement, relevant invoice data is due by the earlier of the actual filing date or the relevant return's filing due date. Filing early can therefore bring forward that submission deadline. IRAS, GST InvoiceNow requirement.

If amounts differ because a mapping dropped a discount or rounded tax incorrectly, identify all affected documents before repairing one. Reconcile the corrected population again. Retain any legally required customer adjustment document separately from a technical reporting repair.

Close with explicit sign-off

The controller can close the reconciliation when these checks pass:

• Every population has a documented scope, extraction time and identity key.
• Document counts and monetary totals agree after evidenced population differences.
• Pending, rejected and duplicate records have confirmed outcomes or explicit unresolved-case decisions.
• The tax owner has approved each return adjustment and its period.
• The ledger, proposed return and payment calculation agree through the bridge.
• A reviewer can retrieve source records and reproduce the calculations.

Carry any approved open item into the next close with its original case ID, owner and deadline. Keep the frozen evidence with the signed worksheet. For the prerequisite obligation inventory, use map tax and reporting obligations. For document repairs, follow correct or cancel an e-invoice.

Source verification date: 17 October 2026.

Worksheet: Invoice reconciliation close worksheet

Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment.

Related on this site

• Country pages: key facts with sources
• E-invoicing matrix: country × ERP support
• All guides

Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17.

Related: Glossary – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more).

Page last updated: 2026-10-17 · Markdown version