SAP Business One and UAE eInvoicing: a practical guide for SMBs

If your business runs SAP Business One, you have probably seen a lot of eInvoicing news recently and wondered how much of it applies to you. The short answer is: all of it. The slightly longer answer is: it is more straightforward than you might think, if you have the right partner.

Here is what UAE eInvoicing means specifically for SAP Business One users, and what you need to do before October.

What changes for your SAP Business One system

SAP Business One is a complete ERP platform and it handles your invoicing today. What it does not do natively is transmit those invoices to a UAE-approved Accredited Service Provider (ASP) in the structured format the mandate requires.

From 1 January 2027, every business invoice needs to be validated and transmitted through an ASP before it reaches your customer. For SAP B1 users, this requires a dedicated connector - a purpose-built integration that sits between your SAP system and your chosen ASP and handles the transmission automatically.

What stays the same: your invoicing process inside SAP B1. Your teams continue to raise invoices the same way they always have. What gets added: the connector running in the background, making your system compliant without changing how your finance team works.

How the connector works with SAP Business One

The connector plugs into your existing SAP B1 environment. Once it is configured and tested, the compliance process is invisible to your finance team. They raise an invoice in SAP B1, the connector formats and transmits it to the ASP, the ASP validates it and passes it to the FTA, and your customer receives a compliant invoice.

There is no new system to learn. There is no parallel process to manage. For the end user, nothing changes.

SEIDOR has built a dedicated UAE eInvoicing connector for SAP Business One, tested with leading ASPs, and is currently running live pilot implementations with UAE-based B1 customers.

What a typical implementation looks like

For SAP Business One, the implementation process is clean and well-defined. A typical project runs as follows:

• Week 1: Kick-off, system assessment, ASP confirmation
• Week 2: Connector configuration and initial setup
• Week 3: Testing and validation in a sandbox environment
• Week 4: Go-live and post-implementation support

Four weeks from start to finish. Your business does not need to pause operations. The only people involved from your side are one or two people from your IT or finance team for sign-off and testing.

The risk of waiting

Waiting until September to start creates two risks. The first is capacity: as the October deadline approaches, implementation partners across the UAE will have full project queues. The businesses that engage now are securing slots before the rush.

The second risk is testing time. A rushed implementation with minimal testing is the worst outcome - you go live on 1 January with a system that has not been properly validated, and the first sign of a problem is a rejected invoice. At AED 2,500 per non-compliant invoice, that adds up quickly.

The businesses we are working with in pilot right now made the decision to move early precisely to avoid both of these risks. They will be live, tested, and confident well before anyone else is scrambling.

What to ask your SAP partner

Not every SAP implementation partner has built a UAE-specific eInvoicing connector for SAP Business One. Before you engage anyone, ask three questions:

1. Have you built and tested a connector specifically for UAE eInvoicing requirements on SAP Business One?
2. How many live implementations have you completed or are currently running in the UAE?
3. What does your post-go-live support process look like?

SEIDOR has built a dedicated UAE eInvoicing connector for SAP Business One, is currently running live pilots with UAE customers, and completes implementations in four weeks with dedicated post-go-live support included as standard.

Book a free compliance assessment