See the Transactions reference documentation for transaction structures, double-entry accounting, N:N transactions, and API integration.
Accessing the Transactions page
Select the Transactions option in the left-side menu to open the Transactions page. The Transactions page shows a table of all Transactions in your Ledger.
If your Ledger has no Transactions, the list is empty and shows a prompt to create your first transaction.
Available actions
From the Transactions page, you can:Create a Transaction
Record a new asset movement between accounts
Check Transaction details
See complete transaction information and operations
Transaction status
Transactions in Midaz have the following statuses:
- CREATED - The initial state of a transaction
- PENDING - A two-step transaction holding funds, awaiting commit or cancel
- APPROVED - Midaz posted the transaction
- CANCELED - Midaz canceled the transaction
- NOTED - An annotation-only transaction with no balance changes. Its operations remain with all balance fields zeroed
After Midaz approves a transaction, you cannot edit its operations or amounts, and you cannot delete it. To reverse it, create a reversal transaction. This protects the integrity of your financial records.
Common use cases
Simple transfer between two accounts
Simple transfer between two accounts
A basic transaction moving funds from one account to another:
- Source: Customer checking account (debit $100)
- Destination: Merchant account (credit $100)
- Single source, single destination, equal amounts
Payment with fees
Payment with fees
A transaction that splits funds between multiple destinations:
- Source: Customer account (debit $103)
- Destinations:
- Merchant account (credit $100)
- Fee collection account (credit $3)
- Single source, multiple destinations
Consolidated payment
Consolidated payment
Multiple sources funding a single destination:
- Sources:
- Primary account (debit $500)
- Secondary account (debit $300)
- Destination: Vendor account (credit $800)
- Multiple sources, single destination
Complex multi-party transaction
Complex multi-party transaction
Multiple sources and destinations in a single transaction:
- Sources:
- Customer A (debit $200)
- Customer B (debit $300)
- Destinations:
- Vendor account (credit $450)
- Tax account (credit $50)
- Multiple sources, multiple destinations
Best practices
1
Write clear transaction descriptions
Include a clear description of the purpose of each transaction.
2
Verify account balances before transacting
Make sure the source account has enough balance before you create a transaction. This avoids rejections.
3
Use metadata for integration context
Store external reference IDs, order numbers, or other system identifiers in the transaction metadata for traceability.
4
Group related operations logically
When possible, combine related transfers into one transaction instead of several separate transactions.
5
Review transactions before confirming
Double-check the source accounts, destination accounts, and amounts before you submit. You cannot edit a transaction after you create it.
Accounting Routes integration
Midaz can validate Transactions against Accounting Routes before it processes them. Accounting Routes define which accounts can transact with each other.

