Every document you have transmitted is somewhere, and an operator's job is to be able to say where without asking anyone. That is what the E-Invoice Documents list is for.

Find it at Accounting → Customers → E-Invoice Documents, or under the UAE E-Invoicing configuration menu. Each document moves through Draft → Generated → Validated → Sent → Delivered → Acknowledged → Cleared (FTA), or it lands on Rejected / Failed.

Be honest about the middle band. The guide names the sequence but does not define what Delivered and Acknowledged mean at your particular provider, because that depends on what the ASP reports back to corner 1. Treat those three states as one condition — in transit — and that is exactly how the list lets you filter them. The filters that matter are Outbound/Inbound, In Transit and Rejected / Failed, and between them they answer the only three questions worth asking of a list this long: is it mine to send or mine to receive, is anything still moving, and is anything broken.

That gives you a daily triage that takes about five minutes. Open Rejected / Failed first, because those are work items with your name on them. Then In Transit, sorted oldest first, because age is the signal — a document in transit for two hours is normal and one in transit since last Thursday is not. Then switch the filter to Inbound for the supplier documents waiting on you, which is Lesson 6. Anything not in those three views is either finished or not yet sent, and neither needs you today.

Now immutability, briefly, because it governs what you may do to anything in that list. A transmitted e-invoice is SHA-256 stamped and cannot be re-generated or reset to draft. Use View XML to download the archived, hash-stamped file — that archived XML, not a PDF reprint, is what you show when someone asks what you actually transmitted. The precision worth holding: a manager does hold Reset to Draft as a permission, and it still will not return a transmitted e-invoice to draft. The permission governs documents that can be reset; immutability governs the ones that cannot.

The consequence for corrections is short and absolute. A correction is a new document, never a mutation of the old one. You issue a credit note, or a corrected invoice, and it travels the lifecycle on its own — which is also how the other side and the FTA see it, since they hold what you sent and no edit of yours could reach it. The instinct to "fix the XML and resend" is the instinct to make your records and the network's records disagree.

The failure mode is a support call that starts "the invoice has disappeared". It has not. It is filtered — the list opened on In Transit and the document cleared, or it is inbound and the filter is on outbound. Before escalating anything, clear the filters and search the document by its invoice number. The second version of the same call starts "we edited the invoice and it will not resend", and the answer is Lesson 4 in one line: it will not, by design, and the correction you want is a new document.

The idea to carry forward: three filters, three questions, five minutes. And nothing you transmitted can be changed — only answered by something new.