DATAMASONLedger

Exception management

Know what doesn’t match. Know why.

Every discrepancy gets a type, an expected and received amount, a ranked set of probable causes, an owner and a timeline. Nothing is silently written off.

Inputs
Failed matches, differences beyond tolerance
Outputs
Resolved items, approved adjustments, audit events
Controls
Roles, approvals, aging rules

The problem

Exceptions are discovered, then lost.

In a spreadsheet a mismatch is a highlighted cell. Nobody owns it, nobody knows why it exists, and nothing records how it was closed.

  • No owner and no due date
  • No explanation of why amounts differ
  • No record of who approved an adjustment

The solution

A workflow, not a highlighted cell.

Exceptions flow through investigate, assign, approve and resolve, with maker–checker approval for adjustments and an audit record at every step.

  • Typed exceptions: Amount mismatch, missing counterpart, suspected duplicate, unmatched credit and FX variance.
  • Probable causes: Rule-based, ranked explanations with the evidence for each.
  • Ownership: Assign to a person or role, with aging so nothing sits unowned.

Product

Work an exception

Pick an exception from the queue and use the actions. State changes are live in this demo.

Exception queue

38 open
Exception #EX-1842Sample data

Amount mismatch

The amount received does not equal the invoice.

Needs review
Expected₹50,000
Received₹49,500
Difference−₹500
Source
Payment Gateway
Invoice
INV-1042
Opened
14 Sep 12:41
Owner
Unassigned

Probable cause · rule-based, ranked

  1. 1Gateway fee or deductionDifference is exactly 1.0% of the invoice amount.strongest evidence
  2. 2Customer short-paymentNo second payment found against INV-1042 within the 7-day window.possible
  3. 3Rounding or FXBoth amounts are in INR; not applicable.unlikely

Timeline

  1. 14 Sep 12:41 · Payment received
  2. 14 Sep 12:41 · Automatic match failed · exception opened (amount mismatch)

Capabilities

What it does, specifically.

  • 01

    Typed exceptions

    Amount mismatch, missing counterpart, suspected duplicate, unmatched credit and FX variance.

  • 02

    Probable causes

    Rule-based, ranked explanations with the evidence for each.

  • 03

    Ownership

    Assign to a person or role, with aging so nothing sits unowned.

  • 04

    Maker–checker

    Require a second approver for adjustments above a threshold.

  • 05

    Aging and priority

    Sort by value and age so the work that matters comes first.

  • 06

    Audit record

    Every action is recorded with actor, time and reason.

Workflow

How it works, step by step.

  1. 1

    Detect

    A match fails or a difference exceeds tolerance.

  2. 2

    Classify

    Assign a type and rank probable causes.

  3. 3

    Assign

    Route to an owner or role.

  4. 4

    Investigate

    Review the evidence and related records.

  5. 5

    Approve

    Approve any adjustment, with a second approver where required.

  6. 6

    Resolve

    Close the exception and update the books.

Exception types in the sample workspace
TypeOpenValue
Amount mismatch14₹0.52M
Missing counterpart9₹0.41M
Suspected duplicate6₹0.19M
Unmatched bank credit7₹0.18M
FX variance2₹0.10M
Total38₹1.40M

Make every financial transaction explainable.

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