Follow a submission, retry and handle an unknown status

Read the Submissions list and record, submit or retry an e-invoice, and deal with blocked, timed-out and unanswered submissions.

Required permission: einvoicing.view; einvoicing.operate (submit, retry, reconcile, validate)

Before you begin

  • E-invoicing is on and an active onboarding exists (see Start with the sandbox).
  • An invoice or credit note has been posted. Each posted document has one submission for its profile.

Read the Submissions list

Open E-invoicing > E-invoicing > Submissions. Each row is one invoice and profile. Retries are attempts inside the row, not new rows. The tabs are All, Open, Blocked, Status unknown, Rejected, Accepted, With deadline and Superseded, each with a count.

Open a row to see the record: a rail Pending, Queued, Submitted, Accepted, a legal-state chip, and tabs Overview, Issues, Attempts & answers, Payloads, Canonical invoice and Lineage & events.

Submit and retry

  1. If Submit automatically when an invoice posts is off, new submissions stay Pending. Open the submission and click Submit. It is queued and sent at once.
  2. To work through everything that is queued, click Process queue now on the Dashboard. It handles up to 50 items. A Pending item is not sent by this button; only queued items are.
  3. If a send failed, click Retry. The same document and UUID are reused.

If the provider is unreachable, the system retries by itself. The default policy allows 6 attempts. It waits about 60 seconds, then 120, 240, 480 and 960, never more than 3,600 seconds, with up to 20% random variation. After the last attempt the item is marked dead and a red alert says "could not be delivered after 6 attempts." Retry puts it back in the queue.

A blocked submission

A submission is Blocked when the profile's checks find a problem, for example a business customer without an endpoint: "Buyer electronic address (endpoint) is required by UAE PINT AE - business." The Issues tab lists each problem with its field path and who normally fixes it (billing, tax, master data or integration). Nothing is sent while a submission is blocked: "Fix the validation issues first; nothing is sent while the submission is blocked."

  1. Open the Issues tab and note the field path.
  2. Fix the master data, for example add the Partner endpoint.
  3. Click Validate again.
Important:

Validate again re-checks the stored copy of the invoice made when it was posted. For a UAE invoice, Rebuild after repair is offered on a blocked submission but the system refuses it because UAE invoices count as legally issued. If a blocked UAE invoice cannot be unblocked, ask your tax reviewer or administrator; the supported correction for an issued invoice is a credit note. This is a known limit.

Status unknown

If the provider accepts a document but the answer is lost (for example a timeout), the submission shows Status unknown with the banner "No confirmed answer." An alert says the provider will be asked before anything is sent again.

  1. Wait for the first back-off (about 60 seconds), or click Ask the provider (reconcile).
  2. The system queries the provider. If the provider already accepted the document, the state becomes Accepted and no second send happens. The attempts list shows "submit: timeout", then "query: accepted".
  3. If the provider confirms it never received the document, the identical bytes are resent and the invoice ends Accepted.

Some providers publish no status query. ZATCA is one. For ZATCA the system says so and resends the identical signed invoice, which ZATCA treats as the same invoice.

Provider rejects

If the answer is a rejection, the submission turns red and the Issues tab shows the provider's code, the field and the meaning from the Rejection codes list. See Repair or correct a rejected e-invoice.

What happens next

An accepted submission keeps the request, the response and a hash of each. Events are written for accepted, rejected and status-unknown results. Alerts appear under E-invoicing > E-invoicing > Alerts (see Alerts and provider outages).

Good to know

  • Pressing a button twice is safe: each click sends a fresh idempotency key, and the same command with the same key is answered once.
  • An unsent invoice that is reversed in Accounting becomes Superseded with "The invoice was reversed before it was sent." A sent invoice cannot be reversed: "was sent for e-invoicing as EIN-...; it cannot be reversed. Issue a credit note to correct it."
  • The smart button on a posted invoice or credit note shows the state: green accepted, amber for rejected, blocked or status unknown.