QuickBooks File Integrity

Overview

QuickBooks Desktop uses a mature SAP SQL Anywhere database. The database itself can handle very large amounts of data.

File integrity problems usually come from years of use, interrupted sessions, damaged transactions, list changes, and changes made across many QuickBooks versions.

Some problems are obvious, such as incorrect inventory balances or an unbalanced Balance Sheet. Others may not appear during a QuickBooks Verify or Rebuild.

How file integrity affects QQube

QQube extracts data through the Intuit Desktop SDK. The SDK may detect errors that QuickBooks Verify or Rebuild does not report.

Important: If the SDK reports corruption, QQube cannot bypass it. The QuickBooks file must be repaired before the affected data can be extracted reliably.

Common contributing factors

• Frequent file access — Users open and close the company file many times each year. Freezes and forced shutdowns increase the risk of damage.
• Large company files
  • QuickBooks Premier files approaching or exceeding 350 MB.
  • QuickBooks Enterprise files approaching or exceeding 1.25 GB.
  • Inactive accounts, classes, names, and other lists that must remain in the file.
• High transaction detail
  • Transactions with many lines.
  • Detailed payroll and job-cost information.
  • Large volumes of time-tracking data.
• Repeated deletions and list merges.
• Many years of QuickBooks upgrades — Older files may contain data structures created by several generations of QuickBooks.

QQube also extracts more detail than most third-party applications. This may expose corruption in areas that other products never request.

First step: rebuild the QuickBooks file

Run a QuickBooks Rebuild, then reload the affected data in QQube.

If the SDK reports no corruption after the rebuild, QQube should be able to extract the available data accurately.

If the rebuild does not resolve the problem

Review the QQube synchronization log. The error message normally includes a link to the appropriate repair instructions.

Depending on the problem, you may need to:

• Run another rebuild and reload the data from scratch.
• Repair the affected transaction or list item.
• Send the QuickBooks file to Intuit or a qualified file-repair specialist.

Options for very large or older files

Consider these options when a company file contains decades of data or is several gigabytes in size.

1. Limit the extraction period. Use the Extraction Start Date to load only the years required for reporting.
2. Start a new QuickBooks file. This is commonly done at the beginning of a quarter or fiscal year.
3. Split the company file. Keep older data in an archive file and use a smaller file for current operations. A qualified QuickBooks file specialist should perform the split.
4. Move operational detail to a specialized application. Inventory, manufacturing, payroll, job-costing, and time-tracking systems can retain detailed activity while sending summarized accounting entries to QuickBooks.