ERPNext finance books for statutory reporting

When ERPNext finance books fit statutory and management reporting

Use ERPNext finance books when one legal entity must report the same transactions to tax or regulators on one basis and to its board on another, and those bases produce different numbers. A finance book is a second accounting view of the same company, kept inside one site. Departments are not a reason to create one. Teams are tracked through cost centers, which let you filter and compare spending by team in every book. A book per department would duplicate balances without adding a reporting basis, and it would make the month-end close harder to check.

In ERPNext, a finance book is a named book that can be attached to transactions and to asset depreciation schedules, so one asset can follow one depreciation method for statutory reporting and another for management reporting. Entries posted under a book carry its name, and reports can be filtered by it. The feature does not replace your chart of accounts, your tax computations or the country-specific returns you file, and it does not change how a legal entity is defined. Confirm the exact book setup, the default book behavior and which documents accept a book against the ERPNext version your client runs before you design around it.

Before configuring a second book, list every transaction type where the two bases will differ. Depreciation is the usual case, but revaluations, provisions and capitalization thresholds can also diverge. For each one, record who owns the rule, which report consumes it and how the difference reconciles back to the main books at period end. Test the setup on a copy of your data through a full month-end close, and ask your auditors or tax adviser to confirm that the statutory book meets their requirements. Write the testing and reconciliation work into the scope so both parties know who performs it.

Which option fits each reporting need

This table compares four ways to separate reporting views in ERPNext: cost centers and accounting dimensions, finance books, separate companies, and report templates. Read each row for what the option answers, what it changes in the ledger, and when it is the wrong tool. Confirm the exact behavior of each feature in the ERPNext version your organization runs before you commit to a design.

Option	What it answers	What it changes in the ledger	When it is the wrong tool
Cost centers and accounting dimensions	Which department, project or branch carried a cost or revenue	Tags each general ledger entry with extra reporting codes; one book, one set of balances	When a second set of balances is needed for a different depreciation or valuation rule
Finance books	How an asset or entry is valued or depreciated under an alternative view	Posts parallel depreciation or value entries per named book alongside the default book	When the difference is only a grouping or a layout, which cost centers or templates handle better
Separate companies	What a distinct legal entity owns, owes and reports	Creates its own chart of accounts and ledger, with inter-company transactions between them	When the need is a departmental split inside one legal entity, which adds setup and reconciliation work
Report templates	How balances are arranged for board, investor or management packs	Changes no postings; reads existing ledger data into grouped rows, signs and calculated lines	When the reader needs a transaction-level view that the underlying ledger cannot support
Confirm in your version	Whether each option supports your required book types, dimension limits and report features	Check the ledger effect in a test site with your own chart of accounts before go-live	Any design that assumes a capability not verified in your release

How different depreciation methods per book change asset reporting

An asset in ERPNext can carry a separate depreciation schedule in each finance book, so one purchase can show different values for statutory and management purposes. The cards below cover what changes in the asset register, the depreciation postings, disposals and the reports that read them, and which decisions must be settled before the first depreciation run.

Values each book carries

Each finance book on an asset holds its own gross purchase amount, accumulated depreciation, depreciation method, useful life and expected value. The asset record shows these side by side, so the net book value can differ between books from the day of purchase. Check that every asset category and every asset that must appear in both books has the book rows filled in, because a missing row means that book does not depreciate the asset.

How depreciation entries post

Each book runs its own depreciation schedule and posts its own journal entries to the accounts mapped for that book. A statutory book and a management book can therefore create entries with different amounts and dates in the same period. Confirm which book the period close uses for each report, and test one asset through a full period before the first live run.

Disposals and gains or losses per book

When an asset is sold or scrapped, the gain or loss is calculated against the book value in each book, so the same disposal can produce a gain in one book and a loss in another. Each book also needs its own disposal accounts. Ask the accountant to confirm how the disposal date and any partial sale should be treated in each book before anyone records a disposal.

Reading the asset register

The asset register and asset depreciation reports should be filtered by finance book, or they will mix values that belong to different bases. Totals that look wrong usually come from a report that does not specify a book. Build a short reconciliation for each book that ties its net book value to its general ledger accounts at period end.

Agreeing each book's method

