How often does Pennylane data sync to Bill.com?

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 Bill.com 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 Bill.com?

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

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

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

The default mapping connects each Pennylane 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 Pennylane 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 Pennylane record. Nothing silently drops.

How does Well authenticate with Pennylane and Bill.com?

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

Pennylane to Bill.com

AvailableNative · PennylaneNative · Bill.com

Connect Pennylane to Bill.com with Well

Move Pennylane invoices and contacts through Well and into Bill.com as 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.

Bill.com

Target

The Bill.

Why this pair

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

What Well does between Pennylane and Bill.com

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

Helix Bio Labs

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

CustomerHelix Bio Labs
Invoice numberINV-1284
Issue date22 Apr 2026
Total€1,284.00
CurrencyEUR

Enrich

against your historical record graph

4 fields added

Customer recordHelix Bio Labs
Domainhelixbio.com
Tax idDE234567891
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
VendorHelix Bio Labs
Amount€1,284.00
LedgerVE · 2026
Source docattached
Confidence97%

audit linkto Bill.com

Action in Bill.com

2 compatible with this trigger

Create a bill in Bill.com inboxResolve a Bill.com vendor from the bill

12 signals and actions across Pennylane and Bill.com

When a Pennylane payment is read
Reads the payment recorded against a Pennylane invoice with method and amount.
Trigger·Payment method
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 customer is read
Pulls Pennylane company customers with name, registration number, and billing detail.
Trigger·Company
When a Pennylane bank account is read
Pulls the bank accounts linked in Pennylane with currency and holder detail.
Trigger·Account
When a Pennylane supplier invoice is read
Pulls Pennylane supplier invoices with the supplier, amount, due date, and VAT.
Trigger·Invoice
When a Pennylane transaction is read
Captures the bank transactions Pennylane holds with amount, date, and counterparty.
Trigger·Transaction
When a Pennylane customer invoice is read
Pulls Pennylane customer invoices with line items, customer, totals, and VAT.
Trigger·Invoice
When a Pennylane credit note is read
Captures Pennylane credit notes with the linked invoice, totals, and VAT so refunds reconcile correctly.
Trigger·Invoice
Resolve a Bill.com vendor from the bill
Bill.com's IVA OCR resolves the vendor name from the document. You complete the vendor setup (banking, tax) separately.
Action·Company

Reference

Field mapping for Pennylane → Bill.com

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

Invoice fields

7 fields flow from Pennylane into Bill.com.

Pennylane field	Label		Bill.com field	Label
invoice.amount.total	Total amount	→	amount	Amount
invoice.currency	Currency	→	currency	Currency
invoice.date.issue_date	Invoice date	→	invoice_date	Invoice date
invoice.deadline.due_date	Due date	→	due_date	Due date
invoice.invoice_number	Reference	→	invoice_number	Invoice number
invoice.pre_tax_amount.subtotal	Subtotal	→	subtotal	Subtotal
invoice.id	Pennylane id	→	external_id	External id

Transaction fields

5 fields flow from Pennylane into Bill.com.

Pennylane field	Label		Bill.com field	Label
transaction.amount	Amount	→	amount	Amount
transaction.currency	Currency	→	currency	Currency
transaction.date.created	Execution date	→	process_date	Process date
transaction.label.description	Label	→	memo	Memo
transaction.id	Transaction id	→	payment_id	Payment id

Company fields

3 fields flow from Pennylane into Bill.com.

Pennylane field	Label		Bill.com field	Label
customer.name	Customer name	→	vendor_name	Vendor name
customer.vat_number.tax_id	VAT number	→	tax_id	Tax id
customer.id	Customer id	→	vendor_id	Vendor id

Connect Pennylane and Bill.com 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 Bill.com inbox awaiting approval. 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 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 Pennylane and Bill.com 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 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 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 Bill.com on Well

01How often does Pennylane data sync to Bill.com?: 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 Bill.com 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 Bill.com?: Well scores every candidate match between Pennylane records and existing Bill.com entries on counterparty name, amount, date proximity, currency, and reference. Above 85% the record links to the historical entry and Bill.com 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 Bill.com?: Pennylane 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.
04Can I customise which Pennylane fields are sent to Bill.com?: The default mapping connects each Pennylane 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 Pennylane 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 Pennylane record. Nothing silently drops.
06How does Well authenticate with Pennylane and Bill.com?: 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 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. Pennylane hosts in the EU and Bill.com hosts outside the EU; Well processes records per the storage region configured for your workspace.