Keeps trading offline
Connections fail. Sales do not stop. Invoices queue locally and transmit themselves once the link is back, with nothing to re-key.
What we build
Some businesses want a point of sale that handles compliance for them. Others want the system they already run to start filing correctly. We do both, and we wrote all of it ourselves.
Our product
INJONGE is our own point-of-sale and electronic billing system. The cashier rings up a sale; the receipt prints with the authority's signature block already on it; the invoice is filed. There is no second system to reconcile against at the end of the day.
Connections fail. Sales do not stop. Invoices queue locally and transmit themselves once the link is back, with nothing to re-key.
Tills, branches and warehouses report into one back office. Pricing and stock are set centrally and pushed out.
Items, batches, expiry, suppliers, purchase orders and stock counts, because an invoice is only as good as the item file behind it.
Z-reports, shift reports and tax summaries that agree with what the authority has actually received.
Terminals, tablets and desktop tills. If you already have hardware we will usually work with it; if not, we supply it.
Deployed in English and French across the countries we serve.
Integration services
This is the larger half of our work. You have an ERP, a POS, an accounting package or something written for you years ago, and it has to start talking to the revenue authority. We build that connection.
We connect established ERP and accounting estates to the authority without asking you to change how your finance team works.
Tills that were never designed for fiscalisation, brought into compliance through our middleware rather than replaced.
Systems written specifically for your business. We work against whatever interface they can offer — database, file drop, or API.
One business trading across several of our markets, integrated once, with the per-country differences handled inside the middleware.
API & middleware
The connector is the part nobody sees and everybody depends on. Here is what ours is responsible for.
Your data is not shaped the way the authority wants it. The middleware translates items, tax classes, customers and totals into the required format.
Each invoice is signed and sent, and the authority's response is captured and written back so the receipt can carry it.
Timeouts, dropped connections and authority downtime are handled by queuing and retrying rather than failing the sale.
Everything sent is logged against what was acknowledged, so a gap is something you can see rather than something you discover at audit.
Beyond fiscalisation
Rhenium was an integration and payments engineering firm before it was a fiscalisation one. That work continues, and it is where the discipline came from.
Support
Specifications get revised, authorities add requirements, and businesses open new branches. An integration that is not maintained quietly stops being compliant.
To give you a straight answer quickly, it helps to know:
A demo with your items, your tax classes and your invoice shapes tells you far more than a slide deck does.