Every book needs an agreed depreciation method, useful life and convention before the asset is created. The rules for the statutory book must come from the client's accountant or tax adviser, and the management book rules should come from the finance leadership that uses it. Record these decisions in writing, because changing a method later affects existing schedules.

Why departments belong in cost centers, not in finance books

A finance book is a second accounting view of the same transactions, so every book you add is another set of entries that must reconcile back to the ledger. When a sales team or a site gets its own book, the reconciliation rarely holds. Postings made in one book drift from the other, adjustments get entered in one place and not the other, and nobody can say which totals are authoritative. Departments are a reporting question, not an accounting basis, and they should be carried as reporting attributes inside the single company book.

In ERPNext, the tools for this are cost centers and accounting dimensions. Cost centers are set on income and expense lines, and accounting dimensions let you add your own tags, such as a sales region, project or site, to journal and invoice lines. Management reports can then be filtered by those values in the General Ledger and Profit and Loss reports without duplicating a single entry. Confirm with your implementation plan which dimensions your reporting needs, how they are made mandatory on the right document types, and who is allowed to create them, because a dimension that is added late cannot retroactively tag history.

*Illustrative example:* a company with three sales teams creates a finance book for each team so each can see its own depreciation and revenue views. Within a year, assets are transferred between teams in one book but not the other, the team books no longer add up to the company balance sheet, and the close takes longer each month as someone reconciles them by hand. The fix is to keep one book, use cost centers for the teams, and add a dimension for anything else the teams need to filter on. Before you agree a scope, ask your partner to show how each proposed book would be reconciled to the company ledger.

Who owns which decisions in a finance book setup

The finance controller owns the accounting meaning of every book. Each parallel book exists because someone needs a different view of the same transactions, so the controller decides what each book is for, which accounting policies it follows and how its results will be read by management. Without this sign-off, the administrator will configure books that match the software's defaults rather than the company's policies.

Book names and purpose: Agree a short name for each book and a one-sentence statement of who uses it and for what decision.
Depreciation methods per book: Confirm the method, useful life and salvage basis for each asset class in each book, including where a book departs from the statutory schedule.
Account postings per book: Decide which general ledger accounts post to which book, and where a transaction must appear in every book.
Report layouts: Approve the management report structure, including groupings, calculated lines and the cost centers that feed each view.
Inputs before build: Provide the current chart of accounts, the fixed asset register with purchase dates and costs, and the existing depreciation schedules.

Confirm that every asset class has an agreed method in each book before the build starts, because changing a method after depreciation has run is a correction exercise.

How to set up finance books in ERPNext step by step

This sequence takes a company from a written list of reporting needs to a documented finance book configuration, with a check at each stage that confirms the statutory and management books behave as intended. The result is a configuration your finance team can explain, test and maintain.

Confirm reporting requirements and the book list
Finance leads and the advisers who sign off statutory accounts write down each reporting purpose, the books that serve it, the accounting standard or tax rule each book follows, and which entries differ between books. Agree the list before anyone touches the system, so every book has an owner and a stated reason to exist. The step is done when the signed list shows each book, its purpose and its differences from the main ledger, and nobody can add a book without changing that document.
Confirm the ERPNext version and book features
The technical lead checks the ERPNext version the company runs or plans to run against the supported versions list, then confirms in the release notes and the installed instance which finance book features that version provides, including how books are linked to companies and assets. Confirm any gap with your implementation partner or in a test site, not from memory. The step is done when the version, the supported features and any missing features are recorded in the configuration document.
Configure the books and default settings
The ERP administrator creates each finance book in the test environment and sets the default values the book needs, such as the book name, the company it belongs to and any default posting behavior the features allow. Keep the main book as the reference and avoid changing its defaults in this step. The step is done when every book appears in the test site with the agreed name and company, and a configuration export or screenshot is stored with the design document.
Map asset categories and depreciation methods per book
The accountant maps each asset category to the depreciation method, useful life and accounts required by each book, using the rules from the reporting list. Where a book uses a different method from the main ledger, the mapping makes that difference explicit rather than relying on manual adjustments. The check is a sample asset report for one asset per category, run for each book, showing the depreciation schedule and the net book value at a chosen date, reviewed line by line against the rule written in step one.
Run test transactions and compare books to the ledger
The finance team posts a fixed set of test transactions in the test site, including purchases of assets, depreciation runs, disposals and at least one journal entry that should appear in every book. They then compare each book's balances against the main ledger, reconciling every difference to a documented reason such as a different depreciation method. The step is done when each difference is explained in writing and the reconciliation shows no unexplained variance for the test period.
Review cost center structure for departments
The controller confirms that departments and cost centers are used for management analysis and that finance books are not created to split results by department. The review checks that the cost center tree reflects the reporting needs and that departmental reports draw from the main ledger. The step is done when the controller signs off the cost center structure and the department view reconciles to the ledger totals used in the test run.
Lock the configuration and document it
After the test results are signed off, the administrator moves the configuration to production using the agreed change process, restricts edit rights on book settings and asset category mappings to named roles, and records who approved each book. The configuration document covers the book list, the mappings, the test evidence and the reconciliation method for each period. The step is done when the production configuration matches the tested export, access is restricted, and the document is filed where auditors and future administrators can find it.

