Multi-entity close support from a Philippines bookkeeper

Give each entity its own close status, bank and subledger dependencies, preparer, reviewer, and cutoff. Shared tasks may use one operating calendar, but the evidence and approval trail should still identify the legal entity so one company’s completion does not mask another’s open work.

Use the same reconciliation and exception structure while keeping each entity’s policy and source systems explicit. A Philippines bookkeeper benefits from repeatable fields, not from pretending the entities are identical.

For each task, show the entity, book, currency, account, source, preparer, reviewer, and deadline. A bill paid by Entity A for Entity B must be held for documented intercompany treatment rather than posted to whichever ledger is open. The Philippines bookkeeper can prepare the evidence and proposed entries; entity owners approve the final posting.

Match balances, invoices, dates, currencies, and references before the final consolidation window. Route differences to the entity owners with a specific question and supporting evidence.

Record the transaction currency, functional currency, rate source, and translation treatment required by policy. Escalate rate or remeasurement questions rather than applying an unapproved shortcut.

After each entity closes, compare intercompany balances, currencies, due-to and due-from accounts, and shared schedules. Explain a difference as timing, exchange movement, a missing source, or an unresolved classification. Keep entity-level evidence attached so a consolidated number does not hide a local exception.

The support role can prepare eliminations and tie-outs under documented instructions. The controller or authorized finance lead approves consolidation adjustments, policy decisions, and final reports.

Show each entity’s close status, unresolved items, confirmations, proposed entries, and reviewer sign-off. This gives management a usable view of readiness without hiding entity-specific risk.