Key answer: define the currency and population before mapping the ERP accounts
A usable SAP Business One handoff identifies the company database, reporting period, currency columns, G/L population, business-partner detail and closing-entry treatment. Reconcile these settings before using the numbers in Schedule III. Mixing local and system currency or adding partner details to a control-account total can invalidate an otherwise balanced report.
This article concerns an Indian company using a file-based statutory-reporting bridge. Division I presentation is assumed for the mapping examples; an Ind AS company must assess its applicable division separately. Research was checked on 22 October 2026. SAP versions, localisations, report layouts and user permissions differ. Historical documentation cited below explains reporting concepts and is explicitly identified as such, rather than being presented as a current screen-by-screen manual.
Keep local, system and foreign currency amounts separate
SAP's official currency learning material explains parallel local and system currencies and account-currency settings. Local and system figures can describe the same transaction in different units. They are not amounts to add together. For an INR statutory working, first confirm that the chosen source column supplies the intended INR accounting amounts; do not infer this solely from the column position or a global parent's reporting currency.
Store source currency, amount, account code and reporting period explicitly in the handoff. Preserve foreign-currency balances as supporting information where needed. A translation or valuation adjustment needs its own supported accounting working. Importing a system-currency total and attaching an INR label does not perform a conversion.
Reconcile business-partner detail to control accounts once
Use the G/L population as the accounting backbone and partner detail to support its breakdown, unless the documented extraction design intentionally substitutes that detail for the corresponding control totals. Define which rows are accounting balances, subtotals and analysis-only lines. A report containing both control and partner information is not permission to import all rows additively.
Retain reconciliation differences by customer/vendor and control account. Check accounts for doubtful debts, bills or other relevant control categories rather than assuming one debtor and one creditor account captures everything. Do not erase an unresolved difference through a suspense classification in the final statements.
Understand what period-end closing did to the report
SAP's 2014 guide for Business One 9.1 discusses partner/control-account reconciliation, report settings and period-end closing. It warns that including closing balances can zero a historical P&L after the closing routine. Its menu examples are historical and based on the stated version/localisation. Confirm the equivalent settings in the installed version and retain both annual-performance evidence and the closing-entry bridge.
A post-close balance-sheet trial balance and an annual P&L can be mutually consistent while serving different purposes. Do not conclude that annual revenue was zero because nominal accounts were transferred to a closing account. Conversely, do not add a second current-year profit transfer to equity when the imported equity already includes the closing result.
Convert the reconciled accounting population into statutory disclosures
The statutory Schedule III text, reproduced in Annexure A of the ICAI Division I publication, supplies the reporting headings and disclosure framework. ERP account names do not determine all current/non-current, borrowing or disclosure decisions. Obtain maturities, counterparty information, asset schedules and other applicable evidence. Identify local statutory adjustments separately from parent-reporting entries.
Keep a bridge from the approved SAP account balances to any local statutory adjustments and then to the final statements. Retain both the annual performance and closing-position views, with precise scope labels. This procedure does not assert a direct SAP connector or automatic India-specific statutory compliance.
Worked illustrations
The following cases use fictional figures and stated assumptions. Amounts are Indian rupees unless a different unit is expressly shown. They illustrate preparation controls and do not represent real client results.
Illustrative example 1: parallel currency columns are the same balance in different units
Assume a source balance is INR ₹8,40,000 and its parallel system-currency amount is USD 10,000. Under the simplified illustrative conversion of ₹84 per USD, both represent the same ₹8,40,000. Adding 8,40,000 and 10,000 as if both were rupees creates ₹8,50,000 without any accounting transaction. Select the intended INR column and retain the USD information separately.
Illustrative example 2: control totals and partner rows must not be added
A debtor control account is ₹9,00,000. Its reconciled customer detail is A ₹5,00,000 and B ₹4,00,000. Import either the control balance with analysis-only detail or the properly designed detail substitute. Importing all three rows as independent assets creates ₹18,00,000, overstating receivables by ₹9,00,000.
Illustrative example 3: the closing routine zeros nominal accounts but not annual performance
Annual revenue is ₹50,00,000 and expenses are ₹42,00,000, giving profit of ₹8,00,000 before omitted consequential matters. After a closing transfer, a nominal-account view can show zero closing revenue and expense balances. Use the correctly scoped annual-performance report to support ₹50,00,000 and ₹42,00,000, and reconcile the ₹8,00,000 transfer rather than reporting no activity.
Illustrative example 4: retained earnings already includes the transfer
Opening retained earnings are ₹12,00,000 and the supported closing transfer is profit of ₹3,00,000. Post-close retained earnings are ₹15,00,000, assuming no dividends or other movements. Adding the same ₹3,00,000 again in the statutory bridge creates ₹18,00,000 and a ₹3,00,000 overstatement.
Illustrative example 5: a supported currency adjustment changes the local balance
Assume a foreign-currency payable of USD 2,000 has a local carrying balance of ₹1,66,000 before a separately supported closing adjustment. An illustrative applicable rate of ₹84 gives ₹1,68,000, a difference of ₹2,000. If that ₹2,000 has already been posted into the chosen local-currency trial balance, applying it again in the bridge creates ₹1,70,000. This example assumes the valuation basis is appropriate to the actual item.
Illustrative example 6: a late local adjustment changes the statutory result
The approved source result is profit ₹6,50,000. A supported local expense accrual of ₹40,000 gives adjusted profit of ₹6,10,000 before consequential tax effects. If the journal is subsequently posted to SAP, refresh the extract and remove or reconcile the separate bridge entry. Keeping both would reduce profit again to ₹5,70,000.
Ten-step verification table
| Step | Verification | Evidence to retain |
|---|---|---|
| 1 | Identify the legal entity and source database. | Database/company and extraction record. |
| 2 | Record period boundaries and date/filter choices. | Report criteria and exported headings. |
| 3 | Choose and label the intended reporting-currency column. | Currency definitions and reconciliation. |
| 4 | Identify accounting rows, subtotals and partner analysis. | Extraction data dictionary. |
| 5 | Reconcile partner details to every relevant control account. | Control/partner bridge and resolved differences. |
| 6 | Document opening and closing-entry report settings. | Annual performance and closing-position evidence. |
| 7 | Reconcile current-year profit transfers to equity once. | Retained-earnings and closing-account working. |
| 8 | Review local statutory and parent-reporting adjustments. | Separate supported adjustment lists. |
| 9 | Prepare required Schedule III notes and comparatives. | Statutory mapping and supporting schedules. |
| 10 | Freeze and reconcile the final source-to-output release. | Versioned files and approved final bridge. |
Sixteen practitioner FAQs
1. Can I add local and system currency balances?
No. They can be parallel representations of the same transaction. Define the reporting currency and retain the other column as separately labelled supporting information.
2. Is system currency always the statutory currency?
No. SAP explains that it may be a different currency useful to a group head office. Confirm the actual company configuration.
3. Does a foreign-currency column replace INR accounting?
No. Establish the appropriate INR source balances and any supported valuation or translation adjustments. A label change is not a currency conversion.
4. Should customer rows be imported in addition to debtor control?
Not as independent additive balances where they break down that control total. Define the extraction design and reconcile the detail.
5. What if the partner report does not match one control account?
Check all relevant assigned control categories and report settings. Investigate actual differences rather than forcing a total through a balancing row.
6. Why might the post-close P&L show zero?
Nominal accounts may have been closed through the period-end routine. Check report settings and obtain the properly scoped annual-performance evidence.
7. Can I reverse every closing journal to recover the P&L?
Do not alter the accounting system merely to obtain a report. Use the supported reporting settings and a documented reconciliation with the responsible finance team.
8. Should current profit be added again to post-close equity?
Only if the source does not already include the relevant transfer. Trace the equity roll-forward and ensure one recognition of the result.
9. Are the cited 9.1 menu steps current for every installation?
No. They are historical documentation of concepts. Check equivalent behaviour in the installed version and localisation.
10. Does this guide assert a native SAP-to-assureFinancials connector?
No. It describes a controlled trial-balance file bridge. Use only integrations and file formats confirmed for the actual products.
11. Can a parent-reporting adjustment be copied into Indian statutory accounts?
Assess its purpose and applicable accounting framework first. Parent-reporting treatment does not by itself establish local recognition or presentation.
12. What if a valuation adjustment has already been posted?
Use the refreshed source amount and avoid duplicating the same adjustment in the statutory bridge. Retain the journal identity.
13. Do ERP headings establish current/non-current classification?
No. Use the actual rights, obligations, maturities and operating-cycle evidence under the applicable reporting framework.
14. Should I rely on a report missing the final adjustment date?
Re-export or reconcile the excluded adjustments explicitly. Identify the final cut-off so the scope is reproducible.
15. Can a balanced ERP trial balance still produce an incorrect statutory set?
Yes. Wrong currency, duplicated analysis, missing notes or unsupported mapping can remain even when debits and credits balance.
16. What should be archived with the handoff?
Retain source settings, G/L balances, partner reconciliations, currency definitions, closing-entry bridge, local adjustments and the final output version.
Practical use with assureFinancials
Use this working alongside assureFinancials and the assureOffice tools. Confirm the import fields and export options actually available in your version before selecting the workflow. A file-based handoff does not itself establish a native integration, automatic legal compliance or the completeness of the supporting disclosures.
Conclusion
Treat the SAP extract as a defined accounting population. Preserve currency labels, use partner detail once, and reconcile annual performance to post-close equity before preparing the statutory statements.