Payment Integrity & Records
A training-voucher system built as a contingency
A Chicago workforce-development nonprofit, roughly 70 staff · 2025–2026
Replayed against past billing, caught all 28 known double billings
The problem
The nonprofit funds job-training vouchers for residents through an outside administrator. Leadership wanted a working fallback in case that work had to come back in-house.
They also wanted independent checks on the administrator's billing in the meantime.
What I built
An independent billing review first
Analysis of the administrator's voucher files flagged duplicate and over-claimed participants. The issues clustered in a way that pointed to a data-reload problem rather than one-off keying errors.
A full voucher system
Django 5.2 on PostgreSQL 16: a career-planner portal for requesting vouchers, staff review, a training-provider billing portal, and Finance approval.
Business rules enforced by the database
An exclusion constraint prevents overlapping vouchers. Separation of duties is a constraint rather than a policy. Funding is an append-only ledger, with balances computed from it and never stored. Audit tables cannot be edited.
Amounts read from the source document
Voucher amounts are parsed from the signed financial-statement PDF, so they cannot be mistyped on the way in.
Separation from live billing
Approved invoices become NetSuite bills awaiting Finance approval, entirely separate from live billing, with a nightly shadow comparison against the outside administrator's data.
Outcomes
- Built and running end-to-end in about a week.
- First full cycle passed against NetSuite with test data: invoice to bill to approval to paid.
- Loaded 118 real providers and 2,693 state-approved programs.
- Replayed against past billing, the system's checks stopped all 28 known double billings.
Stack
- Python
- Django
- PostgreSQL
- Exclusion constraints
- Database triggers
- Docker Compose
- PDF parsing
- NetSuite RESTlets
- Entra ID sign-in