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.
Finance teams · Fintech · SaaS · Ecommerce · Marketplaces · Enterprise
Connected sources
- Bank3,120
- Payment Gateway5,840
- ERP1,710
- Invoices1,260
- Subscriptions550
DATAMASON Ledger
against INV-1031 · rule exact_amount_ref
Financial truth
| Source | Reference | Amount | Status |
|---|---|---|---|
| ICICI Bank | TXN-48291 | ₹50,000 | Matched |
| Razorpay | PAY-92812 | ₹21,500 | Matched |
| Stripe | ST-19382 | ₹18,400 | Review |
| Cashfree | CF-84219 | ₹32,800 | Matched |
| Razorpay | PAY-92841 | ₹49,500 | Review |
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
- 01NormalizeOne transaction model
- 02MatchRules, references, scoring
- 03ReconcileContinuous comparison
- 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
- Bank
UTR 482910•••• · CR 50000.00 - Payment Gateway
pay_Nx82kQ1a · 5000000 paise - ERP
GL-20418 · Dr 1010 · 50,000.00 - Invoices
INV-1024 · due 2026-09-14 - Subscriptions
sub_8821 · plan_growth · INR - Marketplace
ord_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.
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
Platform
Five operations. One continuous workflow.
Connect, normalize, match, reconcile and resolve: each stage is a product surface, not a feature checkbox.
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- 1 Choose
- 2 Authenticate
- 3 Map fields
- Bank accountConnector
- Payment gatewayConnector
- ERPFile import
- REST APIAPI
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 layerAs received
{"id":"pay_Nx82kQ1a",
"amount":5000000,
"created_at":1757846531}
14/09 UTR482910 CR 50000.00
INV-1024|50000|INR|2026-09-14As normalized
| Reference | Amount | Currency | Timestamp |
|---|---|---|---|
| pay_Nx82kQ1a | 50,000.00 | INR | 2026-09-14 10:42 |
| UTR482910•••• | 50,000.00 | INR | 2026-09-14 10:42 |
| INV-1024 | 50,000.00 | INR | 2026-09-14 00:00 |
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 worksReconcile
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 reconciliationResolve
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- Amount mismatch14
- Missing counterpart9
- Suspected duplicate6
- Unmatched bank credit7
- FX variance2
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.
| Source | Reference | Amount | Currency | Status | Match |
|---|---|---|---|---|---|
| ICICI Bank | ₹50,000 | INR | Matched | Matched | |
| Razorpay | ₹21,500 | INR | Matched | Matched | |
| Stripe | ₹18,400 | INR | Review | Needs review | |
| Cashfree | ₹32,800 | INR | Matched | Matched | |
| Razorpay | ₹49,500 | INR | Review | Needs review | |
| Axis Bank | ₹124,300 | INR | Pending | Awaiting | |
| Subscription billing | ₹4,999 | INR | Matched | Matched | |
| Shopify | ₹7,850 | INR | Matched | Matched | |
| Stripe | $1,200 | USD | Review | Needs review | |
| ICICI Bank | ₹32,000 | INR | Review | Needs review | |
| Cashfree | ₹12,600 | INR | Pending | Awaiting | |
| ERP | ₹15,000 | INR | Matched | Matched | |
| Stripe | ₹26,500 | INR | Matched | Matched | |
| Razorpay | ₹9,200 | INR | Pending | Awaiting |
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.
- Bank transaction₹50,000ICICI Bank ••4821Credit · UTR 482910••••14 Sep 10:42
- PaymentPAY-92790Razorpay · captured₹50,000 · INRSettlement stl_7H2K9P
- InvoiceINV-1024₹50,000 · due 14 SepCustomer cus_20418Status: open
- Ledger entryLE-004217Debit Bank 50,000Credit Receivable 50,000Balanced · Dr = Cr
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 openAmount mismatch
The amount received does not equal the invoice.
Probable cause · rule-based, ranked
- 1Gateway fee or deductionDifference is exactly 1.0% of the invoice amount.strongest evidence
- 2Customer short-paymentNo second payment found against INV-1042 within the 7-day window.possible
- 3Rounding or FXBoth amounts are in INR; not applicable.unlikely
Timeline
- 14 Sep 12:41 · Payment received
- 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
Field
invoice
The receivable this money should settle.
Mapped from
| Bank statement | Narration (parsed) |
|---|---|
| Payment gateway | notes.invoice_id |
| ERP | doc_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.
- PlannedBank accountsStatements, credits, debits Connector
- PlannedStatement filesCSV, MT940, CAMT.053 File import
- PlannedAccount aggregationConsent-based account feeds Connector
- PlannedRazorpayPayments, refunds, settlements Connector
- PlannedStripeCharges, payouts, balance transactions Connector
- PlannedCashfreePayments, settlements Connector
- PlannedOther gatewaysSettlement report files File import
- PlannedAccounting platformsLedgers, invoices, journals Connector
- PlannedJournal exportReconciled entries back to books API
- PlannedERP systemsGL postings, vouchers, receivables Connector
- PlannedVoucher importScheduled file drops File import
- PlannedShopifyOrders, refunds, payouts Connector
- PlannedOther storefrontsOrder and refund feeds API
- PlannedSubscription billingPlans, invoices, renewals Connector
- PlannedREST APIIngest and query transactions API
- PlannedWebhooksSigned events on state change API
- PlannedSFTP 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.
# 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 targetSecure credentials
Source credentials are stored encrypted, scoped to one connector and never displayed again after entry.
Architecture targetRole-based access
Roles for viewers, operators, approvers and administrators, with least privilege by default.
Architecture targetAudit logs
Access, changes and approvals are recorded with the actor, the time and the previous value.
Architecture targetAPI security
Scoped API keys per workspace and environment, rate limits, idempotency and signed webhooks.
Architecture targetWorkspace isolation
Each workspace’s data is logically separated, with no cross-workspace queries by design.
Architecture targetMFA
Multi-factor authentication for user accounts, enforceable per workspace.
PlannedSSO-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.
- Subscription
- Invoice
- Payment
- Settlement
Pricing
Priced on what you reconcile.
Plans are measured on transaction volume, connected sources, runs, retention, API usage and controls.
Starter
For small finance operations.
$49/moRequest access- Up to 3 connected sources
- Automated matching
- Exception queue
Growth
For growing teams.
$199/moRequest access- Up to 10 connected sources
- Custom matching rules
- Assignments and approvals
Business
For larger financial operations.
$599/moRequest access- Unlimited sources, fair-use
- Maker–checker approvals
- Scheduled reports
Enterprise
For complex organizations.
CustomTalk to sales- Custom volume and sources
- SSO and SAML
- Data residency options
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.
Records are ingested, mapped into a common transaction model and matched using rules: exact references, amounts, date windows and configurable tolerances. Where rules are inconclusive a score is applied; anything unresolved becomes an exception with a type, a probable cause and an owner.
The platform is designed for banks, payment gateways, accounting and ERP systems, ecommerce and subscription platforms, and internal APIs. Named connectors on this site are shown as an integration ecosystem with a Planned status. File import and API ingestion are the routes for any other source.
No. Accounting software records your books. DATAMASON Ledger checks that what your books say matches what actually happened across banks, gateways and billing, and feeds reconciled data back.
Deterministic rules run first (reference, amount, date window), then tolerances and scoring, then manual review. Each match records which rule applied and the evidence used, so every result can be explained.
Rule-based reconciliation is a core part of the design, including tolerances and one-to-many matching. The rule builder is shown conceptually on this site and is part of the proposed Growth plan and above.
Each exception has a type, expected and received amounts, a ranked set of probable causes, an owner and a timeline. Teams can investigate, assign, approve and resolve, and every action is recorded in the audit trail.
Yes, API-first by design: ingestion, reconciliation, queries and webhooks. The API shapes on this site are conceptual until documentation is published, and the sandbox runs entirely in your browser against sample data.
Make every financial transaction explainable.
Connect your financial systems, reconcile transactions automatically, and build a reliable source of financial truth.