DrupardGet Started

Financial Provenance Infrastructure

Know where every financial number came from.

Drupard tracks the complete lineage of financial data, connecting every value to the transactions, records and transformations that created it.

Get StartedExplore the infrastructure →
Illustrative values
Cash position$14,281,400
    1. 1,842transactions
    2. 43reconciliations
    3. 12adjustments
    4. 3disputed transactions
    5. Current balance$8,421,000

01The problem

A financial number is assembled from many systems. The final figure can depend on hundreds or thousands of underlying events — and once it lands on a report, that history is gone.
  • 01Banks
  • 02Payments
  • 03ERP
  • 04Accounting
  • 05Invoicing
  • 06Payroll
  • 07Cards
  • 08Treasury
  • 09Manual adjustments
Illustrative
Revenue · current state$17,920,400
$17.9M
Original state
$18.4M$18,432,800

Select any change to see the number as it stood at that moment.

02Financial lineage

Every balance is a stack of layers. Expand any node to see what sits beneath it — down to the original financial events.
Illustrative

01Accounts receivable

02Customer balances

03Invoices

04Payments

05Bank transactions

06Original financial events

traceAccounts receivable→CUST-1093→issued 09:42:18→pmt_82931→Operating Account · ACH credit→stl_20260920_07

03Financial time machine

Version history for money. Move backward and forward through a day of events and watch the financial state rewind and replay.
Event log · 2026-09-20Illustrative
Current balance2026-09-20 · 13:02:42
$5,782,430

evt_f28b · Invoice corrected

− $5,770,430

+ $5,782,430

00:0013:02

04Impact analysis

Lineage runs in both directions. Follow an event forward to every record that depends on it, or start from a metric and work back to the transactions behind it.
Illustrative example

7downstream records affected

Illustrative example · Payment #82931 · $84,000

Reverse one payment and Drupard shows every balance, forecast and report that depended on it. Hover any record to isolate its own downstream.

05Data trust

Every number carries a record of how reliable its origin is — what was verified, what was edited by hand, and what can’t yet be traced.
All figures illustrativeHover a status to see where it appears
Source verified
55%of value
Transformation verified
24%of value
Reconciliation verified
15%of value
External source
2%of value
Manual change
3%of value
Unresolved
1%of value

06The financial graph

Customers, contracts, invoices, payments, bank transactions, journal entries and reports are all related. Drupard stores the relationships, not just the rows.
Illustrative entities
  1. ↓ signs
  2. ↓ bills through
  3. ↓ is settled by
  4. ↓ clears into
  5. ↓ is booked as
  6. ↓ posts to

Also connected: vendors · bank accounts · ledger accounts. Every record links to several others — one invoice can be settled by many payments, and one payment can clear many invoices.

07AI explanation layer

A natural-language interface to financial lineage. Answers are resolved against the provenance graph, so every claim links back to the records behind it.

Try asking

Provenance queryIllustrative

Ask a question to trace it through the graph.

08API infrastructure

Trace any value to its sources, or ask what an event touches, with a single request.
Illustrative · not a live endpoint
POST /v1/provenance/tracerequest
{  "entity": "accounts_receivable",  "value": 8420000,  "as_of": "2026-09-20"}
200 OK · application/jsonresponse
{  "source_count": 1842,  "transformations": 43,  "adjustments": 12,  "unresolved": 3,  "lineage_status": "traceable"}
  1. Request
  2. Provenance graph
  3. Response
Build with financial provenance

09Built for financial systems

Drupard sits between the systems that create financial data and the applications that depend on it.

Consumers of financial data

DrupardFinancial provenance layer
  • events
  • relationships
  • transformations
  • history
  • impact

Systems of record

Hover a source to see which consumers depend on its data — or a consumer to see where its data comes from. Illustrative mapping.

10Audit without the digging

Traditional

  1. Spreadsheet
  2. Email
  3. Accounting system
  4. Bank statement
  5. Manual reconciliation
  6. Investigation
  7. Answer

Drupard

  1. Financial event
  2. Provenance graph
  3. Source
  4. Transformation
  5. Impact
  6. Answer

11Developer experience

  1. 01 — CONNECT

    Connect financial systems and event sources.

  2. 02 — RECORD

    Drupard records financial events and their relationships.

  3. 03 — TRACE

    Query the lineage, history and downstream impact of financial data.

Every event.Every transformation.Every dependency.

Drupard gives financial systems a complete memory of where their data came from, how it changed and what it affects.

Get Started

Get started

Give your numbers a history.

A few details and we’ll be in touch about access.