Start with a reconciliation that explains both bases
Suppose asset A001 has an accounting cost of RM100,000 and approved accounting depreciation of RM20,000, leaving a carrying amount of RM80,000. The independently prepared tax schedule records qualifying expenditure of RM80,000 and allowances of RM24,000, leaving residual expenditure of RM56,000. These are illustrative approved inputs, not prescribed rates or a calculation of tax entitlement.
The register should explain the RM24,000 difference between the closing balances: RM20,000 comes from the different starting bases and RM4,000 from the different charges for the period. Keep the evidence for those differences against the same asset identifier. The test is whether the accounting book reconciles to the accounts and the tax book to the approved tax schedule, with each difference explained.
Dynamics 365 Business Central can hold parallel depreciation books against an asset. The finance team owns the accounting policy and postings; the organisation and its tax adviser approve eligibility, qualifying expenditure, allowances and tax adjustments. The implementation team configures and tests how those approved figures are recorded and reported.
What Schedule 3 computes, and what it computes it on
Capital allowance is given as a combination of initial allowance and annual allowance on qualifying expenditure. The Inland Revenue Board of Malaysia's Public Ruling No. 6/2015, Qualifying Expenditure and Computation of Capital Allowances, sets out how qualifying expenditure is established and then used in that computation, and defines residual expenditure as the cost of the asset less initial allowances and annual allowances, or a notional allowance equal to the annual allowance if it was claimed or should have been claimed. Whether an asset is plant at all is a separate question, addressed in Public Ruling No. 12/2014, and it turns on the character and function of the asset rather than on how the asset was classified in the accounts. Rates are set by Schedule 3 and the relevant Income Tax Rules and are revised from time to time; confirm the applicable rates, and any accelerated allowance, against the Board's own current published material rather than against a percentage sitting in a system. These are general statements of the mechanism, not a determination of any company's entitlement.
Three features of that mechanism matter once it is put inside an asset register. The allowance is computed on qualifying expenditure rather than on what remains of the asset's carrying amount. Initial allowance and annual allowance are distinct components whose eligibility, timing and amounts must follow the approved tax schedule. And entitlement depends on facts that live outside the register — ownership of the asset, and its use for the purposes of the business at the end of the basis period. Public Ruling No. 6/2015 also treats assets acquired on hire purchase differently again: qualifying expenditure is the capital portion of the instalment payments actually made in the basis period, so the amount the tax basis starts from is not the amount the accounting basis starts from.
Business Central already holds more than one basis per asset
Microsoft's documentation on setting up fixed asset depreciation describes the container this needs. A depreciation book defines how a group of assets is depreciated; a book assigned to a particular asset becomes a fixed asset depreciation book; and, in Microsoft's own words, an unlimited number of depreciation books can be set up for a fixed asset. Microsoft's stated reason for the feature is close to the Malaysian position without being about it: many businesses use straight-line depreciation in their financial statements and an accelerated method for income tax purposes.
The second element is the Integration FastTab on the depreciation book card, where a check box for each fixed asset activity determines whether that activity posts through the Fixed Asset G/L Journal or the Fixed Asset Journal. A book with no integration selected keeps its own complete entry history without touching the general ledger. That is precisely what a capital allowance basis needs: a parallel record attached to the same assets, with no direct general-ledger posting from the tax book. Tax schedules may still inform current or deferred tax accounting where applicable.
Entering each asset once
The failure mode worth designing against is a second register maintained by hand that slowly drifts from the first. Business Central offers two native mechanisms. The Create FA Depreciation Books batch job assigns a book across a filtered set of assets in a single run, with a Copy from FA No. field that populates the new books from an existing one. Separately, mark the intended destination depreciation books as Part of Duplication List and select Use Duplication List on the relevant source journal lines. Posting the source journal creates lines in the destination journal for review and posting. Microsoft’s example uses a G/L-integrated source book and non-integrated destination books. This reduces re-entry, but does not by itself approve the tax basis or finish posting the destination books.
Define which journal entries should be duplicated and review the destination journal before posting. Copying an acquisition amount does not establish qualifying expenditure, particularly for hire-purchase assets, and copying a disposal entry does not determine the tax adjustment. Keep the same asset identifier across books, with documented adjustments wherever the approved bases differ.
Where the built-in methods fit, and where they do not
Business Central supports eight depreciation methods, and the differences between them matter here more than usual. Microsoft's documentation on depreciation methods for fixed assets gives the formulas. Straight-Line driven by a depreciation period calculates the amount as book value less salvage value, apportioned across remaining depreciation days — a mechanism that re-spreads whatever is left over the life still to run. An allowance computed as a fixed percentage of original qualifying expenditure does not behave that way, and a period-based method should not be assumed to reproduce the approved capital-allowance schedule; compare the full calculation, timing and residual balance.
Straight-Line driven by a fixed yearly percentage is the closer fit: Microsoft's formula applies that percentage to the depreciable basis rather than to the remaining book value. Declining-Balance 1 applies its percentage to the book value at the beginning of the year, which is a reducing-balance pattern rather than a Malaysian one. Neither, on its own, produces the separate initial- and annual-allowance components, including annual allowance in the acquisition year where eligible. Where that combined pattern has to be reproduced exactly, the user-defined depreciation method and its depreciation tables are the built-in route to a bespoke schedule, and the Manual method exists for assets that are not to be calculated at all.
Two further configuration details need explicit testing. The Calculate Depreciation batch job normally uses a standardised year of 360 days with twelve 30-day months, unless the Fiscal Year 365 Days field is selected. Microsoft also notes that this option treats February as 28 days even in a leap year. Test the chosen calculation against the approved schedule rather than assuming the day-count setting reproduces the tax basis period. And Microsoft explicitly recommends against changing the setup of a depreciation book for entries that have already been posted, because the change does not affect posted entries and leaves the book's statistics misleading. Both are reasons to settle the tax book's configuration before it is populated rather than after.
What the second book still cannot decide
A correctly configured tax book produces a consistent, traceable schedule. It does not decide whether an asset is plant, whether the ownership and business-use conditions were met at the end of the basis period, or whether a year's allowance was claimed or should have been claimed and therefore reduces residual expenditure as a notional allowance. It does not know that the company's basis period may not coincide with the fiscal year defined in the system. It does not determine whether unabsorbed allowances remain available against the relevant business source; that assessment belongs in the tax computation. SCSB treats the second depreciation book as an instrument for producing and evidencing a schedule, not as a substitute for the judgement that decides what belongs in it.
Reconcile the approved schedule at each close
Use a common asset list to compare opening balances, additions, approved allowances or depreciation, disposals and closing balances in both books. Assign each difference an explanation, supporting schedule and reviewer. Escalate assets missing from either book, unapproved duplicated amounts and changes in use or financing before treating the tax schedule as ready for the computation.
Decisions to settle before configuration starts
- Which depreciation book is the accounting basis and integrates with the general ledger, and which is the tax basis and does not.
- Whether the tax book reproduces the allowance pattern through a fixed yearly percentage, a user-defined depreciation table, or entries prepared manually, and who verifies the first full year against an independently prepared computation.
- How assets acquired on hire purchase are handled, given that qualifying expenditure follows instalments paid rather than the accounting acquisition cost.
- How every new asset is reviewed for tax-book inclusion, including a documented reason where the approved tax treatment excludes it.
- Which review confirms, each year, that the population of assets in the tax book still matches the population in the accounting book, and what explains any difference.
When this can be managed without outside help
A company with a short asset register, few additions each year, no hire purchase and a single business source may reasonably maintain its capital allowance schedule outside the system, prepared from the fixed asset register and reviewed alongside the tax computation. At that scale a second depreciation book adds configuration without adding much control. The case for building the second basis inside Business Central grows with the number of additions and disposals, with hire purchase or assets brought into the business after non-business use, with more than one business source, and above all where the two bases have already diverged and no one can currently explain by how much or why.
What to do next
Confirm the applicable rates, conditions and treatment directly against the Inland Revenue Board of Malaysia's current published material before relying on this article for anything beyond the mechanics of configuration; the organisation and its qualified advisers approve those inputs; the asset register records their implementation. Where the requirement is to build and maintain this dual-basis register inside Dynamics 365 Business Central, Business Central financial reporting automation can be discussed within an agreed scope.
General-information limitation
This article is general technical information about fixed asset and depreciation book configuration concepts in Dynamics 365 Business Central. It is not tax, legal or accounting advice, does not determine any company's entitlement to capital allowance or the rates applicable to it, and does not confirm that a particular configuration satisfies the Inland Revenue Board of Malaysia's current requirements. The Board's public rulings and the Income Tax Act 1967, and Business Central's own functionality, are set by their respective publishers and are revised over time. Confirm the current position against the Board's published material and Microsoft's current Business Central documentation before implementation.
Dynamics 365 Business Central and Microsoft are trademarks of the Microsoft group of companies.