DATAMASONLedger

Reconciliation

Reconciliation that doesn’t wait for month-end.

DATAMASON Ledger continuously compares transactions across banks, gateways and books, closes what agrees, and measures what does not.

Inputs
Matched records, settlements, ledger entries
Outputs
Reconciled items, classified differences
Controls
Cut-offs, tolerances, run history

The problem

Reconciliation happens too late.

When reconciliation is a monthly spreadsheet exercise, differences are found weeks after they occur, when evidence is harder to trace and the books may already be reported.

  • Differences surface weeks after the transaction
  • Timing differences look like errors
  • Evidence is scattered across exports

The solution

Continuous comparison across three views.

Gateway activity, bank receipts and ledger postings are compared on every run. Timing differences are separated from true exceptions, so people only investigate what needs a human.

  • Continuous runs: Reconcile as data arrives instead of waiting for a period end.
  • Three-way comparison: Compare gateway, bank and ledger views of the same money.
  • Settlement tracking: Follow captured payments through batches to bank receipt.

Product

Gateway, bank and books, side by side

Captured funds should equal funds received plus funds still in settlement. Anything else is a difference to explain.

Three-way reconciliationSample data
Gateway captured₹48.2M
Bank received₹46.1M
Books posted₹48.2M
Timing difference₹2.1MCaptured by the gateway, not yet received in the bank. In settlement; expected on the settlement schedule.
  • Captured ₹48.2M = Bank ₹46.1M + In settlement ₹2.1M
  • Books ₹48.2M = Captured ₹48.2M
  • Unexplained difference ₹0

Capabilities

What it does, specifically.

  • 01

    Continuous runs

    Reconcile as data arrives instead of waiting for a period end.

  • 02

    Three-way comparison

    Compare gateway, bank and ledger views of the same money.

  • 03

    Settlement tracking

    Follow captured payments through batches to bank receipt.

  • 04

    Timing differences

    Classify in-transit amounts so they are not raised as exceptions.

  • 05

    FX variance

    Measure differences caused by exchange rates between booking and settlement.

  • 06

    Run history

    Every run is recorded with scope, counts and outcomes.

Workflow

How it works, step by step.

  1. 1

    Ingest

    New records arrive from every connected source.

  2. 2

    Compare

    Matched records are compared with settlements and ledger entries.

  3. 3

    Classify

    Differences are typed: timing, amount, missing, duplicate, FX.

  4. 4

    Close or raise

    Balanced items close; the rest become exceptions.

  5. 5

    Report

    Summaries update for finance and for the API.

Sample reconciliation run · Sep 2026
OutcomeRecordsValueMeaning
Matched12,196₹48.2MAgree under a rule; closed or in settlement
Exceptions38₹1.4MDifferences classified and routed to owners
Pending246₹620KAwaiting a counterpart or settlement report
Total ingested12,480₹50.22MEverything the run compared

Make every financial transaction explainable.

Connect your financial systems, reconcile transactions automatically, and build a reliable source of financial truth.