DATAMASONLedger

Financial data infrastructure

One financial data layer.
Every transaction reconciled.

DATAMASON Ledger connects your financial systems, normalizes transaction data, automatically matches records, and creates one reliable source of financial truth.

EARLY ACCESS · SAMPLE DATA SHOWN

Finance teams · Fintech · SaaS · Ecommerce · Marketplaces · Enterprise

DATAMASON Ledger / Reconciliation overviewSample data
Sample workspaceSample period · Sep 2026

Connected sources

  • Bank3,120
  • Payment Gateway5,840
  • ERP1,710
  • Invoices1,260
  • Subscriptions550

DATAMASON Ledger

PAY-92812 MATCHED
₹21,500Razorpay · Payment Gateway

against INV-1031 · rule exact_amount_ref

  • Normalized12,480
  • Matched12,196
  • Reconciled96.0%

Financial truth

Matched₹48.2M96.0% by value
Exceptions₹1.4M38 open
Pending₹620K246 records
Settled₹46.1M₹2.1M in settlement
SourceReferenceAmountStatus
ICICI BankTXN-48291₹50,000Matched
RazorpayPAY-92812₹21,500Matched
StripeST-19382₹18,400Review
CashfreeCF-84219₹32,800Matched
RazorpayPAY-92841₹49,500Review
Open the interactive table

The layer

Between your transactions and your books.

Most finance stacks leave the work between where money moves and where it is recorded to spreadsheets. DATAMASON Ledger is the infrastructure layer for that work.

Where money moves

  • Banks
  • Payment gateways
  • ERP systems
  • Invoicing
  • Subscription billing
  • Marketplaces
  • Ecommerce platforms
  • Internal APIs
The layerDATAMASON Ledger
  1. 01NormalizeOne transaction model
  2. 02MatchRules, references, scoring
  3. 03ReconcileContinuous comparison
  4. 04VerifyApproved and recorded

One financial source of truth

Where truth goes

  • Reconciliation reports
  • Financial APIs
  • Accounting systems
  • ERP postings
  • Webhooks and exports

The problem

Your financial data shouldn’t live in five different systems.

Finance teams often have to manually compare transactions across disconnected systems.

Six systems, six dialects

  • BankUTR 482910•••• · CR 50000.00
  • Payment Gatewaypay_Nx82kQ1a · 5000000 paise
  • ERPGL-20418 · Dr 1010 · 50,000.00
  • InvoicesINV-1024 · due 2026-09-14
  • Subscriptionssub_8821 · plan_growth · INR
  • Marketplaceord_77310 · payout hold

Nothing lines up

  • Different formatsCSV · JSON · MT940 · XML
  • Different IDsUTR · pay_ · INV- · GL-
  • Different timestampsIST · UTC · epoch · date only
  • Different settlement statesCaptured · batched · pending · paid out

Manual reconciliation

Compared by hand, every week or month-end.

The solution

A unified infrastructure layer.

DATAMASON Ledger provides one place where every source is normalized, matched and reconciled, so finance teams spend their time on exceptions instead of comparisons.

Without a layerWith DATAMASON Ledger
FormatsEach source exported and reshaped by hand One transaction model, lineage preserved
MatchingLookups and manual comparison Rules, tolerances and explainable scores
DifferencesHighlighted cells with no owner Typed exceptions with causes and owners
EvidenceRebuilt for every audit Audit trail created as work happens

Workflow

Build one reliable financial source of truth.

Six stages take raw transactions to verified financial data. Select a stage, or let it play.

Stage 1 of 6

Raw transactions

Bank rows, gateway JSON, ERP vouchers and invoices arrive exactly as the source sends them: different fields, identifiers and clocks.

In
Statements · API payloads · reports
Out
Unaltered source records, preserved
{"id":"pay_Nx82","amt":5000000,"ts":1757846531}14/09 UTR482910 CR 50000.00INV-1024|50000|INR|2026-09-14

Platform

Five operations. One continuous workflow.

Connect, normalize, match, reconcile and resolve: each stage is a product surface, not a feature checkbox.

01

Connect

Connect financial systems and data sources.

