# How to design parallel books for local GAAP and group reporting Start with the differences that finance has approved, then decide where to record them. A second book is useful when transactions need different accounting treatments. Another currency, a different account name or a new management report may require a different solution. **Diagram:** Preserve common transactions and basis-specific adjustments. Illustrative architecture. Approved accounting policies determine which adjustments each basis requires. This guide takes one entity from an ordinary operating ledger to a reconciled group reporting basis. Its worked example is synthetic. The policies and tax assumptions are deliberately explicit; they are not a claim that every local GAAP differs from [IFRS](https://erplocalization.com/glossary/accounting/#accounting-ifrs-accounting-standards) in the same way. Use the [parallel-books decision worksheet](#template) to record the basis, adjustments, report composition and approval. The controls below are an implementation method, not additional accounting rules. ## Define the results before choosing the mechanism Give every reporting basis a short specification. Identify the legal entity, standards and edition, approved policies, functional currency, reporting period, required statements and accountable controller. Keep the statutory basis separate from the group's consolidation basis even if their numbers currently agree. Then classify each proposed difference. A new account mapping changes presentation. A different measurement policy can change assets and equity. A recognition-timing difference can change profit and liabilities. A note disclosure may require additional source data without another journal. Ask finance to state the reason and authority for each difference. Do not accept "local GAAP versus IFRS" as the entire explanation. An estimate based on the same facts does not become different merely because another book exists. Correct local errors in the local accounts when appropriate; do not hide them indefinitely in group adjustments. Record whether an adjustment recurs, reverses, rolls forward or affects later depreciation. That lifecycle matters more to implementation than the initial journal amount. ## Choose where the difference belongs A full parallel book records a complete alternative accounting result. An adjustment layer records differences and relies on an identified base ledger. Alternate asset or revenue schedules may calculate differences before journals reach either structure. A consolidation-only adjustment can be appropriate when the result is required only in the group package. NetSuite's current OneWorld documentation distinguishes Full Multi-Book Accounting from Adjustment-Only Books. Full Multi-Book can use shared transactions with book-specific accounting; its implementation requires NetSuite Professional Services or an authorised partner. These statements concern NetSuite OneWorld, not every Oracle ERP or every NetSuite subscription. [Oracle, Using Multi-Book Accounting](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/chapter_3831569045.html). Oracle explains that adjustment-only reports combine the base book and its adjustment book. The adjustment-only book uses its base book's currency and does not support Foreign Currency Management. It therefore is not a shortcut for creating an independently denominated operational ledger. [Oracle, Adjustment-Only Books overview](https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/chapter_1546505267.html). For the example below, select a base ledger plus a year-end adjustment layer. That choice is proportionate because only one approved measurement difference exists. A high volume of daily differences might justify full parallel accounting instead. Confirm the proposed report includes the base exactly once before purchasing or configuring the feature. ## Approve the example's accounting assumptions The entity begins its first year with cash and share capital of 100,000 currency units. Both reporting bases use the same currency and calendar year. It buys a machine for cash on 1 January for 24,000. The machine has a four-year useful life, no residual value and straight-line depreciation. The local basis uses the cost model. The group basis uses an approved revaluation model for the entire relevant asset class, which contains only this machine. A reliable year-end valuation is 20,000. There are no previous revaluation losses, impairment losses or other assets in the class. Cost and revaluation are accounting-policy models, not labels automatically assigned to "local" and "international" reporting. The published AASB 116 text illustrates the distinction and the requirement to apply the chosen policy to an entire asset class. Its Australian context does not determine another jurisdiction's permitted local policy. [AASB 116, measurement after recognition](https://standards.aasb.gov.au/aasb-116-dec-2022). IAS 16 is the corresponding IFRS subject governing property, plant and equipment. [IFRS Foundation, IAS 16 overview](https://www.ifrs.org/issued-standards/list-of-standards/ias-16-property-plant-and-equipment/). The entity also receives 12,000 cash in advance for a service delivered evenly over the year. Both bases recognise the same 12,000 revenue by year-end. Other operating expenses of 4,000 are paid in cash. There is no VAT, financing, dividend or other transaction in this exercise. For arithmetic only, assume current tax is 25% of the local pretax profit, is paid at year-end and has no other adjustments. The machine's closing tax base equals its local carrying amount. Assume the applicable deferred-tax rate is also 25%. These are fictional tax assumptions, not a country's tax calculation. ## Close the local ledger first Record the machine purchase as a 24,000 debit to the asset and credit to cash. The advance service receipt debits cash and credits a contract liability for 12,000. Release that liability to revenue as the service is delivered; the year-end liability is zero. Annual depreciation is 24,000 divided by four, or 6,000. Debit depreciation expense and credit accumulated depreciation. The machine's local closing carrying amount is 18,000. Record the 4,000 cash operating expenses separately. Local pretax profit is 12,000 revenue less 4,000 operating expenses less 6,000 depreciation, or 2,000. Current tax is 500 under the example's assumption, leaving profit after tax of 1,500. Closing cash is 100,000 minus 24,000 plus 12,000 minus 4,000 minus 500, or 83,500. Local assets therefore total 101,500: cash of 83,500 plus the machine at 18,000. There are no closing liabilities. Capital of 100,000 plus retained profit of 1,500 also totals 101,500. Retain both the balance check and the service liability roll-forward. The advance receipt illustrates why cash timing and revenue timing can differ even when both reporting bases use identical accounting. That difference alone creates no local-to-group adjustment. ## Build and reconcile the group adjustment The group asset value must rise from 18,000 to the approved 20,000 valuation. Record a 2,000 net increase in the asset and a 2,000 revaluation gain in other comprehensive income in the group adjustment layer. The detailed treatment of gross cost and accumulated depreciation follows the approved asset policy; this exercise shows the net effect. The 2,000 difference between group carrying amount and unchanged tax base creates a 500 deferred-tax liability under the assumed rate. Record the corresponding 500 tax charge against the revaluation gain in other comprehensive income. IAS 12 addresses temporary differences between carrying amounts and tax bases; actual recognition and exceptions require the entity's own tax review. [IFRS Foundation, IAS 12 overview](https://www.ifrs.org/issued-standards/list-of-standards/ias-12-income-taxes/). Group cash remains 83,500. The machine is 20,000, making total assets 103,500. Liabilities are now 500. Equity comprises capital of 100,000, retained profit of 1,500 and net revaluation surplus of 1,500, totalling 103,000. Liabilities plus equity equal assets: 500 plus 103,000 equals 103,500. The bridge is therefore precise: assets increase by 2,000, liabilities by 500 and equity by 1,500. Profit after tax remains 1,500. Do not place the revaluation gain in operating revenue to make the bridge balance. ## Carry the difference into the next period At the next year's start, retain the group revaluation and deferred-tax balances. They are not automatically reversing accruals. Assuming unchanged life, residual value and policy, the remaining three-year depreciation is 6,000 annually locally and 20,000 divided by three on the group basis. For the first following year, rounded group depreciation is 6,666.67. The incremental group charge is 666.67. Maintain a schedule for the remaining carrying-value difference and tax effect, with a final-period rounding rule. This is where an apparently simple year-end adjustment becomes an ongoing subledger responsibility. The asset accountant owns that schedule. The tax reviewer owns the updated temporary-difference analysis. The group controller approves its incorporation into the next package. Avoid recalculating next year's adjustment from an unsupported opening spreadsheet balance. ## Recover from a duplicated adjustment Suppose the reporting operator imports the same revaluation pack twice. The report can still balance: the asset rises to 22,000, deferred tax to 1,000 and net revaluation surplus to 3,000. A trial-balance equality check will not detect the duplicate. Compare the report to the valuation reference and the approved 2,000 bridge. Stop package release, identify both journal batches and reverse the duplicate through the controlled process. Rerun the complete report using the same base snapshot. The controller should confirm the asset is 20,000 and the liability 500 before accepting the rerun. Give each adjustment a unique entity, period, basis, asset and policy reference. Record import attempts and report composition. If the underlying asset record changes, replace or correct the prior adjustment explicitly rather than adding another unexplained amount. ## Complete the design and hand it over The local controller owns the statutory ledger and local close. The group controller owns basis differences and the final bridge. The application owner implements book rules and access. An operator runs the package using an approved configuration; an independent reviewer accepts the outcome. Before completion, confirm: - Each reporting basis and policy difference has an approved specification. - The base ledger appears exactly once in the alternative result. - Currency translation, presentation mapping and measurement adjustments remain distinguishable. - Local and group closing positions reconcile to source schedules. - Recurring differences, deferred tax, reversals and rounding have owners. - A duplicate or corrected adjustment can be detected and recovered. - The local accounts remain reproducible after the group package is closed. Keep the completed worksheet, source extracts, valuation, journals, reconciliation and approvals together. For surrounding procurement controls, use [how to read an ERP country-support claim](https://erplocalization.com/guides/erp-editions-and-compliance-dependencies/). Continue with [local statutory accounts and group reporting](https://erplocalization.com/guides/local-statutory-accounts-group-reporting/) when designing the final reporting package. Source verification date: 17 October 2026. Product documentation establishes the described mechanisms; this guide does not claim the synthetic transactions were executed in a live NetSuite account. ## Worksheet: Parallel-books decision and reconciliation worksheet Copy this worksheet for each case. It records decisions and evidence; it does not determine the tax or legal treatment. Show the worksheet Use with [the parallel-books guide](https://erplocalization.com/guides/parallel-books-local-gaap-group-reporting/). Complete one copy for each entity and pair of accounting bases. Blank fields are intentional inputs. The reference case below is synthetic and does not establish permitted local policies or tax rates. ### Identify the reporting results - Legal entity and reporting period: - Local accounting basis, edition and approved policies: - Group accounting basis, edition and approved policies: - Functional currency and presentation currency: - Required statements and reports: - Local controller: - Group controller: - Tax reviewer: - ERP family, edition, deployment and release/build: - Book or adjustment component and entitlement evidence: ### Record each difference Repeat this record for every policy, estimate, timing or presentation difference. Explain whether it needs a journal, a mapping change or additional disclosure information. - Difference reference: - Affected transactions/assets and applicable policy evidence: - Local treatment: - Group treatment: - Recognition, measurement, presentation or disclosure: - Why the treatments are appropriate on the same underlying facts: - Calculation and source schedule: - Current and deferred tax consequences: - Initial journal and reporting layer: - Recurring schedule, reversal or roll-forward: - Rounding rule: - Preparer, reviewer and approval date: ### Define report composition - Base ledger/snapshot reference: - Full alternative book OR base-plus-adjustments: - Adjustment layer and report filter: - How base inclusion exactly once is checked: - Unique adjustment identifier: - Duplicate-import prevention/detection: - Correction and rerun method: - Local close and group close ownership: ### Reference case and expected checks The example uses one currency and a first-year opening capital contribution of 100,000. Machine cost is 24,000, life four years, no residual value; annual depreciation is 6,000. Cash service receipts and recognised annual revenue are both 12,000. Cash operating expenses are 4,000. Fictional current and deferred tax rates are 25%; current tax is paid before close. - Local pretax profit: 12,000 - 4,000 - 6,000 = 2,000. - Local current tax: 2,000 × 25% = 500. - Local profit after tax: 2,000 - 500 = 1,500. - Closing cash: 100,000 - 24,000 + 12,000 - 4,000 - 500 = 83,500. - Local net machine: 24,000 - 6,000 = 18,000. - Local assets and equity: 83,500 + 18,000 = 101,500. Assume the group's approved revaluation model gives the sole machine in the relevant class a closing value of 20,000, with no prior revaluation loss and an unchanged tax base of 18,000. - Group asset increase: 20,000 - 18,000 = 2,000. - Deferred-tax liability: 2,000 × 25% = 500. - Net other-comprehensive-income increase: 2,000 - 500 = 1,500. - Group assets: 83,500 + 20,000 = 103,500. - Group equity: 100,000 + 1,500 + 1,500 = 103,000. - Balance check: 103,500 - 500 - 103,000 = 0. The next year's unrounded group depreciation is 20,000 ÷ 3; local depreciation remains 6,000 under these assumptions. Keep a residual rounding rule for the final period. ### Rehearse failure and accept Importing the adjustment twice produces machine value 22,000, deferred tax 1,000 and net revaluation surplus 3,000. It still balances. Record how your process detects the incorrect valuation and removes the duplicate. - Failure batch references and detected control difference: - Correction/reversal reference: - Rerun snapshot and expected values: - Tax and roll-forward review: - Local/controller acceptance: - Group/controller acceptance: - Outstanding issues, owner and due date: - Evidence folder and retrieval owner: ## Related on this site - [Country pages](https://erplocalization.com/countries/): key facts with sources - [E-invoicing matrix](https://erplocalization.com/e-invoicing/): country × ERP support - [All guides](https://erplocalization.com/guides/) Vendor documentation is cited only as an example of the level of evidence to ask for; it is not a recommendation or a ranking. This guide is general information, not tax or legal advice. Checked 2026-10-17. Related: [Glossary](https://erplocalization.com/glossary/) – abbreviations and terms used in these guides (SAF-T, Peppol, CTC, EN 16931, IFRS and more). --- Canonical: https://erplocalization.com/guides/parallel-books-local-gaap-group-reporting/ · Last updated: 2026-10-17 · Informational only; not tax, legal or implementation advice. Featured placements are paid or promotional and do not affect the compliance data. Data: CC BY-NC 4.0 (commercial use needs a licence: https://erplocalization.com/data-licence/), attribution "ERP Localization (erplocalization.com)".