E-invoicing · Reference

End-to-end workflows

How work moves through E-invoicing from start to finish, who does each step and what the system does in response.

On this page (7)

Switch on and send the first UAE e-invoice

Who: Configurer, Operator, Auditor

#	What the person does	What the system does
1	Dashboard: Start with the sandbox	E-invoicing on; sandbox onboarding Active with callback and signing credentials
2	Settings: set Our endpoint identifier (company TRN) and keep Submit automatically on; on a business customer add Partner endpoint 0235 with its TRN	Saved; endpoint format valid
3	Sales: create and post an invoice 2 x 50.00 AED with 5% VAT for that customer	Smart button E-invoice appears on the invoice
4	Dashboard: Process queue now; open Submissions	Submission Accepted, legal state Issued, Net 100.00 / Tax 5.00 / Payable 105.00
5	Auditor: Payloads tab, download the request XML	File hash equals the screen; XML shows CustomizationID urn:peppol:pint:billing-1@ae-1
6	Reports: Submission monitor and Invoice-to-provider bridge	One row per invoice; 1 submission, 1 attempt; no 'missing' flag

Who: Operator, Tax reviewer, Accountant

#	What the person does	What the system does
1	Sandbox behaviour: reject; post a UAE invoice	Submission Rejected, legal state Issued, issue SIM-ADDR-001 with remediation
2	Reject analysis report and Alerts	Group shows the code with Open 1; red alert 'was rejected'
3	Tax reviewer: open the submission, look at the actions	Correct by credit note offered; Rebuild after repair NOT offered
4	Press Correct by credit note with reason 'Wrong address'	Draft credit note with the same lines; issue remediation updated
5	Sandbox behaviour: accept; Accountant confirms and posts the credit note	Credit note gets its own submission
6	Process queue now; open both submissions	Credit note Accepted with a reference to the invoice; invoice stays Rejected; bridge shows both

Who: Configurer, Tax reviewer

#	What the person does	What the system does
1	Saudi test company: Settings seller CRN, building number, district, postal code; sandbox 'once reject'	Settings saved
2	Post a standard invoice to a business customer with an incomplete address	Submission Pending clearance and Blocked; issues list buyer building number, street, district, postal, city by path
3	Add a Partner endpoint with the full Saudi address; Validate again, then Rebuild after repair 'Address fixed'	New submission in the lineage; old one Superseded
4	Process queue now: sandbox rejects once	Submission Rejected, legal state 'Not cleared'
5	Rebuild after repair again	New submission Accepted, legal state Cleared, ICV continues the chain without a gap or reuse
6	Open Lineage & events	Chain old to new visible; old issues Resolved; payloads of every attempt kept

Who: Operator, Approver

#	What the person does	What the system does
1	Sandbox: timeout_after_accept; post an invoice	Status unknown with banner; alert 'no answer from SANDBOX'
2	Sandbox: accept; press Ask the provider	Accepted without a second send
3	Sandbox: unavailable; post three invoices	Items queued; after three failures an outage case opens, red alert
4	Approver: Approve contingency text; Operator tries the same	Approver accepted (another person than the opener); operator refused
5	Sandbox: accept; wait or Process queue now	Queued invoices Accepted; detected outage closes by itself
6	Dashboard and Unknown and deadline queue	No open items at risk; outages card empty; no document sent twice (attempt lists checked)

Who: Configurer A, Custodian, Approver B

#	What the person does	What the system does
1	A: create a production provider (https, allowlist) and a production profile; Review attempts by A	A is not offered Review/Activate
2	B: Review and Activate the provider and the profile (profile needs Certified + evidence + passed conformance)	Both Active; gates name anything missing
3	A: new Production onboarding, production evidence entered, Request activation	Awaiting approval
4	Custodian: bind auth token and signing key (authority certificate, not self-signed) [Blocked if no sandbox for real certificates]	Credentials Awaiting approval
5	B: Approve each credential, then Approve the onboarding	Credentials Active; onboarding Active; A cannot approve own
6	Post a production invoice [Blocked if no sandbox]	Sent to the real authority or provider; evidence stored

Who: Custodian, Approver, Operator

#	What the person does	What the system does
1	Create one Accepted, one Pending (auto submit off) and one Status unknown submission on a KSA sandbox company	Three states ready
2	Custodian: bind a new signing key; test environment activates it	Old key Rotated
3	Operator: open the unknown one	Queried first, no resend
4	Open the pending one and Submit	Signed with the new key, same ICV and previous hash as before
5	Custodian: Compromised on the new key with a reason	Onboarding Suspended; alert; secret destroyed
6	Approver: Reinstate after binding a fresh key; Credential health report	Onboarding Active again only through approver who did not request; health report shows rotated/compromised/active keys

Who: Inbound clerk, Accountant

#	What the person does	What the system does
1	Settings: choose the Product for unmatched received lines	Saved
2	Received e-invoices: upload a valid UBL file from a known supplier	State Valid, supplier matched
3	Upload the same file again	Duplicate, no second bill possible
4	Open the valid row: Draft the bill	State Bill drafted; open bill shows a DRAFT supplier bill
5	Accountant reviews and posts the bill in Purchase	Bill posted by a person, not by e-invoicing
6	Upload a file with a DOCTYPE	Rejected with the safety message; no bill

Updated 3 October 2026