Skip to main content
Use Midaz Module to manage Alias Accounts. Alias Accounts create the link between Holders and Midaz ledger accounts, adding business context like bank account numbers and financial institution details.

​
What are Alias Accounts?

An Alias Account connects a Holder (individual or company) to a specific Midaz ledger account. In Midaz Module, each alias account stores:
  • Account identification - Bank ID, branch, account, and type
  • Holder reference - Link to the associated holder (Natural or Legal Person)
  • Ledger account link - Connection to the underlying Midaz account
  • Banking details - Opening date, IBAN, country code, and the Participant Document under Regulatory
  • Custom metadata - Additional fields for integration and business-specific needs
Alias Accounts enable you to maintain customer-facing account information separately from the transactional ledger, providing flexibility for multi-bank scenarios and external system integration. For technical details about the underlying CRM capabilities, refer to the CRM Overview page.

​
Accessing the Alias Accounts page

To open the Alias Accounts page, select the Alias option from the Accounts section of the left-side menu. The Alias Accounts page displays a table listing all Alias Accounts in your system, including:
  • Holder Name - The associated holder name
  • Holder ID - The identifier of the associated holder
  • Account ID - The identifier of the linked ledger account
  • Ledger - The ledger the linked account belongs to
  • Type - Classification of the account (checking, savings, etc.)
  • Actions - The actions available for each alias account
If you do not have any Alias Accounts, the list will appear empty with a prompt to create your first alias account.

​
Available actions

From the Alias Accounts page, you can:

Create an Alias Account

Link a holder to a Midaz ledger account with bank details

Edit an Alias Account

Update account information and financial details

Delete an Alias Account

Remove the link between a holder and ledger account

​
Common use cases

When a customer opens an account:
  1. Create a Holder with customer information (Natural or Legal Person)
  2. Create an Alias Account linking the holder to a Midaz ledger account
  3. Add banking details (bank ID, branch, account, type)
  4. The customer can now transact using their familiar bank account number
When customers have accounts at multiple institutions:
  • Create multiple Alias Accounts for the same Holder
  • Each alias account references a different Midaz ledger account
  • Track different account numbers and bank relationships
  • Maintain clear separation between institutional relationships
When integrating with external banking systems:
  • Use Alias Accounts to map external account numbers to internal ledger accounts
  • Store regulatory identifiers such as the Participant Document
  • Maintain metadata for integration-specific fields
  • Synchronize status changes between systems

​
Best practices

1

Create holders before alias accounts

Always create the Holder record first, then create Alias Accounts to link them to ledger accounts. This ensures proper data relationships.
2

Use consistent account numbering

Follow your institution’s account numbering standards when creating alias accounts to avoid confusion and integration issues.
3

Keep financial institution details accurate

Ensure Bank IDs and other banking details are correct for proper payment routing and regulatory compliance.
4

Document account relationships

Use metadata to store additional context about account relationships, especially in multi-bank or integration scenarios.
5

Manage status appropriately

Update alias account status to reflect changes in the account relationship (active, inactive, closed).