RRA EBM Invoice — every invoice, declared
Declare every customer invoice and credit note to the Rwanda Revenue Authority through the VSDC (saveSales), with the fiscal receipt signature and a verification QR on the printed invoice.
One-time purchase · unlimited documents · free updates on every RRA spec change. Requires the free RRA EBM Base.
Post as usual — compliance happens for you
Posting a customer invoice enqueues a VSDC sales declaration; the accountant never waits on the RRA server. Credit notes are declared as refunds referencing the original invoice, and the RRA receipt number, signature and QR land on the PDF.
saveSales, done right
Invoices are declared as VSDC sales (rcptTyCd S); credit notes as refunds (rcptTyCd R) referencing the original invoice number.
The signature on the paper
The RRA receipt number, signature (rcptSign), internal data, SDC ID and MRC are stored and printed, with a QR that verifies on the RRA portal.
VAT the RRA way
Tax is reported in the A/B/C/D bands (18% standard) with the VAT-inclusive amounts the VSDC expects — matched to the cent.
Twelve things it does — each on its own screen
Every posted invoice carries its RRA proof
Post a customer invoice and the app builds the saveSales call for the VSDC. The RRA tab then holds exactly what the device returned — receipt number, total receipt number, the 16-character rcptSign and the 26-character intrlData. Nothing is typed by hand.
The whole ledger, with its RRA state beside it
The invoice list carries an RRA status column, so a month of sales can be reconciled against the authority without opening a single record.
Who declared what, and when
Each declaration is written to the document chatter, so the fiscal history sits with the invoice itself rather than in a separate log a buyer has to be told about.
A credit note declares as receipt type R
Rwanda distinguishes a sale (S) from a refund (R). Credit notes are declared as refunds automatically and carry the reason code the RRA expects.
A rejection tells you what the RRA said
When the VSDC rejects a document the app keeps the result code and the authority’s own message on the invoice, so the fix is obvious rather than guessed at.
Exempt supplies are declared, not skipped
Exempt lines still have to reach the RRA under tax band A. The exemption is explicit on the document rather than an accident of a missing tax.
Your taxes carry their RRA band
Each Odoo tax is mapped to an RRA band — A exempt, B 18% standard, C zero-rated, D non-VAT. The mapping lives on the tax, so every document inherits it.
The mapping is visible in one place
The tax list shows which band each tax declares under, so an accountant can verify the whole configuration at a glance.
The exact JSON you sent
Every submission keeps its payload. When a buyer, an auditor or the RRA asks what was actually transmitted, the answer is one click away rather than a support ticket.
And the result code that came back
The VSDC reply is kept beside the request — result code, message and the attempt history — so a failure is diagnosable after the fact.
TIN validation before you declare
A customer TIN can be checked against the RRA before it ends up on a declaration, which is where most rejections actually start.
Device, environment and keys in one screen
TIN, branch, device serial, sandbox or production, and the keys the VSDC handed back at initialisation — all in one settings screen.
We connect you to the RRA VSDC
Buying the app includes the setup: we help you register the device on MyRRA, point the app at your local VSDC, validate the full flow on the RRA sandbox, then switch you to production.
Device on MyRRA, VSDC installed locally
TIN, branch, tax bands, sequences
Full flow on the RRA sandbox
Switch to production, declare for real
One suite, sold your way
Buy only what you need on the free Base, or take the all-in-one Suite.
Frequently asked
Does it need RRA EBM Base?
Yes — the free Base provides the VSDC client, the queue and the taxpayer configuration.
What about credit notes?
Declared automatically as refunds (rcptTyCd R) referencing the original invoice number, with a refund reason.
Do I sell at a till?
Add RRA EBM POS to declare every point-of-sale order too, with the fiscal signature printed on the receipt.
Any limits or subscription?
None. One-time purchase, unlimited invoices, free updates on every RRA spec change.
Ready for RRA EBM compliance?
Install now, or write to us — we set up your VSDC connection with you.
reach@aminitechsolutions.comRRA EBM Invoice — chaque facture, déclarée
Déclarez chaque facture client et avoir à la RRA via le VSDC (saveSales), avec la signature fiscale et un QR de vérification sur la facture imprimée. TVA en bandes A/B/C/D (18%).
RRA e-invoicing for Odoo · saveSales · rcptSign · VSDC
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 1835 |
| Technical Name |
aminitech_rra_invoice |
| License | OPL-1 |
| Website | https://www.aminitechsolutions.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module