E-invoicing
Structured e-invoices for Europe and Latin America: Peppol, XRechnung, Factur-X, FatturaPA, KSeF and CFDI.
12 steps · 10 questions · 10 screens on this shelf
The screens on this shelf
View
E-invoices
Every structured e-invoice generated from a customer invoice or credit note: its format, whether it validates, and what the network said. Generate one from Customer Invoices.
Open
Records
E-invoicing Profiles
How this company issues structured e-invoices: the country, the format (Peppol BIS, XRechnung, Factur-X, FatturaPA, KSeF, CFDI 4.0), the seller’s identifiers and how documents leave. A company with no active profile issues no e-invoices.
Open
Records
E-invoicing Customer Identifiers
What each customer’s e-invoice must carry: the Peppol participant id, a German public buyer’s Leitweg-ID, the Italian codice destinatario or PEC, the Mexican RFC and uso CFDI, the Polish NIP.
Open
Records
E-invoicing Connections
The networks e-invoices are sent through: a Peppol access point, Italy’s SdI, Poland’s KSeF, a Mexican PAC. The credential is sealed and never shown again. These adapters have not been tried against a live network from this installation; send by file until a connection has been tested with real credentials.
Open
Records
ZATCA Signing Units
The e-invoice generation solution units (EGS) registered with ZATCA. Under Phase 2 every invoice is stamped by one -- the branch’s own, or the company’s default -- and carries its counter (ICV) and the previous invoice’s hash (PIH). The private key and the ZATCA secrets are sealed and never shown. A TEST unit stamps with a self-signed certificate ZATCA would not accept: for demonstrations only.
Open
View
ZATCA Dashboard
Each signing unit at a glance: how many of its invoices ZATCA cleared, reported, accepted with warnings or rejected; how old the oldest invoice still waiting is (a simplified invoice must be reported within 24 hours); when its certificate expires; and the latest rejection. Open ZATCA Submissions for the invoices themselves.
Open
View
ZATCA Submissions
Every invoice and note stamped under ZATCA Phase 2 and what ZATCA said. A tax invoice (B2B) is cleared when it is posted and may be given to the buyer only once cleared; a simplified invoice (B2C) is reported within 24 hours. One that could not be sent is tried again automatically with the same document. A REJECTED document may not be given to anybody and is never sent again as it is: re-issue it, correct the cause and post the new one.
Open
View
ZATCA Onboarding
Each signing unit taken through ZATCA’s onboarding: choose the environment (the Developer Portal sandbox, simulation, or production), enter the one-time password from the Fatoora portal, run the compliance checks (one sample of each document the unit issues), then request the production certificate. Renew before the certificate expires — a warning is raised 30 days ahead. The keys and ZATCA’s secrets are sealed and never shown. Register the unit itself under ZATCA Signing Units first.
Open
View
ZATCA Archive
Every stamped document as issued, every document ZATCA cleared, and every answer ZATCA gave, with the SHA-256 of what was kept. Append-only: the database refuses any change or removal, except the retention purge of records older than the company’s retention (at least six years, the KSA VAT record-keeping period).
Open
View
ZATCA API Log
Every request this company sent to ZATCA’s Fatoora platform and what it answered — onboarding, compliance checks, clearance and reporting — with the one-time passwords, the secrets and the authorization header taken out before it was written. Append-only.
Open
Progress is kept in this browser only — it is not sent anywhere and nobody else can see it.