We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
QuickBooks Desktop behaviour the reference doesn't mention
Things real QuickBooks Desktop and the Web Connector did that Intuit's qbXML reference or schema didn't predict. Each one shows the request, QuickBooks' exact answer, and what to do about it.
- When the QuickBooks the Web Connector starts never finishes opening the company file, the Web Connector waits on "Connecting to QuickBooks..." with no timeout and calls nothing, blocking every entry behind it; ending the QuickBooks process gives connectionError 0x80040402
- A ReceivePaymentAdd may apply less than its TotalAmount, or nothing at all with IsAutoApply false, and QuickBooks keeps the rest as the payment's UnusedPayment
- Adding a QWC file while other entries are scheduled can throw an unhandled .NET exception from the Web Connector's scheduler, three times; Continue each time and the add completes, with the entry's password left empty
- An amount written without its decimals, such as <TotalAmount>40</TotalAmount>, is refused with 3040 though the XSD allows it; quantities and rates are taken as integers
- Two Web Connector entries on different company files both run when QuickBooks has no company open or is closed altogether, each file opened in turn; with one file open in QuickBooks, the other entry gets connectionError 0x8004040A and its request stays retryable
- An invoice's AppliedAmount comes back negative (-80.00 for an invoice paid 80.00), so BalanceRemaining is the total plus AppliedAmount, not minus
- A payment applied to an invoice, a credit applied from a credit memo, a deposit taking a payment, or an InvoiceMod changing an amount or the date moves the other transaction's TimeModified but leaves its EditSequence
- A character Windows-1252 has above 0x7F (é, ©, –, ’, a no-break space) fails the whole document with 0x80040400 when written as itself, and is stored exactly when written as a reference (é); a character Windows-1252 doesn't have is stored as its nearest match, or ?
- A ReceivePaymentAdd of TotalAmount 0.00 that only applies credits creates no payment, and answers a ReceivePaymentRet holding nothing but each applied transaction's TxnID and TxnType
- A custom field added on Customer answers with AssignToObject listing Customer and five sales forms, DataExtID 0 and DataExtFormatString "Any text", and takes values on a sales order
- A DataExtDefQuery with no OwnerID answers 1, "did not find a matching object", even when definitions exist
- A DataExtMod sets a custom field's first value on a sales order that never had one; no DataExtAdd is needed
- Deleting a payment gives the invoices it paid their balance back, and moves their TimeModified to the deletion but leaves their EditSequence
- QuickBooks declines requests its edition, preferences or subscriptions don't allow, sometimes with 3231 "not processed" for a request sent alone
- 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
- An iterated query by ListID or FullName answers 3150 for a missing MaxReturned, which the XSD forbids beside an id, so an iterator can never be combined with an id
- A JournalEntryAdd with an entry-level Memo is saved without it and answers 530 Warn, "The field "Memo" is not supported by this implementation."
- An unbalanced journal entry is refused with 3180 on add and 3170 on mod, both ending "Transaction not in balance."
- A payment's AppliedToTxnRet lists as LinkedTxn every other payment and credit applied to that invoice, in the order applied, and reads the invoice as it is now; the invoice's own LinkedTxn lists them all, and a credit memo's lists the invoice its credit went to
- A ListID is unique within its list family, not within one list or across the file - customers, vendors, employees and other names share one sequence, every item type another, each other list its own - so records in two families can hold the same ListID
- A ListMerge's merged-away record is listed by ListDeletedQuery as an ordinary deletion, with a TimeDeleted one second earlier than the merge's own answer gave, and the surviving record keeps its TimeModified and EditSequence
- An add whose *Ref names a record that isn't there answers 3120 when the ref gives a ListID, and 3140 when it gives a FullName
- TimeModified is local wall-clock time with the standard-time offset all year (-08:00 in Pacific daylight time), and a modified-date filter reads an offset the same way, so a TimeModified sent back as FromModifiedDate finds its own record
- A NameFilter compares with the record's full name, so Contains "foobar:a" finds the job "foobar:a job for foobar", and it ignores case
- 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
- A ReceivePaymentAdd whose PaymentAmount is more than the invoice's balance is refused with 3210, "You cannot pay more than the amount due.", and nothing is saved
- A ReceivePaymentQuery answers what each payment was applied to (AppliedToTxnRet) only with IncludeLineItems true
- A ReceivePaymentAdd without a RefNumber saves a payment with no RefNumber, while an InvoiceAdd without one is numbered
- An item add with no AccountRef answers 3180 "A posting account must be specified.", but with an empty <AccountRef/> it answers 3140 for Account ""
- QuickBooks Desktop refuses onError="rollbackOnError" for the whole document, though the XSD allows it
- A QWC file with RunEveryNSeconds leaves the Web Connector's Every_Min column blank rather than showing "Real Time", and a postponement in the authenticate answer still holds the entry to that delay
- A Mod with an out-of-date EditSequence is refused with 3200 and still answers the record as it stands, its current EditSequence included
- With onError="stopOnError", QuickBooks answers every request after the first failure with 3231 instead of leaving it out
- A journal entry's debit and credit lines come back in the order they were entered, not every debit line before every credit line
- A payment's UnusedCredits is the credit the customer's credit memos still have when the payment is read, whether or not the payment applied any
- Voiding an invoice that a payment paid in full succeeds, and the payment stays with its whole amount unused
- Voiding an invoice keeps it, sets its amounts and its lines' quantities to zero, marks it paid, and puts "VOID: " in front of its memo
- A second QWC file with the same AppName becomes a cloned Web Connector entry ("App-1") whose scheduled runs sent the first entry's saved password; a per-file AppUniqueName keeps each entry apart
- With unattended access granted, the Web Connector opens the company file itself when QuickBooks is closed, runs the session and exits it, so a closed QuickBooks is not a connection error for that app