Hardi Jain is a product manager. This portfolio is drawn in the browser and needs JavaScript to play. You can find him on LinkedIn and GitHub.

Hardi Jain · AI and SaaS product manager

Turning audit logic into an automated workflow

I converted an auditor’s repeated reconciliation logic into a reusable system, so auditors could focus on investigating exceptions rather than performing the same calculations manually.

01 · THE OLD WAY

Thousands of transactions. The same logic, repeated every time.

Investment registers contained thousands of transactions that had to be tested through a series of reconciliations and account mappings.

For each sample, auditors had to reconstruct the expected closing position, validate purchases and sales against the relevant accounts, and verify other income such as dividends and interest.

02 · THE RECONCILIATION WEB

Every transaction had to find its way back to the financial statements.

The work wasn’t a single calculation. Each transaction had to connect to the right financial evidence and ultimately reconcile back to the financial statements.

The challenge was doing this consistently across large transaction populations while still identifying the exceptions that required auditor judgment.

03 · THE QUESTION

What if the logic didn’t have to be repeated by the auditor?

The underlying audit logic was repeatable.

If the rules could be defined once, the system could perform the calculations and reconciliations consistently, leaving the auditor to investigate what didn’t reconcile.

04 · DEFINE THE LOGIC

We turned audit procedures into rules.

We defined the underlying audit logic at the backend.

The system could calculate the expected closing balance, map transactions to the relevant accounts, calculate profit or loss on sales, incorporate dividend and interest income, and identify differences against the expected balances.

05 · THE USER EXPERIENCE

The auditor didn’t need to perform the calculations anymore.

The user’s job became simpler: upload the required data, review the automated output, investigate the differences, and document the conclusion.

The auditor moved from calculation to investigation, rather than simply from manual to automated.

06 · THE EXCEPTION BECOMES THE PRODUCT

Automation didn’t replace the auditor. It changed what the auditor spent time on.

Instead of spending time performing the same calculations across samples, auditors could focus their attention on the transactions where the system identified a difference.

07 · THE INVESTIGATION

Automation identifies where human judgment is needed.

When the expected closing position did not agree with the financial statements, the system surfaced the difference rather than resolving it.

Deciding what the difference meant stayed with the auditor.

08 · THE SCALE

From repeated calculations to exception-driven review.

The workflow was standardised across 50 client engagements and more than 150 auditors, contributing to a 40–50% reduction in audit cycle time.

The numbers are the proof, not the story.

Transaction → logic → exception

Where this leads

Contact me

Connecting the dots

“You can’t connect the dots looking forward; you can only connect them looking backward.”

— Steve Jobs

Map