Choosing Between a Reporting Currency Ledger and a Secondary Ledger for a Mexican Subsidiary
Northwind Components is implementing Oracle Cloud General Ledger. The US parent, Northwind Inc., has a primary ledger in USD, calendar Jan–Dec, and a chart of accounts with Company, Cost Center, Natural Account, and Product segments. Its Mexican subsidiary, Northwind de México, must keep local statutory books in MXN under Mexican GAAP, maintain a local chart of accounts with a different natural-account structure, and post local adjusting journals that should not appear in the US parent's consolidation. The subsidiary's controller also wants a monthly USD view for group reporting. The design team proposes one primary ledger in USD with Company as the balancing segment, plus a reporting currency ledger in MXN, arguing that this meets the local requirement because the reporting currency ledger can hold the local adjustments. Go-live is in eight weeks, and the team has not yet decided whether to use a secondary ledger. Volume is modest: about 1,200 subledger journals and 60 manual journals per month at the subsidiary.
1. Is the proposed reporting currency ledger sufficient for the Mexican statutory requirement? Explain the decision criteria and recommend the ledger architecture.
Read the worked answer
No. A reporting currency ledger is tied to the primary ledger, uses the same chart of accounts and calendar, and holds only converted balances; it cannot accept local adjusting journals or a different natural-account structure. The Mexican requirement therefore points to a secondary ledger: MXN currency, local chart of accounts, and local accounting method, attached to the USD primary ledger. Keep the US primary ledger as the consolidation ledger. The secondary ledger is maintained from the primary ledger by journal conversion, so the next decision is the conversion level, not whether the reporting currency ledger can hold adjustments. A reporting currency ledger can give the subsidiary a USD view, but it is not a local book of record. Confirm the supported conversion path early because the Mexican chart of accounts differs.
2. What conversion level and configuration would you recommend, and what would you validate in the eight weeks before go-live?
Read the worked answer
Choose the conversion level from how the local controller uses the books. If local statutory reporting needs local journals and detail, and the different chart of accounts can be mapped, use subledger or journal conversion; if local books are only a summary statutory balance, balance-level conversion is simpler and less fragile. Map local natural accounts to the primary accounts, set the secondary ledger's calendar and currency, and decide which local adjustments are allowed. Validate with a full month of representative transactions, including local entries that must not reach the US primary ledger. Confirm that intercompany and elimination entries behave correctly and that the secondary ledger period can be controlled independently. Also verify that no one posts to the reporting currency ledger. Eight weeks is tight for a different chart of accounts; prioritize account mapping and a parallel close.
3. What is the risk of representing Mexico only through a balancing segment in the USD primary ledger?
Read the worked answer
If Mexico is represented only by a balancing segment in the USD primary ledger, local MXN statutory balances and local GAAP adjustments are forced into the group ledger and chart of accounts. Local reporting then depends on translation or revaluation rather than local books, auditability of statutory entries weakens, and the team carries continuous mapping effort. It also mixes local adjustments into the consolidation ledger, which the group wants to avoid. A balancing segment is for legal-entity balancing, not for creating a separate statutory book. Use the secondary ledger and keep Company as the balancing segment in each ledger.