Reconciling ERP Sales, EFRIS, VAT and Income Tax Returns: A Practical Guide

Scope: Uganda · Topic: Revenue reconciliation across ERP, EFRIS, VAT and income tax · FGL review: September 2026

Sales should be explainable across every system a business uses, but they will not always be numerically identical. An ERP may record invoices and journals, EFRIS records fiscal documents, VAT follows statutory supply rules, financial statements apply accounting standards, and the income-tax return applies tax rules to annual business income.

The control objective is therefore not to force all four numbers to match. It is to build a documented bridge that explains why they differ, whether each difference is valid, and what evidence supports it.

Why the numbers can legitimately differ

A difference can arise from timing, classification, system configuration or tax treatment. Common examples include advance billings, deferred income, unbilled revenue, credit notes, exempt or zero-rated supplies, manual journals, foreign-currency treatment, customer-contract milestones and cut-off errors.

Some differences are valid. Others reveal errors. The finance team's job is to distinguish the two before a return is filed or an audit query arrives.

What each record is actually measuring

ERP sales records reflect transactions captured by the accounting or billing system. Depending on the configuration, these may include sales invoices, credit notes, debit notes, manual revenue journals, recurring invoices, imported transactions and adjustments.

EFRIS records provide the fiscal-document trail for transactions that are required to be fiscalised. URA describes EFRIS as a system for recording transactions and sharing transaction information with the authority, and identifies e-invoices, e-receipts, e-credit notes and e-debit notes among the documents generated by the system.

VAT returns report taxable supplies and other VAT information for the relevant tax period. URA currently requires VAT returns to be filed monthly by the 15th day of the following month.

Accounting revenue is governed by the applicable financial-reporting framework. Under IFRS 15, revenue from contracts with customers is recognised to depict the transfer of promised goods or services, using the standard's five-step model.

Income-tax reporting applies the income-tax rules to business income and deductions for the year of income. The final tax return therefore should be traceable to the accounting records, but it is not simply a copy of the VAT return or the ERP sales report.

Build a reconciliation bridge instead of forcing equality

A useful reconciliation starts with one reliable data set and explains every material movement to the next reporting basis. For example:

• ERP invoiced sales;
• less or add cancelled invoices and approved credit-note timing items;
• less or add EFRIS timing or fiscal-document differences;
• less VAT-only items that are not accounting revenue;
• less advance billings that remain contract liabilities or deferred income;
• add unbilled revenue recognised under the accounting policy;
• add or less exempt, zero-rated or out-of-scope classification differences;
• add or less foreign-exchange and cut-off adjustments where supported;
• equals accounting revenue or the appropriate income-tax turnover basis before tax-specific adjustments.

The exact bridge depends on the business model. A distributor, telecom company, school, construction contractor, software business and professional-services firm may all require different reconciliation schedules.

Contracts with customers create timing differences

Invoice timing and revenue recognition are not always the same event. A business may invoice a customer before it has fully performed the promised service, or it may perform before an invoice is issued.

Under IFRS 15, a finance team first identifies the contract and the performance obligations, determines and allocates the transaction price, and then recognises revenue when or as those obligations are satisfied. FGL's IFRS 15 practical guide explains that accounting framework in more detail.

Consider a 12-month support contract billed in full at the start of the year. The ERP and EFRIS records may show the full invoice when issued. VAT treatment depends on the applicable statutory time-of-supply rules. Accounting revenue may, however, be recognised over the service period if the performance obligation is satisfied over time. The reconciliation should identify and document that timing difference rather than trying to eliminate it with an unsupported journal.

EFRIS and VAT need their own control layer

EFRIS is not merely an invoice archive. For businesses required to use it, the fiscal-document trail should reconcile to the sales system and VAT return. This includes e-invoices, e-receipts, e-credit notes, e-debit notes and any valid adjustments.

A monthly control should therefore compare ERP invoice populations to EFRIS fiscal documents, not just compare total values. Missing documents, duplicate fiscalisation, cancelled documents, unmatched credit notes and incorrect tax codes are easier to correct when identified transaction by transaction.

For the wider EFRIS control environment, see FGL's EFRIS and VAT withholding guide.

Why reconciliation has become a tax-risk issue

URA's FY2026/27 Compliance Improvement Plan is explicitly data-driven and identifies risks such as inaccurate sales reporting, EFRIS non-compliance, ASYCUDA exports differing from VAT exports, ASYCUDA exports differing from income-tax sales, overstated cost of sales and stock variances. That makes cross-system reconciliation a compliance-control issue, not merely a month-end accounting exercise.

