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

# Midaz Billing v2 ledger scope

> Billing packages and calculations use ledger-scoped v2 routes; the URL is the only ledger input.

<Badge stroke icon="calendar-days" iconType="regular">August 29, 2026</Badge> <Badge stroke icon="file-code" iconType="regular">Documentation correction</Badge> <Badge color="red" size="lg" stroke icon="triangle-exclamation" iconType="regular">Action required</Badge>

## Affects

Teams that create, manage, or calculate Midaz billing packages.

## What changed

The documentation now correctly states the current Billing contract: use the ledger-scoped v2 routes for billing packages and calculations. The organization and ledger belong in the URL. Do not send `ledgerId` in a query parameter or request body; the body field is rejected. Midaz monetary values are decimal strings with no asset-specific scale.

This is a documentation correction of the current runtime behavior; it does not announce a runtime release.

## Impact

**Classification: Action required.**

## What you need to do

Update Billing clients, examples, and deployment runbooks to use `/v2/organizations/{organization_id}/ledgers/{ledger_id}/...`. Remove request-body `ledgerId` and define display and rounding rules in your integration instead of treating Midaz values as binary floating point.

### Deadline

Update before the next Billing integration deployment.