Reconcile container obligations by customer, container type and the business’s chosen identity method before importing an opening position. Keep disputed or undocumented balances visible rather than converting them into confirmed debts. Finance should review any associated deposit balance separately, and operations should approve how the first post-cutover return will reduce the correct obligation.
Understand the decision
One spreadsheet counts containers while the accounting system records deposits, and neither contains the same customer names. Some old balances may already have been resolved informally. Migration needs a reviewed bridge between physical accountability and financial records, not a copied total that staff cannot later explain.
Work through the requirements
- Match customer identities across container records
- Classify confirmed disputed and unresolved balances
- Rehearse the first return against opening obligations
| Record or decision | Why it matters |
|---|---|
| Container opening register | Lists accountable quantities by customer |
| Deposit reconciliation | Explains the financial position |
| Dispute register | Preserves unconfirmed legacy differences |
What would a passing test show?
Use these hypothetical cases in a demonstration. Mark the evidence you have reviewed, then download the checklist. Selections stay in this tab.
Watch for this failure
Do not turn an old spreadsheet quantity into a collectible amount without reviewing the underlying arrangement. Container counts and deposits may differ for valid reasons, and migration should preserve those explanations rather than force artificial agreement.
Continue the evaluation
This example defines what to verify, rather than promising a particular Odoo feature. Keep a record of the demonstrated result, configuration, unresolved gaps and person who accepts it.
Read the wider implementation guideBring your workflow to the conversation.
Discuss requirements for Beverage distribution in a business needs review. Start with your current systems, the handoff that fails and the result you need to prove.
Sources & scope
The linked product documentation is a starting point for validating your chosen version, edition, apps and hosting. The scenarios and acceptance criteria are editorial planning guidance, not customer case studies or a guarantee of built-in functionality. See how this library is prepared.
Packaging ↗Lot numbers ↗Units of measure ↗