Affects
Anyone who reads or relies on the Accounting module documentation in the Console — including teams configuring routing rules between accounts and reviewing accounting scenarios. Content is available in English, Spanish, and Portuguese. This update applies to the public documentation portal. It does not change the runtime API behavior, endpoints, or payloads.
What changed
1. “Transaction Routing / Routes” is now “Accounting Routes”
Across the Accounting module documentation, the feature previously called Transaction Routing (and Transaction Routes) is now consistently named Accounting Routes, with the equivalent terms updated in Spanish and Portuguese. The new name better reflects that these routes are an accounting concept. The change spans the full module documentation set across all three languages. Before Transaction Routing · Transaction Routes (Enrutamiento de transacciones · Roteamento de transações) After Accounting Routes (Rutas contables · Rotas contábeis)2. New “Overdraft” scenario
A new Overdraft scenario has been added to the Accounting Routes documentation, available in English, Spanish, and Portuguese. It documents how this case is handled so teams can model it correctly when designing their accounting routes.3. Reorganized Accounting module navigation
The Accounting module navigation has been restructured for a clearer reading path:- The module intro page now leads with the core concepts, merging the previous “understanding” content into a single starting point.
- Accounting setup in Console is restored as the second page, so setup follows the concepts naturally.
- A Managing Accounting Routes subgroup is restored, containing the Creating and Editing pages.
Impact
This is a documentation-only update. There is no change to product behavior, API contracts, or configuration. No migration is required. The main practical effect is terminology and navigation: bookmarks or saved links into the Accounting module pages may point to renamed or reorganized pages, and internal references to “Transaction Routing” should be updated to “Accounting Routes” for consistency.
What you need to do
1
Start from the Accounting module intro page to get the refreshed concepts overview.
2
Update any internal notes, runbooks, or links that say “Transaction Routing/Routes” to use “Accounting Routes”.
3
Review the new Overdraft scenario if your accounting setup needs to handle overdraft cases.
4
Re-check saved bookmarks against the updated Managing Accounting Routes subgroup (Creating, Editing).
Deadline
None. No action is required to keep your integration working.Why
To give the Accounting module a consistent name across all languages, document the Overdraft scenario explicitly, and make the module easier to navigate from concepts through setup to day-to-day route management.Resources
- Accounting module overview — Midaz Console documentation
- Accounting setup in Console
- Managing Accounting Routes — Creating and Editing
- Accounting Routes scenarios, including the new Overdraft scenario