A FullName filter matches case-insensitively, as given or with its spaces collapsed, against the name as stored, and QuickBooks stores a name with its inner spacing

Observed 2026-09-29 on QuickBooks Enterprise Solutions 24.0 (US), reporting qbXML 17.0.

A FullName filter on CustomerQueryRq ignores case and trims the filter's ends. QuickBooks then matches the filter either as given or with each run of spaces collapsed to one, and compares that with the name as it is stored. When QuickBooks stores a name it trims the ends but keeps the spacing inside it, so a name added with two spaces between two words is stored with both. Intuit's reference does not say how a FullName filter compares.

Against a customer stored as WF Real 085202, each of these filters found it (spaces written as ·):

Text
··WF·Real·085202··   0, found
wf·real·085202       0, found
WF··Real·085202      0, found
WF···Real·085202     0, found

Against a customer stored with a double space between its first two words, filters with exactly two spaces there found it, in either case. Filters with one space there, three spaces there, double spaces between every word, or no spaces at all answered the usual 500 Warn: not found.

What to do

To look a record up by the name your application sent, send that name as it was sent, or trimmed. Do not normalise inner spacing before the lookup: a single-spaced filter misses a double-spaced stored name. Case does not matter.

Not observed

  • Line breaks, tabs or non-breaking spaces inside a name.
  • Sublevel names such as Parent:Child.
  • Filters other than the top-level FullName of CustomerQueryRq, such as NameFilter or a FullName inside a reference.

Error codes on this page

QuBe Sync is a JSON API for QuickBooks Desktop that is built on what these findings show.