~/About~/Systems~/Foundry~/Blueprint~/Journal~/Projects
Book a Call

Transaction Reconciliation Engine

The complete system record. Choose the proof lens that fits your role.

View on GitHub

Choose The Proof Lens

One system record, three reader paths.

Feature-frozen3-act recordGitHub available
Business proofFounder / operator

Transaction Reconciliation Engine: Foundry Case Study

Finance teams stop losing days to Stripe, PayPal, and bank statement matching. A confidence cascade turns unmatched rows into reviewable discrepancies.

System FlowData ModelArchitecture LayersDecision Log
Open business proof7 min read
Architecture proofCTO / architect

Transaction Reconciliation Engine: Blueprint

Money as int64 cents, never floats. Two-tier Redis plus Postgres dedup with owner-verified Lua lock release across every gateway-ledger pair.

System TopologyInfrastructure DecisionsConstraintsDecision Log
Open architecture proof5 min read
Technical proofSenior engineer

The Matching Problem No One Talks About

Bank settlement dates differ from charge dates on 23% of transactions, and 4% by two days. Exact-match reconciliation flags all of them as discrepancies.

Code SampleFailureConstraintScaling Limit
Open technical proof5 min read

Related Systems

More proof in the same problem space.

View systems map

Invoice Reconciliation Engine

Accounts payable matching

Shows how five resolution strategies move invoice matching from manual review to controlled exception handling.

Financial Compliance Ledger

Immutable operational record

Defends append-only records, sequence ordering, and the constraints needed when history must be defensible.

SLA Penalty Settlement Engine

SLA credit settlement

Connects missed vendor obligations to a collectible settlement process with paired ledger discipline.