Supplier & bill details
Supplier, invoice number, dates and totals read from the document and mapped to QuickBooks fields.
Home › Integrations › QuickBooks Online
How receipts and invoices get into QuickBooks Online
QuickBooks Online has receipt capture built into the product, but that feature is not exposed through the API, so an integration cannot use it. A pipeline reads the document separately and creates the bill through the API instead.
In-app capture, no APIQuickBooks Online can capture receipts inside the product, but that capability is not available to an external integration through the API.
In-app capture Receipt capture in productVia API Not exposedBills created Through the APISource file Attached to the bill
Capturereceipt or invoice arrives by email or bot
Readan ai reader pulls totals and line items
Codeline items matched to accounts and class
Checkduplicates flagged before anything posts
Postbill created via the api, file attached
What lands in QuickBooks Online
Line items
Each line item is extracted and coded to an account before the bill is created.
Bill via the API
The bill is created through the QuickBooks Online API, the same route as a manually entered bill.
Source PDF or photo
The original file is attached to the bill record, so the paper trail stays with the entry.
Duplicate check
A document that matches a bill already in QuickBooks is flagged rather than entered twice.
Review task
Anything that fails validation is sent to a review queue instead of posted on a guess.
Where it gets awkward
Every system has edges. These are the ones that shape the build — better known before the pilot than during it.
Receipt capture not in the API
QuickBooks Online has receipt capture in the product, but there is no way to push a photo into that flow from outside. Our pipeline reads the document separately and posts the bill through the API instead.
Bills only through the API
The API creates bills, with the source file attached; other document types need their own mapping.
Is a custom pipeline worth it here?
Worth building
- Receipts and invoices arriving by photo, email or a channel outside the app
- Several entities or a high volume of bills that need consistent coding
- Supplier or line-item data that needs checking before a bill is created
Native tools are enough
- A handful of bills a month entered by hand alongside in-app receipt capture
- You only need the documents already flowing through the built-in capture
The task behind this
Solution
Invoices and receipts posted into your accounting system automatically
Supplier invoices and staff-photographed receipts posted straight into Merit Aktiva, Xero, QuickBooks and more, with exceptions sent to a review queue.
→How the stream is built
Processed in the EU. The original files and extracted data stay in your own systems; a data-processing agreement is available on request — see security and data handling.
From audit to autopilot
Step 1
Audit
We map one document or enquiry stream end-to-end, count volumes and name the systems it touches. You get a written scope and a fixed pilot price.
Free · 3 working daysStep 2
Pilot
One stream goes live on your real documents. Acceptance is measured, not felt: straight-through rate, minutes per document, exceptions.
About two weeks · fixed priceStep 3
Rollout
The remaining streams follow the proven pattern. Monthly report, support, and changes as your systems change.
Stream by streamFrequently asked questions
Does QuickBooks Online read receipts automatically?
The product has receipt capture, but that feature sits inside the app and is not exposed through the API. An external pipeline cannot use it, so it has to read the document on its own.
How does a document turn into a bill?
The pipeline reads the receipt or invoice, maps supplier, line items and totals to QuickBooks fields, and creates the bill through the API. The source file is attached to that bill.
Why not just use the built-in receipt capture?
It works for receipts entered inside the app by someone with a login. It is not available to an outside integration, so documents arriving by email, a shared mailbox or a messaging channel need a separate route in.
What happens to documents that fail validation?
They go to a review queue in a tool you already use rather than being posted as a guess. Someone checks the entry, then it goes in as a normal bill.
Is there a case study for QuickBooks Online specifically?
Our published case study was built on another ledger, Merit Aktiva, for an Estonian accounting firm. The intake and validation work, reading the document, checking data, flagging duplicates and routing exceptions, carries over directly; only the final posting call changes for QuickBooks Online.
Using QuickBooks Online? Start with the audit
Three working days, one document stream mapped end to end, a fixed pilot price on paper. No commitment.
Get a free automation audit