← tools

ClaimBench

Test claim accounting without touching patient data

Ten synthetic claim-to-cash fixtures define each event, the balanced journal entry, and the expected subledger state afterward. Revenue-cycle software, classroom exercises, and internal tools can be tested against one public answer key.

Clean payment, event by event

Expected subledger after selected event

The suite

Clean payment · partial payment · denial · zero-pay remittance · takeback · refund · credit balance · coordination of benefits · late charge · wrong-account correction.

Run it

python3 claimbench.py check-fixtures
python3 claimbench.py validate takeback system-output.json

The fine print

Invented identifiers, amounts, and account names; no PHI, proprietary code sets, or real payer terms. The entries demonstrate mechanics, not a required recognition policy. MIT licensed. Source on GitHub.