Create an invoice: Steps 3 and 4, audit and transmit
How to read the UBL / PINT AE audit screen and what happens when you click Save & Transmit.
Step 3: UBL 2.1 and PINT AE audit
Step 3 shows every business term the portal has mapped, grouped as the standard groups them:
- Document profile and headers: invoice ID, type code, currency, specification ID
urn:peppol:pint:billing-1@ae-1, transaction type code. - Supplier (seller): name, Peppol endpoint
0235:<TIN>, TRN, legal address, contact. - Buyer: name, endpoint, TRN.
- Totals and tax scheme: line total, tax exclusive, tax, tax inclusive, payable.
- Lines: each line's net, gross, base quantity, tax category, rate and GTIN.
- Compliance matrix: which groups came from your input, which were calculated and which are fixed.
Check here before you send. In particular:
- The buyer endpoint is the one you expect (a real TIN, or a predefined receiver for special scenarios).
- The transaction type code matches the boxes you ticked.
- Every line shows the tax category and rate you intended.
- Reverse-charge lines show a GTIN.
Anything wrong in the seller block is fixed in Settings; anything wrong in the buyer block is fixed on the customer record.
Step 4: review and transmit
Step 4 summarises the customer, the dates and the financials, and confirms the 51 mandatory fields are present.
- Mark Draft saves without sending. The invoice appears with status Draft.
- Save & Transmit validates the document, sends it through your ASP and starts FTA reporting.
Once transmitted, an invoice cannot be edited or withdrawn. Corrections are made with a credit note or debit note. Watch the status change to Delivered or Tax Reported on the Invoices page.