Reconciliation and certified evidence · How-to guide

Run a dry-run Xero reconciliation before posting

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Audience: Administrators, finance staff and authorised integration operatorsPermission: ReconcileModule v1.0.0

Jump to steps

Where to goXero Accounting Automation → Reconciliation

Before you startConfirm the intended tenant, remote account or invoice context, and your Reconcile access. Keep credentials and tokens out of screenshots, tickets and exported evidence. If a previous write may have reached an external service, verify remote state before retrying.

What this guide helps you do

Detailed client guidance covering run a dry-run Xero reconciliation before posting, including prerequisites, exact controls, verification evidence, failure boundaries and safe recovery steps for the shipped Xero connector. This article is intentionally scoped to the behaviour enforced or exposed by the supplied module and does not treat provider marketing features as implemented integration capabilities.

How it works

The connector keeps native CRM records authoritative while mapping verified Contact, ACCREC Invoice and Payment evidence in Xero. Queue, exception, API, reconciliation and compliance records are separate evidence layers, so each material action should be verified at both the native and remote sides.

Follow these steps

Open Xero Accounting Automation → Reconciliation.
Confirm you are in the intended tenant and connected organisation and that your role has the required Reconcile access.
Select the intended native invoices and required bank/payment context.
Use dry run first when testing a match or unfamiliar dataset.
Review proposed amounts, references and match-confidence values.
For a live run, submit once and wait for mandatory remote verification.
Open the run result, evidence PDF/history and any resulting native payment before closing the task.

Settings to check

This guide’s focusDetailed client guidance covering run a dry-run Xero reconciliation before posting, including prerequisites, exact controls, verification evidence, failure boundaries and safe recovery steps for the shipped Xero connector.

Dry runA dry run calculates the proposed matches without certifying money as posted.

ConfidenceThe default minimum match confidence is 98%. A lower score must not be presented as a passed match.

Remote proofRemote verification is mandatory for live reconciliation and is forced on server-side.

Native paymentWhen configured, the native invoice payment is created only after the remote allocation is verified.

EvidenceReconciliation can generate a compact PDF with SHA-256 integrity evidence and can email completion results.

RetentionEvidence PDF retention defaults to 0 days, meaning indefinite storage unless an organisation retention policy sets a bounded period.

Check it worked

Reopen the native record and the relevant integration history/register. Confirm the stored remote accounting identifier, exact amount/status, latest timestamps and the expected audit or reconciliation evidence. If the provider-side state cannot be independently verified, keep the task unresolved and use the controlled exception or troubleshooting flow.

Frequently asked questions

What should I verify before I trust the result?Verify the native record, the mapped remote record, the stored remote identifier, the current status/amount and the audit or history evidence. A success message alone is not the accounting evidence.

Should I press the action again after a timeout?Not until you have checked the remote accounting service and the Exceptions/API evidence. A timeout can occur after the remote side accepted a non-idempotent write, so a blind retry can create a duplicate.

Does the connector replace the native CRM record?No. Native clients, invoices and payments remain the operational source records. The connector records mappings, remote evidence and controlled reconciliation around them.

What should I include in a support case?Include the native record ID, remote ID if known, date/time, action, exact visible error and request/audit identifier. Never send client secrets, access tokens, refresh tokens or authorization headers.

Technical basis for this guidance

This guide was checked against the supplied module code paths: controllers/Xero_accounting_automation.php; models/Xero_accounting_automation_model.php; libraries/Xero_api_client.php; libraries/Xero_reconciliation_service.php; libraries/Xero_document_import_service.php; views/admin; install.php; docs/FEATURE_MATRIX.md. It documents shipped behaviour, validation, routes and evidence controls; it does not claim successful live provider network calls from offline inspection.

Common mistakes to avoid

Work in the intended tenant and remote accounting/business context.
Do not paste credentials, access tokens, refresh tokens or private keys into tickets or notes.
Do not bypass a missing mapping, validation error, permission gate, duplicate check or remote-verification requirement.
Do not repeat a non-idempotent write until you know whether the previous request reached the remote service.
Keep native record, remote evidence and audit/history state aligned before closing the task.

Provider and accounting boundaryThe integration fails closed when required mapping, remote identity, validation, concurrency or verification evidence is missing. Do not bypass a blocker by editing unrelated records or repeating an uncertain write.

Browse connected topics: Reconciliation and certified evidence Xero Accounting Automation Accounting & Bookkeeping

Was this guide useful?Your response is stored only in this browser.

Run a dry-run Xero reconciliation before posting

What this guide helps you do

How it works

Follow these steps

Settings to check

Check it worked

Frequently asked questions

Technical basis for this guidance

Common mistakes to avoid

Related guides