Will every QuickBooks record post to Pennylane automatically?

Not always. On the next hourly pull from QuickBooks, 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 Pennylane email-in address and Pennylane 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 QuickBooks records to entries in Pennylane?

Well scores every candidate match between QuickBooks records and existing Pennylane entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Pennylane 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 QuickBooks data when I first connect to Pennylane?

QuickBooks exposes seven years of accounting history 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 QuickBooks record IDs and updates existing Pennylane entries instead of duplicating them.

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

What happens if I disconnect QuickBooks or Pennylane?

Disconnecting QuickBooks stops the flow at the source. Well calls the QuickBooks OAuth revoke endpoint; the refresh token is invalidated and any in-flight access token is rejected on the next call. Anything you already reviewed and posted in Pennylane is Pennylane'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 QuickBooks and Pennylane?

QuickBooks runs a manual OAuth 2.0 flow that you approve inside QuickBooks; Well receives a refresh token scoped to the resources it needs to read. 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 QuickBooks hosts outside the EU; Well processes records per the storage region configured for your workspace.

QuickBooks to Pennylane

AvailableNative · QuickBooksNative · Pennylane

Connect QuickBooks to Pennylane with Well

Move QuickBooks bills and customers through Well and into Pennylane as supplier and customer invoices, with the audit trail kept on every record.

Connect both toolsView all integrations

QuickBooks

Source

The QuickBooks connection delivers documents into QuickBooks Online through its @qbodocs.

Pennylane

Target

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

Why this pair

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

What Well does between QuickBooks and Pennylane

One-way: QuickBooks into Well into Pennylane
Sync mode: Polling every 60 minutes
Up to 24 syncs/day

Trigger from QuickBooks

5 events · pick one

Well engine·recipe·When a QuickBooks bill is read

Source

from upload · hourly poll

Slack Technologies

via QuickBooks

Bill

When a QuickBooks bill is read

INV-2026-04-100 · 22 Apr 2026€1,284.00

Extract

6 fields read from QuickBooks

6 fields read

VendorSlack Technologies
Invoice numberINV-2026-04-100
Issue date22 Apr 2026
Total€1,284.00
Tax€256.80

Enrich

against your historical record graph

5 fields added

Legal entitySlack Technologies
Tax idEU372014983
Domainslack.com
Ledger account6064 · SaaS

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
VendorSlack Technologies
Amount€1,284.00
Ledger6064 · SaaS
Source docattached
Confidence97%

audit linkto Pennylane

Action in Pennylane

2 compatible with this trigger

Create a supplier invoice in PennylaneResolve a Pennylane supplier from the document

13 signals and actions across QuickBooks and Pennylane

When a QuickBooks sales invoice is read
Captures QuickBooks sales invoices with customer, amount, currency, and reference for reconciliation. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When a QuickBooks account is read
Pulls bank-type accounts from the QuickBooks chart of accounts with currency and account number. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Account
When a QuickBooks bill is read
Pulls QuickBooks bills with vendor, due date, line items, totals, and tax code on the hourly poll. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When a QuickBooks payment is read
Reads the payment recorded against a QuickBooks invoice or bill with method and amount. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Payment method
When a QuickBooks customer is read
Reads QuickBooks customer and vendor records with name, billing address, and tax registration to match against your companies. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Company
When a QuickBooks credit memo is read
Captures QuickBooks credit memos with customer, totals, and tax so refunds reconcile against the original invoice. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When a QuickBooks purchase order is read
Pulls QuickBooks purchase orders with vendor, line items, and totals to match against the arriving bill. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When a QuickBooks attachment is read
Picks up the source document attached to a QuickBooks bill or invoice. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Document
Resolve a Pennylane customer from the invoice
Pennylane reads the customer name off the outbound invoice for collections. You confirm on first sight.
Action·Company

Reference

Field mapping for QuickBooks → Pennylane

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

Invoice fields

