What Gmail data does Well pull into Pennylane?

Well watches Gmail for attachments matching the configured invoice and receipt filters, extracts invoice and receipt PDFs from email attachments, plus the sender, subject, and date headers, and forwards the structured output to Pennylane as supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR, with the original email message ID stored on every record for audit.

Will every Gmail record post to Pennylane automatically?

Not always. Within seconds of Gmail firing the event, 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.

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

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

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

Every Gmail message has a stable message ID, and Well stores it the moment the attachment is parsed. If the same email is reprocessed (label change, mailbox migration, or a manual rerun), Well recognises the message ID and skips the duplicate, or updates the linked Pennylane entry if a downstream field changed. Forwarded copies of the same invoice are caught by counterparty-plus-amount matching before they reach Pennylane.

What happens if I disconnect Gmail or Pennylane?

Disconnecting Gmail stops the flow at the source. Well calls the Gmail 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 Gmail and Pennylane?

Gmail runs a manual OAuth 2.0 flow that you approve inside Gmail; 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 Gmail hosts outside the EU; Well processes records per the storage region configured for your workspace.

Gmail to Pennylane

AvailableNative · GmailNative · Pennylane

Connect Gmail to Pennylane with Well

Gmail attachments are parsed inside Well for vendor, amount, VAT, and due date, then the documents arrive at Pennylane as drafts with the original message ID attached.

Connect both toolsView all integrations

Active in production

On this connection

6workspaces

Live in production since February 2026.

67% also use Google Drive

Most common third connector on this pair

Bank, FX & payment-processing fees · Business & productivity software · Travel & transport

Most-matched vendor categories

7,282

Matches analyzed to date across these workspaces

962

Records synced to date across these workspaces

4,192

Invoices processed to date across these workspaces

98%

Auto-post-ready across Well, to date

Adoption figures for this connection · updated 2026-06-19. Auto-post-ready % is a platform-wide rate across all of Well, to date (confidence ≥ 0.85). Numbers anonymised; no customer identifying data.

Gmail

Source

The Gmail integration turns your inbox into an automated invoice capture flow.

Pennylane

Target

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

Why this pair

Gmail and Pennylane are both unavoidable in the day-to-day of a French SMB ops team, but neither speaks the other's language.

Suppliers email PDF invoices; Pennylane wants structured supplier invoices with VAT codes and ledger accounts already mapped. Well reads each Gmail attachment, extracts vendor, totals, VAT, and line items, matches the supplier against the Pennylane contact graph, and drafts the supplier invoice with the PDF kept on the record.

What Well does between Gmail and Pennylane

One-way: Gmail into Well into Pennylane
Sync mode: Real-time webhooks
Events arrive within a minute

Trigger from Gmail

5 events · pick one

Well engine·recipe·When an invoice PDF arrives as an attachment

Source

from email · live webhook

EDF Entreprises

via Gmail

Invoice

When an invoice PDF arrives as an attachment

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

Extract

6 fields read from Gmail

6 fields read

VendorEDF Entreprises
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 entityEDF Entreprises
Tax idFR03552081317
Domainedf.com
Ledger account6061 · Utilities

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
VendorEDF Entreprises
Amount€1,284.00
Ledger6061 · Utilities
Source docattached
Confidence97%

audit linkto Pennylane

Action in Pennylane

1 compatible with this trigger

Create a supplier invoice in Pennylane

What Well does with Gmail invoices on the way to Pennylane.

01Featured

Capture supplier invoices from email

Well watches Gmail for attachments matching invoice patterns, extracts amount, VAT, supplier, and due date in Well, then forwards the PDF to Pennylane's email-in inbox. The original message ID stays on the document so the audit trail traces from Pennylane back to the email that delivered the invoice.

Deduplicate forwarded receipts

Forwarded copies of the same receipt are caught by counterparty-plus-amount matching inside Well before delivery. If two team members forward the same supplier invoice from Gmail on the same day, Well keeps the first copy as canonical and tags the second as a duplicate so Pennylane only receives one document.

Resolve a new vendor from the invoice header

When an invoice arrives from a vendor Well does not recognise, the header (legal name, tax ID, bank IBAN) is parsed and a vendor record is proposed inside Well. The matched document is then forwarded to Pennylane with the proposed match so Pennylane's OCR can resolve it on arrival.

Catch missing attachments before delivery

If an Gmail invoice references a credit memo or a delivery note that did not arrive, Well flags the missing attachment inside its own queue and holds delivery until you forward the supporting document. Documents reaching Pennylane always carry their supporting paperwork.

11 signals and actions across Gmail and Pennylane

