FIFO Adjustment Invoice was generated and the root cause is unknown.

1. On the FIFO Adjustment Invoice, navigate to one of the Products in table view. Sub-Table Inventory, and review the FOB. If there is a change to the FOB, then that is likely the cause of the adjustment. Further investigation can be completed to determine which Purchase Trans caused a change in FOB.
​
2. Check if the Product's Wholesale Units Per Case has been changed recently. WUPC is a virtual field from the Package, but it can still be viewed in the Product audit.
​
3. Check System Setting 3245. This was a change as of Q4 2024 that changed all databases from 24 months to 12 months. This is unexpected for many customers who did not see the release note, so a FIFO Adjustment would be also unexpected if this is the cause.
​
4. Check whether or not the Product Type has been updated from Track inventory = True to False, or False to True. This would cause an adjustment for every unit that was on Purchase Trans for every Product under that Product Type.

FIFO- First In, First Out. Used in the context of picking the oldest products first.

Layer- Group of Products in inventory that are costed the same

General ledger (GL) Impact: All FIFO Adjustment Invoices will build a related Journal Entry to account for the value changes.Most of the time, FIFO Adjustments will only impact the related Inventory Account (set in Inventory Account Maps) and a COGS Account (set in Income Account Maps). There should never be an impact to Accounts Receivable. if there is, then there is a misconfiguration.