ETA e-invoicing in Egypt — the F&B factory implementation guide

Egypt’s e-invoicing platform — operated by the Egyptian Tax Authority (ETA) — has been live since November 2020 and is now fully mandatory for B2B transactions across the country. For F&B factories, where invoice volumes are high and tax treatment is complex (14% VAT, 5% withholding on services, lot tracking requirements), implementation is non-trivial but tractable.

This guide walks through what ETA actually requires, what AION handles end-to-end, and how a typical Egyptian factory implements the platform with the Nile Foods (Egypt) demo BG as a reference.

What ETA e-invoicing actually requires

The Egyptian mandate centres on the ETA Tax Invoicing Portal — a government-operated platform that receives, validates, and acknowledges electronic invoices in real time.

Five technical requirements:

1. Structured JSON or XML payload. Every invoice is a structured document with line items, tax breakdowns, buyer/seller identifiers (tax registration number for B2B, national ID or VAT number for B2C), and metadata.

2. Serial numbering. Every invoice has an internal serial number that is unique per issuer and sequential over time. ETA validates the sequence; gaps and duplicates are rejected.

3. ETA item catalog mapping. Every line item must map to a code from ETA’s master catalog of goods and services. The catalog includes thousands of entries; F&B factories typically map their items once during setup.

4. Document type codes. Invoices, credit notes, debit notes, and corrections each have their own ETA document type identifier. The portal validates the type matches the content.

5. UUID upon clearance. ETA returns a UUID when the document is successfully submitted. The UUID is embedded in the final invoice and is the reference for any future actions on that invoice (returns, credit notes).

Beyond the technical requirements, ETA expects:

• Submissions in near real-time (within seconds to minutes of invoice creation)
• WHT (withholding tax) details where applicable, particularly on service invoices
• Bilingual content support (Arabic + English on the invoice itself)
• Reconciliation with the monthly VAT return (Form 10)

How AION generates compliant invoices

In the Nile Foods (Egypt) demo BG, the pipeline runs end-to-end:

1. Sales clerk posts an invoice to a customer like Carrefour Egypt or Nile Delta Distribution Co.
2. SLA engine fires. GL entries post simultaneously. ETA payload generation kicks off.
3. Item code lookup. Each line item’s ETA code is pulled from the configured mapping table.
4. Serial number assigned. Atomic sequence increment.
5. WHT computation. If the invoice is for services (less common in factory sales, but happens for service-based revenue), 5% WHT is deducted and tracked separately.
6. Document type set. Standard invoice, credit note, debit note — whichever fits.
7. Submission to ETA portal. Through your configured channel (direct or clearance partner).
8. UUID received. Final PDF generated, including the UUID for reference.
9. PDF distribution. Emailed to buyer or made available for download.

The clerk’s view: post invoice, see it appear with status “Cleared by ETA — UUID 8a3f2b9c-…”. No technical complexity visible.

The item catalog mapping process

This is the longest part of go-live. For a 200-SKU factory, here’s the typical effort:

Day 1: Inventory of items. Pull a list of every active item that appears on invoices — finished goods, raw materials (for inter-factory transfers), services, freight charges. Categorise by type.

Day 2: ETA catalog browsing. For each item category, identify the ETA catalog codes that apply. Mango juice 1L might map to a single beverage-category code. Carton packaging might map to a packaging-services code. Some items will be obvious; others will require tax-advisor judgment.

Day 3: Bulk mapping import. Build a spreadsheet mapping your internal item codes to ETA codes. Import into AION via the bulk update tool. Spot-check 20-30 items by running test invoices.

Day 4-5: Test invoicing. Issue test invoices for each major item category against the ETA sandbox. Confirm clearance returns successfully. Adjust mappings for any rejections.

After 5 days, most factories are in steady-state mapping. The catalog will need ongoing maintenance as ETA adds new categories or as you launch new SKUs.

The 5% WHT mechanism

Egypt’s withholding tax on services is unique among the regions AION supports — it’s not a feature most factories think about until they encounter their first service invoice and find the math is off.

The mechanism:

• Service supplier invoices Nile Foods for, say, EGP 100,000 of freight services.
• WHT 5% = EGP 5,000.
• Nile Foods pays EGP 95,000 to the supplier and remits EGP 5,000 to ETA.
• The supplier accounts for the WHT as a prepaid tax against their own corporate tax obligation.