When an email with an invoice attachment is received
Pulls from your Gmail inbox. Well picks up any received email with a PDF attachment; forwarded headers are recovered automatically. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When an invoice PDF arrives as an attachment
Pulls from your Gmail inbox. Picks up emails matching has:attachment filename:pdf and runs the document through extraction. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When an email with a bill attachment is processed by Well
Pulls from your Gmail inbox. Well's AI extracts the bill from the attached PDF and matches the vendor against your existing records. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When an email arrives from a sender domain already in your vendor list
Pulls from your Gmail inbox. The vendor is matched against your existing company records. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When an email arrives from a sender domain not yet in your vendor list
Pulls from your Gmail inbox. Well prepares a new vendor record from the email and document headers for your confirmation. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Invoice
When an email attachment is processed by Well
Pulls from your Gmail inbox. Receipts, invoices, statements: any PDF attachment is read and captured into your records. Forwarded to Pennylane's email-in with amount, VAT, and date pre-filled by Pennylane's OCR.
Trigger·Document
Create a customer invoice in Pennylane
Driven by emailed invoices, receipts, and notifications. Well forwards the document to Pennylane's collections address; Pennylane creates the customer invoice with the same OCR pre-fill.
Action·Invoice
Create a supplier invoice in Pennylane
Driven by emailed invoices, receipts, and notifications. Well forwards the extracted PDF to Pennylane's supplier inbox; Pennylane creates the supplier invoice with amount, VAT, and date pre-filled.
Action·Invoice
Resolve a Pennylane supplier from the document
Driven by emailed invoices, receipts, and notifications. Pennylane's OCR resolves the supplier name from the PDF. You confirm or correct the match on first sight.
Action·Company

Reference

Field mapping for Gmail → Pennylane

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

Invoice fields

7 fields flow from Gmail into Pennylane.

Gmail field	Label		Pennylane field	Label
extracted.invoice_number	Invoice number	→	label	Reference
extracted.issue_date	Issue date	→	date	Invoice date
extracted.due_date	Due date	→	deadline	Due date
extracted.total	Total	→	amount	Total amount
extracted.subtotal	Subtotal	→	pre_tax_amount	Subtotal
extracted.tax	Tax	→	vat_amount	VAT
extracted.currency	Currency	→	currency	Currency

Company fields

3 fields flow from Gmail into Pennylane.

Gmail field	Label		Pennylane field	Label
extracted.vendor_name	Vendor name	→	name	Customer name
extracted.vendor_domain	Vendor domain	→	website	Website
extracted.vendor_tax_id	Vendor tax id	→	vat_number	VAT number

Connect Gmail and Pennylane in three steps.

1
Connect Gmail
Click Connect with Google; Google asks which mailbox to scope and returns a refresh token and authorise read access to invoice and receipt PDFs from email attachments, plus the sender, subject, and date headers. Access tokens are exchanged and refreshed automatically before they expire, and the grant is revocable from your Google Workspace.
- AuthConnect
2
Map your accounts
Well discovers the Gmail attachments matching your invoice pattern (invoice and receipt PDFs from email attachments, plus the sender, subject, and date headers) and the the Pennylane Purchases tab and the customer-invoice collections list. Tune the parsing prompt once on the first ten records; Well saves the mapping and applies it to every subsequent attachment above 85% confidence.
- 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 Gmail and Pennylane stay secure with Well

Well calls Gmail with an OAuth 2.0 token scoped to read-only access. Gmail'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 Gmail records
Scoped to invoice and receipt PDFs from email attachments, plus the sender, subject, and date headers. No access to anything else in your Gmail 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 Gmail records
Not granted. Gmail 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 Gmail’s admin panel.

Frequently asked questions about Gmail and Pennylane on Well

01What Gmail data does Well pull into Pennylane?: Well watches Gmail for attachments matching the configured invoice and receipt filters, extracts invoice and receipt PDFs from email attachments, plus the sender, subject, and date headers, and forwards the structured output to Pennylane as supplier and customer invoices via email-in, with amount, VAT, and date pre-filled by Pennylane's OCR, with the original email message ID stored on every record for audit.
02Will every Gmail record post to Pennylane automatically?: Not always. Within seconds of Gmail firing the event, 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.
03Does Well handle multi-currency records between Gmail and Pennylane?: Gmail carries the original transaction currency on every record and Pennylane natively ledgers in multiple currencies. Well preserves the original amount, applies your Pennylane chart-of-accounts conversion rules at posting time, and both the source and converted amounts ride on the document Well forwards to Pennylane, so the Pennylane entry you post keeps both sides of the trade.
04How does Well prevent duplicates when posting Gmail records to Pennylane?: Every Gmail message has a stable message ID, and Well stores it the moment the attachment is parsed. If the same email is reprocessed (label change, mailbox migration, or a manual rerun), Well recognises the message ID and skips the duplicate, or updates the linked Pennylane entry if a downstream field changed. Forwarded copies of the same invoice are caught by counterparty-plus-amount matching before they reach Pennylane.
05What happens if I disconnect Gmail or Pennylane?: Disconnecting Gmail stops the flow at the source. Well calls the Gmail 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 Gmail and Pennylane?: Gmail runs a manual OAuth 2.0 flow that you approve inside Gmail; 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 Gmail hosts outside the EU; Well processes records per the storage region configured for your workspace.