Controls and operating habits for finance books

Parallel books change how postings, assets and closing periods behave, so the controls around them matter as much as the setup. The five areas below cover who can change book configuration, how postings are permissioned, how changes are reviewed, how closing interacts with each book, and whether you can restore a known-good state.

Who can change book settings

Creating a finance book and setting a default book on a company both alter how every later posting is recorded. Limit these changes to a small finance administration group and keep them separate from people who post daily entries. Confirm in your ERPNext version which standard roles can edit company and accounting settings, and test that a regular accountant cannot change the default book. Document who approves a new book before it is created.

Asset register and journal entry permissions

Depreciation schedules and manual journal entries can be posted to one book or to several, so a user with rights to the asset register may affect more than one set of figures. Decide which roles can submit asset depreciation, cancel it and post journal entries that carry a book. Use role permissions in general terms and confirm exact role names and document-level rules in your version before you grant access to finance staff.

Logging and reviewing configuration changes

Keep a record of who changed a book's depreciation method, default settings or company links, and when. Frappe's version tracking on documents helps, but you should also agree a review rhythm where someone outside the finance team checks recent changes to book configuration. Ask your implementation partner to show how change history is retrieved for a sample configuration change, so the review step is tested rather than assumed.

Period closing and posted entries

A closed accounting period should stop new postings in every book for that period, but each book's depreciation and revaluation entries need their own check before lock. Confirm whether your period-closing setup applies to all books or only the default one, and test a posting dated into a locked period in each book. Agree the reopening rules and who signs off before a period is reopened for correction.

Backup and restore testing

Parallel books are stored in the same database as the rest of the company's ledgers, so a restore must bring back every book consistently. Schedule backups of the database and attached files, then restore them to a separate environment and compare trial balances and asset values for each book against the source. Record the restore procedure, the person who runs it and the date of the last successful test.

What to confirm before you rely on finance books

Start with the version. Open the Frappe supported versions page and confirm that the ERPNext and Frappe Framework version your site runs is still listed and supported. Frappe lists version 14 as end of life from January 31, 2026, version 15 as planned for support until the end of 2027, and version 16 until the end of 2029. Frappe also states that warranty coverage requires a listed version and a matching Frappe Cloud support plan, so a site on an unlisted version has no vendor warranty however well its books are configured. Record the current version, its support end date and the upgrade window your finance team can accept before you design any book-level setup.

Next, test the reports on your own data. Enter representative transactions in a staging copy and check whether the standard financial reports show each finance book in the layout your management and statutory reviewers expect. Confirm how books appear as columns or filters, how totals reconcile between books, and whether any additional accounts are needed to hold the differences. Then ask whether your custom report templates can read book-level figures. If a template cannot select a book, the second set of figures may need a separate report or export, and that work belongs in the scope before the build starts. Write down who signs off each report and which figures they compare against.

Finally, confirm the hosting model and whether custom code is needed. Behavior can differ between Frappe Cloud and a self-hosted bench or Docker deployment, so check the feature on the platform you will run, not only on a demo site. If the design needs a server script to calculate or validate book-level entries, note that from version 15 Server Scripts are disabled by default and must be enabled with the server_script_enabled setting, and Frappe Cloud public shared benches do not allow them. Decide whether a custom app is the right home for that logic and who approves the change. DeployOpen prepares and tests the configuration in your environment, but it does not issue audit or tax opinions. Confirm the accounting and tax treatment with your external auditors and tax advisers.

