Business Central can run three depreciation books, and in the Microsoft example only B1 posts to the general accounts. B2 and B3 stay in the fixed asset register and never touch the accounts.
- B1 integrates with the general accounts and uses the fixed asset G/L journal.
- B2 and B3 use the fixed asset journal; posting there changes only the register, not the trial balance.
- With the Part of Duplication List toggle on for B2 and B3, a single post in the G/L journal mirrors entries into both register books automatically.
- The first period's amount will be partial if you run partway through it — only days elapsed are counted.
- In the ERPNext example, a schedule row with no Journal Entry means that period has not fallen due yet.
What a depreciation book is for
A depreciation book is a separate set of fixed asset entries. It keeps its own method, its own schedule and its own posting path. You can run one book for statutory reporting and another for an internal view. You can keep a third for a method you are only testing. Each one holds its own rows.
The choice that matters most at setup is not the method. It is which book posts to the general accounts. In the Microsoft example there are three books, B1, B2 and B3. The naming in the product example is B1, B2 and B3. B1 is the one wired into the general accounts. B2 and B3 sit outside it.
If you set this up in Business Central, the depreciation methods page from Microsoft explains the split between the books, the two journals and the duplication toggle. The points below about how B1, B2 and B3 post and mirror entries come from Microsoft's Business Central depreciation methods documentation.
That one decision drives where your entries land. It drives which journal your staff open at close. It also drives whether a trial balance row moves when you run depreciation.
The one book that touches the general accounts
B1 integrates with the general accounts and uses the fixed asset G/L journal, so its entries post through that journal into the books. Every time you run depreciation in B1, the entries flow through that journal and post into the accounts. B1's entries reach the accounts through the fixed asset G/L journal. Your balance sheet and your profit and loss see the change in the same close.
This is the book you point an external reader at. It is the book a partner signs off on. When someone asks for the asset roll-forward, B1 is the answer.
A point worth making early: a run date changes the first period's amount. Microsoft's example walks through an asset acquired on a date early in a year. If you run depreciation partway through that first stretch, Business Central only counts the days that have passed. The example shows a run on 6/30/2023 with 148 days from 2/2/2023, and the suggested amount is 5000. The lesson for you at setup: your first post will rarely equal a full period. Build the expectation into your close notes so a partner does not flag it as an error.
The two books that stay out of the general accounts
B2 and B3 don't integrate with the general accounts and use the fixed asset journal. That journal is separate. Posting there does not touch the trial balance. Nothing in your profit and loss moves. Nothing in accumulated depreciation moves either.
This is where you keep a second method, an internal policy view, or a run you are checking before you trust it. The entries exist. They are visible in the fixed asset register. They simply do not reach the accounts.
Your staff need to know this at setup, not at close. If someone opens the fixed asset journal, posts a batch, and then looks at the balance sheet, the accounts will look untouched. That is the design working correctly.
So the answer to which book posts to the general accounts is B1, every time. B2 and B3 are register-only. If a client or partner asks why the second method never hits the accounts, this is the sentence to give them.
How the three books work together
Microsoft's example sets out a case with three books named B1, B2 and B3. B1 runs the posting into the general accounts. B2 and B3 run outside it. The setup also includes a duplication rule: B2 and B3 carry the Part of Duplication List toggle on their depreciation book cards.
When you make an entry in B1 in the fixed asset G/L journal, and turn on the Part of Duplication List toggle, Business Central duplicates the entry in book B2 and B3 in the fixed asset journal when you post the entry. One post in the G/L journal. Two mirrored entries in the fixed asset journal. Your staff do the work once.
This matters for how you staff the close. Someone opens the fixed asset G/L journal, reviews B1's rows, and posts. The mirrored rows land in the other two books without a second pass. If your plan was three separate manual runs, drop that plan.
There is a cost to the mirror, though. The duplication runs off the toggle on each book card. Turn it on for B2 and B3 and you get mirroring. Turn it off and the books run independently, which means your staff run them by hand. Pick one approach for each book and write it down.
Comparing the three books
Here is the shape of the three books side by side, using the fields your team touches most.
| Book | Journal it uses | Reaches the general accounts | Duplication toggle | Typical use |
|---|---|---|---|---|
| B1 | Fixed asset G/L journal | Yes | Can seed B2 and B3 | Posts to the accounts, the book a partner reads |
| B2 | Fixed asset journal | No | Part of Duplication List on | Register-only second view |
| B3 | Fixed asset journal | No | Part of Duplication List on | Register-only third view |
Keep this table near your setup sheet. The journal column is the one your staff check most often, because it tells them which screen to open.
Setting up your books at client onboarding
Before you import a single asset, decide three things for the file.
How B1's method is set. B1 is always the book that posts to the general accounts; for most client work you point it at the method the client's accounts need. Everything downstream depends on this call.
Which books stay outside the accounts. B2 and B3 are your testing and internal views. Decide now whether the client's policy view belongs in B2, or whether B2 is purely a scratch book. Leave B3 free for whatever comes up.
Whether duplication is on. If you turn the toggle on for B2 and B3, your entries mirror automatically. If you leave it off, your staff run each book by hand. Neither approach is wrong. Mixing them without writing it down is where errors start.
Write the three decisions on the client's setup sheet. A partner reading the file six months later should be able to tell, from that sheet alone, which book posts to the general accounts.
Method, frequency and what your staff see at close
In ERPNext, the asset category can default to a yearly schedule. An example from the Frappe documentation shows a Production Equipment category that defaults to yearly depreciation over five years, and an accountant who changed the row to monthly so the expense follows each month-end close. The category default did not decide the answer. The accountant did, on the row.
That is the pattern to copy. Your client's close cadence decides the frequency. If the client closes monthly, monthly rows keep the expense aligned with the period. If the client only reviews the register yearly, a yearly schedule may be enough.
The same Frappe documentation shows how a schedule reads once rows exist. In the example, the Statutory Reporting schedule has rows 1 to 7 covering February through August 2026, each linked to Journal Entries ACC-JV-2026-00015 through ACC-JV-2026-00021. Row 8, dated September 1, 2026, has not fallen due yet, so it has no Journal Entry. Rows 1 to 7 link to Journal Entries, and row 8 has none because it has not fallen due.
That gap at the bottom of a schedule is normal. Staff who do not expect it raise it as an issue every close. Show them the pattern once and it stops.
The asset itself sits under a company and a finance book in that example: company Nova Industries, dates January 1, 2026 to December 31, 2027, asset ACC-ASS-2026-00002, Statutory Reporting finance book. If a schedule looks short, check which finance book you are viewing against the asset's finance book first. If a schedule looks short, check the book filter first.
Where the entries land: two journals, one set of accounts
This is the section your staff will revisit.
Business Central gives you two journals for fixed assets. The fixed asset G/L journal is the one whose entries post into the general accounts. The fixed asset journal is not. B1 lives in the first. B2 and B3 live in the second.
A run in B1 posts expense and accumulated depreciation into the accounts. A run in B2 or B3 changes only the fixed asset register. When duplication is on, your single post in the G/L journal produces the mirrored rows in the other two books at the same moment.
Manager's fixed asset guide adds a related point for firms that want a tighter link between assets and accounts. Depreciation can be accumulated in custom control accounts instead of a standard account, and these custom control accounts can be assigned on an asset-by-asset basis. In practice that means one asset can feed one accumulated depreciation line while a second asset feeds another. See Manager's guide to depreciating fixed assets.
We have not seen a source that says how Business Central handles a client that needs both the mirrored-book setup and custom control accounts assigned asset by asset in the same file. If your client needs both, ask your Business Central partner how the two settings interact before you commit the client's chart of accounts.
A working close with three books
Take a client with a Production Equipment class, monthly close, and three books set up.
Your staff open the fixed asset G/L journal. They review B1's rows for the period. Duplication is on for B2 and B3, so posting B1 creates the mirrored rows in the fixed asset journal. They post B1. The accounts move. The register for B2 and B3 updates, and the accounts stay as B1 left them.
They check the schedule preview. In the ERPNext example, rows for periods already run carry Journal Entries. The row for the next period has no entry yet, because it has not fallen due. That is the sign the schedule is healthy, not a sign of a missed run.
If duplication were off, they would run B2 and B3 by hand after B1. That is three passes through the same period instead of one. Decide which you prefer and keep the decision visible on the setup sheet.
Setup checklist before you hand the file back
Work this list at onboarding, while the file is still clean.
Confirm the books tied to the general accounts. B1 is the one that posts there. Name it in the file so nobody has to guess.
Confirm the register books. B2 and B3 stay out of the general accounts. Keep B2 and B3 register-only, and route any posting into the accounts through B1.
Confirm duplication. Turn the Part of Duplication List toggle on for the books that should mirror B1. Leave it off for books that run by hand.
Set the frequency to the client's close. Match the row to the close cadence. Match the row to the close cadence.
Check the first period. Early runs only cover the days that have passed. Expect a partial first amount and note it in the file.
Check the ERPNext schedule example. Periods already run carry Journal Entries. The next period has none until it falls due.
Decide on control accounts (Manager). If the client wants accumulated depreciation split for each asset, assign custom control accounts asset by asset.
Write the three decisions on the setup sheet. Book tied to the accounts, register books, duplication on or off. A partner should read the answer in one line.
Working the file after handover
Once the file is live, most of your time goes into two things: keeping the frequency matched to the close, and keeping the books from drifting apart.
Drift happens when someone edits a row in B2 directly. Duplication covers new posts from B1, not manual overrides in the other books. If a row in a register book looks wrong, trace it back before you correct it. The fix usually belongs in B1.
The other drift is the forgotten book. The register books show a short asset list. Check all three books when an asset arrives, not just B1.
What to tell the partner
Partners care about two sentences.
The first: only B1 posts to the general accounts. Everything a reader sees in the accounts comes from B1.
The second: B2 and B3 mirror B1 through duplication when the toggle is on. One post, three books, one set of accounts.
If a partner asks why the register shows more activity than the accounts, those two sentences answer it. The books run wider than the set of accounts, and that is how the product is built.
Related guides: Depreciation methods: 3 rules for client assets · Accounting Client Intake Checklist for a Clear Handoff · ACH invoice fees: 4 facts to check before a client pays.