Developers modifying Sales Order line item custom fields via QBXML hit a parse error when the request declares an outdated QBXML version instead of a current one.
QuickBooks Web Connector reports "Authentication failed" with a 404 error when a WCF service endpoint omits required contract attributes that the connector depends on.
QuickBooks Enterprise throws an XML parsing error when customer names contain em dashes or accented characters imported through the PHP Web Connector devkit.
Developers connecting custom Rails apps to QuickBooks Online via qbXML hit a "Failed to notify third party" error caused by GoDaddy SSL and rDNS limitations.
Developers integrating with QuickBooks Online find no API method to retrieve invoice fields for mapping, forcing them to rely on schema files or manual documentation review.
QuickBooks Desktop returns error 3180 when a qbXML InvoiceAdd request contains no line items, because the application requires at least one entry to save.
QuickBooks Desktop V3 REST API was deprecated, but Intuit offered case-by-case grandfathering for invested developers and pointed others to the QBXML SDK.
QuickBooks Web Connector users querying inventory items can hit a misleading error when the item type queried doesn't match what exists in the company file.
Developers discover that QuickBooks payroll items are locked down from the SDK, forcing workaround approaches for commission imports tied to employee pay.
A community answer explains the correct debit and credit entries when event attendees pay ahead, clarifying why the initial credit is a liability rather than revenue.
QuickBooks users back-filling early books can clear personally paid bills through a journal entry to equity, then apply the resulting credits in Pay Bills.
When integrated software sends overpayments to QuickBooks Desktop via the Web Connector, the ReceivePaymentAdd request should carry the full check amount with only the invoice portion applied.
QuickBooks Desktop requires the desktop application and the official SDK for custom integrations. There is no way to read company files directly, but in-house development is free.
Comparing Web Connector, third-party import tools, and the QuickBooks Online API for moving transactions from an internal application into QuickBooks Pro.
QuickBooks SDK users who need to remove list objects like employees or customers can use the ListDel request rather than simply marking items inactive.
QuickBooks cannot accept third-party network connections on its own, so remote RSSBus integration requires a helper application running alongside the company file.
Developers using the QuickBooks SDK find that blank or description-only invoice lines vanish during modification unless only the transaction line ID is passed for untouched rows.
Submitting multiple invoice numbers in a single QuickBooks query causes the entire batch to fail if even one number has no matching record in the company file.
Developers connecting to QuickBooks Merchant Services hit an ARSC262 error when the CSR common name is not in the required applogin:hostname format or includes an email address.
Custom web applications running under IIS cannot connect to an already-open QuickBooks company file due to session and GUI limitations in the QBXML SDK.