Every transaction that is missing its receipt, in one list

An owner signs in to Intuit and approves BilagPilot for one company. Access refreshes automatically.

Intuit scopes an approval to a single company file, so each client is connected separately.

Account numbers are optional in QuickBooks, so accounts are matched on their name and type when no number exists.

Purchase, Bill and Journal Entry records.

QuickBooks has no per-transaction flag, so BilagPilot reads the attachment list and compares. Same result, slightly more work per sync.

Read as four 92-day windows, newest first. QuickBooks cannot filter on the missing ones, so every transaction in a window counts against the limit, and a quarter too large to finish ends the run at that date rather than skipping ahead.

Attached to the expense, bill or journal it belongs to.

It goes to the company's Attachments list in QuickBooks, where whoever books the transaction can pick it up.

Intuit publishes no per-transaction limit, so the pages of a receipt can go up as separate files.

By design. Your ledger is only ever added to, never changed.

An owner signs in to Xero and approves BilagPilot. Access refreshes automatically.

Xero scopes an approval to one organisation too. Approvals accumulate, so a practice builds up its client list one at a time, and you choose which of them to sync — none are synced until you do.

Account codes are read exactly as they appear in Xero.

Bank transactions of type Spend, and supplier bills.

Xero exposes an attachment flag per transaction, so the search is exact and cheap.

Xero returns only the transactions with nothing attached, so all 300 are documents you are chasing rather than ordinary traffic.

Deleted and voided transactions are skipped.

Attached to the bank transaction or bill, and visible in Xero straight away.

Xero stores an attachment on an existing transaction and nowhere else. The file stays approved in BilagPilot until the transaction exists.

Xero's own ceiling. A transaction already carrying ten is refused with that reason instead of failing at the ledger.

By design. Your ledger is only ever added to, never changed.

Someone signs in to FreeAgent and approves BilagPilot. Access refreshes automatically. What the connection can read follows that user's own FreeAgent permission level: level 5 (Bills) covers supplier bills and expenses, and level 6 (Banking) is needed for bank payments as well.

A single FreeAgent approval covers one company. A practice can instead connect through FreeAgent's Practice Dashboard, which covers every client at once — FreeAgent grants that separately, on request.

Categories are read by nominal code, and the tax rates come from the company's own settings.

Supplier bills, out-of-pocket expenses, and money-out entries explained against a bank account. Bank payments need the connecting user to hold FreeAgent's Banking level; without it the sync reports that it skipped them rather than quietly finding less.

FreeAgent has no filter for it, so BilagPilot reads the transactions in the period and checks each one. Same result, more work per sync, which is why the search window matters more here.

FreeAgent cannot filter on the missing ones, so every bill and expense in the window is read and checked here — ordinary bookkeeping spends the same budget as the documents you are chasing. Bank payments are read per account, up to 10 business accounts; personal accounts are left out.

Mileage claims are skipped too — the rate is the evidence, so there is no receipt to chase.

Transfers, bill payments and invoice receipts are left alone.

Attached to the bill, expense or bank entry it belongs to.

An attachment is created by writing to the bill, expense or bank entry itself, so with no record there is nowhere to put it. The file stays approved in BilagPilot until the transaction exists.

FreeAgent holds a single attachment per record. One already there is left alone rather than overwritten, so several pages have to be sent as one combined file.

A transaction that already carries a document is left alone rather than overwritten.

By design. Your ledger is only ever added to, never changed.

The Sage Accounting API version BilagPilot uses serves these three regions only.

Someone signs in to Sage and approves BilagPilot. Access refreshes automatically, and a connection left unused for a month has to be approved again.

One sign-in reaches every business that Sage user can open, so a Sage for Accountants login brings the client list in at once. You choose which of them to sync — none are synced until you do.

Ledger accounts and tax rates are read exactly as they appear in Sage.

Purchase invoices, purchase credit notes, and other payments booked straight against a bank account.

Sage can filter a list down to the records with nothing attached, so the search is exact and cheap.

Sage returns only the records with nothing attached, so all 600 are documents you are chasing rather than ordinary traffic.

Deleted and voided documents are skipped.

Only the payment side of a bank entry is chased.

Attached to the purchase invoice, credit note or payment it belongs to.

Sage addresses an attachment by the record it belongs to, so it has nowhere to put one that belongs to nothing yet. The file stays approved in BilagPilot until the transaction exists.

Sage stores several, and would store the same file twice, which is why BilagPilot checks name and size against what is already attached before sending.

A document already attached under the same name and size is not sent again.

By design. Your ledger is only ever added to, never changed.