Skip to main content

Medisell v URA: Accounting Differences, Tax Evidence and the Limits of Audit Methodology

Jurisdiction: Uganda · Decision: Tax Appeals Tribunal, Applications Nos. 51 & 72 of 2023 · Ruling date: 4 August 2026 · FGL review: September 2026

Medisell Uganda Limited v Uganda Revenue Authority is a useful finance case because it shows the difference between an accounting or reconciliation variance and a legally taxable transaction. The dispute covered corporate income tax, VAT and PAYE for periods between 2017 and 2020 and arose from URA audit work that compared accounting records with customs, stock and payroll information.

The Tribunal set aside a corporate income tax assessment of UGX 996,746,527 and VAT of UGX 9,630,468 that had been derived from cost-of-sales variances. It nevertheless upheld VAT of UGX 1,465,020 on a disposal to Medisell Rwanda where the taxpayer did not provide sufficient evidence that the goods had actually been exported. The PAYE findings were also mixed, depending on the evidence supporting the relevant payments and motor-vehicle use.

A reconciliation difference is not automatically taxable income

URA's corporate-income-tax assessment was built from alleged cost-of-sales variances using information such as imports, opening stock, closing stock and ASYCUDA data. Medisell argued that the differences arose from matters including accounting presentation, imported capital assets, spare-parts adjustments and foreign-exchange translation.

The practical lesson is not that reconciliation differences can be ignored. A variance is a legitimate audit signal and may justify further investigation. But the tax analysis still has to identify what the difference represents. A computed accounting variance does not become undeclared income merely because two datasets do not agree.

This principle connects directly with FGL's ERP, VAT and income-tax reconciliation guide, which explains why finance teams should build bridges between accounting, tax and system records before a reviewer has to ask for them.

Customs and import data must be classified before being treated as cost of sales

A particularly important part of the dispute concerned imported items captured in customs data. Medisell argued that some of those imports were not stock purchased for resale but laboratory equipment, spare parts and other capital or service-related items.

That distinction matters. ASYCUDA and customs records are powerful audit data sources, but they are not automatically a cost-of-sales ledger. A finance team should be able to separate trading stock, fixed assets, spare parts, consumables, equipment used in service arrangements and foreign-exchange effects before comparing customs data with the income statement.

A useful control is a monthly or quarterly import bridge that maps each customs entry to its accounting destination: inventory, expense, fixed asset, work in progress, prepayment or another clearly explained category.

Audit methodology still has to connect the variance to a taxable event

The wider point in the ruling is evidential. Data analytics can identify unusual movements, unexplained balances or mismatches, but an assessment still needs to connect the result of that analysis to the relevant charging provision and the underlying facts.

This is increasingly important because URA's FY 2026/27 compliance plan expressly identifies risks such as opening and closing stock variances, overstated cost of sales, ASYCUDA exports differing from VAT or income-tax declarations, and other cross-system inconsistencies. Finance teams should therefore expect reconciliations to be used as risk indicators and should prepare the supporting explanations before an audit begins.

Information requests need a clear evidence trail

The case also considered URA's reliance on section 49(4) of the Tax Procedures Code Act in relation to information requested during the audit and objection process. The Tribunal's treatment of the issue reinforces a practical control point for both taxpayers and reviewers: maintain a clear chronology of what information was requested, when it was requested, the deadline, what was supplied and what remained outstanding.

For taxpayers, the safest response is not to rely on informal conversations or assumptions that an auditor has already seen a document. Maintain a request register, preserve email submissions and record the evidence delivered against each query.

VAT follows taxable supplies, not unexplained numbers alone

URA also applied VAT to a marked-up version of the cost-of-sales variance. The Tribunal set aside VAT of UGX 9,630,468 on that component.

The practical principle is straightforward: VAT liability must still be connected to a taxable supply. A variance may suggest that sales or supplies need to be investigated, but the assessment should be supported by the underlying transaction, invoice, receipt, consideration, delivery or other evidence showing why VAT is chargeable.

The related Ericsson AB v URA analysis makes a similar point from a different direction: differences between VAT sales and income-tax revenue require investigation and correct tax treatment rather than an assumption that the entire variance is underdeclared sales.

Zero-rated exports require evidence that the goods actually left Uganda

Medisell was less successful on a disposal of furniture, equipment and fittings to Medisell Rwanda. The taxpayer argued that the transaction was an export and should therefore be zero-rated, but the Tribunal upheld VAT of UGX 1,465,020 because sufficient export evidence had not been produced.

