The thesis
So myInvoice.ae was not built as a billing tool with accounting added later. It was built the other way round: a double-entry ledger first, with the documents that feed it on top.
Everything follows from the order it was built in.
Most finance software is a document tool wearing an accounting badge. You can tell from what was built first.
The usual order
Invoices come first, because invoices are what people ask for. Reports arrive later, assembled from the invoices. Then stock is added, kept in a second place. By the time a quarter closes, three parts of the same business disagree, and the reconciliation is somebody's Thursday.
Ours
A real double-entry general ledger, with posting rules per document type, period locking, and reversal rather than edit. Then the documents that feed it. Then the stock engine, writing to the same ledger inside the same transaction that moves the quantity.
Five rules, and what each one cost us.
A principle nobody had to build around is a slogan. Each of these names the decision it forced.
- 01
Enter it once
Every handoff between systems is a place for a figure to change. A quotation should become an invoice without anyone retyping a line, and that invoice should reach the ledger without anyone opening a second application.
→ Conversion carries line items, customer and VAT treatment across untouched.
- 02
The mechanism is the promise
"Compliant" is a claim; a row lock is a mechanism. Where a rule has to hold under concurrency, under a rollback, or under an audit, it belongs in the database or in one choke point of code — not in a validation message.
→ Gapless numbering under a row lock; one journal writer; one stock movement path.
- 03
Never destroy a record
Financial history is not a list you tidy. Deleting a document removes it from a view; it does not remove it from the record. Voiding posts a mirror-reversal rather than editing what was already stated.
→ Soft deletes across every financial document; five-year retention by construction.
- 04
Two languages, not a translation
Arabic is a first-class direction, not a stylesheet. If the layout does not mirror — navigation, tables, forms, charts — then the product works in Arabic the way a subtitled film works: adequately, and obviously second.
→ A full right-to-left layout, with figures kept in Latin digits as documents are issued.
- 05
Automation stops at the signature
Software should remove the typing, not the responsibility. Reading, summarising and drafting are genuinely useful. Issuing, posting, approving and filing are acts with a named responsible person behind them.
→ Ledger AI reads and drafts; it does not file, post or approve.
Compliance features are rarely hard to describe. They are hard to guarantee under concurrency.
From the engineering notes on gapless numbering
Where this goes next.
62 modules are in production today across seven groups. What follows is set by the FTA's timetable rather than by ours.
- Now
- The full cycle in production — documents, VAT, ledger, inventory, payments, reporting, in English and Arabic.
- Next
- Deeper Peppol delivery as the FTA's phases activate, and corporate tax filed from the same books.
- Always
- One surface. Every new module posts to the same ledger, or it does not ship.
Start where you are
Issue one compliant invoice. Then look at the ledger.
Fourteen days of every feature, no card, and nothing to migrate before you can see whether it works the way you do.
English & Arabic · AED and multi-currency · UAE-built for FTA rules