The practical implication is straightforward: where two systems show different numbers, the taxpayer should be able to produce the bridge, source documents and control evidence that explain the difference.

What Ericsson and Medisell add to the control framework

In Ericsson AB v URA, the Tax Appeals Tribunal considered an unreconciled sales variance between VAT and income-tax reporting. The case is useful because it demonstrates that a numerical variance still has to be connected to the correct VAT treatment and underlying evidence.

In Medisell v URA, the Tribunal examined differences arising from cost-of-sales and import-data reconciliations. The broader lesson for finance teams is that accounting differences need tax characterisation: a variance is a reason to investigate, not automatically proof of undeclared income or a taxable supply.

Together, the cases reinforce the same operational rule: numbers do not explain themselves. The reconciliation must lead back to transactions, documents and the legal or accounting treatment applied.

Ten common causes of unexplained differences

1. Advance billing and deferred income: an invoice is issued before revenue is earned for accounting purposes.
2. Unbilled revenue: revenue is recognised before the billing event.
3. Credit notes and cancellations: timing differs between ERP, EFRIS and the return.
4. Exempt, zero-rated or out-of-scope items: accounting revenue may not equal standard-rated VAT sales.
5. Manual journals: revenue posted directly to the general ledger may bypass the billing module.
6. Gross-versus-net presentation: one system records gross customer collections while accounting recognises only a fee or margin.
7. Cut-off errors: invoices or credit notes are captured in the wrong reporting period.
8. ERP mapping errors: tax codes, revenue accounts, document types or customer classifications are configured incorrectly.
9. Foreign-currency differences: systems may use different transaction, tax or reporting exchange rates.
10. Master-data problems: customer tax status, VAT classification or product/service coding may be wrong.

The monthly reconciliation pack

At minimum, the finance team should retain the following for each reporting period:

• ERP sales-invoice and credit-note register;
• EFRIS transaction and adjustment reports;
• VAT sales schedule and filed VAT return;
• general-ledger revenue by account;
• manual revenue-journal listing;
• deferred-income or contract-liability movement schedule;
• unbilled-revenue or contract-asset schedule;
• major customer-contract or billing-milestone analysis;
• foreign-currency adjustment schedule where relevant;
• the reconciliation bridge, with each reconciling item explained and supported.

Material reconciling items should carry an owner, explanation, evidence reference and expected clearance date. Old unexplained items should not roll forward indefinitely simply because the total reconciliation still balances.

Control ownership and sign-off matter

A strong reconciliation should separate preparation from review where the size of the finance function permits. The preparer should assemble the schedules and investigate exceptions. The reviewer should challenge unusual movements, unsupported classifications, large manual journals, late credit notes and recurring differences.

Where the same person prepares invoices, maintains the ERP mapping and files the VAT return, compensating review controls become especially important. The risk is not only fraud. A configuration error can consistently produce an apparently clean but incorrect report.

This is where the guide connects to FGL's broader Systems & Automation desk and Accounting & IFRS desk: reconciliation quality depends on both accounting judgement and system design.

A practical month-end sequence

1. Extract ERP invoices, credit notes and manual revenue journals for the period.
2. Extract the corresponding EFRIS fiscal-document population.
3. Reconcile document counts and values, then investigate missing and duplicated items.
4. Prepare the VAT sales schedule by tax category and reconcile it to the fiscalised population.
5. Reconcile VAT sales to general-ledger revenue, identifying timing and classification differences.
6. Update deferred-income, unbilled-revenue and major-contract schedules.
7. Document every material reconciling item with the underlying contract, invoice, delivery or service evidence.
8. Review tax-code and account-mapping exceptions rather than adjusting totals manually to force agreement.
9. Obtain reviewer sign-off before filing.
10. Carry unresolved items into an exception log with an owner and deadline.

The wider Uganda tax library is available through the Uganda Tax knowledge desk.

Sources

• Uganda Revenue Authority — File a Tax Return.
• Uganda Revenue Authority — Electronic Fiscal Receipting and Invoicing Solution (EFRIS).
• Uganda Revenue Authority — FY2026/27 Compliance Improvement Plan.
• IFRS Foundation — IFRS 15 Revenue from Contracts with Customers.
• Ericsson AB v Uganda Revenue Authority, [2026] UGTAT 24.

FGL note: This guide is a control and reconciliation framework for general professional learning. The correct accounting and tax treatment of a particular transaction depends on the applicable law, reporting framework, contract terms and supporting evidence.