
Financial Due Diligence
Get to the earnings questions sooner.
Reconcile the exports, investigate earnings and working capital, and bring the evidence into senior review.
Every hour spent rebuilding the data is an hour less to investigate the business.
Explore an example
From EBITDA to the entries behind it.
Start with reported earnings. Click an adjustment to see the ledger, supporting record, and reconciliation behind it.
Illustrative sample data. Click to explore the analysis and its supporting evidence.
See it with your own dataFinancial Due Diligence
From incoming files to findings ready for review.
- 01
Prepare the financials
Bring GL detail, trial balances, and supporting schedules into a reconciled dataset. Review the mappings, transformations, and remaining differences.
- 02
Investigate earnings
Explore revenue and margin movements, isolate one-offs, and follow the transactions behind a proposed adjustment.
- 03
Work through working capital
Analyze balances and movements across periods. Investigate cut-off questions and unusual entries with the supporting records alongside them.
- 04
Follow the supporting evidence
Compare contracts, invoices, and other documents using the same questions, with answers linked to the relevant pages.
- 05
Bring the work into review
Prepare an editable workbook with findings linked to their source, so senior reviewers can challenge an adjustment without rebuilding the analysis.
Example workflow
Is the proposed EBITDA add-back supported?
- 01
Start with the records
Bring in the GL, trial balance, management’s adjustment schedule, and supporting invoices.
- 02
Reconcile the inputs
Map the accounts, check the balances, and identify missing records before assessing the adjustment.
- 03
Investigate the adjustment
Isolate the relevant transactions and compare management’s explanation with the underlying evidence.
- 04
Prepare for review
Carry the proposed adjustment, supporting records, and open questions into an editable workbook.
For review
An adjustment analysis the engagement team can inspect, challenge, and trace to source.
Every team, every engagement.
Client datastays under control.
Ask about securityYou’re working with client ledgers and confidential data rooms. SecondState keeps each engagement separate, every change reviewable, and every answer traceable.

EU or US hosting
Your data stays in the region you choose. The two deployments are separate, and nothing is copied between them.
One project per engagement
Files and analysis are scoped to a project. Nothing is visible outside it unless you share it.
Every figure traced
Answers link to the rows and pages behind them, so a reviewer can check any number.
Nothing changes without you
Data transformations are validated and shown to you before they’re used. Destructive actions need approval.
Full revision history
Workbooks keep every revision. Inspect what changed or restore an earlier version.
Activity on record
Project activity and agent work are logged, so you can see who did what and when.