ERPNext asset management and depreciation for finance teams that own fixed assets
If your finance or operations team tracks fixed assets in spreadsheets or a separate tool, the question is whether ERPNext's Assets module can carry depreciation into the general ledger without a manual step each month. In short, the module covers asset records, depreciation schedules and the journal entries that post each scheduled amount. Teams usually implement it during a new ERPNext rollout, when they move off spreadsheets, or when they need one asset register across several companies. Each case changes the setup work, so decide early which one applies.
The setup starts with asset categories and their accounts, because each asset copies its defaults from the category. Each asset then holds one or more rows in its Finance Books table. Every row is a separate depreciation policy with its own method, salvage value, frequency in months and total number of depreciations. Finance teams often need one book for statutory reporting and another for management reporting, so confirm with your auditors and tax advisers how many books you need and which policy each one follows. ERPNext prorates the first period when an asset becomes available partway through a period, so agree the availability date convention before loading historical assets.
The month-end checks matter as much as the setup. Review the depreciation schedule against the asset register, confirm that each due Journal Entry posted to the expected accounts, and check any assets moved, repaired, capitalized or revalued during the period. ERPNext includes DocTypes for asset movement, maintenance, repair, capitalization and value adjustment, and the version-16 branch also includes shift-based depreciation, so confirm which of these your version supports before you write the procedure. Ask your implementation partner to document these checks as a close routine and to test them on migrated data before the first live period.
What the ERPNext Assets module does
The Assets module holds each fixed asset as a record, schedules its depreciation, and posts the resulting journal entries to your ledger. Around that core sit DocTypes for movement, maintenance, repair, capitalization and value adjustment, which determine how an asset's value and location change over its life.
Asset records and finance books
Each asset is a record that carries its category, cost, location and depreciation settings. Depreciation sits in a Finance Books table, where each row holds one policy with its own method, salvage value, frequency in months and total number of depreciations. Rows are copied from the asset category by default, so review them on every asset. Use a second finance book when tax or group reporting needs a different policy, and confirm which book your reports read.
Depreciation schedules and journal entries
ERPNext builds a depreciation schedule for each finance book and posts a Journal Entry for each scheduled amount when it falls due. The first period is prorated when an asset becomes available partway through a period, so the availability date drives the first charge. Check the schedule before the first run, because a wrong start date or salvage value flows into every later entry.
Asset movement and value adjustment
Asset Movement records transfers between locations, cost centers or custodians, which keeps the asset register aligned with the physical position. Value Adjustment changes an asset's value and posts the effect to accounts. Confirm with your installed version that both DocTypes exist and that your approval process covers who may move or revalue an asset.
Maintenance and repair records
Asset Maintenance schedules recurring service tasks against an asset, while Asset Repair records unplanned or completed repair work. Repair cost can be capitalized into the asset or expensed, and that choice changes the depreciation base. Agree the rule with your finance team before the first repair is booked, and confirm how your version handles each treatment.
Capitalization and shift-based depreciation
Asset Capitalization groups completed work-in-progress or purchase costs into a finished asset, so the depreciable base includes all related spend. Shift-based depreciation ties the charge to shift usage rather than calendar time, which suits machinery with variable output. Both appear on the version-16 branch, so confirm they are present in your installed release before designing around them.
How ERPNext builds a depreciation schedule and posts it
Depreciation policy lives on the Asset record itself, in a Finance Books table. Each row holds one depreciation policy: a method, a salvage value, a frequency in months and the total number of depreciations. When an asset is created from a category, these values are copied from the category by default, so the category sets the starting point and the individual asset can be adjusted. Check each asset's Finance Books rows before submission, because a schedule built from a wrong salvage value or frequency will post wrong amounts every period until it is corrected. Confirm with your finance lead how many books your organization needs, since each row produces its own schedule and its own postings.
From those settings, ERPNext builds a depreciation schedule and posts a *Journal Entry* for each scheduled amount when it falls due. The entries debit the depreciation expense account and credit the accumulated depreciation account configured on the category, so the account mapping you set up in advance determines where every month's charge lands in the ledger. Review a sample of generated journal entries against the schedule after the first run. Errors in account mapping are far cheaper to fix in the first cycle than after several periods have closed.
When an asset becomes available for use partway through a period, ERPNext prorates the first depreciation period rather than charging a full period. Confirm the available-for-use date on each asset, because it drives the first-period amount and therefore every later amount in the schedule. Assets bought in bulk or put into service late in a month are the usual source of disputes at month end, so agree the proration convention with your auditors and document it in your accounting policy before go-live. Changes to the available-for-use date after depreciation has started should be treated as a controlled adjustment, not a casual edit.
Configuration decisions before go-live
This table compares the setup decisions that are hard to change once assets are posted, with the options ERPNext documents, when each fits, and what to confirm with your auditors and tax advisers. Read it before building asset categories, so that finance books, salvage rules and capitalization are agreed in one pass rather than corrected after the first depreciation run.
| Decision | Options in ERPNext | When it fits and what to confirm |
|---|---|---|
| Asset category defaults and linked accounts | Category holds default depreciation settings, fixed asset, accumulated depreciation and expense accounts, copied onto each asset | Use one category per asset class so defaults are consistent. Confirm the account mapping and depreciation expense cost centers with your controller before creating assets. |
| Number of finance books per asset | One row per depreciation policy in the Finance Books table, each with its own method, salvage value and schedule | Use separate books when book and tax treatment differ. Confirm with your tax adviser which books are required and whether each must be reported separately. |
| Depreciation method and frequency | Method, frequency in months and total number of depreciations set per finance book, defaulted from the category | Choose the method your accounting policy specifies. Confirm the frequency matches your close calendar, since each scheduled amount posts a Journal Entry when due. |
| Salvage value rules | Salvage value entered per finance book on the asset record | Set a salvage value only where policy supports a residual estimate. Confirm the basis of the estimate and who approves changes with your auditors. |
| Shift-based depreciation | Shift-based depreciation DocType available in the version-16 Assets module, driven by usage rather than elapsed time | Use it for machines whose wear follows operating hours. Confirm the version you run includes it and agree the usage evidence with your auditors before go-live. |
| Availability date and first period | ERPNext prorates the first period from the date an asset becomes available for use | Set the available-for-use date from commissioning evidence, not purchase date. Confirm the proration convention your policy requires. |
| Capitalization of later costs | Capitalization DocType for adding costs to an existing asset after acquisition | Use it for upgrades that extend life or capacity. Agree a threshold between capitalized improvements and expensed repairs with your controller and auditors. |
| Value adjustments | Value adjustment DocType for changes to an asset's carrying value | Use it for documented impairments or revaluations. Confirm the approval steps and the journal treatment with your auditors before the first adjustment. |
Movement, maintenance, repair and capitalization in practice
An Asset Movement record changes where an asset sits, such as moving it between locations or reassigning it to another cost center or employee. It does not change the asset's value or its depreciation schedule, but it does change the reporting view, so the location and cost center on the asset record should always match what the movement shows. Finance teams need to decide which cost center should carry future depreciation, whether a transfer between companies needs a separate accounting approach, and who approves the movement.
- Location and cost center: Confirm whether depreciation expense follows the asset to the new cost center from the movement date or stays with the original one for the current period.
- Approval owner: Decide who signs off on transfers, usually the asset custodian plus a finance approver.
- Physical verification: Agree how movements are checked against a periodic asset count so records match the floor.
- Inter-company moves: Treat these as a policy question, since they can require a separate accounting entry and tax review.
- Disposal interaction: Confirm that a moved asset is not also scheduled for disposal in the same period.
Before go-live, confirm the movement treatment with your accounting policy owner and your external auditor's expectations for cost center reporting.
The Asset Maintenance record holds the planned servicing schedule for an asset, including the maintenance team, task descriptions and due dates. Planned maintenance is an operating activity, so its cost is normally expensed as incurred, not added to the asset's book value. The finance decision is therefore less about capitalization and more about how service spend is tracked, budgeted and matched to the right cost center or project.
- Task list: Define each maintenance task, its frequency and the responsible team so the schedule is auditable.
- Cost tracking: Decide whether service invoices post to an expense account or are charged to a project or department.
- Overdue handling: Set a rule for what happens when a service is missed, including who is notified and how the asset is flagged.
- Warranty alignment: Check whether a service visit is covered by a supplier warranty before the cost is booked.
- Maintenance log evidence: Keep completed maintenance records attached to the asset for audit and safety inspections.
Confirm with your finance team which expense accounts and cost centers the maintenance spend should use, and whether any servicing ever extends an asset's useful life enough to be treated as capital.
Unplanned repairs are where capitalization questions arise. An Asset Repair record captures the work done, the parts and labor, and the cost. Whether that cost is expensed or added to the asset's carrying value depends on your capitalization policy. Many policies expense routine repairs that restore an asset to its previous condition and capitalize costs that extend useful life, improve capacity or change the asset's function. The Capitalization DocType lets finance add such costs to an existing asset, so the treatment must be decided before the repair is recorded.
- Expense or capitalize: Set written thresholds and criteria for each repair type, and record the reasoning on the repair.
- Useful life impact: Decide whether a capitalized cost changes the remaining depreciation schedule and whether that change needs a documented estimate revision.
- Component treatment: Agree how major components with different lives are tracked, if your policy requires it.
- Cutoff: Confirm which period a repair belongs to when the work spans month end.
- Evidence: Keep invoices, work orders and approvals linked so the capitalization decision can be reviewed.
The accounting treatment of each repair type must be confirmed against your company's written policy and, where relevant, the applicable accounting framework before posting.
Value adjustments cover changes to an asset's carrying value that are not routine depreciation, such as impairment after a decline in recoverable value or a revaluation where your policy allows it. In ERPNext, the Asset Value Adjustment DocType records the change, the reason and the resulting value, and it affects the depreciation that follows. Because these entries can move reported profit and balance sheet values, they need a clear decision trail, not just a number typed into the asset.
- Trigger evidence: Document what prompted the adjustment, such as a physical condition review, a market valuation or a change in use.
- Method choice: Decide whether the revised value is depreciated over the remaining life or over a newly estimated life.
- Revaluation policy: Confirm whether revaluation is permitted at all under your accounting framework before enabling it in practice.
- Approval level: Set who can approve a value change and the amount above which a second approver is required.
- Reversal rules: Agree whether impairment can be reversed later, since reversal rules often differ by framework.
Before posting any value adjustment, confirm the treatment with your accounting policy owner and external auditors, since the impairment and revaluation rules depend on your reporting framework.
How the Assets rollout runs, step by step
This sequence moves the Assets module from version confirmation to a live month-end routine, with each step ending in a document that finance and the platform team can sign off before the next one starts.
Confirm the ERPNext version and deployment
The platform engineer confirms which ERPNext major version and Frappe Framework release the company will run, checks it against the supported versions list, and records how it will be deployed (Frappe Cloud, Docker Compose or bench). Asset depreciation behavior and DocType details can differ between versions, so the team checks the Assets documentation for the chosen release before any configuration begins. The step closes with a signed environment record that names the version, the hosting model and the test and production sites.
Define the chart of accounts and asset categories
Finance and the implementation consultant agree on the fixed asset accounts (asset, accumulated depreciation, depreciation expense and any disposal or impairment accounts), the cost centers that will carry depreciation, and the asset categories that group similar assets. Each category records its default finance book settings, so the choices made here flow into every asset created from it. The output is a signed category map that lists each category, its accounts, its default depreciation method and its owner.
Load and reconcile the opening asset register
The team extracts the existing fixed asset register from the current system and maps each asset to a category, location, cost center, purchase date, gross value and accumulated depreciation to date. Records are loaded in small batches, and the Data Import tool is the usual route for bulk loading, with the documentation advising only a few thousand records per import. The step closes when total gross value and accumulated depreciation in ERPNext match the source register and the general ledger balances for the asset accounts agree.
Configure finance books for each asset
For each asset that needs more than one depreciation policy, such as a tax book alongside the statutory book, the finance team sets up the Finance Books table with method, salvage value, frequency in months and total number of depreciations. Values copied from the category are reviewed rather than accepted blindly, because an asset's policy can differ from the category default. The output is a list of assets with their finance books, reviewed by the controller who owns the depreciation policy.
Run test depreciation against a closed period
On the test site, the team submits depreciation for a period that finance has already closed in the production ledger, then compares the Journal Entries ERPNext creates against the depreciation the company actually booked for that period. Prorating of the first period is checked for assets that became available partway through a month. Any difference is traced to a category default, a finance book setting or an opening value. The test run report lists each asset, the expected amount, the posted amount and the explanation for every variance.
Reconcile depreciation schedules to the asset register
Before go-live, the team compares the generated depreciation schedule for each asset with the schedule in the register and confirms the remaining book value at the cut-over date. Assets that are fully depreciated, fully impaired or disposed of are checked separately so they do not generate further entries. The step closes when the schedule totals, the remaining values and the asset account balances all agree with the signed opening register from the earlier step.
Set up the month-end checklist
Finance and the platform team write a month-end checklist that covers the depreciation run, review of posted Journal Entries, reconciliation of accumulated depreciation to the ledger, and the handling of asset movements, maintenance, repairs, capitalization and value adjustments recorded during the month. Responsibility for each check is named, and the list states what evidence each check leaves behind. The output is a month-end checklist approved by the controller, with a sample of completed checks kept for audit review.
Go live and confirm the first production cycle
The team moves the approved configuration to production, runs the first live depreciation cycle under the checklist, and verifies that the entries match the reconciled schedules. Access to asset creation, depreciation submission and value changes is limited to the roles the category map assigns. Hypercare continues until the first full month-end close has been completed and signed off. The go-live record lists the configuration version, the signed approvals and the first cycle results.
What drives effort and cost in an assets implementation
This table lists the factors that most change the effort of an ERPNext Assets rollout, why each one matters, and how to keep it manageable. Read it before asking for a quote, because the scope of your asset register and finance book design usually decides the timeline more than the software setup does.
| Driver | Why it raises effort | How to reduce it |
|---|---|---|
| Number of asset classes and finance books | Each asset category carries its own accounts and default finance book rows, and each extra book (for example tax and management) needs its own method, salvage value and schedule to be tested. | Keep categories to the groups finance actually reports on, and agree which books are required before building anything. |
| Quality of the existing register | Missing serial numbers, unclear locations, duplicate tags and inconsistent purchase dates force cleaning before import and slow reconciliation to the general ledger. | Run a physical count and clean the register in a spreadsheet before import, and assign one owner to sign off each asset class. |
| Number of companies and currencies | Each company needs its own asset accounts, cost centers and depreciation accounts, and foreign-currency purchases add exchange checks to every capitalized amount. | Confirm the company structure and base currency up front, and limit cross-company asset transfers to a short list of documented cases. |
| Integration with purchasing and projects | Assets created from purchase receipts, or capitalized from project costs, need matching accounts, item setup and cut-off rules, and each link must be tested with real transactions. | Decide which source documents create assets (purchase invoice, receipt or manual entry) and document one path per source. |
| Volume of historical assets | Opening balances for many assets with partly elapsed depreciation require accumulated depreciation and schedule dates to be entered correctly, and mistakes spread across every later period. | Load historical assets in batches, reconcile each batch to the opening trial balance, and keep the import file under version control. |
| Approval steps and controls | Asset disposals, value adjustments, transfers and capitalization often need sign-off from more than one person, and each role needs permissions and a tested workflow. | Map approvers to roles in the design phase, keep the number of approval levels low, and test the rejection path as well as approval. |
Loading the opening asset register without breaking the ledger
Load the opening asset register in controlled batches and reconcile it to the trial balance before anyone runs depreciation. The Data Import tool accepts CSV or Excel files built from downloadable templates, and its documentation advises importing only a few thousand records at a time, so a large register should be split into batches by asset category or location. Import a small test batch first, check how child table rows such as Finance Books were mapped, and keep each file so a failed batch can be corrected and re-imported without duplicating assets that already loaded. Confirm the import template version matches the ERPNext version you run in production, since templates can change between releases.
Reconcile two figures for each asset category before go-live: the gross purchase value of the assets and the accumulated depreciation carried on them. Compare the totals in the register to the Fixed Asset and accumulated depreciation control accounts in the trial balance for the opening period, and agree any difference to a named account, not a suspense balance. Ask your finance lead to sign off the reconciliation, and keep the report as evidence for the first period close. Where assets are bought mid-period or partly depreciated, confirm how the opening accumulated depreciation and the next depreciation date were entered.
Confirm that the opening schedules do not post a second set of depreciation entries. Imported assets that already carry prior depreciation need their opening depreciation recorded so the schedule starts at the correct point, and the first scheduled Journal Entry should cover only the remaining periods. Run depreciation for a single test asset in a non-production company or a copy of the site, then check the generated Journal Entries against the expected schedule and the accumulated depreciation balance. Document who is allowed to submit depreciation runs during the migration window, and freeze that step until the reconciliation is complete.
How the Assets module connects to the rest of ERPNext and your systems
The Assets module does not run alone. Asset values, depreciation and disposals post into the same ledgers, cost centers and permissions that the rest of finance uses, and the access model decides who can approve each step. Check each link below in the ERPNext version you run, because behavior differs between releases.
Purchase invoices create assets
An asset can be created from a purchase invoice or purchase receipt for a fixed asset item, so the capitalized cost traces back to the supplier bill. Confirm in your version whether the asset is generated automatically or created manually, and whether partial quantities split into separate asset records. Test a multi-quantity purchase before go-live, because one invoice line can produce several assets that each need their own depreciation settings.
General ledger and Journal Entries
Each depreciation amount is posted as a Journal Entry when it falls due, so the asset register and the general ledger must reconcile every period. Map the accumulated depreciation and depreciation expense accounts in the asset category before the first run. Ask finance to compare the asset book value report with the balance sheet at month end, and confirm how reversals and cancelled entries are treated in your version.
Cost centers and projects
Cost centers and projects on the asset determine where depreciation expense lands in management reporting. Decide whether assets are tagged to a cost center at purchase, moved later through asset movement, or assigned to a project for capital work in progress. Ask your team to confirm which dimension drives departmental P&L, because changing the tag after depreciation has started can split history across two reports.
Roles for asset approvers
Asset creation, value adjustment, disposal and movement should sit with different roles, so no single user can buy, depreciate and write off an asset. Review which roles can submit and cancel Asset and Asset Movement documents, and who can edit the finance books table after the schedule exists. Confirm the exact permissions in your version with a test user before you grant them to finance staff.
LDAP or social login for finance users
Finance users usually sign in through the same directory as the rest of the organization, so ERPNext LDAP login or a Social Login Key can control access to the Assets module. LDAP maps directory groups to ERPNext roles at each login, which means group membership changes flow into asset permissions. Confirm the group-to-role mapping for approvers, and test that a removed user loses access on the next login.
Reporting exports and audit evidence
Asset registers, depreciation schedules and disposal records are often exported for auditors and tax advisers. Confirm which asset reports can be exported in your version, which fields they include, and whether schedule details appear in the export. Store a dated export after each month-end close so that the evidence matches the ledger at that date, and check that exported files are handled under your data retention rules.
Questions finance and IT teams ask before hiring help with ERPNext assets
How much does an ERPNext assets implementation cost?
The cost depends on the scope written into the engagement, not on a list price. Self-hosting ERPNext is free under its open-source license, and the ERPNext pricing page confirms this, but the Assets setup is a services cost. The main components are discovery of your asset register, configuration of categories and finance books, data loading, testing of depreciation runs, and handover. Ask for a quote that lists each component, who performs it, and what is excluded, such as hosting, custom reports or integrations with a fixed asset register elsewhere.
What sets the timeline for an assets project?
The timeline is driven mostly by the quality of your existing asset data and the number of distinct depreciation policies. Clean registers with consistent categories move quickly, while registers that mix tax and book rules, or that lack acquisition dates and invoice links, take longer to reconcile. Other drivers include the number of companies and currencies, whether capitalization and maintenance workflows are in scope, and how many approval cycles finance needs before go-live. Ask the partner to tie milestones to a closed period so the first live depreciation run is tested.
What does the assets work need from finance, IT and auditors?
Finance owns the policy decisions: asset categories, useful lives, salvage values, depreciation methods and the accounts they post to. IT owns the environment, the ERPNext version, backups, user roles and any integration with procurement or the general ledger. Auditors should review the policy set and the reconciliation approach before go-live, not after the first year-end. Ask the partner what evidence it will hand over, such as configuration exports, test scripts and reconciliation templates, and confirm with your auditor which of these they expect to see.
Can our own team configure ERPNext Assets without a partner?
Yes, a team with ERPNext experience can configure categories, accounts and finance books, because the settings are documented in the ERPNext asset depreciation guide. The harder part is deciding the policies and testing the edge cases, such as mid-year additions, disposals and capitalized repairs. Teams that build internally should still plan a test period and a second reviewer for the depreciation journal entries. A partner is most useful when the register is large, the policies conflict, or the team has no one who has run a full period close in ERPNext.
How does depreciation change when an asset is added mid-year?
ERPNext prorates the first period from the date the asset becomes available for use, so a mid-period addition receives a partial charge. The Asset record holds the depreciation policy in its Finance Books table, and each row can use a different method, salvage value and frequency. Changes to the availability date, useful life or value after posting require care, because they can alter the schedule that has already produced journal entries. Ask your partner to document how adjustments are reviewed and reversed under your close process.
How are month-end depreciation checks run?
Month-end checks confirm that every depreciation journal entry due in the period was posted once, to the correct accounts and cost centers, and that the asset register agrees to the general ledger. Typical steps include reviewing the schedule for assets due that month, checking for failed or duplicate postings, reconciling accumulated depreciation to the ledger, and reviewing movements, maintenance and capitalization records. Ask for the checklist in writing and confirm with your finance team who signs off each step.
What should the quote for assets include?
A useful quote lists discovery, configuration of asset categories and accounts, finance book policies, data migration of the asset register, depreciation testing across at least one period close, user training and documentation. It should state what is excluded, such as custom reports, integrations and post-go-live support, and whether support is a separate retainer. Ask who performs each task and what you must provide, including data extracts, policy approvals and test users.
The month-end checks finance teams run on depreciation
The first month-end check is whether every depreciation Journal Entry scheduled for the period has actually posted. ERPNext builds a depreciation schedule on each Asset record and posts a Journal Entry for each scheduled amount when it falls due, so a missing or failed posting shows up as a gap between the schedule and the ledger. Finance should confirm that each Finance Book on each active asset has a posted entry for the period, and that the depreciation accounts and cost centers on the Asset Category still match the chart of accounts after any recent changes. Because a posting can fail silently in the background, the team should also check the scheduler and error logs before closing the period, and record the exact report or list view used so the check is repeatable.
The second check reconciles the fixed asset register to the general ledger. Compare the gross purchase amount, accumulated depreciation and net book value for each asset category against the asset, accumulated depreciation and depreciation expense accounts in the ledger, and investigate any difference before sign-off. Review assets with status changes during the month, such as those moved between locations or cost centers through Asset Movement, those under Asset Repair or Asset Maintenance, and any assets flagged for disposal or scrapping. Check that capitalized repair costs were recorded as intended and that proration was applied correctly to assets that became available partway through the month, since the first depreciation period is prorated from the available-for-use date. Exact report names and field labels vary by version, so confirm them in the installed release before writing the procedure into the close checklist.
The final step is a documented sign-off. Record who ran each check, the period, the report or query used, the reconciliation totals, every exception with its owner and resolution, and the reviewer's approval. Agree in advance how an error found after close will be corrected, for example through a reversing entry or a Value Adjustment, so that the audit trail stays intact. Decide who owns the checklist, how often it is reviewed and whether it changes with each ERPNext upgrade. If you are preparing for an external audit, ask your auditors which evidence they expect to see, since DeployOpen prepares controls and records for assessment but does not issue audit opinions.
How DeployOpen scopes and delivers an assets implementation
The sequence turns an asset register and a depreciation policy into a configured Assets module that posts correctly to the ledger and runs at month end without manual rework. Each step ends with a written output the finance and IT owners can check.
Agree the written fixed scope
DeployOpen reviews your asset classes, entities, depreciation policies, number of assets to load, integrations with procurement or the general ledger, and the people who approve each stage. The result is a written scope with deliverables, exclusions and acceptance criteria, agreed before any configuration starts. Your finance lead and the IT owner sign off on it, and any question about asset volume or source systems is settled here, not during the build.
Configure categories, accounts and finance books
DeployOpen builds the Asset Category records with their fixed asset, accumulated depreciation, depreciation expense and capital work-in-progress accounts, then defines the Finance Books each category needs, such as a statutory book and a management book with different methods, salvage values, frequencies and totals. Each finance book is tested against a sample asset so you can see the schedule it produces. The output is a configuration document listing every category, account mapping and policy, reviewed by your accountants.
Design the asset register and loading template
Before loading any data, DeployOpen agrees which fields come from your register or fixed asset listing, how serial numbers, locations, custodians and purchase invoices are referenced, and how opening balances are represented. Opening assets are separated from new purchases so their accumulated depreciation to date is not double counted. The output is a mapping sheet and a template your team confirms against a small set of real records.
Load assets in controlled batches
DeployOpen loads assets through the Data Import tool in small batches, since the documentation advises importing only a few thousand records at a time, and checks each batch against the source register before moving on. Import errors are logged and corrected in the source file rather than patched by hand in the database. The output is a load log showing record counts, rejected rows and the reason for each rejection, signed off by the asset owner.
Reconcile the register to the ledger
DeployOpen compares the asset register totals for cost, accumulated depreciation and net book value against the balances in the general ledger for each asset account and entity. Differences are traced to specific assets, purchase invoices or depreciation entries and resolved before go-live. Test depreciation runs are reviewed against an independent schedule for a sample of assets. The output is a signed reconciliation that shows zero unexplained difference or a documented list of open items with owners.
Test movements, maintenance and capitalization
DeployOpen walks through asset movement between locations and custodians, maintenance and repair records, capitalization of costs after purchase, and value adjustments, using test assets in a non-production site. The team confirms which entries post to the ledger, which only update the register, and which need an approval step. The output is a test script with expected results and the actual outcome for each case, which your finance team reviews before sign-off.
Hand over the month-end runbook
DeployOpen writes a month-end runbook covering when depreciation is run, how the generated Journal Entries are reviewed and submitted, how new assets and disposals are recorded, and the checks to run before the period closes. Each check names an owner, the report or screen to use and the expected result. Your team runs one cycle with DeployOpen observing, then owns the process. The output is the runbook and a completed handover session record.
Agree optional retainer support
After handover, you can choose a retainer for ongoing support, upgrades and periodic review of depreciation policies, or keep the work with your own team. The retainer scope, response expectations and any review cadence are written down in advance and priced from that scope. Ask DeployOpen to confirm what a retainer covers, what it excludes, and which upgrades of ERPNext it would plan for. The output is a signed support agreement or a documented decision to proceed without one.
