When a QuickBooks bill is read
Pulls QuickBooks bills with vendor, due date, line items, totals, and tax code on the hourly poll.
Forward extracted invoice and receipt PDFs to your QuickBooks @qbodocs.com inbox and QuickBooks creates a bill or receipt with vendor, date, and amount populated. Delivery is email-in; QuickBooks handles the accounting itself, and reading QuickBooks data back into Well is on the roadmap.
Well writes reconciled draft bill, vendor, attachment back to QuickBooks after they clear your review queue, with the source-record link preserved. Use QuickBooks as the destination for entries enriched across your other connected tools.
| From QuickBooks | In Well | Relation | |
|---|---|---|---|
| Journal entry | Transaction | Balances against | |
| Chart of accounts | Category | Maps to | |
| Vendor | Supplier | Resolves to | |
| Invoice | Receivable | Becomes |
Pulls QuickBooks bills with vendor, due date, line items, totals, and tax code on the hourly poll.
Reads QuickBooks customer and vendor records with name, billing address, and tax registration to match against your companies.
Captures QuickBooks sales invoices with customer, amount, currency, and reference for reconciliation.
Reads the payment recorded against a QuickBooks invoice or bill with method and amount.
Pulls bank-type accounts from the QuickBooks chart of accounts with currency and account number.
Captures QuickBooks credit memos with customer, totals, and tax so refunds reconcile against the original invoice.
Pulls QuickBooks purchase orders with vendor, line items, and totals to match against the arriving bill.
Picks up the source document attached to a QuickBooks bill or invoice.
Well forwards the PDF to your @qbodocs.com address; QuickBooks creates a bill or receipt with vendor, date, and amount populated. QuickBooks picks the record type per document.
Connect QuickBooks over OAuth 2.0: you approve on QuickBooks's authorize screen, so the password never reaches Well; Well holds only a scoped token it can refresh.
Well brings journal entry, chart of accounts, and vendor in from QuickBooks on a recurring poll that fetches only what changed since the last read. The first sync backfills history in the background and the connection stays live after.
Well resolves each QuickBooks entity into transaction, category, and supplier, assigns categories, and links every record to an audit trail across the rest of your connected tools.
Your data from QuickBooks lands as transaction, category, and supplier you can search, chart, and automate, and approved records flow back to QuickBooks once they clear your review queue.
Ask in plain language. Well answers from your connected QuickBooks connection, resolved against the rest of your stack.
Ask anything about your QuickBooks connection
Ask about your QuickBooks connection…
Find your QuickBooks Online receipts-and-bills inbox address (it ends in @qbodocs.com) and set it as the QuickBooks delivery target in Well. The link is the inbox address; there is no OAuth consent to grant for the delivery path.
With the address set, Well forwards each extracted invoice or receipt PDF to @qbodocs.com. QuickBooks reads the attachment and creates a bill or receipt with vendor, date, and amount filled in.
You review and categorise the record inside QuickBooks, which remains the system of record. Well keeps the same document linked to its vendor in your workspace, and inbound read of QuickBooks data is on the roadmap rather than live.
An email-in link carries no secret to rotate. Clearing the @qbodocs.com address in Well stops delivery; records already in QuickBooks are unaffected. QuickBooks developer docs.
QuickBooks accepts documents at its @qbodocs.com inbox, so the only thing Well configures is that delivery address, not an OAuth credential. Well emails extracted PDFs and QuickBooks creates the bill or receipt from them; QuickBooks does the accounting on its own side, and Well, for now, reads nothing back, since the inbound direction is still coming soon. Delivery in, accounting handled by QuickBooks, read on the roadmap.
Read QuickBooks records
Endpoints the QuickBooks API token grants, scoped by your consent.
Resolve journal entry, chart of accounts, vendor, and invoice across your stack
Match identifiers in QuickBooks against the same entities your other connected tools expose, so each record carries cross-tool context.
Deliver documents to your QuickBooks inbox
Well forwards approved documents to your QuickBooks email-in address; QuickBooks drafts the record and you post it. No write credential to QuickBooks is requested.
Store QuickBooks passwords or session cookies
Authentication runs through OAuth 2.0 tokens we never see.
Well forwards the extracted PDF to your QuickBooks @qbodocs.com email-in inbox. QuickBooks reads the attachment, decides whether it is a bill or a receipt, and creates the record with the vendor, date, and amount populated, keeping the source document attached. The type call is QuickBooks', not Well's; Well's part is delivering a clean, pre-extracted document.
No. Well delivers documents to the @qbodocs.com inbox so QuickBooks can create a bill or receipt; it has no API path that writes to the QuickBooks ledger. Booking accounting entries is not a shipped capability of this connector. If you need entries recorded, that happens inside QuickBooks after the document arrives, with QuickBooks as the system of record.
Not today. The inbound read direction for QuickBooks is marked coming soon, so Well does not import your QuickBooks chart of accounts, invoices, or transactions yet. The live path is one-way delivery into the @qbodocs.com inbox. The page describes that live path and treats read as a roadmap item, not a current feature.
The bill or receipt QuickBooks creates from Well's email arrives with the vendor, date, and amount QuickBooks read off the PDF, plus the source document attached for audit. Because Well extracted the fields before forwarding, the record is review-ready rather than a stub. You confirm or categorise it inside QuickBooks.
QuickBooks tracks the currency on the bill or receipt it creates, and the amount Well extracts carries its currency, so a USD receipt against a EUR base is not collapsed into a single figure. The conversion lives on the QuickBooks record where you reconcile it; Well preserves the original-currency amount on the document it forwarded.
Remove the QuickBooks delivery target in Well and forwarding to @qbodocs.com stops immediately. There is no write token into QuickBooks to revoke, since Well only emailed PDFs to the inbox. Bills and receipts QuickBooks already created stay in QuickBooks; the records Well captured remain in your workspace.
Ready-to-ship workflows that pair QuickBooks with another tool through Well.
Stripe
Match Stripe charges, refunds, payouts inside Well, then for…
Gmail
Capture Gmail vendor invoices, extract lines inside Well, fo…
PayPal
Match PayPal sales, refunds, and disputes inside Well, then…
Mercury
Reconcile Mercury transactions inside Well with vendors reso…
Square
Reconcile Square sales, refunds, and customer activity insid…
Razorpay
Reconcile Razorpay sales, refunds, and settlements inside We…
Xero
Migrate or mirror Xero records into QuickBooks through Well:…
Xero
Pull QuickBooks bills and customers into Well, match them ag…
Ramp
Reconcile Ramp card transactions and reimbursements inside W…
More in Accounting
Evoliz
Connect Evoliz to Well to sync accounting data and ledger records.
Freshbooks
Connect Freshbooks 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.
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 journal entry, chart of accounts, vendor from QuickBooks becomes searchable, queryable, and ready for your agents and tables. Disconnect any time.