Create an expense in FreshBooks
Well forwards the receipt PDF to your FreshBooks email-in address; FreshBooks creates an expense with merchant, total, and tax populated.
Forward extracted receipt PDFs to your FreshBooks email-in address and FreshBooks creates an expense, or a bill on the Select plan, with merchant, total, and tax filled in. The source receipt rides along on the record FreshBooks builds.
Well writes reconciled expense, bill, attachment to Freshbooks after they clear your review queue, with the source-record link preserved. Use Freshbooks as the destination for entries enriched across your other connected tools.
| In Well | To Freshbooks | Relation | |
|---|---|---|---|
Ledger line | Expense | Writes as | |
Payable | Bill | Creates as | |
Source PDF | Attachment | Attaches as |
Well forwards the receipt PDF to your FreshBooks email-in address; FreshBooks creates an expense with merchant, total, and tax populated.
On the FreshBooks Select plan, the same email-in feature also creates a bill (with line items) instead of an expense.
The forwarded PDF is stored on the expense or bill as the source.
FreshBooks reads the merchant name off the forwarded receipt and matches it on the expense (or bill). You confirm or correct the merchant on first sight.
Connect Freshbooks over OAuth 2.0: you approve on Freshbooks's authorize screen, so the password never reaches Well; Well holds only a scoped token it can refresh.
Freshbooks is a delivery target, not a source, so Well pulls nothing in. Once a record clears review, Well's pipeline can create an expense in FreshBooks.
Before delivery Well reconciles and enriches each document, resolving the expense, bill, and attachment so what reaches Freshbooks arrives matched and carries its full audit trail.
Well forwards each reconciled document to your Freshbooks email-in address; Freshbooks drafts the record from it and you review and post. Well holds no write credential to Freshbooks.
Ask in plain language. Well answers from your connected Freshbooks connection, resolved against the rest of your stack.
Ask anything about your Freshbooks connection
Ask about your Freshbooks connection…
Copy your FreshBooks email-in address from FreshBooks (the one expenses and bills are created from) and set it as the FreshBooks delivery target in Well. The connection is the inbound address, so there is no consent screen to clear.
With the address in place, Well forwards each extracted receipt or bill PDF to FreshBooks. FreshBooks reads the attachment and creates an expense with merchant, total, and tax, or a bill with line items on the Select plan.
You then assign the expense or bill to a client or project inside FreshBooks for billing, while Well keeps the same record linked to its customer or vendor for workspace queries. FreshBooks remains the source of truth for invoicing.
No secret is exchanged, so nothing rotates. Clearing the delivery address in Well halts forwarding; records already in FreshBooks are untouched.
FreshBooks captures documents through its email-in address, so Well authenticates nothing into FreshBooks beyond the delivery target you set. Well emails extracted PDFs to that address and FreshBooks creates the expense or bill; Well never reads FreshBooks data or edits a posted record. Delivery is the whole contract here, and it is one-way into FreshBooks' inbox.
Read Freshbooks records
Endpoints the Freshbooks API token grants, scoped by your consent.
Resolve invoice, client, expense, and payment across your stack
Match identifiers in Freshbooks against the same entities your other connected tools expose, so each record carries cross-tool context.
Deliver documents to your Freshbooks inbox
Well forwards approved documents to your Freshbooks email-in address; Freshbooks drafts the record and you post it. No write credential to Freshbooks is requested.
Store Freshbooks passwords or session cookies
Authentication runs through OAuth 2.0 tokens we never see.
Each receipt or bill PDF Well extracts is forwarded to your FreshBooks email-in address. On the Plus and Premium plans FreshBooks turns the attachment into an expense with the merchant, total, and tax filled in; on the Select plan the same email-in feature creates a bill with line items. Either way the source receipt rides along as an attachment on the record FreshBooks creates.
It is the email handoff FreshBooks publishes for document capture. Well forwards the PDF to the FreshBooks email-in address and FreshBooks builds the expense or bill from it. There is no direct OAuth write that creates the FreshBooks record without the email step, so the page describes what actually runs rather than an API path that is not wired.
FreshBooks tracks the currency on the expense or bill it creates, and the figure Well extracts from the PDF carries its currency too, so a receipt in USD against a EUR base does not get flattened into one number. The conversion stays visible on the FreshBooks side where you reconcile it, and Well keeps the original-currency amount on the record it forwarded.
In your workspace, Well keeps each forwarded receipt linked to the customer or vendor it belongs to, so the expense is not orphaned. On FreshBooks, the email-in record arrives with the merchant, total, and tax populated; you assign it to a client or project inside FreshBooks, which stays the system of record for billable-expense routing.
Well forwards the extracted PDF to the FreshBooks email-in address in the background as soon as a document clears extraction, so it appears for FreshBooks to process shortly after. FreshBooks then creates the expense or bill on its own timing. Well does not read back FreshBooks state; it captures, extracts, and delivers.
Remove the FreshBooks delivery target in Well and forwarding stops at once. Because Well only ever emailed PDFs to FreshBooks' inbox, there is no write token to revoke and nothing posted to roll back. The expenses and bills FreshBooks already created remain in FreshBooks, and the records Well captured stay queryable in your workspace.
Ready-to-ship workflows that pair Freshbooks with another tool through Well.
Square
Reconcile Square sales, refunds, and customer activity insid…
Ramp
Reconcile Ramp card transactions, bills, and reimbursements…
Razorpay
Reconcile Razorpay sales, refunds, and settlements inside We…
Stripe
Reconcile Stripe charges, refunds, payouts inside Well with…
Gmail
Capture supplier invoices from Gmail attachments and draft F…
Mercury
Sync Mercury transactions to FreshBooks as expenses or bills…
More in Accounting
Evoliz
Connect Evoliz to Well to sync accounting data and ledger records.
Kolecto
Connect Kolecto to Well to sync accounting data and ledger records.
Pennylane
Connect Pennylane to Well to sync accounting data and ledger records.
QuickBooks
Connect QuickBooks to Well to sync accounting data and ledger records.
Popular cross-category
Stripe
Connect Stripe to Well to sync payments and transaction data.
Gmail
Connect Gmail to Well to collect and process invoices from your inbox.
Google Drive
Connect Google Drive to Well to import and export documents and invoices from your cloud storage.
Notion
Connect Notion to Well to sync tasks, projects, and team workflows.
Connect once. Every invoice, client, expense reconciled in Well flows out to Freshbooks with its source-graph link preserved. Disconnect any time.