The lost document nightmare: when the purchase is not recorded on time
Maria, manager of an office supplies distributor, was reviewing her monthly reports when she noticed an alarming discrepancy. Her profit margins on the "Office Share" product did not match her projections. Upon investigating, she discovered that a purchase of 50 units made three weeks earlier had never been recorded in the system. The document had been misplaced on her assistant's desk, and now there were sales recorded for products that, according to Odoo, did not technically exist in her inventory. Worse still, the calculated cost of sales was incorrect, affecting her financial statements. This situation, common in many companies, can be resolved systematically.
The problem of late recording and its impact on costing
When a product receipt is not recorded on its actual date, the system calculates costs based on incomplete information. This distorts the average cost of your products and affects the accuracy of your inventory and profit reports. Not knowing about that "ghost" purchase, the system assigns incorrect costs to subsequent sales.
Applied example: At Maria's company, they had 10 units of "Office Share" at $800 and received 10 more at $500, setting an average cost of $65. They then sold 10 units at that cost. However, in between, an unrecorded purchase of 1 unit at $50 had occurred. When selling those 10 units, the system used $65 as the cost, when the real average should have been $64.29 considering the missing purchase. This difference, though small per unit, multiplies across hundreds of transactions, generating significant accounting errors. Companies working with Ganemo implement controls to prevent these discrepancies from the start.
Step 1: Record the purchase with the correct date
The first step is to create the product receipt that was missing. In Odoo, you normally validate a receipt and the system assigns the current date and time as the "effective date". But for retroactive corrections, you need to modify this date so it matches the real moment the transaction took place.
Use case: Maria opened her pending purchase order and validated it, but the date shown was the current one, not the one from three weeks earlier. When she tried to edit it directly, the system did not allow it. Following the standard process, she used the unlock function (from the gear icon on the transfer), adjusted the date to "12:30 PM" on the corresponding day, and set the exact time with seconds when needed. This way, the receipt appeared at the correct point in the inventory timeline. This level of precision is crucial for companies that, with Ganemo's support, maintain flawless audits.
Step 2: Understand how the unit cost changes
When you enter a new product with a value different from the existing average, the average unit cost is automatically recalculated. This affects all transactions after that date, since the system must use the new average to value outgoing stock.
Implementation story: After correcting the date, Maria reviewed the inventory valuation report. The calculation was clear: initially $1,300 in value for 20 units ($65 each). By adding 1 unit at $50, the total became $1,350 for 21 units, giving a new average of $64.29. Therefore, the 10 units sold afterward should have been valued at $642.86 total, not the $650 shown in her old reports. This automatic cost correction is a strength of Odoo that experts like Ganemo help you take full advantage of.
Step 3: The retroactive cost update (crucial step)
Changing the date does not automatically update transactions already recorded. You must run a retroactive recomputation so the system revalues all affected moves from the correction date onward.
Realistic example: Maria selected the "Office Share" product and, from the corrected receipt date, ran the "Recompute average valuation" action. She confirmed the process in the wizard that appeared. When finished, she verified that her sale now showed the correct value of $642.86 and that the product's current unit cost was $64.29, ready for future transactions. For companies with hundreds of corrections, Ganemo recommends and implements bulk solutions that streamline this process.
When you need bulk tools (third-party module)
Odoo lets you move dates natively through unlocking, but bulk retroactive cost recomputation for multiple products or moves requires an additional module. This is essential when you have many pending corrections.
Business situation: Imagine a retail chain discovers that, due to a system error, 200 receipts for different products were not recorded in the previous month. Correcting each one manually would be unfeasible. With the bulk cost update module, they can select all affected transactions and recompute in a single process, ensuring consistency and saving hours of work. Ganemo facilitates the acquisition and implementation of this module for clients with scalability needs.
Conclusion: recovered precision, lessons learned
Correcting receipts with past dates is more than a technical adjustment; it is about recovering the reliability of your financial information. By mastering these steps (recording with the correct date, understanding the new costing, and retroactive updating), you turn errors into opportunities to strengthen your internal controls. Implementing these practices with the support of an expert partner like Ganemo ensures that your Odoo not only records transactions, but tells the real story of your business, second by second, with unwavering accuracy.