RRA EBM Suite — complete, all-in-one
Invoicing, Point of Sale, Stock (Traders & Manufacturer), Importers and the Pro control tower — the whole RRA EBM 2.1 / VSDC compliance suite in one module, one purchase, one configuration.
All six paid apps in one module — the price of the six, one configuration.
Everything, configured once
The Suite bundles all six paid RRA EBM apps into a single, self-contained module on top of the free Base. Real-time e-invoicing and POS, item registration and stock movements, manufacturing and imports, and the Pro control tower — with the fiscal signature and QR on every invoice and receipt.
Invoicing + POS
Every invoice, credit note and till order declared to the VSDC (saveSales), with the fiscal signature and QR on the paper.
Stock, Mfg & Imports
Item registration, stock in/out, stock master, manufacturing processing movements and customs-import reconciliation.
Pro control tower
The RRA Bot, declaration and stock dashboards and health monitoring — supervise the whole suite from one screen.
Eighteen screens across the whole suite
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.
A normal register your cashier already knows
No parallel POS and no retraining. The Rwandan till is the standard register, with the RRA work happening underneath it.
Sell exactly the way you sell today
Products, categories, quantities and discounts behave normally. The fiscal side does not change how a sale is made.
Attach the buyer when the receipt needs a TIN
A business buyer can be attached to the sale so their TIN travels with the declaration, which is what makes the receipt claimable.
Every payment method, unchanged
Cash, card, mobile money and split payments all work as they did. The payment type is derived and sent with the declaration.
A compliant receipt, printed at the counter
This is the point of the app: the customer walks away with a receipt carrying the RRA signature, internal data, SDC ID and MRC number that make it a valid Rwandan fiscal receipt.
Goods registered with the RRA before they move
The RRA needs every item registered with its classification, packaging and quantity units before stock movements referencing it will be accepted. That registration lives on the product.
See what is registered and what is not
The product list shows registration state across the catalogue, so the gap before go-live is a filter rather than an audit.
Deliveries declare themselves
Validate a picking and the matching stock movement is declared with the right sarTyCd for its direction. No second data entry.
Every movement and its RRA state
The picking list can be filtered and grouped by RRA state, so reconciling a month of warehouse activity is a filter, not an export.
One screen that answers "are we compliant?"
Pending, sending, failed, ambiguous, declared today and critical alerts — the state of the whole integration without opening a record.
Everything waiting, in one place
Every document bound for the RRA sits in one queue with its state, attempts and next retry.
Group the backlog the way you need to clear it
Grouping by state turns a flat backlog into a work list — what failed, what is waiting, what already went.
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
What’s the price logic?
The Suite is the price of the six paid apps bought together ($2,444) on top of the free Base — one module, one configuration, no dependency surprises at checkout.
Can I install it next to the standalone apps?
No — the Suite ships the full code of all six, so it refuses to co-install with the standalone apps (a clean guard prevents any clash).
Do I still need the Base?
Yes — the free RRA EBM Base is the shared engine; the Suite depends on it.
Any limits?
None. Unlimited documents, one-time purchase, 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 Suite — complète, tout-en-un
Facturation, Point de vente, Stock (Commerçants & Fabricants), Importateurs et la tour de contrôle Pro — toute la conformité RRA EBM 2.1 / VSDC en un module, un achat, une configuration.
RRA EBM Suite for Odoo · all-in-one Rwanda e-invoicing · VSDC
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Inventory (stock)
• Invoicing (account) • Manufacturing (mrp) • Point of Sale (point_of_sale) • Purchase (purchase) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 3899 |
| Technical Name |
aminitech_rra_suite |
| 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