Python · Professional · Free practice
Controlled Finance Reconciliation Pipeline
Run a two-source reconciliation with prematch validation, exception classes, control totals, and a human review queue — based on the PYFIN-004 Master Lesson pattern.
What you will produce
Run a two-source reconciliation with prematch validation, exception classes, control totals, and a human review queue — based on the PYFIN-004 Master Lesson pattern.
RAW_A = PREMATCH_EX_A + MATCHABLE_A MATCHABLE_A = CLEAN + AMT_MISMATCH + CCY_MISMATCH + UNMATCHED_A # Cross-source amount delta = diagnostic, not completeness
// Control identities — completeness before trust
- Comfortable with pandas
- Familiar with finance reconciliation concepts (keys, amounts, currency)
- PYFIN-004 Master Lesson approved in Content OS (source pattern)
Run the drill
Step sequence
- 01
Validate required schema on both sources before any merge.
Step - 02
Classify prematch exceptions: missing keys, duplicate keys, invalid amounts/currency.
Step - 03
Match on the reconciliation key; separate clean matches, amount mismatches, currency mismatches, and unmatched rows.
Step - 04
Prove completeness with control identities (raw → prematch exceptions + matchable; matchable → clean + mismatches + unmatched).
Step - 05
Write an exception log and a short human-review queue for residual judgment.
Step
Validation gates in this drill
Validate required schema on both sources before any merge.
PassClassify prematch exceptions: missing keys, duplicate keys, invalid amounts/currency.
ExceptionProve completeness with control identities (raw → prematch exceptions + matchable; matchable → clean + mismatches + unmatched).
ExceptionWrite an exception log and a short human-review queue for residual judgment.
Exception
Expected outcome
A professional drill that treats reconciliation as a controlled system — not a single merge — with completeness evidence and exception ownership.
// Use Content OS reconciliation datasets when published with this drill