How often does Square data sync to Freshbooks?

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

How does Well match Square records to entries in Freshbooks?

Every Square charge is scored against your open Freshbooks 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 Freshbooks. 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 Freshbooks?

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

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

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

What happens if I disconnect Square or Freshbooks?

Disconnecting Square stops the flow at the source. Well asks the Square MCP server to revoke the access token; Square returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Freshbooks is Freshbooks's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.

How does Well authenticate with Square and Freshbooks?

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

Square to Freshbooks

AvailableNative · SquareNative · Freshbooks

Connect Square to FreshBooks with Well

Skip the spreadsheet middle step: Square card payments, payouts, and refunds are matched in Well, then the matched PDFs land in Freshbooks as expenses and 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.

Freshbooks

Target

The FreshBooks connection delivers extracted documents into FreshBooks through its email-in address.

Why this pair

Square processes payments at the point of sale and pays out in net deposits; FreshBooks accepts emailed PDFs and creates expenses or bills from them.

Connecting Square to FreshBooks through Well matches each Square sale inside its own ledger with the processing fee split out and tax broken out per item, then forwards the matched PDF to FreshBooks' email-in. Square's MCP server pushes payout events to Well; FreshBooks creates the expense (or bill on the Select plan) from the forwarded PDF for your team to confirm and reconcile.

What Well does between Square and Freshbooks

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

Nordstern Werke

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

CustomerNordstern Werke
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordNordstern Werke
Domainnordstern-werke.de
Tax idDE298473651
Sales journalVE · 2026

Confidence97%

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

Post

post as expenses and bills

Create an expense in FreshBooks

auto-posted

posted

TypeExpense
VendorNordstern Werke
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Freshbooks

Action in Freshbooks

2 compatible with this trigger

Create an expense in FreshBooksCreate a bill in FreshBooks (Select plan)

Reconcile Square multi-currency charges to Freshbooks entries.

01Featured

Forward resolved documents to FreshBooks

Well reads the invoices and transactions from Square, resolves the company behind each one, and forwards it to your FreshBooks email-in address with the customer attached.

Resolve the customer before the books

Each company and payment detail from Square is matched to a canonical company inside Well, so the record reaching FreshBooks names a verified business.

Keep the sale traceable

The Square transaction stays attached to what Well forwards, so each FreshBooks record keeps the payment behind it.

13 signals and actions across Square and Freshbooks

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 customer is created in Square
Pulls new customer records with name, email, and stored payment methods.
Trigger·Company
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 refund is issued
Captures partial and full refunds with the originating payment id.
Trigger·Transaction
When a Square dispute is opened
Captures chargebacks with the contested payment and reason code.
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 order is completed
Captures the completed Square order with its line items, taxes, and the payment that settled it.
Trigger·Invoice
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 invoice is paid
Detects paid Square invoices with line items, applied discounts, and tax breakdown.
Trigger·Invoice

Reference

Field mapping for Square → Freshbooks

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

Transaction fields

5 fields flow from Square into Freshbooks.

Square field	Label		Freshbooks field	Label
payment.amount_money.amount	Payment amount	→	amount	Amount
payment.amount_money.currency	Currency	→	currency_code	Currency
payment.created_at	Charge date	→	date	Transaction date
payment.note	Description	→	note	Description
payment.id	Charge id	→	external_id	External id

Invoice fields

5 fields flow from Square into Freshbooks.

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

Connect Square and Freshbooks 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 FreshBooks expense or bill queue. 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 Freshbooks
Click Connect with FreshBooks; FreshBooks asks for the account to authorise and returns a refresh token and authorise read-only discovery of your existing records so Well can match against them when forwarding documents. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your FreshBooks.
- AuthConnect
- First syncup to an hour

How Square and Freshbooks 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 Freshbooks 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 Freshbooks inbox
Well forwards the extracted document to your Freshbooks email-in address; Freshbooks reads expenses (or bills on the Select plan) via email-in, with merchant, total, and tax populated from it and you review and post. No write credential to Freshbooks 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 Freshbooks on Well

01How often does Square data sync to Freshbooks?: 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 Freshbooks within a confidence window: above 85% it posts, 55-85% queues for review, below 55% is refused.
02How does Well match Square records to entries in Freshbooks?: Every Square charge is scored against your open Freshbooks 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 Freshbooks. Between 55% and 85% the candidate list is queued for review with the alternative customers ranked.
03Does Well handle multi-currency records between Square and Freshbooks?: Square carries the original transaction currency on every record and Freshbooks natively ledgers in multiple currencies. Well preserves the original amount, applies your Freshbooks chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Freshbooks, so the Freshbooks entry you post keeps both sides of the trade.
04What happens if a Square record fails to post to Freshbooks?: When a record fails to post to Freshbooks (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.
05What happens if I disconnect Square or Freshbooks?: Disconnecting Square stops the flow at the source. Well asks the Square MCP server to revoke the access token; Square returns confirmation and stops streaming events the moment it is acknowledged. Anything you already reviewed and posted in Freshbooks is Freshbooks's own record and is untouched; Well never held a write credential to it. Records held for review in Well remain in the queue so you can finish them by hand. Reconnecting later resumes from the last successful sync, not from scratch.
06How does Well authenticate with Square and Freshbooks?: 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 Freshbooks email-in address once it clears the matching threshold; Freshbooks creates the draft record from it and you confirm and post it. Well holds no write credential to Freshbooks. Tokens are encrypted at rest and in transit under TLS 1.3. Square and Freshbooks together cover multiple regions; Well's storage region is configured per workspace.