E-Invoicing Is Coming to Algeria: What the e-facture-dz Protocol Means for Businesses
Algeria is the last major economy in the MENA region without an e-invoicing standard. An open-source protocol is being built to change that.
E-Invoicing Is Coming to Algeria. An Open Protocol Is Being Built to Make It Work
On April 18, I attended a closed-door meetup in Algiers organized by Amir Achraf Boudour through the Digital Transformation Meetup. The topic: building a standardized electronic invoicing protocol for Algeria. The room was small, the invite list was curated, and the conversation was concrete. No pitch decks, no abstractions. Just software editors, accountants, and builders discussing what it would take to move Algerian invoicing from PDFs and WhatsApp photos to structured, machine-readable data.
The project is called e-facture-dz. It is open-source, Apache 2.0 licensed, and it already has a working specification. After sitting through the discussion, I am convinced this is the right approach for Algeria.
Algeria is the last one standing
Every major economy in the region has already mandated or is actively rolling out e-invoicing:
| Country | E-invoicing mandate |
|---|---|
| Tunisia | 2016 |
| Egypt | 2020 |
| Saudi Arabia | 2021 |
| Morocco | 2025-2026 |
| France | 2026-2027 |
| Algeria | Not yet mandated |
Algeria's Direction Generale des Impots (DGI) has signaled that e-invoicing requirements are coming. The 2023 Finance Law made electronic invoicing optional for public contracts, and mandatory adoption has been discussed for 2026 and beyond. But there is no official timeline, no published standard, and no technical specification from the government.
The question is not if Algeria will require e-invoicing. It is when. And when that happens, the ecosystem needs to be ready with a standard that actually works for Algerian businesses.
The reality on the ground
If you have never worked with Algerian SMEs or accounting firms, here is what the current invoicing workflow looks like in practice.
A business owner creates an invoice in Excel, Word, or a basic desktop application. They print it, stamp it, sign it by hand, and either deliver it physically or take a photo and send it via WhatsApp. The accountant on the other end receives a JPEG of a crumpled invoice, manually re-enters every field into their accounting software, and hopes the numbers match. Tax declarations are compiled by hand from stacks of paper and screenshots.
This is not an exaggeration. It is the default workflow for the majority of Algerian businesses. The tools exist to do better, but there is no common format, no shared protocol, and no interoperability between the dozens of billing and accounting applications on the market. Every software editor speaks its own language.
What e-facture-dz actually is
e-facture-dz is not a product. It is a protocol. An open specification for creating, validating, digitally signing, and exchanging electronic invoices in Algeria.
The core format is JSON, not PDF. That distinction matters. A PDF invoice is a picture of data. A JSON invoice is the data itself: structured, queryable, and machine-readable. Software can validate it against a schema, tax authorities can process it automatically, and accountants can import it without touching a keyboard.
The specification covers the full lifecycle:
- Document types: invoices, credit notes, debit notes, and proformas
- Algerian tax fields: NIF, RC, NIS, TVA at 19% and 9%, TAP, droit de timbre, wilaya designations
- Digital signatures: native support for AECE THI9A-ENTREPRISE certificates, compliant with Loi 15-04 on electronic signatures
- Interoperability: bidirectional conversion with UBL 2.1 and Factur-X international standards
- Validation: JSON Schema with a TypeScript reference validator that enforces both schema conformance and business rules
- PDF/A-3 output: optional generation of archivable PDFs with the JSON payload embedded
The full specification and schema are published on GitHub under Apache 2.0. The text itself is CC BY 4.0. Anyone can implement it, extend it, or contribute to it.
Why this approach is right
There are two ways a country can get an e-invoicing standard. The government can design one top-down and mandate it, or the industry can build one collaboratively and present it for adoption.
The top-down approach works when the government has the technical capacity and the mandate is clear. Saudi Arabia's ZATCA did this well with FATOORAH. France is doing it with Factur-X and the PPF/PDP architecture.
But Algeria does not have a published e-invoicing regulation yet. Waiting for the government to design a protocol from scratch means waiting indefinitely while the entire region moves ahead. The alternative is what happened in that room on April 18: software editors, accountants, and technical contributors building a standard together, in the open, designed specifically for Algerian tax and regulatory requirements, and ready for DGI to adopt when the time comes.
The fact that it is open-source matters. No single vendor controls it. No license fee to implement it. No lock-in. Any accounting software, any billing platform, any ERP system can integrate it. The specification explicitly targets integration with Jibayatic, Algeria's online tax declaration platform, for automated G50 preparation.
What this means for businesses and accountants
For software editors, adopting e-facture-dz now is a competitive move. When e-invoicing becomes mandatory, the editors already supporting the standard will be ahead. Integration is described as achievable in days, not months.
For accountants, this is the single biggest operational upgrade available. Instead of manually re-entering data from photos and PDFs, you receive structured JSON that your software can import and validate automatically. Tax calculations are verified against rules embedded in the schema. Reconciliation becomes instant. G50 declarations can be pre-filled from invoice data. The site estimates an 80% reduction in invoice processing time, and based on what I have seen in Algerian accounting workflows, that number is conservative.
For businesses, the value is simpler. Invoices become traceable, tamper-proof when digitally signed, and machine-readable. You stop losing invoices in WhatsApp threads. Your accountant stops asking you to re-send the same document three times because the photo was blurry.
What I am doing about it
I did not attend this meetup as an observer. I went because invoicing and accounting software is what I build. I am committing to adopting the e-facture-dz protocol in every project I lead where it applies, at IdeaCrafters and beyond.
The protocol is ready. The specification is published. The schema is validated. What it needs now is adoption: software editors integrating it, accountants demanding it from their tools, and businesses asking for structured invoices instead of PDFs. If you build software that touches invoicing in Algeria, go read the specification and start implementing.
Algeria does not need to be the last country in the region without a standard. The standard is here. The question is whether the ecosystem adopts it before the government has to mandate it.