Questions buyers ask before hiring help with finance books

What makes the cost of a finance books setup go up or down?

The main cost drivers are the number of books, the number of fixed assets, how many depreciation rules you need, how many report templates your board and statutory filings require, and how much historical data has to move across. Each extra book adds configuration, testing and reconciliation work, because every book must post the same transactions and still produce its own totals. Asset count and depreciation rule variety matter because each rule has to be checked against your accounting policy. Ask any partner for a quote that lists these items separately so you can see which ones you can reduce.

How long does a finance books implementation take?

Duration depends on the scope written into the engagement, so there is no standard timeline that applies to every company. A setup with one additional book and a short asset register is far smaller than one with several books, a large asset base, and historical balances to reconcile for multiple periods. Timing also depends on how quickly your controller can approve the accounting policies and test results. DeployOpen agrees timelines in writing as part of a fixed-scope quote, so ask for the milestones and the sign-off points that drive them.

What must our team provide before the work starts?

Expect to provide the written accounting policies for each book, including depreciation methods, useful lives and capitalization thresholds. You will also need a current fixed asset register with cost, acquisition date, location and existing depreciation, plus the chart of accounts and cost center structure. Your controller should name who signs off each book's opening balances and each report template. Missing or late inputs are one of the most common causes of delay, so confirm the list of inputs in the quote before work begins.

Can our internal finance and IT team set up the books alone?

Yes, a capable internal team can configure additional books in ERPNext if it has the accounting knowledge, the time, and someone who understands the Frappe data model. The work that tends to take longer in-house is testing: checking that every book reconciles to the ledger, that depreciation schedules match policy in each book, and that the reports produce the figures the auditors expect. Consider whether you have a second person to review the configuration. A partner can take on the build and testing under a written scope while your team keeps control of the policy decisions.

Which parts of the setup create the most risk if they are wrong?

Depreciation settings and opening balances carry the highest risk because errors flow into every later period and into the statutory numbers. Mixing up which transactions post to which book, or treating departments as cost centers in a way that duplicates reporting, causes reconciliation problems that are hard to unwind after go-live. Access controls over who can change book settings also matter. Ask for a test plan that compares each book's totals with the ledger before the first live period is closed.

Does DeployOpen issue the audit or compliance sign-off for our books?

No. DeployOpen configures, documents and tests the books and prepares the controls and evidence that your external auditors or tax authorities may ask for. Audit reports, attestations and certifications are issued only by independent auditors and certification bodies. Confirm with your auditor which records, reconciliations and configuration exports they will request, and include producing them in the written scope.

What does a fixed-scope quote for finance books depend on?

A DeployOpen quote follows from the written scope, which lists the books, the depreciation rules, the asset and opening balance data to migrate, the report templates, the test cases and the deliverables. DeployOpen does not publish a price list, so the figure depends entirely on what is agreed in that document. Ask for the scope to state what is excluded, who provides each input, and what counts as acceptance. Changes after signing should go through a written change request so cost and timing stay visible.

How DeployOpen scopes and delivers ERPNext finance books

DeployOpen plans, implements, customizes, tests, documents and supports self-hosted open-source platforms inside your own infrastructure, and ERPNext finance books are scoped the same way. The work starts from your statutory and management reporting requirements, then moves through a written, fixed-scope plan before any configuration begins.

How we scope

Map which reports need statutory treatment and which need management views before choosing any book setup.
Record each book, its depreciation method, its currency and its owner in the written scope.
Agree in writing which deliverables, test cases and handover documents are included, and which are excluded.

How we build

Configure the company's books and asset categories in a test environment before touching production data.
Define cost center structures for departments and check that reports group them without duplicate asset postings.
Test depreciation runs, journal entries and report outputs for each book against signed-off reference figures.

How we hand over

Document the book setup, depreciation settings, cost center hierarchy and the month-end steps your finance team runs.
Walk finance and accounting staff through posting, reporting and exception handling on your own site.
Provide the configuration and customization record so your team or a future partner can maintain it.

How we support

Offer ongoing support, upgrades and continuous testing as a retainer after go-live.
Review changes to books, depreciation rules and reports before they reach production.
Confirm with your auditors which evidence and controls they expect, since DeployOpen prepares records but does not issue attestations.

ERPNext finance books for statutory and management reporting