SAP to ETA e-invoicing

Post it in SAP. It reaches the tax authority on its own.

We build and run the connection that sends your sales invoices, credit notes and debit notes from SAP to the Egyptian Tax Authority, signed with your own certificate, and brings every status back.

Get a quote

One posted invoice, four steps, one status back in SAP

Nobody exports a file or retypes an invoice on the tax portal. A document posted in SAP is picked up, sent, and answered.

  1. 01 SAP

    A sales invoice, credit note or debit note is posted.

  2. 02 Mapping

    Item codes, tax types and the buyer are set out as the ETA document expects them.

  3. 03 Signing

    Signed with your registered certificate, on your USB token or HSM.

    On your side
  4. 04 ETA

    Submitted through the ETA e-invoicing API and validated there.

The ETA UUID and status are written back to the same SAP document.

Documents sent today Valid Submitted Rejected
  • 90012841 Invoice Valid UUID 7ZEX1G…KGJG
  • 90012842 Credit note Valid UUID N5PS8B…QMN7
  • 90012843 Invoice Rejected Item code not registered for your company - sent to your accountant to correct
  • 90012844 Debit note Submitted Waiting for the ETA to validate
  • 90012843 Invoice Valid Resubmitted after the correction
An example list. Document numbers and UUIDs are invented.

What SAP knows, in the words the ETA reads

Most rejections come from here, so this is where the work goes: every document type, item and tax code is matched once, then checked on every document.

The billing document type
documentTypeinvoice, credit note or debit note
The material or service
itemCodea GS1 or EGS code registered to your company
The tax code on each line
taxTypeVAT and any other tax type the line carries
The customer
receivera business, a person or a foreign buyer, with the tax registration number where there is one
Your company code
issueryour tax registration number and the branch that issued the document
Amounts, discounts and tax
totalscalculated and rounded the way the ETA checks them

The month's VAT, reconciled before you file

At the end of each month we set the tax on your sales against the tax on your purchases, compare both with what the ETA holds, and list every difference with the documents behind it.

Example month - illustrative figures, not a real company
VAT In SAP Held by the ETA Check
Tax on sales invoices 1,184,560.00 1,184,560.00 Matches
Less credit notes −36,120.00 −36,120.00 Matches
Plus debit notes 8,400.00 8,400.00 Matches
Output tax 1,156,840.00 1,156,840.00 Matches
Input tax on purchases 612,380.50 598,930.50 13,450.00 differs: 2 supplier invoices not found at the ETA
Net VAT for the return 544,459.50 557,909.50 For your review

We prepare and reconcile the figures. Your company reviews them, approves the VAT return and submits it - nothing is filed in your name without you.

A typical rollout, week by week

Your own timeline depends on how your SAP is set up and how many document types you issue. It is written into the quote.

Stage
Week 1 Week 2 Week 3 Week 4 Monthly
Access and reviewYour document types, tax codes and ETA portal registration
Codes and mappingItem codes registered, tax types matched
Signing on your sideYour token or HSM connected, test signatures
Tests on the ETA pre-production systemEvery document type, including the ones meant to be rejected
Go liveThe first real documents watched one by one
Running and reconcilingRejections followed up, VAT figures every month

What we run, and what stays yours

The connection is ours to build and keep working. The certificate, the registration and the return belong to your company.

We

  • Build the connection around your SAP and your document types
  • Keep the mapping of item codes and tax types up to date
  • Retry what failed to send, and flag every rejection with the ETA's reason
  • Prepare the monthly VAT figures and reconcile them with the ETA

Your company

  • Keeps the signing certificate - the token or HSM never leaves your side
  • Holds the ETA registration and the system credentials it issues
  • Corrects documents in SAP when a rejection needs it
  • Approves and submits the VAT return

EGPHP is an independent developer. We are not an SAP partner and not an intermediary certified by the ETA; the connection uses the ETA's published API under your company's own registration.

The layers between your SAP and the ETA

Each layer has one job and one owner, so when a document needs attention you know which layer to look at.

1 SAP 2 3 4 ETA
↓ Documents go down ↑ UUID and status come back up
  1. SAP Yours

    Your team posts sales invoices, credit notes and debit notes in SAP.

  2. The connection Built and run by EGPHP

    Maps each document to the ETA layout, checks it, retries what failed to send, and writes the ETA UUID and status back to the SAP document.

  3. Signing Yours, on your token or HSM

    The document is reduced to a canonical form, hashed with SHA-256 and signed as CAdES-BES with your certificate. The signature travels inside the document.

  4. ETA Run by the Egyptian Tax Authority

    Its identity service admits your registered system, its e-invoicing API receives and validates the document, and its e-receipt API takes retail receipts.

What happens to a document after it is sent

The ETA answers in stages. The connection follows each one and writes it back to SAP, so the status you read there is the one the ETA holds.

  1. The ETA takes the submission Submitted

    The first answer is quick and checks only the basics. It returns a submission ID and a UUID for each document taken in, and names any document it refused outright.

  2. The full check runs Submitted

    Structure, codes, tax arithmetic and the signature are checked after the first answer, not during it. The ETA's API is read by asking, so the connection keeps asking until each document has a verdict.

  3. The verdict

    Valid

    The document carries its ETA UUID. That is written back to the SAP document, and your buyer can now retrieve it from the ETA.

    Not accepted

    The ETA returns the reason for each failed check. We flag the document with that reason, your accountant corrects it in SAP, and the corrected document is sent again.

  4. After it is valid: the correction window

    The issuer can cancel and the buyer can reject a valid document, but only within a time window the ETA sets for each document type. Once the window has passed, the way to correct it is a credit note or debit note linked to the original.

  5. Month end

    The valid documents, credit notes and debit notes of the month are what the VAT reconciliation starts from.

The stages and the correction rules follow the ETA e-invoicing SDK documentation.

Selling over the counter? E-receipts too.

Where your sales are recorded as retail receipts, the same connection can send them to the ETA e-receipt system, so the receipt your customer takes carries its ETA reference.

Tell us how you invoice today

Which SAP you run, which documents you issue, and where the ETA filing stands now. We quote the integration after one conversation about it.

Get a quote

Related services

Business systems Orders, stock, accounts and a cashier, built around how you work, on every phone as an app.Databases MySQL, MariaDB, PostgreSQL, Redis, MongoDB and more, tuned, replicated and restored on test.Server security Firewall, bans, a web firewall, patching and tested backups, with a person watching.Talk to us Tell us what you need and get a reply from the team in Cairo.
MickeyAnswers in seconds