The mandate, briefly
As regulatory context: the Egyptian Tax Authority (ETA) began mandating B2B e-invoicing in phased waves from late 2020, starting with the largest taxpayers and extending to VAT-registered businesses generally. The consumer side followed — e-receipts, with broad obligations in force from September 2025 — and enforcement keeps tightening through 2026, with unregistered paper invoices progressively losing recognition for VAT deduction and for dealings with government bodies.
The plain reading for a contractor: a paper invoice is becoming a non-document. If your invoice does not exist as a registered electronic record in the ETA’s system, it increasingly does not exist for your client’s tax deduction, for your VAT position, or for the public-sector work that anchors much of Egypt’s solar pipeline.
What a compliant e-invoice actually requires
An ETA e-invoice is not a PDF with a logo. It is a structured electronic document: the issuer’s and buyer’s tax registration details; line items, each carrying a standard item code (GS1 or the Egyptian EGS coding scheme) with quantities, unit values and line totals; tax computed per line at the applicable rate — the standard VAT rate in Egypt is 14%; an electronic signature; and, once accepted, a unique identifier from the authority and a QR code through which the document can be verified.
The hard part is not the QR — that is the last and easiest step. The hard part is the line discipline: every item on every invoice must exist as structured, coded data. A billing process that lives in free-text Word templates faces a choice between manually coding every invoice forever, or finally structuring the data at the source.
Why it bites an EPC harder than a shop
A retailer’s invoice is quantity × unit price; the mandate maps onto it naturally. An EPC’s invoice is a progress claim against a schedule of values, with retention withheld, advance payments recovered, and change orders amending the contract sum mid-stream. All of that must still flatten, every billing cycle, into structured coded lines that a validation engine will accept — and the certificate your client’s engineer approved must reconcile, line for line, with the e-invoice the tax system records.
Stack the rest of the Egyptian rulebook on top: withholding tax at 3–10% depending on vendor category on the payables side, WHT certificates to issue and chase, and multi-currency reality — modules priced in dollars, labour paid in pounds. This is not bookkeeping a spreadsheet-and-Word workflow survives gracefully. The structure the ETA demands has to exist inside the billing system itself, not in the accountant’s head at month-end.
What Voltara does — and what it does not, yet
The claim discipline first, because this is an area where vendors blur lines: Voltara generates ETA-compliant e-invoices; submission to the government gateway is on the integration roadmap. We say it that precisely because the difference matters to your compliance officer.
What that means in practice: invoices come out of the billing engine already structured — whether the document is a milestone invoice, a progress-SOV draw, a cost-plus or a time-and-materials bill, it is built as coded lines with Egyptian VAT at 14% computed under the jurisdiction’s rules, carries the QR, and is archived on the project alongside the certificates and the audit trail. The document that goes to the gateway is produced by the same system that certified the progress, so the claim and the tax record cannot drift apart. The submission step itself runs through your existing channel today; direct gateway submission from the platform is on the integration roadmap, and we will keep saying so plainly until it ships.
A practical sequence for an EPC
First, register on the ETA portal and obtain your credentials and electronic signature — the administrative step with the longest lead time. Second, map your catalogue once: your BOM categories and service lines to standard item codes. A procurement price book that already structures equipment into defined categories turns this into a mapping exercise rather than archaeology. Third, make billing emit structured data from day one — retrofitting structure onto a year of free-text invoices is the expensive path, and it is the default path if you wait. Fourth, keep the audit trail together: identifiers, QRs, certificates and the invoice history living with the project, because the tax review that tests all of this happens years after the crew left the roof.
Egypt is the proving ground for how we build jurisdiction logic — it is our own validated home market, and our EPC arm bills under this mandate on this platform. The honest summary: the mandate rewards contractors whose billing was structured all along, and punishes the rest one invoice at a time.