Affects
Teams that use the double-entry guide for Midaz control design, audit evidence, or financial-system training.
What changed
The guide now states the implemented scope of the balancing check: Midaz validates that the source total, destination total, and sent value match. This detects recorded amount mismatches; it does not by itself prove authorization, classification, or completeness. It also scopes the debit-as-source and credit-as-destination phrasing to the illustrated transfer. Whether a debit or credit increases or decreases a balance depends on account type and configured direction. This is a documentation correction; it does not announce a runtime release.
Impact
Classification: Review recommended. Do not use the balancing check as evidence that other financial controls have passed.
What you need to do
Review control narratives, audit evidence, and training material that treated double-entry balancing as proof of authorization, classification, or completeness. Keep those controls separate.