Most Rwandan VAT returns are not hard — they are just assembled in the wrong place. Here is what the return needs, where each figure should come from, and the two habits that stop the 15th from being a bad day.
General information for Rwandan businesses, not advice on your specific filing. Rates, thresholds and deadlines move with the gazette — confirm the current figures on the RRA's own guidance before you file, and talk to your accountant about anything unusual.
A VAT return is one subtraction. Output VAT — the 18% you charged on standard-rated sales — less input VAT on purchases you are entitled to claim. What makes it painful is not the arithmetic; it is that most businesses cannot answer “what did we charge, on what, to whom” without rebuilding it from invoice copies.
If your sales and purchases are posted as they happen, with the VAT treatment recorded on each line, the return is a report. If they are not, the return is a research project you repeat every month.
| What the return needs | Where it comes from | What goes wrong |
|---|---|---|
| Standard-rated sales and output VAT | Sales invoices, per line, at 18% | Cash sales never invoiced |
| Zero-rated and exempt sales | The VAT treatment set on the item or the line | Everything lumped in as standard |
| Claimable input VAT | Purchase bills marked as EBM-backed | Bills with no compliant invoice behind them |
| Annexure detail | Customer and supplier records with TIN | Contacts entered as “walk-in” |
Notice that three of the four failures are data-entry habits, not tax questions. That is the whole point: a clean return is built in the first week of the month, not the fifteenth day of the next one.
Rwanda has required VAT-registered taxpayers to invoice through the Electronic Billing Machine / Electronic Invoicing System since 2021. Your accounting software does not replace that device — but the EBM/EIS number should be captured against the sale in your books at the moment you record it.
Do that and three things become easy: your annexure lists the right references, your customer statement matches the invoice the customer holds, and your month-end reconciliation between the device and the ledger is a comparison rather than an investigation.
On the purchase side, the question is not only “how much VAT did we pay” but “are we entitled to claim it”. A purchase without a compliant invoice behind it generally costs you twice: the input VAT is not claimable, and the expense may be disallowed for corporate income tax at 28%.
So the flag belongs on the bill, at capture. Then the awkward conversation with a supplier who never sent a compliant invoice happens in week one, while they still remember the delivery — not in an audit two years later.
The shortcut that isn't one. Rebuilding the return in a spreadsheet each month feels faster than fixing the capture habits. It is not — it just moves the cost to the one person who understands the spreadsheet, and makes the business fragile the week they take leave.
Any system worth paying for should let you record the VAT treatment per line, capture the EBM/EIS number on the sale, flag EBM-backed purchases, keep TINs on customer and supplier records, and produce VAT and CIT annexures in the format the RRA expects — without a consultant and without an export to Excel. That is the test: can you file from the books, or do you have to rebuild them first?
See how the reporting module fits the rest of the ledger, or read the payroll deductions guide for the other monthly filing.
Start free — no card, no contract.