These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Financial Consolidation
- Implementation
How a Financial Consolidation rollout works
Configure one reconciled corporate close before extending the rollout.
Agree the reporting scope
Confirm entities, functional currencies, USD reporting, methods, source ledgers and reviewer authority.
Reconcile reference data
Verify effective ownership, group accounts, local mappings and approved rate layers.
Run a complete close
Accept each required entity, calculate translation, resolve intercompany differences and review supported adjustments and movements.
Exercise failures and corrections
Test missing entities, unmapped accounts, duplicate imports, unknown integrations, self-approval, rate changes and a linked restatement.
Review publication access
Verify signatures, financial locks, executive file access, auditor expiry and source-ledger permissions through both UI and API.
What the customer provides
Supply source-close evidence, account mappings, accounting-method workpapers, approved FX sources, ownership history, reporting layouts, movement evidence and the authorised recipient list. Confirm access to the source ledgers and document service.
Changing it afterwards
Future-period changes use new effective configuration versions. A changed open candidate repeats affected reviews; a published close is preserved and corrected through an authorised restatement. Keep the source specification, website capability descriptions and Proto app skill aligned with the approved change.
Set up Financial Consolidation your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.