integration
Xero integration for operations
Connect Xero to your warehouse and operations systems. When an invoice is paid in Xero, OnDraft passes it on to the systems that need to act. Built and run in the UK.
Xero is often the system of record for cash. OnDraft listens for invoice payment events and forwards enriched payloads to operational systems such as Logistaas.
What happens when a Xero invoice is paid
A customer pays an invoice and Xero records the payment. OnDraft picks up that payment event.
We add the details the next system needs, then pass it on to the operations system, for example Logistaas.
Before anything is recorded, we check whether that payment is already there. If it is, we treat it as done. A payment never gets recorded twice, even if Xero sends the same event again.
Taking payment first: branded Pay Now pages
If you want the customer to pay before anything else happens, a branded Pay Now page can collect it. It is registered as a Xero Payment Service, so the receipt lands in Xero and the flow above takes over.
When a Xero integration is worth building
- Someone re-keys payments from Xero into another system.
- Orders sit on hold until someone checks Xero to see if they have been paid.
- At month end Xero and the warehouse disagree, and nobody is sure which one is right.
If any of those happen every week, it is worth a conversation. Give me a shout.
Shipped example
The indexed flagship is Xero → Logistaas. It covers payment receipt through duplicate-safe create_payment.
Not claimed here
- Two-way stock sync to Xero
- Automated invoice creation for every WMS movement
- Partner or certification status beyond what Xero and Logistaas APIs support in your tenant
Ask via Contact if your Xero tenant needs scoping against a different destination.