Contact import
Xero → Orderverse
Contacts are synced and linked to Orderverse customers. A mapped Xero contact is required before invoice push.
Bring Xero contacts, items and tax rates into the ordering workflow. Collect the buyer's structured order in Orderverse, prepare the invoice, then send an eligible draft to Xero through a traceable background job.
Invoice push
INV-1048 · Harbour View Café
Preflight checks
Contact mapping
Xero contact linked
Item mapping
6 invoice lines linked
Tax mapping
All tax types resolved
Freight
Final amount confirmed
From
Orderverse
Create as
Xero Draft
One order, clear system boundaries
The integration does not turn Xero into a buyer portal. Xero remains the accounting source while Orderverse handles the customer ordering experience, order review and invoice preparation.
Xero
Accounting master data
Orderverse
Mapped ordering records
Buyer
Prices, units & quantities
Orderverse
Submitted order snapshot
Orderverse
Mapping preflight
Xero
Linked accounting record
Tax rates are also imported and mapped before invoice push. The arrows show data responsibility, not an immediate real-time transaction.
Clear ownership prevents the integration from becoming a second, conflicting copy of your accounting records.
Contact import
Xero → Orderverse
Contacts are synced and linked to Orderverse customers. A mapped Xero contact is required before invoice push.
Item & tax setup
Xero → Orderverse
Items and tax rates are imported. Xero tax types must be mapped to local tax codes before invoice operations.
Buyer pricing
Orderverse
Customer price groups, selling units and current order settings are resolved when the buyer orders.
Submitted order
Orderverse
The order keeps the submitted products, quantities, units and price snapshot for review.
Invoice preparation
Orderverse
Your team creates the local invoice and resolves contact, item, tax and freight checks before sending.
Accounting invoice
Xero
A successful push creates and links an ACCREC draft invoice. Accounting approval continues in Xero.
| Stage | System boundary | What happens |
|---|---|---|
| Contact import | Xero → Orderverse | Contacts are synced and linked to Orderverse customers. A mapped Xero contact is required before invoice push. |
| Item & tax setup | Xero → Orderverse | Items and tax rates are imported. Xero tax types must be mapped to local tax codes before invoice operations. |
| Buyer pricing | Orderverse | Customer price groups, selling units and current order settings are resolved when the buyer orders. |
| Submitted order | Orderverse | The order keeps the submitted products, quantities, units and price snapshot for review. |
| Invoice preparation | Orderverse | Your team creates the local invoice and resolves contact, item, tax and freight checks before sending. |
| Accounting invoice | Xero | A successful push creates and links an ACCREC draft invoice. Accounting approval continues in Xero. |
Set up the dependency chain
Invoice push stays blocked until contacts, items and tax rates are synced, and every required tax type is mapped. This preflight prevents an incomplete invoice from quietly entering the accounting system.

Current integration scope
A useful integration is explicit about its edges. These are the current implementation boundaries verified against the API and background worker.
After preflight, the API places the job on a queue. A background Function builds the Xero payload, creates the draft, saves the Xero link and updates the local sync state.
Mappings and invoice eligibility checked
Background job accepted and processing
Transient upstream errors use bounded retries
Xero link saved, or a visible error recorded


Product proof
The interactive demo lets you place a buyer order, review it in the supplier workspace and simulate the transition to a Xero-ready invoice. It never contacts a real Xero organisation.
Run the invoice demoImplementation questions
Read the Xero integration overview or the invoice push guide for setup detail and recovery steps.
Product scope reviewed 14 August 2026
Yes. The current integration can pull Xero contacts into customer mappings and Xero items into product mappings. Tax rates are also pulled so each Xero tax type can be mapped to the correct local tax code.
A buyer order does not immediately create an accounting invoice. Your team first reviews the order and creates a local invoice. When that invoice passes the Xero preflight checks and you choose Push to Xero, Orderverse queues a draft invoice for background delivery.
The background worker retries transient network, rate-limit and service errors with a bounded retry policy. If the push still fails, the invoice records a failed sync state and error details so the issue can be corrected and retried.
Yes. Wholesale ordering and local order management do not require a Xero connection. Connect Xero when you want its contacts, items, tax mappings and draft invoice workflow.
Not in the current invoice-push workflow. Each eligible local invoice is pushed once and linked to its Xero counterpart. Orderverse can pull status updates for linked invoices, but it does not push later local edits over the existing Xero invoice.
See the handoff before connecting
Use fictional data to understand the buyer view, order review, invoice preparation and simulated accounting sync—without signing up or touching Xero.