Connectors
However your customers keep their books.
Onboarding a business to an access point fails on integration far more often than on compliance. A UAE client book spans SAP at the top and Tally or a spreadsheet at the bottom, and all of it has to work.
Available now
Three paths that work on day one.
These ship with the platform. Nothing here is a roadmap item.
REST API
Available nowCreate, validate, send and track invoices directly. OAuth2 client-credentials, scoped service accounts.
Webhooks
Available nowSigned, retried delivery of every status change to your own endpoint, with a delivery log and replay.
Dashboard entry
Available nowFor customers with no system to integrate. They raise invoices in the console you give them.
ERP connectors
Named systems, built per engagement.
We build these against your customer's actual instance rather than shipping a generic adapter, because two SAP deployments rarely export the same thing the same way.
SAP
Built on requestS/4HANA and ECC
Microsoft Dynamics 365
Built on requestBusiness Central and F&O
Oracle NetSuite
Built on requestSuiteScript integration
Odoo
Built on requestCommunity and Enterprise
Zoho Books
Built on requestVia the Zoho API
Tally
Built on requestWidely used across UAE SMEs
QuickBooks
Built on requestOnline and Desktop
Xero
Built on requestVia the Xero accounting API
Custom / in-house
Built on requestAnything with an export or a database we can read
To be exact about what “built on request” means: these are scoped as work, not sold as features you switch on. We agree the data mapping with the customer, build the connector, and maintain it as their ERP changes. What makes that quick rather than open-ended is that everything underneath it is already built and the same for every connector: validation, transport, reporting, retries.
Build your own
Or your customers write it themselves.
Some of your larger customers will have their own engineering teams and will prefer to own the integration. That should be a supported path, not a special case.
What they get
- Scoped service-account credentials, issued from their own console
- A REST API for the full invoice lifecycle
- Signed webhooks for every status change, with delivery logs and replay
- A sandbox that behaves identically but never touches the live network
What you get
Self-serve integration is the difference between onboarding scaling with your headcount and onboarding scaling with your customer count. Every customer who integrates themselves is one you did not have to staff.
Tell us which ERPs your clients run.
That list is usually the fastest way to scope an engagement, and it tells us more than a requirements document would.