How often does Square data sync to Pennylane?

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 Pennylane 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 Pennylane?

Every Square charge is scored against your open Pennylane 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 Pennylane. Between 55% and 85% the candidate list is queued for review with the alternative customers ranked.

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

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

How does Well prevent duplicates when posting Square records to Pennylane?

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

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

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

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 Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Pennylane hosts in the EU and Square hosts outside the EU; Well processes records per the storage region configured for your workspace.

Square to Pennylane

AvailableNative · SquareNative · Pennylane

Connect Square to Pennylane with Well

Match Square card payments, payouts, and refunds against your invoices inside Well, then forward the matched documents to Pennylane's email-in inbox as supplier and customer invoices you confirm in one click.

Connect both toolsView all integrations

Square

Source

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

Pennylane

Target

The Pennylane integration creates a bidirectional bridge between Well and your accounting workspace.

Why this pair

Square processes card payments at the point of sale, primarily in retail and food service; Pennylane runs on French SMB accounting in EUR.

Connecting Square to Pennylane through Well matches each Square sale inside its own ledger with French VAT context attached per item, the processing fee split out, and the payout reconciled against the bank line. The matched document is then forwarded to Pennylane's customer email-in address. Square's MCP server pushes payout events to Well; Pennylane's OCR creates the customer invoice from the forwarded PDF with French VAT broken out per item.

What Well does between Square and Pennylane

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

Aldercroft Trading

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

CustomerAldercroft Trading
Charge date22 Apr 2026
Charge amount€1,284.00
CurrencyEUR
Processing fee€37.24

Enrich

against your historical record graph

4 fields added

Customer recordAldercroft Trading
Domainaldercroft.co.uk
Tax idGB987604123
Sales journalVE · 2026

Confidence97%

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

Post

post as supplier and customer invoices

Create a supplier invoice in Pennylane

auto-posted

posted

TypeSupplier invoice
VendorAldercroft Trading
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Pennylane

Action in Pennylane

1 compatible with this trigger

Create a supplier invoice in Pennylane

Reconcile Square multi-currency charges to Pennylane entries.

01Featured

Resolve the customer on a Square sale

Well matches the customer on a Square transaction to a company record and forwards the document to your Pennylane email-in address, so the record your team confirms carries a resolved buyer.

Match against existing Pennylane records

Well reads your Pennylane companies and invoices to check whether a Square customer already exists there, so the forwarded document points at the right record instead of creating a duplicate.

Group repeat buyers by domain

Square customers that share one web domain resolve to a single company inside Well before the document is forwarded, so one buyer does not read as several in Pennylane.

Keep the sale behind each record

The Square invoice and transaction Well read stay linked to the document forwarded to your Pennylane email-in address, so every entry your team confirms traces back to the sale it came from.

14 signals and actions across Square and Pennylane

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

Reference

Field mapping for Square → Pennylane

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

Transaction fields

5 fields flow from Square into Pennylane.

Square field	Label		Pennylane field	Label
payment.amount_money.amount	Payment amount	→	amount	Amount
payment.amount_money.currency	Currency	→	currency	Currency
payment.created_at	Charge date	→	date	Execution date
payment.note	Description	→	label	Label
payment.id	Charge id	→	external_reference	Source id

Invoice fields

5 fields flow from Square into Pennylane.

Square field	Label		Pennylane field	Label
invoice.invoice_number	Invoice number	→	label	Reference
invoice.invoice_date	Issue date	→	date	Invoice date
invoice.due_date	Due date	→	deadline	Due date
invoice.total_money.currency	Currency	→	currency	Currency
invoice.primary_recipient.customer_id	Customer	→	external_reference	Source id

Connect Square and Pennylane 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 Pennylane Purchases tab and the customer-invoice collections list. 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 Pennylane
Click Connect with Pennylane; Well's OAuth proxy handles Pennylane authorisation through Dynamic Client Registration. Pennylane'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 Pennylane 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 processes records per the storage region configured for your workspace; only fields strictly required by the write surface are ferried across regions.

MCP server authEU residency optionGDPR-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 Pennylane inbox
Well forwards the extracted document to your Pennylane email-in address; Pennylane reads supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR from it and you review and post. No write credential to Pennylane 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 Pennylane on Well

01How often does Square data sync to Pennylane?: 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 Pennylane 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 Pennylane?: Every Square charge is scored against your open Pennylane 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 Pennylane. Between 55% and 85% the candidate list is queued for review with the alternative customers ranked.
03What happens to historical Square data when I first connect to Pennylane?: 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 Pennylane ledger, and re-running the backfill is safe because Well tracks the Square record IDs and updates existing Pennylane entries instead of duplicating them.
04How does Well prevent duplicates when posting Square records to Pennylane?: Square sends each event with a stable resource ID that Well tracks against the Pennylane ledger. Webhook replays (which Square can issue for delivery retries) are recognised by ID and either skipped or used to update the existing Pennylane entry. Distinct records that look similar are caught by Well before posting, with the candidates surfaced in the review queue when confidence is ambiguous.
05What happens if a Square record fails to post to Pennylane?: When a record fails to post to Pennylane (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 Pennylane?: 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 Pennylane email-in address once it clears the matching threshold; Pennylane creates the draft record from it and you confirm and post it. Well holds no write credential to Pennylane. Tokens are encrypted at rest and in transit under TLS 1.3. Pennylane hosts in the EU and Square hosts outside the EU; Well processes records per the storage region configured for your workspace.