Condensing an Enterprise File That Runs Advanced Inventory With FIFO Costing

The built-in condense refuses Enterprise files on Advanced Inventory with FIFO costing; this playbook maps the safe route to a smaller, faster file.

A QuickBooks Enterprise company file that runs Advanced Inventory with FIFO costing is a combination the built-in condense utility will not accept. The tool refuses the job outright, and no preference or setting changes its mind. This playbook explains the refusal, then maps the route we use to shrink such a file while its FIFO valuation layers, assemblies, and site quantities survive.

Why does the built-in condense refuse the file?

Condensing collapses dated transactions before a cutoff into summary entries that preserve balances. FIFO costing breaks that assumption. Every unit in stock carries a cost from a specific purchase, held in valuation layers the program consumes in date order when you sell or build. Collapse the purchase history and those layers strand, leaving stock values that drift without any error message.

Advanced Inventory adds a second dependency. Quantities live by site, and often by bin, lot, or serial number, tracked transaction by transaction. A summary entry cannot carry that detail.

Faced with the combination, the utility stops rather than write valuations it cannot prove. The refusal is a designed boundary, not damage in your file. Verify and Rebuild will not lift it, and neither will a fresh copy. The route past the boundary is a specialized condense, and our engineers run these jobs through our QuickBooks Super Condense service.

When is the job worth doing?

The job earns its place when the file has slowed, or when old history survives only as balances you no longer drill into. It is also a sensible step before any larger conversion project. One caution there: bin, lot, and serial tracking have no equivalent in QuickBooks Online, so treat that decision separately from the condense.

Gather the baseline before anything changes

Start with numbers you can compare against later. Record the file size and a Product Information screenshot (press F2 within QuickBooks) showing customer, vendor, transaction, and item counts, together with the date of the first transaction.

You choose the cutoff date. Pick a date before which you need account balances and inventory values but not individual transactions. A fiscal year start keeps the summary entries aligned with your reporting.

Describe the inventory profile as well: item and assembly counts, the sites in use, and whether bins, lot numbers, or serial numbers are active. The plan is built from these counts.

Which checks must pass before the run?

The file must pass Verify Data in its current condition, in single-user mode. A file that fails verify needs repair before anything else, because condensing bakes existing damage into the summary entries; our QuickBooks rebuild and verification service handles files in that state. Do not run Rebuild just to see what a damaged file does; a rebuild on damaged data can spread it.

Then check inventory health. Negative quantity on hand anywhere means the FIFO layers are already suspect, so clear it first. Run an Inventory Valuation Summary by site and reconcile the totals against the Inventory Asset account. Tell the engineer whether multi-currency is switched on, because it shapes the plan.

Last, protect the file. Take a full backup and a copy of the matching .TLG file, and store both off the machine.

The condense run

The work runs on a working copy, never the original, in single-user mode with every workstation out of the file. That makes it an off-hours job, typically over a weekend.

Transactions dated before the cutoff are replaced with summary entries that preserve every account balance. Detail from the cutoff forward stays exactly as it was.

Inventory is rebuilt in three moves. The FIFO layers behind every unit still on hand are reconstructed from surviving detail, so the next sale or build consumes cost in the right order. Assembly builds before the cutoff collapse into their summaries with component and build costs preserved. Site quantities, including bin, lot, and serial counts where you use them, are rebuilt per warehouse and reconciled against the pre-run valuation summary.

Rollback points

There are three points where a stop costs you nothing. Before the run, nothing has changed; the original file sits untouched. Immediately after the run, if the condensed file fails Verify or any reconciliation disagrees with the baseline, restore the backup and the original stays live. Keep the original, its backup, and the .TLG until the post-run reports agree with the baseline; only then retire the spare copies. Even then, keep one backup.

The checks after the run

Verify the condensed file first. Compare total assets and inventory value against the baseline; both must match. Compare the Inventory Valuation Summary site by site. Run a trial balance for a period before the cutoff; its totals must equal the old file's figures for the same period.

Then test behavior. Sell an item that draws on the oldest layer and check the cost it picked up. Build an assembly and confirm the components issued at the right layers. Receive stock at one site and sell it from another if your workflow does that. These tests prove the layers, the builds, and the site counts all survived.

What does a clean result look like?

The condensed file verifies and rebuilds clean. Its size drops, in our experience by 40 to 80 percent, depending on how many years fall before the cutoff.

Every account balance matches the pre-run file. Inventory value and quantity match by site, bin, lot, or serial where tracked. Sales and builds consume FIFO cost in the correct order. Reports before the cutoff show summary totals rather than transaction detail, and everything from the cutoff forward remains intact. A file in that state is safe to put back into daily use.

Keep going

Your Desktop doesn’t have to end when Intuit says so.

Start with the master survival guide, or jump straight to the fix you need.