E-invoicing Copilot
Reads a company's invoice export and reports, invoice by invoice, what would stop each one being sent as a UAE e-invoice.
- Status
- Stage 1 built
- Role
- Developer
- Year
- 2026
- Type
- UAE e-invoicing readiness validator
Where it stands
The validator is built and tested against a fictional sample dataset. It checks the Ministry of Finance mandatory fields. The full PINT-AE schema rules are not checked yet.
There is no public link for this project.
My part
Design and build of the validator and its report.
- Wrote the rule engine and its checks for seller, buyer, header, line and total fields
- Built loaders for flat CSV and Excel tables, and for formatted Excel invoices through a per-template cell map
- Detected data damaged by spreadsheet software, such as a 15-digit tax number turned into scientific notation
- Wrote the report generator and 53 unit tests
What it is
The UAE is introducing mandatory e-invoicing in the PINT-AE format. Most businesses do not know whether the invoices their accounting system produces today would pass. This tool answers that from an export.
It reads a CSV or Excel export, checks every invoice against the Ministry of Finance mandatory-fields document, and writes a readiness report and a findings file: which invoices are ready, which are blocked, and what to fix first.
Each rule is tagged by how certain it is: stated in the official document, plain arithmetic, or an assumption that still needs confirming against the specification. The report never presents a guess as a requirement.
Built with
Python · Standard library · CSV · Excel · unittest
Need something like this built?
Tell me what you are making. I will tell you how I would approach it, and whether I am the right person.
Start a conversation