Skip to content
Wayam AI
TechnologyQuality & ComplianceRepresentative scenario

Proving Parity on Regulated Financial Reporting Before Cutover

A bank migrating its risk and finance reporting cannot cut over until an internal audit function accepts that migrated figures are identical to the source.

Run on Setu · Legacy-to-Modern BI

Old and new outputs held side by side and shown to match exactly

The challenge

    01

    Any variance between source and migrated output, however small, blocks sign-off entirely.

    02

    Rounding, null handling, and date-boundary behaviour differ subtly between the source and target platforms.

    03

    Audit needs documented evidence per report, not a summary assurance that migration succeeded.

How Setu solves it

    01

    Deterministic Replay

    Source and migrated reports are executed against the same frozen dataset so any difference is attributable to the migration, not to data movement.

    02

    Value-Level Comparison

    Output is compared cell by cell rather than by summary statistic, so silent variance cannot pass.

    03

    Variance Classification

    Differences are classified as rounding, null-handling, or genuine logic divergence, and only the last requires engineering work.

    04

    Evidence Pack Generation

    Each report produces a documented parity record suitable for the audit file.

    05

    Gated Cutover

    A report cuts over only once its parity record is accepted.

The outcome

  • Parity evidenced per report rather than asserted across the programme.

  • Audit sign-off obtained on documented comparison rather than on assurance.

  • Cutover gated on evidence, so no report moved before it was proven.

Representative scenario: a modelled industry situation showing how this accelerator applies. Figures are projections, not a named client result.

Capabilities used

Every accelerator is assembled from the same capability layer, so a workflow you adopt here shares its foundation with the rest of the portfolio.

Bring us the version of this that you actually have.

Every engagement is fixed-scope and outcome-guaranteed. The scoping conversation starts with your systems, not with a template.