What Happens After You Select an ASP for UAE e-Invoicing?

Selecting an Accredited Service Provider (ASP) is just the start of your UAE e-invoicing journey. Once the contract is signed, your business still needs to connect its systems to the ASP, validate invoices against the Ministry of Finance’s (MoF) structured XML format and ensure the required tax data reaches the Federal Tax Authority (FTA) with each invoice.

Getting from contract signing to live production typically takes 4 to 12 weeks. There are several steps to complete along the way, and each one has a role in keeping your e-invoicing setup compliant. 

Skipping or rushing these steps can increase the risk of errors and rejected invoices.

What does your ASP actually do once you have signed on?

Once you sign on with an ASP, it becomes the main technical link between your business and the UAE e-invoicing system. Your business does not connect to the FTA directly. Instead, the ASP receives your invoice data, validates it, sends it to the buyer’s ASP and reports the required tax data to the FTA.

The UAE uses what the MoF calls the Decentralised Continuous Transaction Control and Exchange (DCTCE) model, often referred to as the five-corner model. It involves five parties: the seller, the seller’s ASP, the buyer’s ASP, the buyer and the FTA.

After you sign on, your ASP performs three main functions:

1. Receives your invoice data: Your ASP receives invoice data from your accounting or Enterprise Resource Planning (ERP) system.
2. Validates and prepares the invoice: It checks the data against the Peppol International Invoice UAE (PINT AE) structured XML standard mandated by the MoF. If your system does not generate PINT AE-compliant output, the ASP converts the invoice into the required format.
3. Exchanges the invoice and reports tax data: The ASP sends the invoice to your buyer’s ASP through the Peppol network. At the same time, it reports the required tax data to the FTA.

There is one important detail to understand here: both businesses need their own ASP. You appoint an ASP for your side of the transaction, while your buyer appoints one for theirs. The two ASPs work together to exchange the invoice through the Peppol network. 

How does the integration with your accounting system work?

Once you have chosen an ASP, your accounting or ERP system also needs to connect to it. The purpose of this connection is simple: when your business creates an e-invoice, the relevant data needs to reach the ASP in the required format. 

The most common approach is an Application Programming Interface (API). Your accounting or ERP system sends the invoice data to the ASP through this connection. If your system cannot make direct API calls, your ASP may provide an alternative such as a middleware connector or file-based transmission.

This connection does not replace your accounting software or ERP system. The two have separate roles. Your existing system continues to create and store your invoices, while the ASP handles the required e-invoice exchange.

How long does integration take? 

Based on comparable e-invoicing implementations in the region, including Saudi Arabia’s Zakat, Tax and Customs Authority (ZATCA) rollout, ASP onboarding typically takes 4 to 12 weeks. The timeline can change based on the intricacy of your ERP environment, particularly where API integration, testing and certification are involved. 

The integration process normally involves the following steps.

• API credentials setup and system access configuration
• Field mapping to align your invoice data with the mandatory PINT AE XML fields specified by the MoF
• Sandbox testing with sample invoices to confirm that data flows correctly end to end
• Reconciliation checks to verify that transmitted data matches your source records exactly
• Formal sign-off from both your team and the ASP before production access is granted

What happens when your system sends an invoice through the ASP?

Once live, each invoice follows the five-corner path in near real time.

1. Your system generates the invoice data and sends it to your ASP via the API. 
2. The ASP checks the invoice structure, tax amounts and mandatory PINT AE fields. If your system does not generate PINT AE XML itself, the ASP converts the invoice into the required format. 
3. The ASP assigns a unique invoice reference number and transmits the invoice through the Peppol network. At the same time, the required tax data is reported to the FTA. 
4. Your buyer’s ASP validates the received invoice and delivers it to your buyer, then sends a confirmation back to your ASP.
5. The confirmation is passed back to your system so your finance team can see whether the invoice was accepted or rejected. 

An accepted invoice is a legally valid tax document. A rejected invoice is not. The business must handle both outcomes within its accounting workflow, which means your finance team needs a clear process for acting on rejection notices before you go live.

What causes an invoice to be rejected and what should you do about it?

Rejection can happen at two points. Your ASP may reject an invoice before it reaches the Peppol network if it fails local PINT AE schema validation. The buyer’s ASP may reject it after receipt if it finds a data mismatch or a compliance issue on their end.

These are the most common reasons for rejection at the sender ASP stage.

• Missing or invalid Tax Registration Number (TRN) for the supplier or the buyer
• Incorrect Value Added Tax (VAT) rate applied to a line item
• Mandatory PINT AE fields left empty or formatted incorrectly
• Invoice sequential number already used in a previous submission
• Date and time fields that do not match the MoF’s prescribed format

When a rejection occurs, the ASP returns an error code with a reason. You must correct the source data in your accounting system and resubmit. An uncorrected rejected invoice has no legal standing. Rejected invoices should not sit in a queue unresolved, as the MoF’s guidelines define timelines for valid invoice submission.

What should you verify before switching to live production?

Before moving from sandbox testing to live production, make sure your systems, data, team and ASP are ready. Going live before these checks are complete could result in invoice rejections from the start.

Use the following checklist to confirm that your setup is ready.

• All mandatory PINT AE fields are correctly mapped in your accounting or ERP system
• Your system can receive rejection responses and route them to the team responsible for corrections
• Finance and billing staff understand the difference between a soft validation warning and a hard rejection that requires resubmission
• Your ASP has confirmed that its production connection to the Peppol network and the FTA reporting channel is active and tested
• The ASP you have signed with has cleared the MoF’s pre-approval requirements under Ministerial Decision No. 64 of 2025. Note that pre-approval and full accreditation under Article 16 are separate stages. Confirm the current accreditation status of your ASP before going live
• Your VAT registration details in the system match your FTA records exactly, including TRN and entity name

Choosing an ASP is an important first step, but your e-invoicing setup needs to be ready before the first live invoice is submitted. Your systems must be integrated, PINT AE fields mapped, the complete invoice flow tested and a clear process put in place for handling rejections.

TallyPrime’s UAE e-invoicing solution is designed to connect with MoF pre-approved accredited service providers so that businesses can meet the mandate without managing the technical transmission layer manually.