7 fields flow from QuickBooks into Pennylane.

QuickBooks field	Label		Pennylane field	Label
Bill.TotalAmt.total	Total	→	amount	Total amount
Bill.CurrencyRef.currency	Currency	→	currency	Currency
Bill.TxnDate.date	Bill date	→	date	Invoice date
Bill.DueDate.due_date	Due date	→	deadline	Due date
Bill.DocNumber.invoice_number	Doc number	→	label	Reference
Bill.TxnTaxDetail.tax	Tax	→	vat_amount	VAT
Bill.Id.id	QuickBooks id	→	external_reference	Source id

Transaction fields

5 fields flow from QuickBooks into Pennylane.

QuickBooks field	Label		Pennylane field	Label
Purchase.TotalAmt.amount	Amount	→	amount	Amount
Purchase.CurrencyRef.currency	Currency	→	currency	Currency
Purchase.TxnDate.created	Transaction date	→	date	Execution date
Purchase.PrivateNote.description	Memo	→	label	Label
Purchase.Id.id	Purchase id	→	external_reference	Source id

Company fields

3 fields flow from QuickBooks into Pennylane.

QuickBooks field	Label		Pennylane field	Label
Vendor.DisplayName.name	Display name	→	name	Customer name
Vendor.WebAddr.website	Website	→	website	Website
Vendor.TaxIdentifier.tax_id	Tax id	→	vat_number	VAT number

Connect QuickBooks and Pennylane in three steps.

1
Connect QuickBooks
Click Connect with QuickBooks; you approve the connection inside QuickBooks Online and authorise read access to bills, customers, and tax codes polled hourly from QuickBooks Online. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your QuickBooks Online.
- AuthConnect
2
Map your accounts
Well discovers QuickBooks's bills, customers, and tax codes polled hourly from QuickBooks Online and the the Pennylane Purchases tab and the customer-invoice collections list. 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 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 QuickBooks and Pennylane stay secure with Well

Well calls QuickBooks with an OAuth 2.0 token scoped to read-only access. QuickBooks's consent screen lists the scopes before you approve; access tokens are exchanged and refreshed automatically before they expire. Well processes records per the storage region configured for your workspace; only fields strictly required by the write surface are ferried across regions.

OAuth 2.0EU residency optionGDPR-aligned

Scopes Well requests

Read QuickBooks records
Scoped to bills, customers, and tax codes polled hourly from QuickBooks Online. No access to anything else in your QuickBooks 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 QuickBooks records
Not granted. QuickBooks 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 QuickBooks’s admin panel.

Frequently asked questions about QuickBooks and Pennylane on Well

01Will every QuickBooks record post to Pennylane automatically?: Not always. On the next hourly pull from QuickBooks, 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 Pennylane email-in address and Pennylane 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.
02How does Well match QuickBooks records to entries in Pennylane?: Well scores every candidate match between QuickBooks records and existing Pennylane entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Pennylane updates; between 55% and 85% the candidates are queued for sign-off; below 55% the record stays open with the candidate list available.
03What happens to historical QuickBooks data when I first connect to Pennylane?: QuickBooks exposes seven years of accounting history 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 QuickBooks record IDs and updates existing Pennylane entries instead of duplicating them.
04What happens if a QuickBooks 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 QuickBooks record. Nothing silently drops.
05What happens if I disconnect QuickBooks or Pennylane?: Disconnecting QuickBooks stops the flow at the source. Well calls the QuickBooks OAuth revoke endpoint; the refresh token is invalidated and any in-flight access token is rejected on the next call. Anything you already reviewed and posted in Pennylane is Pennylane'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 QuickBooks and Pennylane?: QuickBooks runs a manual OAuth 2.0 flow that you approve inside QuickBooks; Well receives a refresh token scoped to the resources it needs to read. 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 QuickBooks hosts outside the EU; Well processes records per the storage region configured for your workspace.