QuickBooks Missing Receipt Software: Native Requests vs Dedicated Chasing

Requests for more information is the relevant feature, and it is more capable than most write-ups suggest. From Intuit’s help article, last updated 5 August 2026:

Availability of the surrounding AI is not uniform, and this is the part most likely to be out of date by the time you read it. Intuit’s UK material describes Intuit Intelligence as available to UK QuickBooks Online Accountant customers, and Intuit’s Australian material describes Intuit Accountant Suite — which includes Intuit Intelligence — being made available to Australian firms to trial from February 2026. Intuit also notes that while it works in all supported languages, some AI output is English only, and that some capabilities have been limited to admin users.

Rather than reproduce a country matrix that will drift, the reliable check is in-product: open a client’s bank transactions and look for the Requests column. If it is there, you have it.

Given all of the above, what is actually left? Three things, and whether they matter depends entirely on how your practice works.

Every route into Requests in Intuit’s documentation goes through Bank transactions. That is the right anchor for the categorisation problem it was built for — an unexplained card payment on the feed. It is a narrower anchor than “every posted transaction in this company with no attachment”, which also includes supplier bills entered directly and journal entries that should carry supporting documentation.

QuickBooks also has no per-transaction attachment flag, so there is no native way to list the undocumented ones across a company. A tool that wants that list has to read the transactions and compare them against the attachment list itself.

This is the significant one for practices with clients who are not desk-based. Intuit is explicit: a contact you add gets “an email invite to sign in to or create a free Intuit account so they can reply from the Client Portal”, and a collaborator using Requests for the first time is “asked to create or sign in to a free Intuit account”.

Free is not the same as frictionless. Every account creation is a step where a request stops. If your clients are trades, food and drink, or landlords with three properties and no interest in your software stack, this is where the process actually fails — not in the wording of the email.

Requests lives inside a client’s QuickBooks company. A practice with sixty clients has sixty Requests lists. Intuit scopes an OAuth approval to a single company file as well, so anything connecting programmatically inherits the same shape. There is no native cross-client view of “every client who still owes me paperwork this month”.

For a lot of QuickBooks-only practices the honest answer is that Requests is enough and you should not buy anything. That is a real recommendation, not a rhetorical one.

The deciding question is narrow: over the last three months, did more requests fail because the reply was incomplete, or because there was no reply at all? Intuit has built well for the first. The second is a cadence-and-access problem, and that is what a dedicated chasing tool is for. If you are unsure, measure it for a fortnight before spending anything.