Skip to main content
Use the Midaz Module to manage Accounting Routes, the configuration for transaction routing in Midaz. A guided 3-step wizard walks you through defining the transaction route, adding operation routes, and reviewing the final setup. An Accounting Route defines the complete routing logic for a transaction: the transaction-level metadata (title and description), the operation routes that specify which accounts participate and in which direction, and the accounting scenarios that control how entries are recorded across different transaction types. For technical details on the underlying entities, refer to the Transaction Routing Entities page.

​
Key concepts

​
Operation route types

Each operation route within an Accounting Route is assigned one of three types:
  • Source — Defines validation rules for accounts where funds originate (debit side)
  • Destination — Defines validation rules for accounts where funds are sent (credit side)
  • Bidirectional — Applies to both sides of the transaction, acting as both source and destination
A valid Accounting Route requires at least one source and one destination operation route, or at least one bidirectional route.

​
Validation types

Each operation route validates accounts using one of two methods:
  • Account Type — Validates against one or more account type categories (e.g., checking, savings). Use when any account of a certain type is valid.
  • @Alias — Validates against a specific account alias (e.g., @treasury_main). Use when you need to target an exact account.

​
Accounting scenarios

Accounting scenarios define how debit and credit entries are recorded for each operation route. You can configure entries for three transaction types:
  • Direct Transaction — Standard one-step transaction. Define the debit and credit account codes and descriptions for immediate settlement.
  • Two-Step Transaction — Transactions that go through a hold-then-commit cycle. Configure entries for:
    • Hold (Value Reserve) — Entries recorded when funds are reserved
    • Commit (Reservation Confirmation) — Entries recorded when the reservation is confirmed
    • Cancel (Reservation Cancellation) — Entries recorded if the reservation is cancelled
  • Reversal — Entries recorded when a completed transaction is reversed
Each scenario entry includes an Account Code and a Description for both the debit and credit sides.
Which entry sides are available depends on the operation route type and the scenario phase. The general rule is:
  • Source — Debit entries in all phases. Credit entries only in Hold and Cancel (not in Direct or Commit).
  • Destination — Credit entries only, shown in Direct and Commit. Hold and Cancel phases are not available.
  • Bidirectional — Both debit and credit entries in all phases, including Reversal.

​
Accessing the Accounting Routes page

The Accounting Routes menu is only visible when the Validate Routes setting is enabled for the current Ledger. To enable it, go to the Ledger settings page and toggle the Validate Routes switch under the Accounting section.
To open the Accounting Routes page, select Accounting Routes in the Accounting section of the left sidebar menu. The Accounting Routes page displays a list of all Accounting Routes you have created for the current Ledger. You can expand each row to view the associated operation routes, including their ID, title, description, and operation type.

​
Available actions

From the Accounting Routes page, you can:

Create an Accounting Route

Define a new transaction route with operation routes and accounting scenarios.

Edit an Accounting Route

Modify an existing accounting route and its operation routes.

​
Common use cases

Create an Accounting Route with a bidirectional operation route that validates checking and savings account types. Enable Direct Transaction scenarios with the appropriate chart of accounts codes for Pix settlement entries.
Create an Accounting Route with separate source and destination routes. Enable Two-Step Transaction scenarios to record the hold (reservation), commit (confirmation), and optional cancel (cancellation) entries independently.
Create an Accounting Route with a source route using alias validation (@treasury_main) and a destination route for department_budget account types. Enable both Direct Transaction and Reversal scenarios to handle standard movements and their reversals.

​
Best practices

1

Use descriptive titles

Name your Accounting Routes clearly to indicate the type of transaction they handle (e.g., Pix Transfer Route instead of Route 1).
2

Choose the right operation type

Use Bidirectional when the same validation rules apply to both sides. Use separate Source and Destination routes when each side has different account requirements.
3

Configure accounting scenarios early

Define your chart of accounts entries during route creation. This ensures that transactions processed through the route produce correct accounting records from the start.
4

Review before confirming

The wizard includes a Review step — use it to verify all operation routes, validation rules, and accounting entries before creating the route.