What happens to historical Square data when I first connect to Bill.com?

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 Bill.com ledger, and re-running the backfill is safe because Well tracks the Square record IDs and updates existing Bill.com entries instead of duplicating them.

Does Well handle multi-currency records between Square and Bill.com?

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

How does Well prevent duplicates when posting Square records to Bill.com?

Square sends each event with a stable resource ID that Well tracks against the Bill.com ledger. Webhook replays (which Square can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Bill.com entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.

Can I customise which Square fields are sent to Bill.com?

The default mapping connects each Square record to the Bill.com bill shape (vendor, amount, due date, approval policy). Settings let you override the vendor source, swap default approvers, attach a different document on the bill, or pull GL codes from your connected data. Mapping versions are immutable for already-paid bills so audit traces stay intact.

What happens if a Square record fails to post to Bill.com?

When a record fails to post to Bill.com (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 Bill.com?

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

Square to Bill.com

AvailableNative · SquareNative · Bill.com

Connect Square to Bill.com with Well

Each Square settlement is forwarded to Bill.com 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.

Bill.com

Target

The Bill.

Why this pair

Square processes the inbound side (customer card payments) and Bill.

com runs the outbound side (vendor bills and scheduled payments). Connecting Square to Bill. com through Well surfaces every Square payout the business would normally use to cover operating cash and pairs it with the Bill. com vendor record so spend and revenue land on one workflow. Square's MCP server pushes payout events to Well; Bill. com's IVA OCR creates the bill from the PDF Well forwards to your inbox so it enters your approval workflow.

What Well does between Square and Bill.com

One-way: Square into Well into Bill.com
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

Lemon Studio

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

CustomerLemon Studio
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordLemon Studio
Domainlemonstudio.io
Tax idFR42514682431
Sales journalVE · 2026

Confidence97%

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

Post

schedule as bills

Create a bill in Bill.com inbox

auto-posted

posted

TypeBill
VendorLemon Studio
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Bill.com

Action in Bill.com

1 compatible with this trigger

Create a bill in Bill.com inbox

Bridge Square payouts to Bill.com 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 Bill.com, 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 Bill.com 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 Bill.com.

13 signals and actions across Square and Bill.com

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 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 dispute is opened
Captures chargebacks with the contested payment and reason code.
Trigger·Transaction
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 Square invoice is paid
Detects paid Square invoices with line items, applied discounts, and tax breakdown.
Trigger·Invoice
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 card payment is captured
Captures successful card-present and card-not-present payments with currency, fees, and customer linkage.
Trigger·Transaction
When a customer is created in Square
Pulls new customer records with name, email, and stored payment methods.
Trigger·Company

Reference

Field mapping for Square → Bill.com

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

Transaction fields

5 fields flow from Square into Bill.com.

Square field	Label		Bill.com field	Label
payment.amount_money.amount	Payment amount	→	amount	Amount
payment.amount_money.currency	Currency	→	currency	Currency
payment.created_at	Charge date	→	process_date	Process date
payment.note	Description	→	memo	Memo
payment.id	Charge id	→	payment_id	Payment id

Invoice fields

5 fields flow from Square into Bill.com.

Square field	Label		Bill.com field	Label
invoice.invoice_number	Invoice number	→	invoice_number	Invoice number
invoice.invoice_date	Issue date	→	invoice_date	Invoice date
invoice.due_date	Due date	→	due_date	Due date
invoice.total_money.currency	Currency	→	currency	Currency
invoice.primary_recipient.customer_id	Customer	→	external_id	External id

Connect Square and Bill.com 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 Bill.com inbox awaiting approval. 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 Bill.com
In Bill.com, open Settings > Developer > API keys and create a key paired with your developer ID. Paste the key into Well; Bill.com'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 Bill.com 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 Bill.com 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 Bill.com inbox
Well forwards the extracted document to your Bill.com email-in address; Bill.com reads bills via email-in inbox, with vendor, invoice number, amount, and related records from it and you review and post. No write credential to Bill.com 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 Bill.com on Well

01What happens to historical Square data when I first connect to Bill.com?: 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 Bill.com ledger, and re-running the backfill is safe because Well tracks the Square record IDs and updates existing Bill.com entries instead of duplicating them.
02Does Well handle multi-currency records between Square and Bill.com?: Square carries the original transaction currency on every record and Bill.com natively ledgers in multiple currencies. Well preserves the original amount, applies your Bill.com chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Bill.com, so the Bill.com entry you post keeps both sides of the trade.
03How does Well prevent duplicates when posting Square records to Bill.com?: Square sends each event with a stable resource ID that Well tracks against the Bill.com ledger. Webhook replays (which Square can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Bill.com entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.
04Can I customise which Square fields are sent to Bill.com?: The default mapping connects each Square record to the Bill.com bill shape (vendor, amount, due date, approval policy). Settings let you override the vendor source, swap default approvers, attach a different document on the bill, or pull GL codes from your connected data. Mapping versions are immutable for already-paid bills so audit traces stay intact.
05What happens if a Square record fails to post to Bill.com?: When a record fails to post to Bill.com (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 Bill.com?: 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 Bill.com email-in address once it clears the matching threshold; Bill.com creates the draft record from it and you confirm and post it. Well holds no write credential to Bill.com. Tokens are encrypted at rest and in transit under TLS 1.3. Square and Bill.com together cover multiple regions; Well's storage region is configured per workspace.