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.
Developers deploying custom QuickBooks-connected applications hit a "COM class factory" error when the required QuickBooks integration components are missing on the target machine.
QuickBooks rejects customer imports that include class assignments when class tracking for names is disabled. Enabling the preference resolves the error immediately.
QuickBooks Desktop errors -6210 and -6120 block company file access in multi-user mode. Here is how to resolve the hosting and connection issues behind them.
Developers using the IPP .NET Dev Kit can query QuickBooks Desktop customers by created-date range using specific query properties rather than relying solely on CDCAsOf.
Developers building QuickBooks integrations hit validation errors when updating customers via newly constructed objects instead of retrieving them first.
QuickBooks Desktop Error H505 occurs when the computer storing the company file is not configured to host multi-user access. Here is how to resolve it.
QuickBooks Desktop may throw Error PS032 or PS077 during payroll updates when subscription details, program files, or company data are out of sync or damaged.
QuickBooks Desktop Error -6000, -77 typically stems from where the company file is stored and the folder permissions around it — here is what resolves it.
QuickBooks Desktop reports Error -6000, -82 or -6000, -83 when it finds the company file but cannot open it — here is what users are doing to resolve it.
Developers pulling customer lists through the QuickBooks Online API hit a hard 100-row limit per query, requiring pagination to retrieve full result sets.
Developers submitting invoices through the QuickBooks Online API hit an error when using numeric tax code references instead of the required TAX or NON values for US company files.
QuickBooks does not create inventory items on demand during invoice import. Developers must batch item-creation and invoice requests together via the Web Connector.
A common Web Connector integration mistake causes the connector to enqueue the same customer or transaction repeatedly, creating unlimited duplicates on every sync.
Developers building SOAP web services for the QuickBooks Web Connector hit a parse error when the queue is empty; the fix lies in the authentication response.
QuickBooks Desktop users encountering Bank Feeds errors OL-301 or OL-393 can resolve connection failures by refreshing account links, updating software, or repairing file damage.