How often does Square data sync to Xero?

Square pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches Xero within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.

Will every Square record post to Xero automatically?

Not always. Within seconds of Square firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Xero email-in address and Xero drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.

How does Well match Square records to entries in Xero?

Every Square charge is scored against your open Xero sales invoices and existing customer records on customer name, amount, currency, and reference. Above 85% the charge collapses onto the right invoice and Square reconciliation builds the matched journal entry in Well's ledger, the ledger accounts mapped and the matched customer and payment pre-filled, ready for you to post to Xero. Between 55% and 85% the candidate list is queued for review with the alternative customers ranked.

Does Well handle multi-currency records between Square and Xero?

Square carries the original transaction currency on every record and Xero natively ledgers in multiple currencies. Well preserves the original amount, applies your Xero chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Xero, so the Xero entry you post keeps both sides of the trade.

Can I customise which Square fields are sent to Xero?

The default mapping covers every Square field your Xero chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields Xero does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in Xero is left exactly as it stands.

How does Well authenticate with Square and Xero?

Square's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Xero email-in address once it clears the matching threshold; Xero creates the draft record from it and you confirm and post it. Well holds no write credential to Xero. Tokens are encrypted at rest and in transit under TLS 1.3. Square and Xero together cover multiple regions; Well's storage region is configured per workspace.

Square to Xero

AvailableNative · SquareNative · Xero

Connect Square to Xero with Well

Skip the spreadsheet middle step: Square card payments, payouts, and refunds are matched in Well, then the matched PDFs land in Xero as draft bills ready for your review.

Connect both toolsView all integrations

Square

Source

The Square connection reads your Square account through the Square MCP server using OAuth.

Xero

Target

The Xero integration connects Well to your accounting platform for bidirectional data flow.

Why this pair

Square handles point-of-sale and online payments; Xero accepts emailed PDFs and creates draft bills via Hubdoc.

Connecting Square to Xero through Well matches each Square transaction inside its own ledger with Square location context, processing-fee breakdown, and bank-deposit context attached, then forwards the matched document to Xero's email-in. Square's MCP server pushes payout events to Well; Hubdoc creates the draft bill from the forwarded PDF, with Square location context surfaced for your team to apply the matching tracking category in Xero.

What Well does between Square and Xero

One-way: Square into Well into Xero
Sync mode: Real-time MCP push
Events arrive in seconds

Trigger from Square

7 events · pick one

Well engine·recipe·When a Square card payment is captured

Source

from payment · live webhook

Selkirk Imports

via Square

Payment

When a Square card payment is captured

ch_1q5nk · 22 Apr 2026€1,284.00

Extract

6 fields read from Square

6 fields read

CustomerSelkirk Imports
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordSelkirk Imports
Domainselkirk-imports.com
Tax idGB342765981
Sales journalVE · 2026

Confidence97%

<55% refused55–85% review≥85% auto-posts

Post

post as draft bills

Create a draft bill in Xero

auto-posted

posted

TypeBill
VendorSelkirk Imports
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Xero

Action in Xero

1 compatible with this trigger

Create a draft bill in Xero

Reconcile Square multi-currency charges to Xero entries.

01Featured

Resolve a Square sale to a Xero contact

Well reads a Square transaction and the contacts already in Xero, matches the buyer to one it recognises, and forwards the prepared document to your Xero email-in address.

Read Xero records before forwarding

Well reads the invoices and contacts already in Xero to check that a Square sale belongs to a known account, so the forwarded document lines up with what Xero holds.

Collapse a duplicate customer

A Square buyer that matches an existing Xero contact by company is resolved to that one record inside Well, so the forwarded document does not create a near-duplicate.

Keep the Square source attached

The originating Square transaction stays linked to the document forwarded to Xero, so each entry traces back to the sale behind it.

13 signals and actions across Square and Xero

When a Square card payment is captured
Captures successful card-present and card-not-present payments with currency, fees, and customer linkage. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
When a customer is created in Square
Pulls new customer records with name, email, and stored payment methods. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Company
When a Square refund is issued
Captures partial and full refunds with the originating payment id. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
When a Square payment includes a tip
Pulls the tip amount off the payment so it can be routed separately. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
When a Square customer is updated
Detects changes to a Square customer's name, email, or stored payment method and refreshes the company record. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Company
When a Square order is completed
Captures the completed Square order with its line items, taxes, and the payment that settled it. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Invoice
When a Square invoice is paid
Detects paid Square invoices with line items, applied discounts, and tax breakdown. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Invoice
When a Square dispute is opened
Captures chargebacks with the contested payment and reason code. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction
When a Square payout is sent to your bank
Detects the moment Square dispatches a payout batch toward your bank account. Forwarded to Xero's email-in via Hubdoc; Hubdoc extracts contact, dates, totals, and tax type into a draft bill.
Trigger·Transaction

