Compute
Xero Finance Sync mapping
Map a Compute customer payable record to Xero ACCPAY, review the dry run, and reconcile the returned object safely.
On this page
The Xero object
For a customer-payable flow, Finance Sync maps the bill owed to Lithi to Xero ACCPAY. This is a direction-specific recipe, not a Lithi-owned Xero connector.
The mapping names the system edition, object kind, accounting treatment, recipe version, and safe external reference.
Confirm finance facts
Inspect the authorized organization, supplier record, duplicate check, currency, invoice period, purchase-order policy, and destination.
Each fact keeps its source, freshness, and conflict state. Never guess tax treatment, legal entity, ledger account, project, cost centre, or approver.
Plan and approve
Finance Sync inspects the source, plans a dry run, shows the exact ACCPAY object, receives entitled approval, applies idempotently, and reads it back.
Review the supplier, dates, currency, lines, allocations, and safe reference. Stop when the Xero edition or accounting treatment is unclear.
Keep statuses separate
Xero Paid is an annotation only. It cannot settle a Lithi invoice. Authoritative Lithi invoice read-back remains the customer payment authority.
If the returned object differs from the plan, keep the evidence and reconcile the mismatch. Do not force a second write.