Separate item identity from opening balances, test retries and reconcile quantity and value before approving a stock migration.
The spreadsheet says “Brake Cable”, the old billing system says “Cable Brake”, and the carton label uses a supplier code. Import all three as new products and your new inventory system may begin with three identities for one item. A clean-looking opening balance can hide that mistake until the first purchase or sale.
An opening-stock migration needs two separate decisions: which item each row represents, and what quantity and value belong to it at the cutover. For a Nepal distributor moving into a business system, separating those decisions makes the result easier to check and correct.
Set the boundary before preparing the file
Choose a cutover date and time, the warehouses included and the source records to freeze. Explain who records receipts and dispatches occurring after that point. Without this boundary, a counted delivery can enter both the opening stock and a new receipt.
Keep the original file unchanged. Work from a versioned copy with a named owner. Record the unit used for each item, and distinguish a quantity from a carton count. A supplier’s product description is useful evidence, but it should not automatically become your permanent item identifier.
Illustrative planning scene with conceptual software screens; not real staff or client evidence.
Resolve the item identity before loading balances
Build a mapping between the old code and the approved new item code. Put uncertain descriptions into a review list. Similar names can describe different sizes or models; different names can describe the same product. Ask the storekeeper to confirm the physical specification when the spreadsheet is insufficient.
ERPNext’s official Data Import guide describes CSV/Excel templates and import validation. Its separate Stock Reconciliation guide includes an opening-stock purpose with item, warehouse, quantity and valuation fields. Those are useful implementation references; they do not establish WorkSphere’s import format or behaviour.
| Field |
What the reviewer confirms |
| Old code and new item code |
One approved identity for the same specification |
| Warehouse and unit |
Correct location and consistent stock unit |
| Quantity and valuation |
Frozen count and approved opening valuation |
| Batch and row reference |
Traceable source version and import outcome |
The mapping table should retain the old identifier even after the new code is assigned. That gives staff a way to explain where a balance came from. Avoid renaming an item simply to make a rejected row pass: the correction must reflect the product, not merely the importer’s requirements.
Suggested decision flow. Review the actual software behaviour and approval rules before implementation.
Prove quantities and values with a small sample
Consider a hypothetical Pokhara bicycle-parts distributor. At the frozen cutover it holds forty brake cables valued at an approved illustrative NPR 150 each, and twenty light brackets valued at NPR 250 each. Their opening values are NPR 6,000 and NPR 5,000, for a combined NPR 11,000.
HYPOTHETICAL / approved opening valuation / NPR. No tax or costing method is selected. Item-level quantities and values must also reconcile.
This example uses an already reviewed opening valuation. It does not select a costing method, establish Nepal accounting treatment or calculate tax. Ask the accounts reviewer to confirm the actual valuation basis and opening-ledger treatment before a production import.
Reconcile both quantity and value. Sixty pieces is a useful total here only because both rows use pieces; adding kilograms and pieces would not produce a meaningful control total. Retain item-level checks even when the overall value agrees, because an overstatement in one row can offset an understatement in another.
Conceptual illustration of the underlying decision; no measured outcomes or exact figures represented.
Make retries safe before the first production run
A timeout is not proof that nothing was imported. Check the recorded result before pressing the button again. A suggested implementation gives the batch a stable identity and retains row outcomes, so a repeated submission of the same intended opening balance can be recognised.
This property is often called idempotency: retrying the same intended operation does not create an additional business effect. Do not assume that a product provides it. Test its actual behaviour with an interrupted sample, and agree how corrected files differ from exact retries. An approved correction may need a new version and a controlled adjustment, rather than silent replacement.
Hypothetical workflow dashboard; not a live WorkSphere screenshot. 40 + 1 + 1 = 42. Held rows are not posted opening stock.
The conceptual review panel shows forty approved rows and two held rows from a hypothetical forty-two-row file. A row on hold has not become opening stock. The import owner needs an explicit answer for every row before declaring the migration complete.
Reconcile and sign off the cutover
Use a trial environment first, then compare the result with the frozen source and physical count. Verify item identity, warehouse, units, quantity, valuation and any batch or serial references that apply. An importer saying “completed” is not the same as the business approving the result.
Illustrative review scene; any screen shown is conceptual, not a live product screenshot.
A completed import message is not the business reconciliation.
For the live cutover, retain the source version, mapping, accepted rows, rejected rows, resulting transaction references and reviewer approval together. If opening quantities are posted through one workflow, do not also load the same opening value through an unrelated transaction without checking its accounting effect.
Prepare one real receipt and one dispatch after cutover, and verify that the balances move from the approved opening position. This checks continuity between migration and normal work. It is a bounded acceptance exercise, not proof that every future transaction will be correct.
ERPNext Data Import
ERPNext Stock Reconciliation