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

# Troubleshooting

> Resolve the most common setup and operation issues when configuring the Midaz Module in Lerian Console.

Use this page when the Console does not show the option you expected, a form cannot be completed, or a transaction does not behave as expected. Most issues come from missing prerequisites or Ledger settings that were enabled before the supporting configuration existed.

## First checks

***

Before troubleshooting a specific screen, confirm these basics:

* You selected the correct **Organization** and **Ledger**.
* The Ledger already has the required **Assets**.
* The Ledger settings match the workflow you are trying to use.
* Required **Account Types**, **Accounts**, and **Accounting Routes** exist before creating transactions.
* You are using account aliases exactly as registered, including the `@` prefix.

<Card title="Setup path" icon="clipboard-list-check" href="/en/lerian-console/midaz-console/midaz-console-setup-path">
  Review the recommended setup order before changing individual screens.
</Card>

## Common issues

***

<AccordionGroup>
  <Accordion title="I cannot see the Account Types menu">
    The **Account Types** menu appears when **Validate Account Type** is enabled in the current Ledger settings.

    To fix it:

    1. Open **Foundation > Ledgers**.
    2. Open the target Ledger details.
    3. Go to the **Settings** tab.
    4. Enable **Validate Account Type**.
    5. Return to the sidebar and open **Accounting > Account Types**.

    <Warning>
      Once this setting is enabled, new Accounts must use a valid Account Type. Create the required types before asking operators to create accounts.
    </Warning>
  </Accordion>

  <Accordion title="I cannot create an Account because the Asset field is empty">
    Accounts must be linked to an existing Asset. If no Asset exists in the selected Ledger, the Account form cannot be completed.

    Create the Asset first in [Creating an Asset](/en/lerian-console/midaz-console/creating-an-asset), then return to [Creating an Account](/en/lerian-console/midaz-console/creating-an-account).
  </Accordion>

  <Accordion title="The Account Type dropdown is empty">
    This usually means **Validate Account Type** is enabled, but no Account Types were created for the selected Ledger.

    Create at least one Account Type in [Creating an Account Type](/en/lerian-console/midaz-console/creating-an-account-type). If type validation is not required for your workflow, disable **Validate Account Type** in Ledger settings.
  </Accordion>

  <Accordion title="I cannot find an Account when creating a Transaction">
    Transaction creation searches accounts by alias. Confirm that:

    * The account exists in the selected Ledger.
    * The alias includes the `@` prefix.
    * The account allows the expected direction: sending for source accounts, receiving for destination accounts.
    * The account Asset matches the Asset selected for the Transaction.

    If the alias is missing or incorrect, open the account details from [Managing Accounts](/en/lerian-console/midaz-console/managing-accounts).
  </Accordion>

  <Accordion title="My Transaction fails route validation">
    Route validation is controlled by **Validate Routes** in Ledger settings. When this setting is enabled, transactions must match an existing Accounting Route.

    Check that:

    * The Accounting Route exists in the selected Ledger.
    * The route has at least one valid source and one valid destination operation route, or one bidirectional route.
    * Account Type or alias validation matches the accounts used in the transaction.
    * The transaction type matches the accounting scenario configured in the route.

    Start with [Managing Accounting Routes](/en/lerian-console/midaz-console/managing-accounting-routes) and then review [Creating an Accounting Route](/en/lerian-console/midaz-console/creating-an-accounting-route).
  </Accordion>

  <Accordion title="My Transaction amounts do not balance">
    For complex transactions, the total amount debited from source accounts must equal the total amount credited to destination accounts.

    Review every operation before sending the transaction. If you are modeling fees, include the fee account as an additional destination so the total credits match the total debits.
  </Accordion>

  <Accordion title="I cannot delete an entity">
    Some entities cannot be deleted after they are used by downstream records. For example, an Asset used by Accounts or an Account used by Transactions should be treated as part of the ledger history.

    Prefer editing optional metadata, disabling future use where supported, or creating a replacement entity for new operations.
  </Accordion>

  <Accordion title="Balances do not look right after a Transaction">
    Start from the transaction details page and check:

    * The source and destination accounts.
    * The Asset used in the transaction.
    * Each debit and credit operation.
    * Whether the transaction is direct, pending, committed, cancelled, or reversed.

    Then open the account balance and operation history for the accounts involved.
  </Accordion>
</AccordionGroup>

## API references

***

When a Console issue needs deeper inspection, use the corresponding API references:

<CardGroup cols={2}>
  <Card title="List Accounts" icon="list" href="/en/reference/midaz/list-accounts">
    Confirm whether the account exists in the selected Ledger.
  </Card>

  <Card title="Retrieve an Account" icon="magnifying-glass" href="/en/reference/midaz/retrieve-an-account">
    Inspect account details, including type, asset, and metadata.
  </Card>

  <Card title="List Transactions" icon="receipt-text" href="/en/reference/midaz/list-transactions">
    Review transaction history for a Ledger.
  </Card>

  <Card title="Retrieve a Transaction" icon="file-search" href="/en/reference/midaz/retrieve-a-transaction">
    Inspect transaction status and operation details.
  </Card>
</CardGroup>