Skip to content

Accounting & ERP

Xero.
Keep your ledger. Connect the floor.

Keep Xero for accounting while connecting invoices, contacts and agreed stock records.

Responsibilities

Agree where each record belongs.

Conceptual illustration: An accounts desk and warehouse shelf linked by a narrow channel carrying record tabs.

Keep your ledger responsibilities in Xero. Agree the tax treatment, payment ownership and stock accounting workflow with your finance team.

What flows where

Scope the records in each direction.

These are proposed flows for scoping, not a promise that every object or event is already supported.

Conceptual illustration: An active record tray, storage cartridge and archive drawer with a shared record marker.
Xero: records, direction and setup requirements
RecordFrom → toTriggerScope note
Contacts and customer recordsXero → OpsUIAgreed during scopingProposed flow. Account-level support must be confirmed.
Items, where stocked in XeroXero → OpsUIAgreed during scopingProposed flow. Account-level support must be confirmed.
Chart of accounts (read-only)Xero → OpsUIAgreed during scopingProposed flow. Account-level support must be confirmed.
Tax codesXero → OpsUIAgreed during scopingProposed flow. Account-level support must be confirmed.
Sales invoices on order fulfilmentOpsUI → XeroAgreed during scopingProposed flow. Account-level support must be confirmed.
Credit notes on returnsOpsUI → XeroAgreed during scopingProposed flow. Account-level support must be confirmed.
Payment status updatesOpsUI → XeroAgreed during scopingProposed flow. Account-level support must be confirmed.
Agreed inventory adjustmentsOpsUI → XeroAgreed during scopingProposed flow. Account-level support must be confirmed.

Set up the connection around your operation.

Conceptual illustration: A disconnected storage module, a second available module and records waiting for review.
  1. Confirm access

    Identify the Xero organisation, authorised access and relevant accounting settings.

  2. Agree the mapping

    Agree contacts, items, invoice, credit-note and stock-journal mappings.

  3. Test the handoff

    Reconcile sample transactions before approving the production handoff.

Questions about Xero.

Is Xero an ERP?

No. Xero is accounting software: invoicing, GST, payroll and basic stock tracking. An ERP runs the whole business: orders, multi-location inventory, warehouse picking, dispatch, returns, manufacturing and Procurement. Xero stops where operations begin. Most NZ businesses pair Xero with an ERP layer rather than replace it. The accountant keeps Xero, the ops team gets a real system. That is exactly what OpsUI is built for.

How does OpsUI integrate with Xero?

Bidirectional, event-driven sync against your Xero tenant. Customers, items, chart of accounts and tax codes flow from Xero into OpsUI. Sales invoices on order fulfilment, credit notes on returns, payment status updates, and inventory adjustments flow back into Xero. Built on the Xero REST API with webhook subscriptions. No iPaaS in the path. Wired into your tenant during onboarding rather than installed from an app marketplace.

Will I have to leave Xero to use OpsUI?

No, and you should not. Xero is excellent at GST, payroll and accountant workflow. We do not try to replace it. OpsUI handles the operations side: orders, inventory, picking, dispatch, returns. Invoices and inventory movements flow into Xero automatically; your bookkeeper keeps their Xero, your ops team gets a real ERP.

What will the OpsUI ↔ Xero sync cover?

Xero → OpsUI: customers, items (where stocked in Xero), chart of accounts (read-only) and tax codes. OpsUI → Xero: sales invoices on order fulfilment, credit notes on returns, payment status updates, and inventory adjustments to COGS / inventory accounts. Bidirectional, event-driven (no nightly batch), built on the Xero REST API with webhook handling.

How is this different from Cin7, Unleashed or DEAR / Cin7 Core?

Compare the required stock and warehouse workflows with the capabilities of your current plan. Bin locations, receiving exceptions, picking, dispatch and returns are more useful fit criteria than a fixed SKU or order-volume threshold.

Can Xero handle inventory?

Compare the required stock and warehouse workflows with the capabilities of your current plan. Bin locations, receiving exceptions, picking, dispatch and returns are more useful fit criteria than a fixed SKU or order-volume threshold.

Does Xero have a warehouse management system (WMS)?

No. Xero does not include WMS functionality: no bin locations, picking workflows, dispatch routing, cycle counting, or scanner support. Xero focuses on the financial side of inventory (cost, on-hand quantity) and leaves the operational side (where it is, how to pick it, how to ship it) to a separate system. OpsUI's Warehouse module is built for exactly that gap.

Does Xero have a CRM?

Xero stores contacts but it is not a CRM. There is no sales pipeline, opportunity tracking, deal stages, lead scoring, or activity timeline. Xero contacts are accounting records, the person you invoice, not customer relationship records. Most ANZ businesses that need real CRM pair Xero with HubSpot, Salesforce, Pipedrive, or an integrated CRM module like OpsUI's.

What is the best WMS or inventory software that works with Xero in New Zealand?

It depends on how operational you are. For light stock tracking, a Xero inventory add-on can be enough. For real warehouse work, such as barcode picking, multi-location bins, batch / lot / expiry tracking, wave picking and NZ Couriers and NZ Post dispatch, you want a WMS layer that syncs to Xero rather than a finance bolt-on. OpsUI is built for that: keep Xero for GST, run the warehouse in OpsUI, with carrier labels and tracking in the same product. Modules from NZ$299/month.

Your next step

Bring your system. Map the connection.

Share the account or version you use, the records that matter and the exceptions your team needs to handle.

Back to all integrations