Square and Xero Integration for Client Books 2026
Connect Square and Xero, then check sales, fees, refunds and clearing balances so the client’s deposits reconcile without duplicate transactions.
- Published
- Updated
Yes, Square and Xero integrate in Australia through the official connector built by Amaka. The Square Xero integration sends sales records into the client’s ledger, but the practice still needs to check the tax mapping and reconcile payouts. A bank deposit alone cannot show whether the sales and fees are correct.
Choose the Supported Connection
Use the official Square and Xero connection for the supported accounting handover. Xero identifies Amaka as the provider that built and supports it. This is a partner-operated connector, distinct from a custom automation or a manual CSV import.
Amaka’s setup guide lists Australia as a supported region and the connector as free for Square and Xero users. The client still pays for their Xero subscription and Square payment processing. Xero Cashbook is unsupported.
Xero’s connection guidance requires a plan with unlimited invoices and bills. Daily summaries consume those records even when the client sends few customer invoices themselves. Keep that requirement in the subscription decision before activating a daily import.
Have the client’s Square account owner authorise the Square connection. On Xero’s side, the connecting user needs the Standard or Administrator role and permission to edit connected apps. Xero’s app permissions explain that requirement. Confirm the selected organisation is the client’s trading entity before allowing access.
The usual output is a daily sales invoice for the preceding day. The connector also records payment information and processing fees. Amaka supports an individual invoice per Square order as an alternative. Choose one format before setting the import boundary. Adding Square as a payment service for Xero invoices is a separate choice from importing point-of-sale sales.
The practice remains responsible for account choices, GST treatment and reconciliation. Imported entries do not establish that the client’s original transaction was correctly recorded. A cash payment recorded in Square also needs its own cash-clearing reconciliation. It will not arrive in a card payout.
Map Sales, Fees and Tax Codes
Map each transaction type to the account that explains its economic purpose. Use the client’s chart of accounts and sample records, including a taxable sale, any GST-free sale and a refund. Record the mapping before switching the connection on.
Keep sales revenue separate from processing fees. Use the Square Balance clearing account for card takings awaiting settlement. Amaka’s default setup creates that account, while advanced setup allows custom sales and payment mapping. Preserve separate handling for cash, gift cards and tips where the client uses them.
Confirm the client’s GST registration and the tax treatment of each sale category. Match the refund’s tax treatment to the original sale. Use the fee documentation to determine its GST treatment independently. Applying the sales tax code to every fee or payment movement can distort the client’s BAS.
Set the sync start date immediately after the last complete period already recorded in Xero. Keep a copy of the final old import and the first proposed new period. If the client already has an importer, allocate a clear end boundary to it before starting Amaka.
For an existing Xero invoice paid through Square, inspect how the payment is applied before importing the same sale again. A daily summary and an individual customer invoice must not both recognise the same revenue. Retain the transaction references that connect the original invoice to its payment.
The bank feed needs a different treatment from the sales import. The correct action is to match the net deposit to the connector’s payout transfer. Coding that deposit to sales creates revenue a second time. Amaka’s bank-feed reconciliation guide describes the transfer match through Square Balance.
Check a Complete Settlement
Check a complete payout from the Square source records through to the bank statement. Use the payout’s included transactions, because a sales day and a settlement period need not contain the same transactions.
The following fictional example assumes a zero opening clearing balance and one payout containing all the listed activity. It illustrates the reconciliation arithmetic, not a Square fee rate or a prescribed journal format.
| Activity | Effect on Square Balance | Evidence to match |
|---|---|---|
| Card sales recorded in the sales summary | $1,100 increase | Square sales and payment records |
| Refund included in the same payout | $110 decrease | Original sale and refund record |
| Processing fee withheld | $20 decrease | Square fee record and imported fee entry |
| Net transfer to the trading bank | $970 decrease | Square payout and bank statement |
| Closing balance for this complete payout | $0 | Clearing account transaction detail |
The expected deposit is $1,100 less $110 less $20, which equals $970. Confirm the sales entry and refund reach the intended revenue accounts. Check their tax lines separately from the fee entry. Then match the $970 bank receipt to the existing transfer, without creating another sale or fee.
A zero balance is expected for this complete fictional payout. A real clearing account can retain unsettled takings. Explain the balance using identified outstanding transactions instead of posting an adjustment simply to make it zero.
Diagnose the Difference Before Changing Records
If sales are missing, inspect the scheduled start boundary and sync history first. A connection started today normally produces its first daily entries on the following day. Then compare the selected Square location and Xero organisation with the source records.
If the bank deposit is missing, inspect the payout record before reimporting sales. Establish whether Square has released the payout and which bank account received it. A delayed deposit and a failed sales import require different repairs.
If the deposit is smaller than the apparent sales total, compare its refunds and withheld fees with the imported entries. Also inspect payment types. Amaka’s discrepancy guidance identifies incorrectly tagged payments and unrecorded refunds as reconciliation causes.
If Square Balance stays uncleared, work from the oldest unmatched amount. Look for an unmatched payout transfer, an omitted refund or an overlapping import. Compare each candidate with source transaction references before correcting it.
Before a repair, retain the Square sales, refund, fee and payout exports, the Xero entries and the connector settings. Record the affected range and the intended correction. Prefer switching the integration off temporarily to deleting its configuration. Amaka documents both controls, and warns that editing or deleting Square Balance can cause sync failure.
Stopping the connection does not complete the accounting correction. Review the entries already imported and document any reversals or replacements separately. A backsync can overlap existing records, so define its exact range before running it. Resume the schedule only after the repaired payout matches and the remaining clearing balance has an explanation.
One client form. One finished return.
Your client completes one guided form. Tax Genie checks it, chases mistakes and sends the details to your engagement letter and tax software.
Made for Australian accounting firms