QuickBooks Desktop backdated invoices slow? Check FIFO first

Quick answer

If QuickBooks Desktop Enterprise is fast on current date inventory invoices but becomes very slow when you backdate them, test FIFO before assuming the server or Windows is broken. In our case, FIFO on made some backdated invoices take tens of seconds or more than a minute. FIFO off made the same kind of entries fast.

The practical workaround was to record the exact FIFO start date, make a full backup, turn FIFO off for the backdated invoice batch, then turn FIFO back on with the exact same start date. Intuit states that QuickBooks recalculates all inventory related transactions starting on the FIFO date when FIFO is enabled again.

What the problem looked like

Current date inventory invoices were fast. Change the date back only a few days and some invoices suddenly took tens of seconds to save. A few tests took more than a minute.

The quantities were not large. We reproduced long waits with only one or a few units on the invoice. Some items with plenty of stock were slow. Other items with plenty of stock were nearly instant. One negative stock case took about 25 seconds, while a positive stock item took much longer.

The delay appeared while QuickBooks showed Record Transaction. The rest of QuickBooks did not feel generally slow.

What we tried before finding the cause

We did not jump straight to FIFO. We first treated it like a normal QuickBooks performance problem.

Verify and Rebuild were run multiple times. The company file verified clean afterward, but the backdated invoice delay remained.

We created and restored a portable company file. Intuit says that opening a restored portable company file automatically reindexes the data and can fix some data issues. In this case, it did not remove the FIFO delay.

We tested with a fresh Windows user profile. No meaningful change.

We later rebuilt the Windows Server environment itself. The same company file still showed the same behavior. That ruled out the original Windows installation and server build as the primary cause.

We also tested the file on a separate, much faster machine. The faster machine did help. Some waits were shorter. But the problem did not disappear. Backdated FIFO entries could still take around 40 seconds or more than a minute. Faster hardware improved the symptom. It did not remove the trigger.

We did not test an Accountant's Copy. Intuit documents Accountant's Copy as a workflow for an accountant to review and change the books while the company keeps working. It is not documented as a repair or performance tool. Intuit also requires Enterprise users with Advanced Inventory to turn those Advanced Inventory features off before creating an Accountant's Copy. Once FIFO itself had already been isolated, an Accountant's Copy would not have been a clean performance test.

How we proved FIFO was the trigger

The useful test was simple.

1. With FIFO on, save the exact backdated inventory transaction and time it.
2. Turn FIFO off in a controlled copy or maintenance window.
3. Repeat the same kind of backdated transaction.
4. Turn FIFO back on using the exact original FIFO start date.

With FIFO on, the backdated transactions were slow. With FIFO off, the backdated entries became fast. After FIFO was restored, QuickBooks returned to the same FIFO behavior.

That same pattern was reproduced on more than one machine, including after the server was rebuilt. At that point the main question was no longer whether Windows, storage, RDP, or the server was broken. The delay followed the FIFO setting.

Why some items were much slower than others

FIFO was the switch that enabled the slowdown, but it did not make every item equally slow.

One ordinary inventory part with positive stock took well over a minute. Another ordinary inventory part with plenty of stock saved in about two seconds. Another positive stock item was almost instant. Another positive stock item took around 40 seconds. An item with negative stock took about 25 seconds.

So current quantity on hand did not predict the wait. Negative inventory was not required. Assembly status did not predict it either because ordinary inventory parts could also be very slow.

The strongest pattern was the exact item and its history. When an already slow item was moved farther back in time, the wait generally became worse.

The FIFO Cost Lot History by Item report helped explain why. Some items had a simple history. Other items had cost lots that were later consumed by many transactions, including Build Assembly activity. A backdated sale can change which older cost lot should be consumed first. That can affect later transactions that previously used those units.

Intuit does not publish the internal save algorithm, so we are not claiming that QuickBooks follows one specific recalculation routine on every file. What we can say from the testing is that the delay followed FIFO, varied heavily by item history, and often became worse as the transaction was moved farther back.

What the reports told us

Opening and using reports inside QuickBooks stayed fast. Inventory reports, item history and FIFO reports could be opened and navigated without the kind of delay we saw when saving a backdated invoice.

Exporting those reports to Excel was a different story. Depending on the report, the export could take roughly five to fifteen minutes. The detailed FIFO Cost Lot History report was one of the slowest and could take around fifteen minutes to finish exporting.

That distinction matters. The company file was not generally too slow to read or report from. QuickBooks could display the information quickly. Turning a large detailed report into an Excel workbook took much longer. We treat that as a separate observation, not proof of the invoice delay by itself.

What the item history showed

The exported inventory history also showed periods of negative quantity on hand for several finished goods.

In one reproduced case, a sale pushed an item below zero and later Build Assembly transactions brought the quantity back up. That is worth correcting because Intuit warns that negative inventory can affect inventory value and cost of goods sold.

But negative inventory was not the main explanation for the save time. A known negative stock test took about 25 seconds. Positive stock items ranged from almost instant to more than a minute.

The cost lot report was more useful when we looked at the full chain. Some inventory lots were later used by many Build Assembly transactions. Those later dependencies help explain why the exact item history matters more than the number of units on the new invoice.

How to test your own file

Do this on a backup or disposable copy first.