Banks, payment gateways, accounting systems, ERP platforms and internal APIs feed one workspace through connectors, file import or API ingestion. Credentials stay encrypted and scoped to a single source.

See integrations
Add a sourceSample data
  1. 1 Choose
  2. 2 Authenticate
  3. 3 Map fields
  • Bank accountConnector
  • Payment gatewayConnector
  • ERPFile import
  • REST APIAPI
Field mapping preview
payment.idpayment
notes.invoice_idinvoice
amount (paise)amount
created_attimestamp
02

Normalize

Transform different transaction structures into a common model.

Every record is mapped into one financial transaction model: amounts, currencies, timestamps, references and parties. The original values are preserved alongside the normalized fields.

The financial data layer
NormalizationSample data

As received

{"id":"pay_Nx82kQ1a",
 "amount":5000000,
 "created_at":1757846531}

14/09 UTR482910 CR 50000.00

INV-1024|50000|INR|2026-09-14

As normalized

ReferenceAmountCurrencyTimestamp
pay_Nx82kQ1a50,000.00INR2026-09-14 10:42
UTR482910••••50,000.00INR2026-09-14 10:42
INV-102450,000.00INR2026-09-14 00:00
03

Match

Match payments, invoices, settlements and ledger records.

Deterministic rules run first, then tolerances and scoring. Each match records the rule that applied and the evidence behind it, so any result can be explained.

How matching works
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
04

Reconcile

Identify differences automatically.

Gateway activity, bank receipts and ledger postings are compared continuously. Timing differences are separated from real exceptions, and every difference is measured.

See reconciliation
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.
05

Resolve

Give teams a workflow for exceptions.

Each exception has a type, an expected and received amount, ranked probable causes, an owner and a timeline. Teams investigate, assign, approve and resolve, with every step recorded.

Exception management
Exception workflowSample data
38open exceptions by type · ₹1.4M in value
  • Amount mismatch14
  • Missing counterpart9
  • Suspected duplicate6
  • Unmatched bank credit7
  • FX variance2
Needs reviewInvestigatingApprovedResolved ✓

Interactive demo

See reconciliation happen.

A sample set of transactions from banks and gateways. Filter, search, replay the run, and open any row for its details.

TransactionsSample data
Sample transactions with reconciliation status. Select a row to open its details.
SourceReferenceAmountCurrencyStatusMatch
ICICI Bank₹50,000INRMatchedMatched
Razorpay₹21,500INRMatchedMatched
Stripe₹18,400INRReviewNeeds review
Cashfree₹32,800INRMatchedMatched
Razorpay₹49,500INRReviewNeeds review
Axis Bank₹124,300INRPendingAwaiting
Subscription billing₹4,999INRMatchedMatched
Shopify₹7,850INRMatchedMatched
Stripe$1,200USDReviewNeeds review
ICICI Bank₹32,000INRReviewNeeds review
Cashfree₹12,600INRPendingAwaiting
ERP₹15,000INRMatchedMatched
Stripe₹26,500INRMatchedMatched
Razorpay₹9,200INRPendingAwaiting

Showing 14 of 14 sample transactions · Select a row for details

Transaction lineage

From transaction to reconciliation—automatically.

Follow one transaction across the bank, the gateway, the invoice and the ledger. Switch scenarios to see how a mismatch is routed.

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

Exception management

Know what doesn’t match. Know why.

Every discrepancy has a type, a difference, a probable cause, an owner and a timeline. Work one below. Try Resolve.

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)

Financial data model

One transaction model for every source.

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

  • Original values preserved beside normalized fields
  • Lineage from every field back to its source record
  • Currency and time zone handled explicitly
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

Integration ecosystem

Connect your existing systems.

