A new capital-mobilization method needs a reporting transition ledger
Keep methodology changes separate from newly mobilized money.
A measurement change is not new money
A change in measurement can change a reported total without creating a new transaction. Development-finance reporting needs to preserve that distinction during a methodology transition. Truthound can check declared methodology identifiers in a prepared ledger. It cannot decide which transactions count as mobilized capital or establish that a higher restated number is better financial performance.
The 2027 transition
The October 17, 2026 MDB heads' joint statement welcomed an updated private-capital-mobilization methodology and said reporting would begin under it in 2027. This is a reporting transition. It does not authorize treating a reclassification of an existing transaction as a new flow of funds.
Preserve both classifications
Before changing a total, record transaction identity, method version, applicable reporting year, reclassification state and approving owner. Preserve the old classification beside the new one. A transaction may legitimately be viewed under both methods for comparison, but the comparison record must not become a second transaction in the operating total.
Check the approved method label
For the transaction methodology-version table prepared as a Polars DataFrame, Truthound Core Python SDK 3.3.4's InSetValidator can compare method-version values with an approved allowed_values list. Unknown or misspelled identifiers can therefore be separated for review. The list and effective policy must come from the reporting owner. A permitted version label does not establish that the transaction was classified correctly under that method.
A maintained membership alternative
Pandera 0.35.0 supports schema and custom checks, including set-membership rules and Polars workflows. Keep an existing tested method-version predicate if it preserves both classifications and makes exceptions reviewable. The tools inspect the ledger's declared contract; neither interprets the financial methodology or supplies the substantive sign-off.
Assign the transition review
Assign a transition review cycle before the first new-method report. Ask the classification owner to explain one transaction whose treatment changes and one whose treatment stays the same. Record the reason and evidence instead of simply overwriting the old amount. That makes the difference between methodological movement and economic movement visible to reviewers.
Explain the basis of the change
Release the report only after unresolved versions and reclassifications have an explicit disposition. Explain a changed measurement basis separately from new financing activity. When guidance evolves, preserve the previous ledger and repeat the transition review. A clean version field is the beginning of reporting accountability, not proof of the reported result.
Evidence
- Event checked
- Subject checked
- Modified
