FAQ
Questions finance and engineering teams ask first.
Search or filter by topic. If your question is not here, ask us.
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.
The security architecture covers encryption, secure credential handling, role-based access, audit logs, API security and workspace isolation, with MFA, SSO and retention controls planned. We describe the architecture and do not claim certifications we do not hold.
Yes by design. Transactions keep their original currency and amount alongside a base-currency conversion with the rate recorded. Differences caused by exchange rates surface as FX variance exceptions.
Plans are measured on transaction volume, connected sources, reconciliation runs, retention, API usage, users and enterprise controls. The prices shown are proposed concepts for illustration, not an offer.
No. Every figure, transaction, exception and payload on this site is sample data created for demonstration. DATAMASON Ledger has no customers or transaction volumes represented here.
Use file import or the API. Any source that can export a statement, a report or JSON can be mapped into the transaction model. You can also request a connector from the Integrations page.
We do not display or claim certifications. This site describes the security architecture we are designing to, and we will publish independent attestations here only once they exist.
A browser-based sandbox is available on this site. It reconciles a payload you edit against sample invoices, entirely on your device with no network request.
Make every financial transaction explainable.
Connect your financial systems, reconcile transactions automatically, and build a reliable source of financial truth.