How to Connect Square to Xero: A UK Guide for Retail & Hospitality

The cleanest way to connect Square to Xero is to post one daily sales summary per location — not every individual transaction — and reconcile Square's bank payout against a clearing account. That keeps your VAT correct, your card fees visible, and your Xero ledger free of thousands of tiny lines. Square's own native Xero integration does exactly this for simple setups; busier retail and hospitality businesses usually outgrow it and move to a dedicated app (Amaka, A2X, Synder) or a custom integration.

This guide covers what to sync, the gotchas that trip up UK shops and venues, and how to choose between native, app and custom.

What "good" looks like: the daily summary, not raw transactions

A busy site can process hundreds or thousands of card taps a day. You do not want each one as a separate line in Xero — it makes reconciliation painful and bloats your ledger. The correct pattern is a daily journal or sales invoice that summarises the day's trading:

• Gross sales, split by your Xero tracking categories or tax rates
• Card fees as a separate expense line
• Tips and gratuities as a liability (money you owe staff), not revenue
• Refunds and returns as negative lines
• The net amount Square will actually pay into your bank

That single summary should net to the payout Square deposits a working day or two later. When the payout lands in your Xero bank feed, you match it against the summary via a clearing account. Clean, auditable, and quick to reconcile.

The card-fees gotcha (and why your VAT can go wrong)

Square deducts its processing fee before paying you. A £100 sale might arrive as £98.25. If you only record the £98.25 that hits your bank, you have under-recorded both your gross sales and your VAT liability, and you've hidden the fee you paid.

Always record the full gross sale, then the Square fee as a separate cost. In the UK, card processing fees are an exempt financial service — they carry no VAT, so there's no input VAT to reclaim on them. Code the fee to a "Merchant/card fees" expense account on a No VAT (or Exempt) rate, not Standard 20%. Getting this wrong is one of the most common errors we see when fixing self-built Square–Xero links.

Tips, service charge and gratuities

Hospitality is where this gets sharp, because the treatment differs:

• Discretionary tips paid by card that you pass on to staff are generally not your turnover and are usually outside the scope of VAT — record them as a liability until paid out.
• A mandatory service charge is part of the supply and is subject to VAT at the rate of the items sold.

Square can capture both, but the native Xero sync may lump them together. If you run a venue, make sure tips land in a separate liability account and service charge flows through sales with the right VAT rate. Bear in mind the UK's Employment (Allocation of Tips) Act 2023, now in force: accurate tip records matter for compliance, not just bookkeeping.

Refunds, partial refunds and chargebacks

Refunds reduce both sales and output VAT in the period they occur. A same-day refund should net within that day's summary; a refund of an earlier sale should appear as a negative on the day it's issued. Watch for:

• Partial refunds — the VAT must reduce proportionally.
• Chargebacks and disputes — Square may claw funds back from a later payout, so a payout can be lower than the day's net sales. A properly set-up clearing account absorbs this.

Multi-location: the most common reason native isn't enough

If you run more than one site, the single biggest decision is keeping locations separate in Xero. Map each Square location to a Xero tracking category so you can see revenue, fees and margin per site. Square's native integration is geared to one location feeding one Xero org; multi-site retail and hospitality groups typically need an app (A2X and Amaka both handle multiple locations) or a custom integration that splits out per site and consolidates correctly.

Payout reconciliation: use a clearing account

This is the mechanism that makes everything balance.

1. The daily summary posts gross sales, fees, tips and refunds, with the net going to a "Square Clearing" account.
2. Square deposits the payout into your real bank a day or two later.
3. In the Xero bank feed, you match the payout to the clearing account — it should zero out.

If the clearing account doesn't return to zero, something's off: a missing fee, a chargeback, a tip handled wrongly, or a timing mismatch. It becomes your early-warning system rather than a month-end mystery.

Native vs app vs custom: how to choose

Option	Best for	Strengths	Limits
Square's native Xero app (free)	One location, simple VAT, low volume	Free, quick to set up, summary-based	Limited multi-location; less control over tips, fee and VAT mapping
Third-party app (Amaka, A2X, Synder)	Busy retail/hospitality, multi-site	Multi-location, tracking categories, configurable VAT and fees, daily summaries	Monthly subscription; still off-the-shelf logic
Custom integration	Groups, unusual VAT (mixed rates, margin schemes), POS + ecommerce + inventory	Exactly your rules, consolidates other systems, full control	Build cost; needs maintenance

Be honest with yourself first. If you're a single café or one shop on standard-rate VAT, the free native app — or a low-cost app such as Amaka — is almost certainly the right answer; don't pay for a custom build you don't need. Custom is worth it when you have multiple locations plus awkward VAT (mixed 0% and 20% retail lines, the second-hand margin scheme, deposits), or when Square is only one of several systems (ecommerce, inventory, bookings) that all need to reconcile together. As a rough guide, expect a custom build to run into the low-to-mid thousands of pounds and up depending on scope — always an indicative market range, never a quote until we've seen your setup.

Setup checklist

• Decide: summary-level posting (yes) over per-transaction (no).
• Create a Square Clearing bank account in Xero.
• Set up a card fees expense account on a No VAT/Exempt rate.
• Create a tips/gratuities liability account (hospitality).
• Map each location to a tracking category if multi-site.
• Confirm your VAT rates per product type before you go live — test one day end to end and check the clearing account hits zero.
• Reconcile the first week daily to catch mapping errors early.

Common mistakes to avoid

• Importing every transaction instead of a daily summary.
• Recording only the net deposit, hiding fees and understating VAT.
• Putting VAT on Square's card fees (they're exempt).
• Treating discretionary tips as revenue.
• One Xero org swallowing multiple locations with no tracking split.
• No clearing account, so chargebacks and timing gaps go unnoticed.

How APIwise can help

We're a UK, vendor-neutral API and integration consultancy. If the native Square–Xero app or an off-the-shelf tool fits, we'll tell you — and help you configure it correctly for UK VAT, tips and multi-location. If you've outgrown it (several sites, mixed VAT rates, or POS plus ecommerce and inventory to reconcile), our fixed-price Integration Health Check maps your data flows and hands you a costed plan. See our API integration, data integration and Xero integration specialist services, or get in touch.