Before you share financial data, you should know how it is handled.
What is in the product today, and what we answer in writing on request. We publish a control as available only once it is confirmed.
A 30-minute walkthrough with the team that builds FinConso.
- Role-based access and maker-checker
- Full audit trail and period locks
- AI never posts without approval
Controls & security
Audit-ready by design.
Built by a firm that also runs a cybersecurity practice, for teams that answer to auditors and audit committees.
Role-based access
Entity-level and module-level permissions. Portal users see only their own balances.
Maker-checker approvals
Journals, mappings and rate changes need a second pair of eyes before they post.
Full audit trail
Every change to structure, mapping, rates and notes is logged with who, when and why.
Period locks
Closed periods and exchange rates are locked, so signed numbers stay signed.
In detail
Data, access, AI and enterprise readiness.
"In the product" means available today. "Answered on request" means we will answer in writing for your security review; ask through the contact page.
Data protection
- Answered on requestEncryption in transit and at rest
- Answered on requestData hosting location
- Answered on requestData retention and deletion
- Answered on requestBackup and disaster recovery
- In the productHandling of pilot and customer financial dataMutual NDA before any data is shared; access limited to the named team.
Access and controls
- In the productRole-based access by entity and moduleUsers see only the entities and modules they are granted.
- In the productApproval workflows (maker-checker)Journals, mappings and rates need a second approver before they post.
- In the productAudit loggingEvery change logged with who, when and what changed.
- In the productPeriod and rate locksClosed periods and exchange rates are locked.
- Answered on requestAuthentication controls (single sign-on, multi-factor)
- In the productSeparation of dutiesPreparer and approver roles are separate on every approval.
AI governance
- In the productAI cannot post journals or change records without approvalAgents propose; a named reviewer approves.
- In the productAI outputs reviewed by a personSuggestions show their evidence and wait for review.
- Answered on requestWhether customer data is used to train external AI models
- Answered on requestWhich AI providers or services process customer data
Enterprise readiness
- Answered on requestSecurity certificationsWe do not claim certifications held only by our infrastructure providers.
- Answered on requestIndependent security assessment
- Answered on requestIncident response procedure
- Answered on requestAvailability and support commitments
- Answered on requestData processing terms
AI governance
How AI touches your financial records.
Proposes, never posts
Agents suggest matches, codes, corrections and drafts. A named reviewer approves before anything posts.
Shows its evidence
Every suggestion carries the records it used, so the reviewer can inspect it before deciding.
Recorded in the trail
The proposal, the change and the approver are all kept with the period.
Switchable
Each agent can be enabled or disabled per entity and module.
Book a demo
See the consolidation workflow, from trial balance to signed statement.
A 30-minute walkthrough with the people who build FinConso.
Entities, eliminations, translation, NCI and the multi-GAAP layer, run live on a sample group. Every consolidated figure drilled back to the entity and account it came from. Questions on IFRS, US GAAP, Ind AS or SFRS(I) answered by the team that builds the product. Want to test it on your own numbers? See how the structured pilot works.
Online booking opens soon.
The booking form is being set up. Please check back shortly.
