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.
From draft to declared, every detail on the invoice
The full fiscal acknowledgement, in place
Every customer invoice carries an RRA EBM tab: status, invoice number, receipt number, the receipt signature, internal data, SDC ID, MRC and VSDC date — the complete RRA acknowledgement, on the record.
Declared, queued or failed — you always know
The invoice list shows the RRA status as a colour badge, so you can see at a glance which invoices reached the RRA and which are still in flight.
The exact figures the RRA received
When the RRA accepts a declaration, the connector posts a clean table in the chatter — header totals, per-band VAT and every line exactly as transmitted, plus the fiscal signature.
Refunds, referencing the original
A credit note is declared as a refund (rcptTyCd R) with the original invoice number (orgInvcNo) and a refund reason — the RRA-correct way to reverse a declared sale.
Map your VAT to the RRA bands, once
Each sale tax carries its RRA band (A exempt, B 18% standard, C zero-rated, D non-VAT). Set it once and every invoice reports VAT in the exact bands the RRA expects.
Your legal proof, retained
Behind every invoice, the queue keeps the exact payload and the RRA response — receipt number, signature, SDC ID, MRC — ready for any audit.
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 | 1837 |
| 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