How often does Square data sync to Melio?

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 Melio within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.

Will every Square record post to Melio 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 Melio email-in address and Melio 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 Melio?

Well scores every candidate match between Square records and existing Melio entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Melio updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.

What happens to historical Square data when I first connect to Melio?

Square exposes the last two years through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Melio ledger, and re-running the backfill is safe because Well tracks the Square record IDs and updates existing Melio entries instead of duplicating them.

What happens if a Square record fails to post to Melio?

When a record fails to post to Melio (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Square record. Nothing silently drops.

How does Well authenticate with Square and Melio?

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 Melio email-in address once it clears the matching threshold; Melio creates the draft record from it and you confirm and post it. Well holds no write credential to Melio. Tokens are encrypted at rest and in transit under TLS 1.3. Square and Melio together cover multiple regions; Well's storage region is configured per workspace.

Square to Melio

AvailableNative · SquareNative · Melio

Connect Square to Melio with Well

Each Square settlement is forwarded to Melio as a bill with the chargeback window tracked inside Well, so AP knows when the funds are unrecoverable before scheduling.

Connect both toolsView all integrations

Square

Source

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

Melio

Target

The Melio connection delivers extracted bills into Melio through its Pay Bills email address.

Why this pair

Square handles incoming card payments while Melio handles outgoing vendor payments.

Connecting Square to Melio through Well surfaces every Square payout alongside the Melio scheduled-payment queue, so treasury sees yesterday's sales and today's bills in the same view. Square's MCP server pushes payout events to Well; Melio's Smart Bill Capture creates the bill from the PDF Well forwards so you can schedule the payment at the configured cadence.

What Well does between Square and Melio

One-way: Square into Well into Melio
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

Atlas Robotics SAS

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

CustomerAtlas Robotics SAS
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordAtlas Robotics SAS
Domainatlasrobotics.fr
Tax idFR21987654321
Sales journalVE · 2026

Confidence97%

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

Post

schedule as bills

Create a bill in your Melio inbox

auto-posted

posted

TypeBill
VendorAtlas Robotics SAS
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Melio

Action in Melio

1 compatible with this trigger

Create a bill in your Melio inbox

Bridge Square payouts to Melio reimbursements.

01Featured

Bridge merchant payouts to vendor reimbursements

Square payout batches are joined to the reimbursement records inside Well by date and total. The per-line breakdown becomes individual documents forwarded to Melio, so a payout that covers 30 reimbursements arrives as 30 entries you can confirm one by one, not one lump sum to chase down later.

Detect failed disbursements

A failed Square disbursement triggers a flag inside Well: the linked vendor payment is marked needs reschedule, the Square failure code is attached, and the workspace owner is notified with the candidate next-payment date based on your standard reschedule policy.

Tie chargebacks to the originating vendor bill

Chargebacks landing in Square are traced back to the originating vendor bill inside Well by reference and amount. The chargeback context is forwarded to Melio on the affected document, so AP can decide whether to reschedule a corrected payment or write off the loss with the original Square reason in hand.

Settle expense reimbursements weekly

Approved expense reimbursements are batched inside Well into a weekly Square disbursement run, paid in a single ACH window, and matched on settlement. The per-claim audit trail stays intact inside Well and on the matched documents forwarded to Melio.

13 signals and actions across Square and Melio

When a Square card payment is captured
Captures successful card-present and card-not-present payments with currency, fees, and customer linkage.
Trigger·Transaction
When a Square payout is sent to your bank
Detects the moment Square dispatches a payout batch toward your bank account.
Trigger·Transaction
When a Square refund is issued
Captures partial and full refunds with the originating payment id.
Trigger·Transaction
When a Square payment includes a tip
Pulls the tip amount off the payment so it can be routed separately.
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.
Trigger·Company
When a Square invoice is paid
Detects paid Square invoices with line items, applied discounts, and tax breakdown.
Trigger·Invoice
When a Square order is completed
Captures the completed Square order with its line items, taxes, and the payment that settled it.
Trigger·Invoice
When a customer is created in Square
Pulls new customer records with name, email, and stored payment methods.
Trigger·Company
When a Square dispute is opened
Captures chargebacks with the contested payment and reason code.
Trigger·Transaction

Reference

Field mapping for Square → Melio

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

Transaction fields

5 fields flow from Square into Melio.

Square field	Label		Melio field	Label
payment.amount_money.amount	Payment amount	→	amount	Amount
payment.amount_money.currency	Currency	→	currency	Currency
payment.created_at	Charge date	→	scheduled_for	Payment date
payment.note	Description	→	reference	Reference
payment.id	Charge id	→	payment_id	Payment id

Invoice fields

4 fields flow from Square into Melio.

Square field	Label		Melio field	Label
invoice.invoice_number	Invoice number	→	bill_number	Bill number
invoice.due_date	Due date	→	due_date	Due date
invoice.total_money.currency	Currency	→	currency	Currency
invoice.primary_recipient.customer_id	Customer	→	bill_id	Bill id

Connect Square and Melio 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 Melio Bills Inbox awaiting payment scheduling. Each payout is paired to its scheduled vendor payment by date and total; failed transfers reverse the linked payment automatically so the schedule self-corrects.
- Auto-post above85% confidence
- Overridemanual anytime
3
Connect Melio
In Melio, open Settings > Integrations and generate an API token with payment-write scope. Paste the key into Well; Melio's discovery endpoints are reached over TLS 1.3 and the secret is never echoed in the UI.
- AuthConnect
- First sync~10 min

How Square and Melio 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 Melio 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 Melio inbox
Well forwards the extracted document to your Melio email-in address; Melio reads bills via email-in at @invoicesmelio.com, with vendor, amount, and due date populated by Smart Bill Capture from it and you review and post. No write credential to Melio 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 Melio on Well

01How often does Square data sync to Melio?: 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 Melio within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
02Will every Square record post to Melio 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 Melio email-in address and Melio 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 Melio?: Well scores every candidate match between Square records and existing Melio entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Melio updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.
04What happens to historical Square data when I first connect to Melio?: Square exposes the last two years through its API on a connected account. The window Well actually pulls is configurable from the integration settings page; each record is matched against your existing Melio ledger, and re-running the backfill is safe because Well tracks the Square record IDs and updates existing Melio entries instead of duplicating them.
05What happens if a Square record fails to post to Melio?: When a record fails to post to Melio (validation rule, missing field, transient 5xx), Well retries automatically with backoff. Auth failures short-circuit the retry loop and notify the workspace owner; schema rejections are kept on the integration status page with a one-click retry-after-fix action pointing back at the original Square record. Nothing silently drops.
06How does Well authenticate with Square and Melio?: 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 Melio email-in address once it clears the matching threshold; Melio creates the draft record from it and you confirm and post it. Well holds no write credential to Melio. Tokens are encrypted at rest and in transit under TLS 1.3. Square and Melio together cover multiple regions; Well's storage region is configured per workspace.