A query that looks a record up by ListID, FullName or TxnID answers 500 Warn when there is no such record, not 1 and not an error
Observed 2026-09-18 on QuickBooks Enterprise Solutions 24.0 (US), reporting qbXML 17.0.
A query that looks a record up by an exact key (ListID, FullName or TxnID) answers statusCode="500", severity Warn, with no *Ret, when there is no such record. It is not status 1, "did not find a matching object", and not an error such as 3120. The message quotes the key that was not found. This held for CustomerQuery, VendorQuery, ItemQuery, StandardTermsQuery and InvoiceQuery.
By ListID:
<CustomerQueryRq>
<ListID>80000001-1234567890</ListID>
</CustomerQueryRq>
<CustomerQueryRs statusCode="500" statusSeverity="Warn" statusMessage="The query request has not been fully completed. There was a required element ("80000001-1234567890") that could not be found in QuickBooks." />
By TxnID:
<InvoiceQueryRq><TxnID>4EF9-1790716999</TxnID><IncludeLineItems>true</IncludeLineItems></InvoiceQueryRq>
<InvoiceQueryRs statusCode="500" statusSeverity="Warn" statusMessage="The query request has not been fully completed. There was a required element ("4EF9-1790716999") that could not be found in QuickBooks." />
A TxnID that is not shaped like one at all, nope, got the same 500 Warn quoting nope. QuickBooks does not check a TxnID's form first, so there is no 3000 for a malformed one. A ListID inside a filter, such as a CreditMemoQueryRq's AccountFilter, also answered 500 Warn.
What to do
Read a 500 Warn on a query by key as "no such record", not as a failure, and do not assume only 0 and 1 mean success. Code that treats every non-zero status as an error, or knows only 0 and 1, will mishandle it.
Not observed
- A query with several keys where some exist and some do not.
- Filters other than
AccountFilter.
Error codes on this page
QuBe Sync is a JSON API for QuickBooks Desktop that is built on what these findings show.