Skip to main content
Use this page when the Console does not show an option you expected, or when you cannot complete a form. Also use it when a transaction does not behave as you expect. Most issues come from missing prerequisites, or from Ledger settings you enabled before the supporting configuration existed.

​
First checks

Before you troubleshoot 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 want to use.
  • The required Account Types, Accounts, and Accounting Routes exist before you create transactions.
  • You use each account alias exactly as registered, with the @ prefix.

Setup path

Review the recommended setup order before you change individual screens.

​
Common issues

The Account Types menu appears when you enable Validate Account Type 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.
After you enable this setting, new Accounts must use a valid Account Type. Create the required types before you ask operators to create accounts.
Each Account must link to an existing Asset. If no Asset exists in the selected Ledger, you cannot complete the Account form.Create the Asset first in Creating an Asset, then return to Creating an Account.
This usually means you enabled Validate Account Type but created no Account Types for the selected Ledger.Create at least one Account Type in Creating an Account Type. If your workflow does not need type validation, disable Validate Account Type in Ledger settings.
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: source accounts can send, destination accounts can receive.
  • The account Asset matches the Asset you selected for the Transaction.
If the alias is wrong or does not exist, open the account details from Managing Accounts.
The Validate Routes setting controls route validation. When you enable it, 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 and then review Creating an Accounting Route.
For complex transactions, the total you debit from source accounts must equal the total you credit to destination accounts.Review every operation before you send the transaction. To model fees, include the fee account as an additional destination so the total credits match the total debits.
You cannot delete some entities after downstream records use them. For example, treat an Asset that Accounts use, or an Account that Transactions use, as part of the ledger history.Instead, edit optional metadata, disable future use where the Console supports it, or create a replacement entity for new operations.
Start from the transaction details page and check:
  • The source and destination accounts.
  • The Asset used in the transaction.
  • Each debit and credit operation.
  • The transaction state: direct, pending, committed, cancelled, or reversed.
Then open the account balance and operation history for the accounts involved.

​
API references

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

List Accounts

Confirm whether the account exists in the selected Ledger.

Retrieve an Account

Inspect account details such as type, asset, and metadata.

List Transactions

Review transaction history for a Ledger.

Retrieve a Transaction

Inspect transaction status and operation details.