Send invoice
This topic explains the four-step outbound flow for invoices and credit notes you send from your system through Sovos to buyers and the Federal Tax Authority (FTA).
The outbound flow covers invoices and credit notes you send from your system to your buyers through the Sovos Compliance Network and Pan-European Public Procurement On-Line (PEPPOL) network. The full four-step flow applies to domestic B2B/B2G transactions where both you (the sender) and the buyer (the receiver) are registered in the United Arab Emirates (UAE) PEPPOL network.
Two variations apply in specific cases:
- Deemed supply or international buyer not on PEPPOL: The invoice doesn't flow to the buyer ASP. Sovosreports the Tax Data Document (TDD) to the Federal Tax Authority (FTA) directly without exchange.
- International buyer registered on PEPPOL: The invoice is delivered to the buyer ASP, but the buyer ASP doesn't validate it against UAE mandate rules.
Key terms
- Message Disposition Notification (MDN)
- A confirmatory message exchanged over the UAE e-invoicing Pan-European Public Procurement On-Line (PEPPOL) Network from buyer ASP to Sovos ASP and FTA to Sovos ASP or buyer ASP upon receipt of the business document
- Message Level Status (MLS)
- A confirmatory message exchanged over the UAE eInvoicing Pan-European Public Procurement On-Line (PEPPOL) Network from buyer ASP to Sovos ASP and FTA to Sovos ASP or buyer ASP upon receipt and validation of the business document.
- PINT-AE
- PEPPOL International Invoice for UAE
Flow steps
- Step 1 - Submit to Sovos
Send your invoice to the Sovos Compliance Network in (Sovos Canonical Invoice) or PINT-AE format. Sovos validates the document and passes it to the ASP.
The following table shows the possible outcomes and the action to take for each one:
Outcome Status Error Code Action Validated 106UPLOADEDProceed. Sovospasses to ASP Validation failure 401FAILEDCorrect the document and resubmit - Step 2 - Sovospasses to ASP
Sovos converts the document to PINT-AE XML and sends it to the Sovos ASP. The ASP acknowledges the request with a message ID that includes the UUID, then begins processing.
The following table shows the possible outcomes and the action to take for each one:
Outcome Status Error code Action Validation success PROCESSING- Continue SMP lookup failure FAILEDSMP_LOOKUP_FAILEDRetry - Step 3 - SovosASP transmits to buyer ASP
The Sovos ASP transmits the invoice to the buyer ASP over the PEPPOL AS4 protocol.
The following table shows the possible outcomes and the action to take for each one:
Outcome Status Error code Action Positive MDN from buyer ASP DELIVERED- Proceed to TDD reporting Negative MDN FAILEDTRANSMISSION_FAILEDRetry Positive MLS from buyer ASP DELIVERED- Complete Negative MLS, validation failure FAILEDFAILED- Correct the document.
- Resubmit to Sovos. This requires a new UUID.
SovosASP withdraws the TDD from FTA ASP
Negative MLS, buyer not reachable FAILEDREJECTED_BY_MLSRetry SovosASP withdraws the TDD from FTA ASP
No MLS received DELIVERED- ASP retries When the ASP receives a positive MLS from the buyer ASP, the PEPPOL transmission is complete.
- Step 4 - Sovos ASP reports TDD to FTA
After receiving an MDN from the buyer ASP, Sovos ASP prepares and submits the TDD to the FTA ASP. The FTA confirmsthe submission against the UAE mandate.
The following table shows the possible outcomes and the action to take for each one:
Outcome Status Error code Action Positive MDN REPORTED- - Positive MLS from FTA ASP DELIVERED- Complete Negative MDN FAILEDTRANSMISSION_FAILEDRetry Negative MLS from FTA ASP FAILEDVALIDATION_ERROR- Correct the document.
- Resubmit to Sovos. This requires a new UUID required.
No MLS from FTA ASP DELIVERED- Retry When the FTA confirms receipt, the document is shared with the FTA and the tax authority reporting status is set to successful.