Reference

Field mapping for Square → Xero

10 fields across 2 record types, open to see the full table.

Transaction fields

5 fields flow from Square into Xero.

Square field	Label		Xero field	Label
payment.amount_money.amount	Payment amount	→	Total	Amount
payment.amount_money.currency	Currency	→	CurrencyCode	Currency
payment.created_at	Charge date	→	Date	Transaction date
payment.note	Description	→	Reference	Reference
payment.id	Charge id	→	BankTransactionID	Bank line id

Invoice fields

5 fields flow from Square into Xero.

Square field	Label		Xero field	Label
invoice.invoice_number	Invoice number	→	InvoiceNumber	Invoice number
invoice.invoice_date	Issue date	→	Date	Bill date
invoice.due_date	Due date	→	DueDate	Due date
invoice.total_money.currency	Currency	→	CurrencyCode	Currency
invoice.primary_recipient.customer_id	Customer	→	Reference	Reference

Connect Square and Xero in three steps.

1
Connect Square
Click Connect with Square; Square's MCP server registers a Well client automatically. Square's MCP server registers a read-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
2
Map your accounts
Well discovers Square's card payments, invoices, refunds, customers, payouts, disputes, and inventory adjustments and the the Xero draft bills queue populated by Hubdoc. Match candidates are scored on counterparty name, amount, currency, and reference; you approve any that need a human eye and Well saves the rule for the next batch.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Xero
Click Connect with Xero; Well's OAuth proxy handles Xero authorisation through Dynamic Client Registration. Xero's MCP server registers a write-scoped Well client through DCR; no credential paste, no shared secret.
- AuthOAuth 2.0
- First syncup to an hour

How Square and Xero stay secure with Well

Well connects to Square through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Square secret; the server refreshes its own tokens on each session. Well's storage region is configured per workspace regardless of where Square and Xero host theirs.

MCP server authStorage region per workspaceGDPR-aligned

Scopes Well requestsmcp.squareup.com/sse

Read Square records
Scoped to card payments, invoices, refunds, customers, and related records. No access to anything else in your Square account.
granted
Deliver documents to your Xero inbox
Well forwards the extracted document to your Xero email-in address; Xero reads draft bills via email-in, with contact, dates, totals, and related records from it and you review and post. No write credential to Xero is requested.
granted
Modify or delete Square records
Not granted. Square is read-only on Well's side; the source of truth never moves.
refused
Read other workspaces' data
Encryption keys are per-workspace; another tenant's records are inaccessible by design.
refused

Disconnect any time from Well settings or Square’s admin panel.

Frequently asked questions about Square and Xero on Well

01How often does Square data sync to Xero?: Square pushes events to Well over its MCP server, so most records land within seconds of the underlying action. Each event is matched immediately and reaches Xero within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
02Will every Square record post to Xero automatically?: Not always. Within seconds of Square firing the event, Well scores the record on field completeness, counterparty strength, and policy fit. Above the 85% default auto-link threshold Well forwards the reconciled document to your Xero email-in address and Xero drafts the record from it for you to confirm. Between 55% and 85% the record waits in the review queue with the alternative matches ranked. Below the 55% default review threshold the record is refused and the candidate list kept so you can pin the right entry by hand.
03How does Well match Square records to entries in Xero?: Every Square charge is scored against your open Xero sales invoices and existing customer records on customer name, amount, currency, and reference. Above 85% the charge collapses onto the right invoice and Square reconciliation builds the matched journal entry in Well's ledger, the ledger accounts mapped and the matched customer and payment pre-filled, ready for you to post to Xero. Between 55% and 85% the candidate list is queued for review with the alternative customers ranked.
04Does Well handle multi-currency records between Square and Xero?: Square carries the original transaction currency on every record and Xero natively ledgers in multiple currencies. Well preserves the original amount, applies your Xero chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Xero, so the Xero entry you post keeps both sides of the trade.
05Can I customise which Square fields are sent to Xero?: The default mapping covers every Square field your Xero chart of accounts accepts (counterparty, amount, currency, reference, tax). From the integration settings page you can override mappings field-by-field, attach computed values from your connected data (GL code, project tag, tax bucket), or ignore fields Xero does not need. Custom mappings are versioned and apply only to records reconciled after the change, so anything you have already reviewed and posted in Xero is left exactly as it stands.
06How does Well authenticate with Square and Xero?: Square's MCP server handles authorisation directly; Well receives an access token through Dynamic Client Registration and never sees raw user credentials. For the delivery side, Well forwards the reconciled document to your Xero email-in address once it clears the matching threshold; Xero creates the draft record from it and you confirm and post it. Well holds no write credential to Xero. Tokens are encrypted at rest and in transit under TLS 1.3. Square and Xero together cover multiple regions; Well's storage region is configured per workspace.