Skip to main content
Accounting Routes are created through a guided 3-step wizard that walks you through defining the transaction route, configuring operation routes with accounting scenarios, and reviewing the final configuration.

​
Step 1: Basic information

1
From the Accounting Routes page, click New Route.
2
The creation wizard opens on Step 1 — Basic information.
3
Fill in the basic information:
​
title
string
required
Title — A descriptive name for this transaction route (max 50 characters).
​
description
string
Description — An optional description of the route’s purpose (max 250 characters).
4
Click Next to proceed to Step 2.

​
Step 2: Operation Routes

In this step, you add and configure the operation routes that define how accounts are validated and how accounting entries are recorded.
1
Click Add Operation Route to create your first operation route card.
2
Configure the operation route:
​
description
string
Description — A description of this operation route’s purpose.
​
operationType
enum
required
Operation Type — The accounting direction for this route:
  • Source — Identifies accounts where funds originate (debit side)
  • Destination — Identifies accounts where funds are sent (credit side)
  • Bidirectional — Applies to both sides of the transaction
The operation type cannot be changed after creation.
​
account.ruleType
enum
Validation Type — How accounts are validated:
  • Account Type — Select one or more account types from the dropdown
  • @Alias — Enter a specific account alias (e.g., @treasury_main)
If left empty, no account validation is applied — any account can be used in this operation route.
​
account.validIf
string | array
Account Type or Alias — Depends on the selected Validation Type:
  • If Account Type: Select one or more account types
  • If Alias: Enter the account alias to validate against
If left empty, no account validation is applied — any account can be used in this operation route.
3
(Optional) Configure Accounting Scenarios to define how entries are recorded. Toggle on the scenarios you need:
Standard one-step transaction. Define the Account Code and Description for:
  • Debit — The account code debited on execution
  • Credit — The account code credited on execution
For Direct Transactions, which sides appear depends on the operation type. Source routes show debit only, destination routes show credit only, and bidirectional routes show both. Other scenarios may differ — see the Two-Step Transaction tab for details.
4
(Optional) Click Add Operation Route again to add more operation routes to this Accounting Route.
You must add at least one source and one destination operation route, or at least one bidirectional route. The wizard will not proceed without a valid route configuration.
5
Click Next to proceed to Step 3.

​
Step 3: Review

1
Review the complete configuration:
  • Transaction route title and description
  • Each operation route with its type, validation rules, and accounting entries
  • Accounting scenarios with debit and credit entries per transaction type
2
If anything needs to be adjusted, click Previous to go back.
3
Click Create Transaction Route to create the Accounting Route.

​
Quick example

Transaction Route
FieldValue
TitlePix Transfer Route
DescriptionHandles Pix instant transfers between checking accounts
Operation Route 1 — Bidirectional
FieldValue
DescriptionChecking account validation for Pix
Operation TypeBidirectional
Validation TypeAccount Type
Account Typeschecking
Direct Transaction scenario
SideAccount CodeDescription
Debit1.1.1.001Customer checking — outbound
Credit1.1.1.002Customer checking — inbound
Two-Step Transaction — Hold
SideAccount CodeDescription
Debit1.1.1.001Customer checking — reserve
Credit2.1.1.001Pending settlement — hold
Two-Step Transaction — Commit
SideAccount CodeDescription
Debit2.1.1.001Pending settlement — release
Credit1.1.1.002Customer checking — settled