Reconcile the commercial handoff
A Xero scope should define contact identity, invoice ownership and the payment status returned to operations. Include corrections and cancelled documents in acceptance scenarios, not just a successful first sync.
What we scope together
Review the installed edition and supported API, map customer and product identifiers, define tax and UoM handling, then agree invoice/payment references and recovery from sync failures. Availability depends on the scoped connector and acceptance tests.
Agree invoice and payment ownership
Identify the Xero organization, account/tax mappings and approved integration access. A first scope may focus on customer and commercial-document references that support the selected Ever workflow. Decide how posted invoices, credit adjustments and payment status are reconciled. Planned status does not imply a completed connection or automatic synchronization of all accounting data.
- 1Daily operations
- 2Ever Platform
- 3Ever Connect
- 4ERP / accounting system
- 5Review & reconcile
Connection scope and availability follow the published status.
What to bring to discovery
Provide the system/version, hosting model, relevant modules, record types, data owner and desired direction of flow. Describe one successful handoff and one exception, such as a duplicate or rejected record. We can then scope mapping, authorization, retries, reconciliation and acceptance. Share synthetic examples first; credentials and private exports belong in an agreed secure implementation process.
Your questions, answered
Does this page mean the connector is live?
No. Use the displayed status. Coming Soon, Planned and On Request entries require further implementation or scoping; they are not represented as accepted production connectors.
Can we request a custom connection now?
Yes. Request an integration with your workflow and system details. Ever Digital can define a bounded custom scope and acceptance plan; delivery depends on the agreed interface, access and implementation.