AION handles this automatically at invoice entry. When the AP clerk enters an invoice from a service-category supplier:

• The gross amount is captured.
• WHT 5% is deducted automatically.
• Net payable to supplier = gross minus WHT.
• WHT amount posts to the WHT payable GL account (a liability).
• Monthly WHT remittance report aggregates all WHT for the period.
• WHT certificate generated for each supplier showing the amount withheld.

If you don’t have this automation, your AP clerk does the math by hand on every service invoice. The error rate climbs. WHT remittance becomes a month-end firefight.

Worked example — Nile Foods invoice to Carrefour Egypt

Walking through as cfo.egypt:

1. Sales → Invoices → New
2. Customer: Carrefour Egypt — Cairo Festival (CUST-EG-CRF)
3. Items: 3,000 × Nile Mango Juice 1L at EGP 55 = EGP 165,000 net
4. VAT 14% = EGP 23,100
5. Gross = EGP 188,100
6. Click Post

Behind the scenes:

• SLA engine posts: DR AR — Carrefour 188,100 / CR Revenue 165,000 / CR VAT Output 23,100
• ETA pipeline assembles JSON payload: header (issuer Nile Foods Co., receiver Carrefour Egypt), line items with ETA catalog codes, tax breakdown, total
• Serial number assigned (e.g., NF-2026-005821)
• Document type: invoice (B2B)
• Submitted to ETA via the configured clearance channel
• UUID returns: 8a3f2b9c-1d4e-4f7a-9c0e-…
• Final PDF generated with bilingual layout, serial, UUID, QR code (optional for ETA)
• Emailed to Carrefour’s AP department

Total elapsed time: ~3 seconds from “Post” click to “Cleared” status.

Common pitfalls in Egypt

Pitfall 1: Stale item catalog mappings. ETA updates the catalog periodically. New categories get added. Some old codes get deprecated. If your mappings drift from ETA’s current state, you’ll start seeing clearance rejections. Schedule a quarterly review of the mapping.

Pitfall 2: WHT-eligible suppliers not flagged. If a service supplier is not flagged as WHT-eligible in the supplier master, the AP clerk has to manually apply WHT — and forgets. Set the WHT category at supplier creation, not invoice entry.

Pitfall 3: USD/EUR/EGP timing on supplier invoices. Egyptian imports are heavily multi-currency (concentrate from Turkey, packaging from Germany, etc.). The EGP devaluation since 2022 means receipt-date FX vs invoice-date FX vs payment-date FX all differ. AION captures FX at receipt and invoice independently — make sure your accounting team understands which rate applies for which leg.

Pitfall 4: Bilingual layout neglected. Like ZATCA, ETA expects the invoice to be readable in Arabic. Some businesses default to English-only PDFs and only generate Arabic on request. This works for now but is increasingly flagged. Default to bilingual layout.

Pitfall 5: Late-month batch submission. Some businesses batch submissions to end-of-day or end-of-week. This works for low-volume B2C but for high-volume B2B it accumulates risk. If the batch fails to clear, you have thousands of invoices to recover. Submit per-invoice; AION’s queue handles the throughput.

How does this connect to Nile Foods’ day-to-day

Nile Foods has 12 customers — 5 retail chains, 4 distributors, 2 hotels, 1 institutional. Average 8-12 invoices per day across them, plus credit notes and adjustments. ~3,000 invoices per year going through ETA.

Without automation: that’s 3,000 manual ETA portal submissions per year, plus 3,000 reconciliations against the monthly Form 10 return.

With AION: 3,000 invoices auto-cleared. Monthly Form 10 generated automatically from the same data. WHT remittance auto-generated from the supplier invoices. The AP/AR team gains back the equivalent of a half-time headcount.

Where to go next

For factories in Saudi Arabia, the parallel article is ZATCA Phase 2 e-invoicing for Saudi F&B manufacturers. For multi-country operations spanning Egypt and the Gulf, GCC VAT 2026 — multi-country in one ERP covers the consolidated picture. For the specific case of migrating from a small-business accounting tool like QuickBooks to a compliant ERP, see Switching from QuickBooks to ZATCA-compliant ERP — the principles apply to Egyptian factories migrating to ETA-ready ERPs too.