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

# Managing Alias Accounts

> Create, edit, and delete Alias Accounts in the CRM to give Holders friendly identifiers for their Accounts.

Use **Midaz Module** to manage **Alias Accounts** through the CRM functionality. 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 account number, branch code, and account type
* **Holder reference** - Link to the associated holder (Natural or Legal Person)
* **Ledger account link** - Connection to the underlying Midaz account
* **Financial institution details** - Bank name, ISPB code, and institution identifiers
* **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 CRM functionality, refer to the [CRM Overview](/en/midaz/crm/crm-overview) page.

## Accessing the Alias Accounts page

***

To open the **Alias Accounts** page, select the **Aliases** 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:

* **Account Number** - The bank account number or identifier
* **Holder** - The associated holder name
* **Account Type** - Classification of the account (checking, savings, etc.)
* **Status** - Current state (Active, Inactive, etc.)
* **Created Date** - When the alias account was created

<Note>
  If you do not have any Alias Accounts, the list will appear empty with a prompt to create your first alias account.
</Note>

### Available actions

From the **Alias Accounts** page, you can:

<Columns cols={2}>
  <Card title="Create an Alias Account" icon="plus" horizontal href="/en/platform/lerian-console/midaz-console/crm-creating-alias-account">
    Link a holder to a Midaz ledger account with bank details
  </Card>

  <Card title="Edit an Alias Account" icon="pen" horizontal href="/en/platform/lerian-console/midaz-console/crm-editing-alias-account">
    Update account information and financial details
  </Card>

  <Card title="Delete an Alias Account" icon="trash" horizontal href="/en/platform/lerian-console/midaz-console/crm-deleting-alias-account">
    Remove the link between a holder and ledger account
  </Card>
</Columns>

## Common use cases

***

<AccordionGroup>
  <Accordion title="Linking customer accounts">
    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 bank details (account number, branch, institution)
    4. The customer can now transact using their familiar bank account number
  </Accordion>

  <Accordion title="Multi-bank scenarios">
    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
  </Accordion>

  <Accordion title="External system integration">
    When integrating with external banking systems:

    * Use Alias Accounts to map external account numbers to internal ledger accounts
    * Store institution-specific identifiers (ISPB, participant codes)
    * Maintain metadata for integration-specific fields
    * Synchronize status changes between systems
  </Accordion>
</AccordionGroup>

## Best practices

***

<Steps>
  <Step title="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.
  </Step>

  <Step title="Use consistent account numbering">
    Follow your institution's account numbering standards when creating alias accounts to avoid confusion and integration issues.
  </Step>

  <Step title="Keep financial institution details accurate">
    Ensure ISPB codes and bank identifiers are correct for proper payment routing and regulatory compliance.
  </Step>

  <Step title="Document account relationships">
    Use metadata to store additional context about account relationships, especially in multi-bank or integration scenarios.
  </Step>

  <Step title="Manage status appropriately">
    Update alias account status to reflect changes in the account relationship (active, inactive, closed).
  </Step>
</Steps>