An EFRIS invoice records a fiscal transaction, but it does not by itself prove the physical export of goods. For zero-rated exports, finance teams should retain the customs export declaration, exit or release evidence, transport and delivery documentation, acknowledgement by the foreign recipient and any other records needed to demonstrate that the goods actually moved out of Uganda.

URA's current export guidance similarly describes export clearance as a documented customs process and identifies commercial, transport and customs documents used to support export movement.

PAYE errors still need to produce an actual tax shortfall

The PAYE findings illustrate the same evidence principle. On director bonus payments, the issue included whether amounts had been reported under the correct schedule and whether reclassification actually produced additional tax. Medisell produced computations and bank evidence supporting its position, and the relevant assessment was set aside.

For motor-vehicle benefits, the result depended on the facts and supporting records. Claims that a vehicle was not available for private use need contemporaneous evidence such as usage logs, custody arrangements, employee financing records, salary deductions and other records that explain who controlled and benefited from the vehicle.

The lesson is balanced: an incorrect classification can require correction, but a classification error is not automatically the same thing as underpaid tax. Equally, a policy saying that an asset is for official use will carry little weight if actual usage cannot be demonstrated.

What finance teams should build before an audit starts

  • Reconciliation bridges: connect ERP balances, tax returns, customs data, EFRIS records and financial statements.
  • Import classifications: distinguish stock, fixed assets, spare parts, consumables and service-related equipment.
  • Variance explanations: identify the transaction and tax character behind every material unexplained difference.
  • Export evidence packs: retain customs, transport, delivery and receipt evidence, not only the invoice.
  • Audit request registers: record every information request, response, submission date and unresolved item.
  • PAYE support: preserve payroll computations, bank evidence and documentation for employee benefits.
  • Vehicle-use evidence: keep logbooks, custody records and other contemporaneous proof where private use is disputed.

For related case analysis and practical guidance, use FGL's Uganda Tax knowledge desk and Case Briefs library.

Sources

FGL note: This article explains the published Tribunal decision for general professional learning. Tax consequences depend on the facts, the applicable law and the evidence available in each case.

Free tools

Use an FGL calculator

Open the calculator directly instead of navigating through a separate tools page.

Continue with FGL

Practical resources
Discussion

Questions, corrections or another perspective?

Join the conversation below. Keep comments constructive, relevant and free of confidential information.

Popular posts from this blog

Ernst & Young v URA: VAT on Imported Services and the UGX 3.48 Billion Assessment

Jurisdiction: Uganda · Decision: Commercial Court, Civil Appeal No. 26 of 2022 · Judgment date: 11 June 2026 · FGL review: September 2026 Uganda's Commercial Court has upheld a VAT assessment of UGX 3,482,492,210 against Ernst & Young Uganda in a dispute over services received from non-resident group entities and other foreign service providers. The decision is important because it gives businesses a current judicial example of how Uganda's imported-services VAT rules can apply to cross-border support, technology and professional-service arrangements. What the case was about In Ernst and Young v Uganda Revenue Authority , Civil Appeal No. 26 of 2022, the dispute concerned services obtained from entities outside Uganda, including members of the wider EY network and third-party foreign suppliers. URA treated the services as imported services and assessed VAT for the period January 2014 to June 2018. EY challenged the treatment, including arguments about where the s...

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-contra...

Stanbic-URA Transfer-Pricing Dispute: What Finance Teams Should Learn While the Case Is Pending

Jurisdiction: Uganda · Topic: Transfer pricing and tax dispute management · Status: Pending before the Tax Appeals Tribunal at the time of this FGL review · FGL review: 21 September 2026 Stanbic Bank Uganda Limited and Stanbic Uganda Holdings Limited are contesting a major transfer-pricing assessment by the Uganda Revenue Authority (URA). Public reporting places the working dispute figure at approximately UGX 117.8 billion , and the Tax Appeals Tribunal listed TAT Application No. 170 of 2025 for conferencing in June 2026. This article does not attempt to decide who is right. The dispute is still being litigated. Instead, it uses the publicly available record to explain what finance teams can learn about related-party charges, evidence, tax governance and the management of unresolved assessments. What the dispute is about The dispute arises from URA's review of related-party transactions involving Stanbic's Ugandan operations and entities within the wider...