DATAMASONLedger

Transaction matching

Match payments to invoices, settlements and ledger entries.

Deterministic rules handle the clear cases, tolerances and scoring handle the near ones, and people see only what is left, with evidence already assembled.

Inputs
Normalized payments, invoices, settlements, ledger entries
Outputs
Matches with rule, score and evidence
Controls
Rule priority, tolerances, review thresholds

The problem

References are missing, partial or wrong.

Customers pay without references, gateways batch payments, and fees reduce amounts. Simple lookups miss these cases and leave teams matching by eye.

  1. 01

    Payments arrive without an invoice reference

  2. 02

    One payment can settle several invoices

  3. 03

    Fees and deductions change the amount

The solution

Rules first, scoring second, people last.

Every match records the rule that fired, the fields compared and the alternatives considered. The result is a decision you can explain to an auditor.

  • Reference rules: Exact and normalized reference matching across sources.
  • Tolerances: Allow bounded differences for fees, rounding and FX, per rule set.
  • One-to-many matching: Match one invoice to several payments, or one payment to several invoices.

Product

Follow one transaction across four systems

Choose a scenario to see how a bank credit, a payment, an invoice and a ledger entry are linked, or why they are not.

Match lineageSample data
  1. Bank transaction₹50,000ICICI Bank ••4821Credit · UTR 482910••••14 Sep 10:42
  2. PaymentPAY-92790Razorpay · captured₹50,000 · INRSettlement stl_7H2K9P
  3. InvoiceINV-1024₹50,000 · due 14 SepCustomer cus_20418Status: open
  4. Ledger entryLE-004217Debit Bank 50,000Credit Receivable 50,000Balanced · Dr = Cr
Matching…Comparing records across systems

Capabilities

What it does, specifically.

  • Reference rules

    Exact and normalized reference matching across sources.

  • Tolerances

    Allow bounded differences for fees, rounding and FX, per rule set.

  • One-to-many matching

    Match one invoice to several payments, or one payment to several invoices.

  • Duplicate detection

    Flag repeated captures with the same reference and amount in a short window.

  • Explainable scores

    A score and its contributing factors accompany every non-exact match.

  • Custom rules

    Define your own rules and priorities. Shown conceptually; part of the proposed Growth plan.

Workflow

How it works, step by step.

  1. 1

    Select candidates

    Narrow possible counterparts by amount, date and party.

  2. 2

    Evaluate rules

    Run rules in priority order against each candidate.

  3. 3

    Score

    Apply tolerances and scoring where rules are inconclusive.

  4. 4

    Decide

    Accept, route to review, or leave unmatched.

  5. 5

    Record evidence

    Store the rule, fields and score with the match.

Matching waterfallSample data
Exact reference9,412ref_equals_invoice
Amount + date window1,980amount_date_window
Tolerance rules612amount_within_tolerance
Scored candidates192candidate_score ≥ 0.90
Matched12,196sum of the stages above
Unresolved28438 exceptions · 246 pending
Rule (conceptual)Proposed Growth plan
# Match payments to invoices within ₹500
rule: "gateway_fee_tolerance"
when:
  payment.reference == invoice.reference
  abs(payment.amount - invoice.amount) <= 500
then:
  match(score=0.92, reason="within_tolerance")
priority: 30

Make every financial transaction explainable.

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