Quickbooky is an independent news publication. Nobody at this desk works for Intuit Inc., and the two have no relationship of any kind — we cover QuickBooks the way a newspaper covers a company: from the outside.
QuickBooks and QuickBooks Online are trademarks of Intuit Inc., used here only to identify the software being covered. What you will read is journalism and information — not accounting, tax, or legal advice.
Sync applications pushing invoices into QuickBooks Desktop Canada Edition fail with error 3140 when they send US-style sales tax item references instead of Canadian tax codes.
Developers looking to pull structured data from QuickBooks QBM files won't find an embedded database, but several integration pathways can expose records as SQL tables.
QuickBooks payroll users working through the Form 941 interview need to know when Schedule B applies and how COBRA premium assistance credits are reported on quarterly returns.
Developers successfully sync accounts and customers to QuickBooks Desktop, but invoices silently fail to appear with no error returned by the application.
QuickBooks Desktop blocks external applications from automatic login during integration setup, requiring a manual permissions reset through Integrated Applications preferences.
QuickBooks Pro users paying bills find only two payment method options. The workaround is simpler than expected and comes down to how the program thinks about funding sources.
Developers retrieving budget data through the QuickBooks Web Connector can hit an XML parsing error caused by an incorrect report type and unsupported qbXML version.
Developers connecting web applications to QuickBooks Desktop cannot get instant responses because the Web Connector architecture is asynchronous by design.
QuickBooks Desktop windows may display black backgrounds instead of their normal colors, making text unreadable. Here is how to identify and fix the cause.
Developers modifying invoices through the QuickBooks Desktop SDK hit a parsing error when XML elements like FOB and ShipDate appear in the wrong order.
Developers using the Web Connector with QuickBooks Desktop report that custom field updates for customers and employees fire simultaneously, with no built-in way to target just one entity type per sync.
Developers creating invoices through the QuickBooks Online API encounter errors when DocNumber values collide, despite no stated uniqueness requirement in the documentation.
QuickBooks Payments offers an API for processing bank-account debits, letting developers accept ACH payments on websites while using separate services for cards.
Developers pulling large record sets from QuickBooks company files via the SDK hit a wall after the first batch. The fix requires explicit iterator continuation logic.
QuickBooks developers forced onto the v3 API encounter authentication errors on query endpoints caused by URL encoding and undocumented POST requirements.
QuickBooks Web Connector error 3140 rejects invoice imports when developers mistake a missing payment-terms reference for a customer-name mismatch between two portal sources.
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.
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 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.
QuickBooks cannot accept third-party network connections on its own, so remote RSSBus integration requires a helper application running alongside the company file.