
Audit
Get the client data ready. Keep the evidence connected.
Prepare accounting populations, investigate unusual entries, and keep the supporting records with the work.
Give the team more time to investigate, with a clear path from each finding to its supporting records.
Audit
From client exports to work a reviewer can follow.
- 01
Prepare the population
Standardize accounting exports, reconcile balances, and identify missing fields or periods before starting the analysis.
- 02
Investigate unusual entries
Query the ledger using the team’s criteria. Explore exceptions and drill into the transactions that need a closer look.
- 03
Connect the support
Review invoices, statements, and agreements alongside the accounting data, with document answers linked to their pages.
- 04
Make the work reviewable
Keep transformations, analysis, and source references visible so a reviewer can follow how the team reached a finding.
- 05
Keep the engagement together
Organize each engagement’s files and work in its own access-controlled project. The team directs the work and reviews the conclusions.
Example workflow
What explains these unusual year-end entries?
- 01
Prepare the ledger
Load the year’s GL and trial balance, check totals, and identify gaps in the population.
- 02
Apply the team’s criteria
Explore entries by date, amount, account, or other available fields to identify items for investigation.
- 03
Examine the support
Review the selected entries against invoices and other records, keeping missing evidence and open questions visible.
- 04
Hand over for review
Bring the analysis, criteria, and supporting references into a workbook for the engagement team to assess.
For review
A reviewable investigation with the underlying records and unresolved questions attached.
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.