Explore

What happens after a financial exception is found?

Reconciliation can tell you that something doesn't match. The harder work is understanding why, gathering the evidence, deciding what to do, following up and remembering what happened next time.

ReclaimLedgerAI is currently in controlled beta validation.

ReclaimLedgerAI is a post-reconciliation financial exception operations platform. Reconciliation finds the difference. ReclaimLedgerAI helps with what happens next. The full explanation is on the company page.

A real kind of problem

Finding the mismatch is not the hard part.

An illustration of the gap. These figures are not a customer result and not a product calculation.

Books

₹10,00,000

GST records

₹8,50,000

Difference

₹1,50,000

Now what?

Why is there a difference?

A mismatch is a signal. It does not yet say which record is incomplete, late, duplicated, or outside the period.

Which records are involved?

The books and the GST records have to be looked at together, invoice by invoice, before anyone can say what the difference is made of.

What evidence explains it?

Someone still has to gather the source rows, the portal lines, and the note that explains the gap.

Who needs to act?

The next step may sit with finance, a supplier, or another team. Finding the mismatch does not assign that work.

What decision should be made?

A person decides what the evidence supports. The product is not the authority for that decision.

Has someone followed up?

The open loop often moves into email or chat, and the review no longer shows whether it moved.

Was it resolved?

Resolution is an outcome someone can point to later, not a feeling that the spreadsheet was closed.

What happened last time?

The next cycle starts colder when the earlier decision lives only in one person's memory.

What happens next month?

A recurring review meets the same supplier, the same kind of gap, and often none of the last answer.

The longer workflow

The work starts after the mismatch.

Reconciliation is one point in the work. The rest is what happens to the exception after it is found.

  1. 01Exception
  2. 02Context
  3. 03Investigation
  4. 04Evidence
  5. 05Decision
  6. 06Action
  7. 07Resolution
  8. 08Memory

How we think about it

From exception to resolution.

GST is our first proving ground. We're testing whether the same resolution pattern creates value across recurring financial workflows. That broader use is not yet proven.

01

Understand

Bring together the records, context and evidence around the exception.

02

Decide

Keep the professional's judgement at the centre.

03

Resolve

Track the action, follow-up and outcome.

04

Remember

Carry the relevant history into the next review.

Where software assists, it assists with summarisation, context extraction, investigation support and drafting. Consequential financial and tax decisions stay with the professional.

The beta path

See the work.

This is the controlled beta review path, described as it works today. It is not a tour of features we have not built.

Overview

A period review separates what matches from what needs attention.

Purchase Register and GST portal files are compared for one company, GSTIN and period. The position is purchase value from the supplied records. It is not an ITC claim and not a tax conclusion.

Validation

We're building from what we learn.

These are observations from the work so far, not measured market facts.

What we initially thought

Reconciliation was the main problem.

What we're learning

Many organisations already have reconciliation tools.

The deeper problem we're exploring

The work after reconciliation is fragmented.

Investigation, evidence, follow-up, decision and continuity often leave the review.

Also in view

Judgement, history, and follow-up still sit with people.

Human judgement remains important. Historical context matters in a recurring review. Systems often identify an exception without owning the rest of the journey. Supplier follow-up can stay manual. Whether this is valuable has to be shown through repeated real use.

Proving ground

Why GST first?

GST is our first proving ground because it creates recurring financial reviews involving multiple records, counterparties, evidence, exceptions and follow-up.

We are not trying to replace accounting or reconciliation systems.

We're exploring what happens after those systems tell you something doesn't match.

If the resolution pattern proves valuable here, we can test it across other recurring financial workflows. Other domains are future hypotheses, not markets we are in.

Building in public

What we're testing now.

  1. Controlled beta

    A small set of people can exercise the review path. This is not a paid launch.

  2. Customer validation

    Does the workflow match work that already happens after a mismatch?

  3. Commercial readiness

    What would a serious offer have to include before anyone is asked to pay?

  4. Commercial launch*

    *Subject to validation. A date on this page is not a promise that launch will happen.

We would rather validate the problem than pretend we've already solved it.

Who is building this

We're building this from the problem outward.

A founder biography is not published on this website. Nothing here should be read as a credential, a customer count, or a completed track record.

The useful next step is a conversation about the work after a mismatch: what we are seeing clearly, and what we are still missing.

Still learning

We're still learning.

If you work in finance, run a finance team, advise businesses, build products or invest in early-stage companies, we'd like to hear what we're getting right — and what we're missing.

Talk to us opens the existing interest form. If that list is not connected, the form says so and nothing is saved. No email is sent. Explore the beta is the same form, with early access selected. It is not a login and not a self-serve account.