> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt
> Use this file to discover all available pages before exploring further.

# Double-entry consistency guidance

> The double-entry guide now distinguishes Midaz amount-consistency validation from authorization, classification, and completeness controls.

<Badge stroke icon="calendar-days" iconType="regular">August 12, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation correction</Badge> <Badge color="yellow" size="lg" stroke icon="triangle-exclamation" iconType="regular">Review recommended</Badge>

## 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.

### Deadline

No product-imposed deadline.

## Resources

***

* [Double-entry explained](/en/fundamentals/core-banking/double-entry-explained)