1. Write down the exact FIFO start date. Take a screenshot of the setting as well.
2. Make a full QuickBooks backup.
3. Pick one slow backdated invoice and record the exact item, full item path, quantity, date and customer.
4. Time that transaction with FIFO on.
5. Test the same item with a current date.
6. Turn FIFO off and repeat the same backdated test.
7. If the delay disappears with FIFO off, you have strong evidence that FIFO is the trigger in that file.
8. Turn FIFO back on using the exact original start date.
9. Let QuickBooks finish the recalculation completely.
10. Run Verify Data once.

Intuit states that when FIFO is turned off, QuickBooks goes back to average cost. Intuit also states that when FIFO is enabled, QuickBooks recalculates all inventory related transactions starting on the FIFO date entered.

FIFO off, enter the batch, FIFO back on

For a controlled backdated batch, this is the workaround we would use.

1. Record the exact FIFO start date.
2. Take a fresh full backup.
3. Have the other users stop inventory work if practical.
4. Turn FIFO off.
5. Enter only the backdated invoices that are being held up by the FIFO delay.
6. Do not mix unrelated builds, inventory bills, item receipts, quantity adjustments, transfers, or other inventory changes into the same window unless there is a real business reason.
7. Turn FIFO back on using the exact original FIFO start date.
8. Leave QuickBooks alone while it recalculates. Do not force close it because it looks busy.
9. Run Verify Data once the recalculation is finished.
10. Review Inventory Valuation, Balance Sheet, and Profit and Loss. Make sure the changes match the invoices that were entered.
11. Take another backup after FIFO is restored and the file verifies clean.

The reason this works is documented by Intuit. FIFO off means QuickBooks is using average cost. FIFO back on means QuickBooks recalculates all inventory related transactions from the FIFO start date you enter. So an invoice entered while FIFO is off is not permanently left on average cost if it falls inside the recalculation period after FIFO is restored.

The exact FIFO date is the critical control. Do not guess it. Do not move it forward to make the file faster.

Could other work continue while FIFO is off? Non inventory activity is not what the FIFO setting is controlling, so technically normal non inventory work can continue. We still prefer a quiet maintenance window. Keeping the change limited to the intended invoice batch makes it much easier to verify the result and much easier to restore the backup if anything looks wrong.

While FIFO is off, do not treat Inventory Valuation, Balance Sheet inventory values, or Profit and Loss cost of goods sold as final. Intuit specifically says those reports change when switching between average cost and FIFO.

If the wrong FIFO date is entered, QuickBooks is interrupted during recalculation, or the reports do not look right afterward, restore the backup from before the switch instead of making a chain of corrective changes in the live file.

What not to do

• Do not keep running Rebuild after Verify reports no data problems just because the save is slow.
• Do not assume a portable company file will fix the problem. In our case it reindexed the data and the FIFO delay remained.
• Do not rebuild Windows or replace the server first when the delay clearly follows FIFO. We rebuilt the server and reproduced the same behavior elsewhere.
• Do not leave FIFO off permanently if the company uses FIFO for accounting.
• Do not move the FIFO start date forward as a speed shortcut.
• Do not rely on an Accountant's Copy as a performance repair step. That is not what Intuit documents it for.
• Do not judge the cause from current quantity on hand alone. Positive stock items can still be very slow.

If turning FIFO off makes no difference, then investigate the server, storage, antivirus, database services, multi user load and the company file itself. Those are real causes of QuickBooks slowness. They were simply not the cause of this case.

Common questions

Why are backdated inventory invoices slow when FIFO is on?

In our reproduced case, the slowdown followed FIFO. The exact wait depended heavily on the item and its history. Some backdated items saved in a couple of seconds while others took tens of seconds or more than a minute.

Will Rebuild fix it?

It did not in this case. Verify and Rebuild were run multiple times and the file verified clean, but the backdated FIFO delay remained.

Will restoring a portable company file fix it?

It did not in this case. The portable file process reindexed the data, but the delay still followed FIFO afterward.

Will a faster server fix it?

A faster machine helped some timings, but it did not remove the problem. We also rebuilt the Windows Server environment and the behavior remained.

Can FIFO be turned off for the batch and then turned back on?

QuickBooks Desktop Enterprise supports turning FIFO off and enabling it again. Intuit states that FIFO off returns inventory valuation to average cost and that enabling FIFO recalculates all inventory related transactions from the FIFO start date entered. The exact original date must be preserved.

Is negative inventory required for the slowdown?

No. Negative inventory is an accounting issue worth correcting, but positive stock items also showed long waits in our testing.

Why was Excel export slow when the reports were fast inside QuickBooks?

We saw reports open and navigate quickly inside QuickBooks, while large exports to Excel took roughly five to fifteen minutes. That export behavior was real, but we do not treat it as proof of the invoice save delay.

Intuit documentation

• FIFO options in QuickBooks Desktop Enterprise
• Create and open portable company files in QuickBooks Desktop
• Create an Accountant's Copy in QuickBooks Desktop
• Verify and rebuild data in QuickBooks Desktop
• Fix negative inventory issues in QuickBooks Desktop
• QuickBooks Desktop company file performance checks

Related guides

• What affects QuickBooks Desktop performance
• Serial and lot tracking in QuickBooks Desktop
• Single user and multi user mode in QuickBooks