Skip to main content
Use the Midaz Module to manage Operation Routes, which define the account types or specific accounts used in a transaction component, along with the accounting direction (source or destination) and annotations. Operation Routes act as a validation layer between user input and ledger design, ensuring every operation follows the required account rules and business logic before being processed.

​
What are Operation Routes?

Operation Routes serve as building blocks for Transaction Routes. They specify:
  • Account validation rules - Which accounts or account types can participate in an operation
  • Operation direction - Whether the route applies to the source (debit) or destination (credit) side
  • Rule types - Validation by specific account alias or by account type categories
When combined with Transaction Routes, Operation Routes create a complete validation framework that ensures financial transactions comply with your organization’s accounting structure. For technical details, refer to the Operation Routes section of the Operations page.

​
Key concepts

  • Source Operations - Define validation rules for accounts where funds originate (debit side). Ensures only authorized accounts can send funds.
  • Destination Operations - Define validation rules for accounts where funds are sent (credit side). Ensures funds only reach valid destination accounts.
  • Alias Validation - Validates against a specific account alias (e.g., @treasury_main). Use when you need to target an exact account.
  • Account Type Validation - Validates against one or more account types (e.g., savings, checking). Use when any account of a certain type is valid.

​
Accessing the Operation Routes page

To open the Operation Routes page, select the Operation Routes option in the Accounting section of the leftside menu. The Operation Routes page displays a table listing all Operation Routes you have created for the current Ledger, including:
  • Name - The operation route title
  • Description - Brief description of the route’s purpose
  • Operation Type - Whether it’s a source or destination route
  • Rule Type - Whether validation uses alias or account_type
  • Created/Updated dates - Timestamps for tracking changes

​
Available actions

From the Operation Routes page, you can:

Create an Operation Route

Define new validation rules for transaction operations

Edit an Operation Route

Modify existing operation route configurations

Delete an Operation Route

Remove operation routes that are no longer needed

​
Common use cases

Create separate operation routes for treasury account sources and destinations to ensure treasury funds are properly tracked and validated.Example:
  • Source route with alias @treasury_main for withdrawals
  • Destination route with alias @treasury_main for deposits
Use account type validation to allow operations across all customer accounts of specific types without creating individual routes per account.Example:
  • Destination route with account types checking, savings for customer deposits
  • Source route with account types checking, savings for customer withdrawals
Define operation routes that validate department-specific accounts to maintain proper internal accounting boundaries.Example:
  • Source route with account type department_operations
  • Destination route with account type department_cost_center

​
Best practices

1

Use descriptive names

Name operation routes clearly to indicate their purpose (e.g., Customer Deposit Destination instead of Route 1).
2

Document your rules

Use the description field to explain when and why this operation route should be used.
3

Choose the right rule type

  • Use Alias when you need strict control over specific accounts
  • Use Account Type when you want flexibility across multiple accounts
4

Test before production

Verify operation routes work correctly with Transaction Routes before using them in production transactions.
Operation Routes only take effect when associated with a Transaction Route. Make sure to link your Operation Routes to Transaction Routes to enable validation. See Managing Transaction Routes for more information.