Condensing a QuickBooks Desktop Canadian Edition Company File
Preparing and condensing an oversized QuickBooks Desktop Canadian edition company file, including regional considerations, multicurrency, and the information needed before starting.
QuickBooks Desktop Canadian edition files grow the same way US edition files do: years of transactions, large customer and vendor lists, and accumulated audit-trail entries push the file past the point where performance stays acceptable. Our engineers handle Canadian edition files regularly, and the condense and SuperCondense processes both work on them. There are regional considerations to account for before the file is touched, and the preparation steps matter more than they do for a typical US file.
What is different about a Canadian edition file
The Canadian edition of QuickBooks Desktop carries features that the US edition does not, and several of them affect how a condense proceeds. The most significant is multicurrency. Many Canadian businesses operate in CAD and USD simultaneously, and once multicurrency is turned on in a QuickBooks file it cannot be toggled off through the application interface. Multicurrency adds currency-list tables, exchange-rate entries, and additional gain-or-loss transactions that all contribute to file size. It also constrains what a condense can safely remove, because historical exchange rates must remain consistent with the transactions that reference them.
The Canadian edition also supports GST, HST, PST, and QST sales tax tracking. The sales-tax tables and associated transaction-level tax-detail records are tied to the transactions they originated on, so a condense that summarizes or removes older transactions must preserve the integrity of those tax-detail links. Our engineers account for this during the scoping phase.
Preparing the file before condensing
Before any condense or SuperCondense process begins, the file needs to be in a repairable, verifiable state.
-
Create a verified backup. Open the file in single-user mode and run File, Back Up Company, Create Local Backup. After the backup completes, run File, Utilities, Verify Data. If Verify reports problems, run Rebuild Data and then Verify again. A file that fails Verify should not be condensed until it is repaired; condensing a damaged file can destroy data. If Rebuild does not resolve the errors, the file may need professional data recovery before condensing is safe.
-
Capture the Product Information screen. With the file open, press F2 (or Ctrl+1) to bring up the Product Information window. Note or screenshot the file size, the total lists counts (customers, vendors, employees, items), the total transaction count, and the target count. These numbers establish a baseline and help our engineers scope the job accurately.
-
Record the first transaction date in the file. Open the Account list or run a QuickReport on the Checking account sorted by date, ascending, to find the earliest entry. This date determines how much history is available to condense.
-
Decide on a cutoff date. The cutoff is the point before which transactions will be summarized or removed. Choose this date carefully. Once older transactions are condensed, the detail behind them is gone. Common cutoff choices are the start of the current fiscal year or a date aligned with CRA retention requirements.
Information our engineers need to scope the job
To provide a quote and turnaround time for a Canadian edition condense or SuperCondense, our engineers need the following:
- The QuickBooks edition and year (Pro, Premier, or Enterprise)
- The company file size
- The Product Information screen (F2) showing list and transaction counts
- The first transaction date in the file
- The desired cutoff date
- Whether Rebuild and Verify currently pass
- Whether multicurrency is in use
- The inventory item count, if the file tracks inventory
- The building or job count, if job costing is used
- The Admin password for the file
How the process works
Once the file is evaluated and scoped, the condense itself is performed on a secure copy. The file is uploaded through an encrypted channel, and our engineers run the condense or SuperCondense against it with the agreed cutoff parameters. The processed file is then returned for the customer to restore and review.
Signs the condense worked
After restoring the condensed file, press F2 and compare the new file size and transaction counts against the baseline captured before the process. The file should open normally, Verify Data should pass without errors, and the retained period (everything after the cutoff date) should contain full transaction detail. Reports for the current and prior fiscal periods should match what was in the original file.
When the problem runs deeper
A condense reduces file size, but it does not fix structural damage, negative quantity-on-hand inventory errors, or a corrupted transaction log. If the file fails Verify before condensing, that damage must be addressed first. Similarly, if the goal is to produce a date-limited copy for a CRA audit rather than to shrink the working file, a Period Copy is the appropriate service rather than a condense. Our engineers will flag this during scoping if the situation calls for it.