Create, sign, and submit an e-invoice in Fatoora

Full document workflow: draft → Ready to sign → Sign (local) → Submit ETA → Refresh status → Valid/Invalid, PDF archive, and cancel on ETA.

submit e-invoice EgyptReady to sign FatooraSubmit ETAإرسال فاتورة إلكترونيةVALID INVALID ETA

Document statuses in Fatoora: DRAFT → READY_TO_SIGN → SIGNED → SUBMITTED → VALID / INVALID (and CANCELLED when cancelled on ETA).

Prerequisites

• Settings saved with Client ID/Secret and issuer profile
• Test ETA login OK
• Local signer running with the correct API key
• At least one customer (receiver) and product/line item codes

1. Create

Open Outbound → New invoice (`/t/{slug}/documents/new`). Choose customer, confirm receiver name/TIN, add lines (description, ETA item code, EGS|GS1, qty, unit price), optional notes. Click Save for draft, or mark ready to sign when the payload is complete.

2. Ready to sign

From the list or detail, use Ready to sign. Fatoora builds the unsigned ETA JSON (`unsignedPayload`) and sets status READY_TO_SIGN. This step validates issuer profile and line/receiver requirements.

3. Sign (local)

Click Sign (local). Complete signing in the local app. Status becomes SIGNED with `signedPayload` and `signedAt`. Without a signed payload, Submit is blocked.

4. Submit ETA

Click Submit ETA. Fatoora calls the ETA submit API for your environment. On acceptance you typically see SUBMITTED with `etaUuid` / longId / submission id. Rejections can land as INVALID with an error message.

5. Refresh status and PDF

Click Refresh ETA (needs `etaUuid`). Status may move to VALID or INVALID. Valid documents can archive the official printout PDF. Use Download PDF, ETA link (portal share URL), Duplicate, or Cancel on ETA as needed. Lists also support bulk refresh and archive.

Draft without credentials

You can create drafts before ETA is configured. You cannot submit or refresh until Client ID + Secret are set — the UI hint explains that.

Common failures

• Ready to sign blocked → missing issuer TIN/name/activity/address or line item codes
• Sign does nothing → signer not running, wrong API key, or token PIN/driver issue
• Submit fails → credentials/environment mismatch or document not SIGNED
• Invalid after submit → fix ETA validation message, correct master data, duplicate/reissue as appropriate