Give support a safe path for unresolved Xero operations

Explain the operation states

Document ready, confirmed, rejected and outcome-unknown states with concrete examples. Show how retries relate to one business operation.

Link the local document, trusted connection and provider resource mapping where known. Keep tokens and unnecessary payloads outside the support view.

The operator should be able to distinguish a request never sent from one whose external result remains uncertain.

Provide a read-first investigation

Show the supported way to inspect the correct organisation and resource. Explain the evidence required to confirm a missing mapping.

Include an ambiguous case where the operator must stop and request review. A runbook that always ends by sending another create request encourages duplicates.

Name the business owner who can decide how to handle legitimate differences or accounting-state questions.

For a synthetic lost-response case, the local ledger has an operation ID and intended invoice details but no Xero resource mapping. The support operator uses the correct connected organisation to inspect candidate records. Matching only the amount is insufficient because several invoices can legitimately share it.

If a confirmed provider identifier can be established through the application's recorded request evidence, repair the mapping through the controlled action. If the evidence remains ambiguous, leave the operation unresolved and involve the business owner. A new create request is not an investigation tool.

Hand over retry and repair authority

Separate safe transport retry, local mapping repair and a new business mutation. Give each the appropriate access and audit trail.

Explain the provider idempotency boundary and why the application ledger remains necessary after it. Avoid a procedure based on indefinite reuse of a transport key.

Record how disconnected access and delayed jobs are resumed under the application's authority policy.

Rehearse one uncertain outcome

Have the receiving team investigate a synthetic lost-response case, identify the existing provider document and complete the local mapping through the controlled path.

Then present two plausible candidates and confirm that the team uses the review route instead of guessing.

Keep ownership current as new organisations and document types are added. The handover is successful when support can recover known outcomes, preserve uncertainty honestly and involve the right person before another financial effect is created.