How often does Pennylane data sync to Freshbooks?

Pennylane 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 Pennylane records to entries in Freshbooks?

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

Does Well handle multi-currency records between Pennylane and Freshbooks?

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

Can I customise which Pennylane fields are sent to Freshbooks?

The default mapping covers every Pennylane field your Freshbooks 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 Freshbooks 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 Freshbooks is left exactly as it stands.

What happens if a Pennylane 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 Pennylane record. Nothing silently drops.

How does Well authenticate with Pennylane and Freshbooks?

Pennylane'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. Pennylane hosts in the EU and Freshbooks hosts outside the EU; Well processes records per the storage region configured for your workspace.

Pennylane to Freshbooks

AvailableNative · PennylaneNative · Freshbooks

Connect Pennylane to Freshbooks with Well

Move Pennylane invoices and contacts through Well and into Freshbooks as expenses and bills, with the audit trail kept on every record.

Connect both toolsView all integrations

Pennylane

Source

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

Freshbooks

Target

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

Why this pair

Connect Pennylane to Freshbooks through Well so records flow without manual rework.

What Well does between Pennylane and Freshbooks

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

Trigger from Pennylane

5 events · pick one

Well engine·recipe·When a Pennylane customer invoice is read

Source

from payment · live webhook

Atlas Robotics SAS

via Pennylane

Invoice

When a Pennylane customer invoice is read

INV-1284 · 22 Apr 2026€1,284.00

Extract

5 fields read from Pennylane

5 fields read

CustomerAtlas Robotics SAS
Invoice numberINV-1284
Issue date22 Apr 2026
Total€1,284.00
CurrencyEUR

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

post as expenses and bills

Create a bill in FreshBooks (Select plan)

auto-posted

posted

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

audit linkto Freshbooks

Action in Freshbooks

3 compatible with this trigger

Create a bill in FreshBooks (Select plan)Resolve a FreshBooks merchant from the receiptCreate an expense in FreshBooks

12 signals and actions across Pennylane and Freshbooks

When a Pennylane transaction is read
Captures the bank transactions Pennylane holds with amount, date, and counterparty.
Trigger·Transaction
When a Pennylane credit note is read
Captures Pennylane credit notes with the linked invoice, totals, and VAT so refunds reconcile correctly.
Trigger·Invoice
When a Pennylane bank account is read
Pulls the bank accounts linked in Pennylane with currency and holder detail.
Trigger·Account
When a Pennylane invoice attachment is read
Picks up the source PDF attached to a Pennylane invoice as a document.
Trigger·Document
When a Pennylane supplier invoice is read
Pulls Pennylane supplier invoices with the supplier, amount, due date, and VAT.
Trigger·Invoice
When a Pennylane customer invoice is read
Pulls Pennylane customer invoices with line items, customer, totals, and VAT.
Trigger·Invoice
When a Pennylane payment is read
Reads the payment recorded against a Pennylane invoice with method and amount.
Trigger·Payment method
When a Pennylane customer is read
Pulls Pennylane company customers with name, registration number, and billing detail.
Trigger·Company
Attach the receipt to the FreshBooks record
The forwarded PDF is stored on the expense or bill as the source.
Action·Document

Reference

Field mapping for Pennylane → Freshbooks

16 fields across 3 record types, open to see the full table.

Invoice fields

8 fields flow from Pennylane into Freshbooks.

Pennylane field	Label		Freshbooks field	Label
invoice.amount.total	Total amount	→	amount	Total
invoice.currency	Currency	→	currency_code	Currency
invoice.date.issue_date	Invoice date	→	create_date	Issue date
invoice.deadline.due_date	Due date	→	due_date	Due date
invoice.invoice_number	Reference	→	invoice_number	Invoice number
invoice.vat_amount.tax	VAT	→	vat_amount	Tax total
invoice.pre_tax_amount.subtotal	Subtotal	→	subtotal	Subtotal
invoice.id	Pennylane id	→	external_id	External id

Transaction fields

5 fields flow from Pennylane into Freshbooks.

Pennylane field	Label		Freshbooks field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency	Currency	→	currency_code	Currency
transaction.date.created	Execution date	→	date	Transaction date
transaction.label.description	Label	→	note	Description
transaction.id	Transaction id	→	external_id	External id

Company fields

3 fields flow from Pennylane into Freshbooks.

Pennylane field	Label		Freshbooks field	Label
customer.name	Customer name	→	organization	Client name
customer.vat_number.tax_id	VAT number	→	vat_number	Tax id
customer.id	Customer id	→	client_id	Client id

Connect Pennylane and Freshbooks in three steps.

1
Connect Pennylane
Click Connect with Pennylane; Well's OAuth proxy handles Pennylane authorisation through Dynamic Client Registration. Pennylane'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 Pennylane's supplier and customer invoices, contacts, and VAT detail read over Pennylane's MCP server and the the FreshBooks expense or bill queue. Match candidates are scored on counterparty, amount, date, and reference; above 85% confidence the link posts automatically, below it the candidate set queues for sign-off.
- 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 Pennylane and Freshbooks stay secure with Well

Well connects to Pennylane through its MCP server, which issues short-lived access tokens via Dynamic Client Registration. Well never holds a long-lived Pennylane 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 requestswellapp.ai/v1/mcps/pennylane/mcp

Read Pennylane records
Scoped to supplier and customer invoices, contacts, and VAT detail read over Pennylane's MCP server. No access to anything else in your Pennylane 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 Pennylane records
Not granted. Pennylane 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 Pennylane’s admin panel.

Frequently asked questions about Pennylane and Freshbooks on Well

01How often does Pennylane data sync to Freshbooks?: Pennylane 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 Pennylane records to entries in Freshbooks?: Well scores every candidate match between Pennylane records and existing Freshbooks entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Freshbooks updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.
03Does Well handle multi-currency records between Pennylane and Freshbooks?: Pennylane 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.
04Can I customise which Pennylane fields are sent to Freshbooks?: The default mapping covers every Pennylane field your Freshbooks 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 Freshbooks 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 Freshbooks is left exactly as it stands.
05What happens if a Pennylane 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 Pennylane record. Nothing silently drops.
06How does Well authenticate with Pennylane and Freshbooks?: Pennylane'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. Pennylane hosts in the EU and Freshbooks hosts outside the EU; Well processes records per the storage region configured for your workspace.