Banks, payment gateways, accounting, ERP, ecommerce, subscriptions and APIs. Connectors, file import or the API, whichever fits the source.

  • Planned
    Bank accountsStatements, credits, debits Connector
  • Planned
    Statement filesCSV, MT940, CAMT.053 File import
  • Planned
    Account aggregationConsent-based account feeds Connector
  • Planned
    RazorpayPayments, refunds, settlements Connector
  • Planned
    StripeCharges, payouts, balance transactions Connector
  • Planned
    CashfreePayments, settlements Connector
  • Planned
    Other gatewaysSettlement report files File import
  • Planned
    Accounting platformsLedgers, invoices, journals Connector
  • Planned
    Journal exportReconciled entries back to books API
  • Planned
    ERP systemsGL postings, vouchers, receivables Connector
  • Planned
    Voucher importScheduled file drops File import
  • Planned
    ShopifyOrders, refunds, payouts Connector
  • Planned
    Other storefrontsOrder and refund feeds API
  • Planned
    Subscription billingPlans, invoices, renewals Connector
  • Planned
    REST APIIngest and query transactions API
  • Planned
    WebhooksSigned events on state change API
  • Planned
    SFTP dropBatch file ingestion File import

Integration ecosystem. Connect your existing systems through connectors, file import or the API. Names indicate planned integration targets; availability is shown per tile, and no partnership or endorsement is implied. See all integrations

For developers

Financial infrastructure, available through APIs.

Ingest transactions, reconcile them and read the results programmatically, with webhooks for every state change.

  • Idempotent writes and typed errors
  • Signed webhooks for matches and exceptions
  • Test mode and a sandbox for safe experimentation

Conceptual API: shapes are illustrative until documentation is published.

POST /v1/transactions/reconcileConceptual
# Conceptual API: shapes are illustrative.
POST /v1/transactions/reconcile
Authorization: Bearer dm_test_••••••••
Idempotency-Key: 9f1c2a7e

{
  "transaction_id": "txn_48291",
  "reference": "INV-1024",
  "amount": 50000,
  "currency": "INR"
}

Security

Built for sensitive financial workflows.

An enterprise security architecture: designed in from the start, described openly, and not dressed up with certifications we have not earned.

  • Encryption

    Financial data is designed to be encrypted in transit and at rest, with keys managed separately from application data.

    Architecture target
  • Secure credentials

    Source credentials are stored encrypted, scoped to one connector and never displayed again after entry.

    Architecture target
  • Role-based access

    Roles for viewers, operators, approvers and administrators, with least privilege by default.

    Architecture target
  • Audit logs

    Access, changes and approvals are recorded with the actor, the time and the previous value.

    Architecture target
  • API security

    Scoped API keys per workspace and environment, rate limits, idempotency and signed webhooks.

    Architecture target
  • Workspace isolation

    Each workspace’s data is logically separated, with no cross-workspace queries by design.

    Architecture target
  • MFA

    Multi-factor authentication for user accounts, enforceable per workspace.

    Planned
  • SSO-ready architecture

    Identity is designed to sit behind SAML or OIDC single sign-on for enterprise workspaces.

    Planned

Controls marked Architecture target describe the design we are building to; Planned items are on the roadmap. Read the security overview

Use cases

Built for teams that move money in more than one place.

SaaS companies

Reconcile subscription payments and invoices.

Match renewals, proration, retries and refunds to invoices and settlements, across currencies.

  1. Subscription
  2. Invoice
  3. Payment
  4. Settlement
See the saas companies solution

Pricing

Priced on what you reconcile.

Plans are measured on transaction volume, connected sources, runs, retention, API usage and controls.

Proposed pricing concept · illustrative, not an offer
  • Starter

    For small finance operations.

    $49/mo
    Request access
    • Up to 3 connected sources
    • Automated matching
    • Exception queue
  • Growth

    For growing teams.

    $199/mo
    Request access
    • Up to 10 connected sources
    • Custom matching rules
    • Assignments and approvals
  • Business

    For larger financial operations.

    $599/mo
    Request access
    • Unlimited sources, fair-use
    • Maker–checker approvals
    • Scheduled reports
  • Enterprise

    For complex organizations.

    Custom
    Talk to sales
    • Custom volume and sources
    • SSO and SAML
    • Data residency options

Compare plans in detail

FAQ

Questions finance and engineering teams ask first.

DATAMASON Ledger is a financial data infrastructure platform. It connects your financial systems, normalizes transactions into one model, matches records automatically and gives you one reconciled source of financial truth.

Make every financial transaction explainable.

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