Consolidation.app
consolidation.app
- Web
What Consolidation.app is
Consolidation.app is a web workspace for controlled group reporting across entities. Its guided close workflow takes entity packages through collection, account and dimension mapping, intercompany matching, explanations, proposed eliminations, and approvals. Packages can include a period, currency, source ledger, owner, and validation status, while mappings connect local accounts and dimensions to the group chart with ownership visible. The workflow pairs receivables and payables by entity, counterparty, currency, document, and period. Reviewer decisions and unresolved limitations remain visible; group output is held until accountable reviewers resolve exceptions and accept the reporting package. People remain responsible for confirming source completeness, resolving policy choices, evaluating explanations, and approving postings and close. The public preview is illustrative only: it does not post entries, run a live close, validate accounting conclusions, or produce financial statements. The site describes security measures including Secure HttpOnly session cookies and organization-scoped PostgreSQL Row Level Security, but says these are not a certification or compliance guarantee. Enterprise controls and production-data scope require a signed agreement. Pricing is available on request.
Who it suits
It may suit teams looking for a structured group-reporting workflow across entities, with people assigned responsibility for review and approval. The public preview is illustrative, not a live close or financial-statement tool.
Good to know, and what to watch
- Entity packages can record period, currency, owner, and validation status.
- Mappings show ownership for local accounts and dimensions.
- Intercompany positions are paired across several identifying fields.
- Reviewer decisions and open limitations remain visible.
- The workflow holds group output pending reviewer resolution.
- The public preview does not operate a live close.
- It does not produce financial statements or post entries.
- Enterprise controls and production-data scope require a signed agreement.
- Pricing is available on request.
The verdict
Consolidation.app presents a controlled review flow for group reporting, with explicit human accountability. Treat the public preview as illustrative and confirm enterprise terms before considering production data.
What the maker publishes
- Close workflow
- The guided tour shows a workflow from collecting entity packages through mapping, matching, explaining, proposing eliminations, and recording approvals. source
- Close workflow
- The described workflow connects collection, mapping, matching, explanation, elimination proposals, and approval through close. source
- Company details
- The maker says registration, address, governing-law, and contracting details must be confirmed in signed commercial documents before enterprise contracting. source
- Company identity
- The site identifies Omni Logical Layers Technology LLC as the working company identity used across its early-access product surfaces. source
- Company identity
- The site identifies Omni Logical Layers Technology LLC as the working company identity used across its early-access product surfaces. source
- Data collection
- Collected entity packages can include period, currency, source ledger, owner, and validation status. source
- Enterprise controls
- Enterprise controls, recovery objectives, incident terms, and production-data scope require a signed agreement. source
- Enterprise terms
- Enterprise controls, recovery objectives, incident terms, and production-data scope require a signed agreement. source
- Entity data
- Its guided workflow collects entity packages with period, currency, source ledger, owner, and validation status. source
- Governance
- The close workflow retains reviewer decisions and open limitations, and holds group output until accountable reviewers resolve exceptions and accept the reporting package. source
- Human review
- The product tour assigns people responsibility for confirming source completeness, resolving policy choices, evaluating explanations, and approving postings and close. source
- Illustrative status
- The maker says the public workflows and records are illustrative and do not establish a live customer implementation or professional conclusion. source
- Intercompany
- The tour describes pairing receivable and payable positions by entity, counterparty, currency, document, and period. source
- Intercompany matching
- Receivable and payable positions are paired by entity, counterparty, currency, document, and period. source
- Mappings
- The tour describes relating local accounts and dimensions to the group chart with visible mapping ownership. source
- Preview limits
- The public preview says it does not post entries, operate a live close, validate accounting conclusions, or produce financial statements. source
- Product limitation
- The maker says this public preview does not post entries, operate a live close, validate accounting conclusions, or produce financial statements. source
- Product status
- The site says it is a public product and knowledge surface, and that illustrative workflows do not establish a live customer implementation or guaranteed outcome. source
- Purpose
- Consolidation describes itself as a controlled group-reporting workspace covering entity structures, collection, mappings, intercompany, eliminations, FX, adjustments, approvals, and reporting. source
- Purpose
- Consolidation describes itself as a controlled group-reporting workspace spanning entity structures, data collection, mappings, intercompany, eliminations, FX, adjustments, approvals, and reporting. source
- Security architecture
- The security page says public surfaces are statically generated, authentication uses same-origin server functions, session tokens stay in Secure HttpOnly cookies, and organization-scoped data uses PostgreSQL Row Level Security and membership checks. source
- Security architecture
- The security page says public surfaces are statically generated, authentication uses same-origin server functions, session tokens remain in Secure HttpOnly cookies, and organization-scoped data uses PostgreSQL Row Level Security and membership checks. source
- Security claims
- The security page says it is not a certification, penetration-test attestation, compliance guarantee, or customer-specific security review. source
- Security claims
- The maker says its security page is not a certification, penetration-test attestation, compliance guarantee, or customer-specific security review. source
Checked against the maker's pages on 5 Oct 2026.