Financial statement review is two kinds of work.

One is judgment: reading for context-dependent issues, knowing what's material. That's what needs your head in the room.

The other is mechanical: recalculating subtotals, chasing cross-references across tables and notes, comparing this draft against the last one, checking whether the entity name is spelled the same way on page 4 as it is on page 47.

Most of what goes into a typical FS review is that second kind. Studio FSX takes it off the table.

How FSX works

You place markers in the source document, one for each figure, cell, or data point that matters. FSX reads the relationships between them and runs the checks.

Findings stay attached to their exact location in the document. When a new draft arrives, completed procedures carry forward. Your team only reviews what changed.

Setup takes under 2 hours for standard templates. Once you've structured a template, you reuse it across engagements.

What FSX checks

• Mathematical Accuracy. Every calculation validated automatically across tables, notes, and disclosures. Deviations shown in context.

• Internal Consistency. Figures compared across statements, notes, and disclosures. Mismatches flagged with source and destination references.

• Prior-Year Comparison. Current-year comparatives checked against the signed prior year before sign-off.

• Spelling & Text Review. Entity names, terminology, and disclosure language checked for inconsistencies that slip through manual review.

• Version Comparison. Drafts compared across values, wording, and structure. Review what changed, not the whole document again.

Output is timestamped and version-referenced. Exportable as a PDF. It fits the ISA 230 audit file without a separate working paper.

If you want to see FSX on a real financial statement, book a demo below or ask your dedicated CSM for more information.