DATAMASONLedger

Financial data layer

One transaction model for every source.

Banks, gateways, ERPs and billing systems describe the same money differently. DATAMASON Ledger maps each into a standardized financial transaction model, so matching, reporting and APIs all speak one language.

Inputs
Statements, API payloads, settlement reports, vouchers
Outputs
Normalized transactions with lineage
Controls
Field validation, mapping versions

The problem

The same payment, five different shapes.

A single customer payment appears as a bank narration, a gateway event, an invoice status, an ERP voucher and a subscription renewal. Each uses its own identifiers, clocks, currencies and states, so nothing can be compared directly.

  1. 01

    Identifiers do not line up across systems

  2. 02

    Timestamps differ in time zone and precision

  3. 03

    Amounts arrive in different units and currencies

The solution

Map once. Match everywhere.

Every source is mapped into the Transaction model with its lineage preserved. Original values are never overwritten; normalized fields sit beside them, so any number can be traced back to the record it came from.

  • Source mapping: Declarative field mappings per source, versioned so changes are reviewable.
  • Identity resolution: Customers, invoices and payments are linked across systems by reference and attributes.
  • Currency handling: Original currency and amount are kept; base-currency conversion records the rate and its source.

Product

The Transaction model

Select a field to see how it is derived from a bank statement, a payment gateway and an ERP.

Transaction modelSample data
Transaction txn_48291

Field

invoice

The receivable this money should settle.

Normalized valueINV-1024string

Mapped from

Bank statementNarration (parsed)
Payment gatewaynotes.invoice_id
ERPdoc_no

Capabilities

What it does, specifically.

  • Source mapping

    Declarative field mappings per source, versioned so changes are reviewable.

  • Identity resolution

    Customers, invoices and payments are linked across systems by reference and attributes.

  • Currency handling

    Original currency and amount are kept; base-currency conversion records the rate and its source.

  • Timestamp normalization

    Every event is stored as timezone-aware ISO 8601, with the source value preserved.

  • Lineage

    Each normalized field points back to the raw record and mapping version that produced it.

  • API access

    Query the normalized model through the same API used for ingestion.

Workflow

How it works, step by step.

  1. 1

    Ingest

    Receive records by connector, file or API, unchanged.

  2. 2

    Map

    Apply the source’s field mapping to the common model.

  3. 3

    Validate

    Check types, totals, currencies and required fields.

  4. 4

    Link

    Resolve customers, invoices and payments across sources.

  5. 5

    Publish

    Make the model available to matching, reports and the API.

A normalized transaction, as the API returns it

Original source values stay available under raw; everything else is standardized.

TransactionConceptual
{
  "id": "txn_48291",
  "source": "gateway_a",
  "amount": 50000,
  "currency": "INR",
  "timestamp": "2026-09-14T10:42:11+05:30",
  "reference": "INV-1024",
  "reconciliation_state": "matched",
  "raw": "{ original gateway payload "}
}

Make every financial transaction explainable.

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