An approved EFRIS credit note can reopen the VAT return for the month of the original invoice. A finance team therefore needs to follow the document, its approval status and the affected return together. This guide explains how to prepare that review without confusing a customer refund, a submitted application and a completed tax correction.
1. Start with the correction, not a replacement invoice
A credit note connects an adjustment to an earlier transaction. URA's credit-note service page describes it as the supplier's document for cancelling or amending a transaction, including an invoicing error, while preserving the original invoice. Keep that connection visible in your accounts. Quietly replacing a saved PDF leaves the original transaction and the revised amount difficult to reconcile.
Use the Uganda VAT calculator to check arithmetic in your working paper once the applicable VAT treatment is established. The calculator is a planning aid. Its result is not an EFRIS fiscal document or evidence that URA has approved a credit note. For the wider monthly process, read the Uganda VAT registration and filing guide; for registration questions, use the Uganda VAT registration checklist.
First identify what actually changed: goods returned, an incorrect price, a quantity difference or another documented correction. Record the original invoice reference, affected lines and reason. Separate a dispute about whether money is payable from an agreed change to the supply. A customer asking for a refund does not by itself establish the correct fiscal adjustment.
2. Distinguish the document types and verify the original
The current URA EFRIS FAQ describes e-invoices as documents issued by VAT-registered suppliers and e-receipts as documents issued by suppliers outside VAT registration. It describes a credit note as reducing or cancelling a previous sale, and a debit note as increasing an understated sale. Fiscal documents carry a Fiscal Document Number, verification code and QR code.
Some older URA pages describe a debit note differently, as a buyer's request for funds. Treat that terminology conflict as a reason to identify the actual EFRIS operation before proceeding. This article focuses on supplier credit notes and their published VAT-return treatment. It does not transfer that treatment to debit notes or promise that every commercial refund belongs in the same menu.
Validate the original through the fiscal-document verification facility linked from URA. Compare the returned details with the invoice in your records. The current FAQ directs users to supply the FDN and generation date. If the printed document differs, ask the supplier to resolve it through the appropriate fiscal correction process. Preserve the discrepancy as a separate review item.
As an internal control, retain the original unchanged and give the adjustment its own reference. Maintain a clear sequence: original document, business evidence, application, outcome and accounting response. That sequence lets another reviewer follow the change without relying on a conversation or a file whose contents were overwritten.
3. Prepare a compact evidence packet
The following checklist is a suggested business control, not a claim that every attachment is mandatory in every URA application. Adapt it to the transaction and current portal requirements. Its purpose is to make the correction understandable before someone enters figures into EFRIS.
- Original FDN, invoice date and the supplier and customer references.
- A short reason explaining what changed and which lines are affected.
- The relevant return, delivery, cancellation or price-agreement evidence.
- Original and proposed quantities, values and VAT treatment.
- The related accounting entries and any separate refund or customer credit.
- The original invoice month's VAT-return submission status.
- A named preparer, reviewer and person responsible for checking the outcome.
Make the reason specific enough to test against the supporting records. A label such as “correction” tells the reviewer little. Describe whether the change concerns quantity, value or the whole supply, and point to the evidence. Include only relevant material; an entire customer account history can make the actual adjustment harder to find.
For a partial adjustment, mark the unaffected lines clearly. Your working paper should preserve the distinction between the original total, the part being corrected and the remaining transaction. Ask the reviewer to check that a quantity change has not accidentally become a full cancellation. Do not alter tax classification solely to obtain a preferred total.
Keep taxpayer identifiers and customer information in authorised business records. Do not paste credentials, contact lists or private invoices into a public calculator, shared screenshot or support post. A colleague reviewing arithmetic normally needs the amounts and treatment, not access to the taxpayer's password or one-time code.
4. Follow the application through to its outcome
Use the official EFRIS route linked from URA and check the instructions displayed for your account. Keep the original FDN, reason and line-level working paper ready. Confirm the required supporting material and review the entries before submission. Public instructions do not establish which fields, restrictions or additional evidence apply to your particular transaction.
Record the application's reference and observed status after submission. If no acknowledgement appears, investigate whether the request reached the system before starting another. A timeout, a saved draft and a rejected request are different outcomes. Your correction register should reflect the evidence you have, rather than marking every attempt as submitted.
Assign someone to check the final response and match it to the requested document. An approval for another invoice does not close the current item. If rejected, preserve the reason, review the supporting evidence and ask URA for clarification where needed. Repeating an unchanged application without understanding the rejection adds work without resolving the underlying issue.
Before accounting closeout, compare the approved document with the working paper and explain any difference. Keep the approval date separate from the original invoice date. Both dates matter to the review, but they do not necessarily identify the same VAT-return month.
5. Identify the VAT return that the credit note affects
URA's September 11, 2024 notice states that, for periods beginning August 2024, approved credit notes are recognised in the return for the original invoice month. Before filing, the affected sales or purchase value is prefilled net of the credit. After filing, both supplier and purchaser must amend the original month's return. URA warns of administrative assessments where a purchaser fails to reverse undue credit.
Build the decision around two facts: which month contains the original invoice, and whether that month's return was already submitted when approval occurred. Checking only the current month can miss an earlier return that needs review. Record these facts next to the document reference so the return preparer can follow the conclusion.
| Review question | Evidence to inspect | Business follow-up |
|---|---|---|
| Which transaction changed? | Original FDN and invoice date | Locate its original return month |
| What is the fiscal outcome? | Actual approval or rejection | Keep unresolved requests open |
| Was that return filed? | Submission record and working paper | Review the appropriate filing or amendment path |
| Has the accounts review finished? | Document chain and revised reconciliation | Explain outstanding differences |
Apply the decision to the document dates and actual submission status in your business records. Where those records disagree, resolve the disagreement before deciding which return to change. An accountant should be able to reconstruct the choice from the file, including the original submission reference and the date the credit-note outcome became available.
6. Supplier review: keep tax, accounts and cash separate
For the supplier, prepare a reconciliation that connects the original sale, the approved reduction and the remaining balance. Show which ledger entry represents the invoice and which represents the correction. Add a separate reference for any cash refund, credit against another bill or outstanding settlement. Those commercial actions should be understandable without being treated as the fiscal approval itself.
Review the accounting period and the tax-return period explicitly. A business may discover an error during a later close, while the published fiscal treatment points to an earlier invoice month. Keep a note explaining the dates and the reason for any accounting treatment your adviser selects. Avoid forcing different records into one month simply to make a summary easier to read.
After any return action, keep the acknowledgement and revised working paper with the correction record. Check that the approved amount is represented once. A manual ledger adjustment followed by an automated import can otherwise produce a second reduction that looks legitimate until someone reconciles the underlying documents.
7. Purchaser review: do not retain the original credit unchecked
For the purchaser, reconcile the revised purchase evidence with the input-tax schedule and supplier account. Confirm that the correction belongs to your business and to the invoice you originally recorded. An email announcing a refund is useful commercial evidence, but it should not replace the fiscal document and its verification.
Track supplier requests separately from received, approved documents. This prevents an expected adjustment being treated as final merely because someone requested it. When a document arrives, notify the person who prepared the original month's return and provide the linked evidence. A later payment-processing team may not know which earlier filing needs attention.
Keep the gross supplier balance, tax working paper and cash movement traceable. Explain whether the customer account now holds a credit or whether money has moved. A settled supplier balance does not demonstrate that the input-tax review has been completed. Close the item only when the responsible reviewer has documented the relevant tax and accounting actions.
8. Use a correction register during month-end close
A useful register can be a spreadsheet or another access-controlled record. Give each correction one row with the original reference, reason, application status, outcome date, affected invoice month, return status, action owner and evidence location. Include an unresolved-issue field so a missing document is visible rather than hidden inside a completion percentage.
Review open items before filing and revisit them after new outcomes arrive. Reconcile the register against your sales or purchases report and the working papers. If an item affects an already filed period, record the follow-up explicitly. Assign a next review date for unresolved portal or supplier questions so they do not disappear at the next close.
For arithmetic, use the amounts from the verified document and the treatment applicable to its lines. Where a standard-rated, VAT-inclusive amount is being reviewed at Uganda's 18% rate, the arithmetic relationships are net = gross / 1.18 and VAT = gross minus net. This is a formula check, not a substitute for confirming classification, approval or return treatment. Mixed or exempt lines need separate review.
Before marking the file complete, another authorised reviewer should be able to answer four questions: what changed, what URA recorded, which return was reviewed and what evidence proves the business finished its action. Keep that review concise. A clear document chain is more useful than a long narrative that cannot be reconciled to the figures.
Frequently asked questions
Can I just edit the invoice PDF?
Preserve the original and follow the appropriate fiscal correction workflow. A revised local PDF does not prove that the EFRIS transaction was changed.
Does submitting a credit-note application finish the job?
No. Track the outcome, match the approved document to the request, and review the related accounts and VAT return before closing the item.
Can AfroTools issue the EFRIS credit note?
No. The Uganda VAT calculator helps check arithmetic. Fiscal documents and return actions must follow the official URA workflow.
What should I do when URA sources use different debit-note definitions?
Check the current EFRIS operation and ask URA to confirm the required process. This guide does not extend its supplier credit-note discussion to every debit-note or refund situation.
Sources, dates and limits of this review
Public primary sources were reviewed on October 3, 2026. No private taxpayer account was accessed and no application or amendment was submitted. The filing-period explanation uses the specific 2024 notice. The evidence packet and correction register are suggested business controls, rather than an official attachment list. Confirm any case-specific restriction or changed portal instruction with URA.
- URA treatment of credit notes upon approval, published September 11, 2024.
- Current URA EFRIS FAQ, fiscal documents, verification and correction guidance.
- URA credit-note and debit-note service explanation, including the terminology difference discussed above.
- URA VAT overview, standard-rate arithmetic context.
- URA July to September 2026 newsletter, published September 30, 2026. It reports the July expansion of EFRIS to twelve additional sectors; it is not a replacement credit-note instruction.