Xero Australia: an ABA file does not prove the bank paid

A downloaded Xero payment file is not evidence that the bank executed the payment. For an Australian batch, separate the Xero bill status, exported file and bank records. The official batch-payment guide describes export and bank upload as separate steps; fully covered bills can already appear as Paid in Xero.

This guide is for someone reviewing an existing batch, not creating or submitting one. Keep “ABA file generated”, “file submitted” and “bank movement observed” as separate claims that need their own evidence.

Read the existing batch without initiating payment

1. Obtain the existing batch transaction or its printed PDF through your authorised Xero access. Record the batch date, bank account, total, bill identities and payment references shown.
2. Retain the already exported file’s identity, if it exists, without editing, regenerating or uploading it for this review.
3. Ask the authorised bank operator for the relevant submission or execution evidence if it is needed and available. Do not share banking passwords or treat a file on disk as the operator’s confirmation.
4. Compare the actual bank statement with the batch at the correct aggregation level. Keep missing execution evidence open.

Xero documents that multiple bills for one supplier are combined in the payment file. Its Australian batch route is limited to the organisation’s base currency, and payroll ABA files follow the pay-run route. Do not interpret this bills example as a payroll-file instruction.

Compare bills, supplier amounts and the bank separately

A synthetic batch contains two bills for supplier A, $80 and $20, and one for supplier B, $50. The batch total is $150; the supplier-level amounts are $100 and $50. That difference in row counts does not prove a bill was lost.

Suppose all three bills show Paid in Xero and the file is in Downloads. The missing evidence is still the bank step. Recreating the batch because there is no statement line could create a second instruction rather than resolve the first one’s status.

Build a status register with evidence, not assumed transitions

Use separate columns for the existing Xero batch, exported-file identity, observed bank submission/authorisation evidence and posted statement reference. Record a state only when the supporting record establishes it. “Unknown” is a valid result when the operator has not supplied evidence.

After an actual payment, Xero’s guide treats reconciliation against the bank statement as a later step. The statement may reflect the batch at an aggregation level that differs from the bills. Investigate the observed structure instead of forcing every bill to have a separate bank line.

The completed review should show the bill-to-supplier grouping and the strongest bank evidence actually available, with unresolved states preserved. It does not certify an ABA file, establish successful upload or prove the suppliers received funds. No Xero organisation, payment file or bank action was executed for this documentary workflow.

Synthetic review case. The values are teaching data, not a vendor export or an import file.

For a bank source available only as PDF, download LocalExtract. It processes one PDF locally into date,description,amount CSV; review and adapt those rows for the actual destination.

Related guide: Import bank statements into Xero: CSV mapping and review.

Documentation for the added task checked October 16, 2026.