Yes. A business can retain Xero for accounting and use a connected operations platform for detailed operational workflows when a supported connection fits the requirement. Agree which product owns contacts, invoices, bills, payments, and operational records; then define transfer direction, timing, mappings, and exception review.
Xero may already serve the accounting team well while the rest of the business struggles with purchasing, stock, project, or production information. In that situation, the decision is not simply “keep or replace Xero.” It is how to strengthen operations while preserving a reliable accounting boundary.
Keep operational and accounting responsibilities clear
Operational records explain what the business is doing: what was requested, ordered, received, reserved, issued, completed, invoiced, and paid. Accounting records the financial effect under the business's policies and reporting requirements.
A connected setup can let each product handle its agreed responsibility. The connection should preserve enough reference and status to trace the relationship without copying every operational event into the ledger.
Agree which product owns each record
Decide where contacts, invoices, bills, payments, credits, taxes, currencies, and account mappings are created and maintained. Decide separately where purchasing, inventory, projects, bills of materials, builds, and detailed operational approvals live.
When ownership is unclear, users may edit the same information in both places. This creates conflicts that no automated connection can resolve safely.
Define the connection before implementation
- Scope: the exact records and statuses covered.
- Direction: which product sends and which receives.
- Timing: immediate, scheduled, or initiated after review.
- Mapping: accounts, taxes, currencies, contacts, and references.
- Exceptions: who reviews rejected, missing, or conflicting information.
- Corrections: how changes and cancellations return to the owning product.
Confirm the exact Xero organization and requirements in scope. Product names alone do not define the behavior of a particular connection.
Keep operational detail where it belongs
A warehouse reservation, project-material requirement, production issue, or supplier-quotation comparison may affect future accounting, but it is not necessarily an accounting record. Forcing all operational detail into the ledger can add noise without improving control.
Keep the detail in the system that governs the workflow. Transfer the accepted accounting record and the references needed to explain its origin.
Compare the full operating model
Compare three paths: continue the present setup, connect Xero to an operations platform, or adopt a platform with native accounting. Score each against real workflows, accounting requirements, migration effort, exception handling, reporting, training, and support.
Test a partial receipt, revised bill, credit, foreign-currency transaction, payment, and rejected transfer. A polished happy path does not show how the setup behaves when real records differ.
Xero and Datum
Datum can use Datum Accounting as its native ledger or retain Xero through an agreed supported connection. Datum manages the connected operational workflows while the implementation scope defines which approved records connect to Xero.
Review ownership, supported records, mapping, visible status, errors, retries, and history for the proposed setup. If native accounting is preferred, treat that as an accounting migration with its own preparation and cutover plan.
Related questions
Does an operations platform duplicate Xero?
It should not. The operational platform manages detailed work such as purchasing, inventory, projects, or production, while Xero can retain the agreed accounting responsibilities.
What information should move to Xero?
Only the records required by the supported accounting process and agreed implementation. Define document status, accounts, taxes, currencies, contacts, references, and corrections explicitly.
How should differences be reviewed?
Use visible status and exception handling. A user should be able to see what transferred, what failed, why it failed, and what must be corrected before a safe retry.
Is connected accounting always the best path?
No. It is one option. Compare it with the current setup and native accounting based on workflow fit, control, migration effort, reporting, and ongoing support.