A ReceivePaymentAdd without a RefNumber saves a payment with no RefNumber, while an InvoiceAdd without one is numbered
Observed 2026-10-09 on QuickBooks Enterprise Solutions 24.0 (US), reporting qbXML 17.0.
A ReceivePaymentAdd sent without a RefNumber saves a payment with no RefNumber. QuickBooks does not number received payments, while an InvoiceAdd without a RefNumber gets the company file's next invoice number.
Three payments added without a RefNumber each answered a ReceivePaymentRet that went from <TxnDate> straight to <TotalAmount>, with no <RefNumber> between, and read back the same way in later queries. Payments that did send a RefNumber kept it.
Three InvoiceAddRqs that sent no RefNumber were numbered in the file's own sequence. The first answered:
<RefNumber>11</RefNumber>
and the next two 12 and 13.
What to do
If your application needs a reference number on a received payment, send RefNumber in the ReceivePaymentAdd yourself. When reading payments, expect RefNumber to be missing and match them by TxnID instead. For invoices, a missing RefNumber continues the file's numbering, so read the number QuickBooks gave from the answer.
Not observed
- A company file whose payments were numbered by hand before.
- Sales receipts, credit memos, estimates, sales orders, purchase orders, checks, journal entries, bill payments, deposits and transfers sent without a
RefNumber.
QuBe Sync is a JSON API for QuickBooks Desktop that is built on what these findings show.