Skip to main content
You create an Accounting Route through a guided 3-step wizard. The wizard walks you through the transaction route, the operation routes with their accounting scenarios, and a final review.

​
Before you start

Create the Account Types and Accounts that the route validates. If you have not chosen the operation type, the validation type, and the accounting scenarios yet, read Accounting rules first.
If you enable Validate Routes for the Ledger, every transaction must match an existing route. Do not enable route validation until the required Accounting Routes are ready.
The sidebar shows Accounting Routes only when Validate Routes is on for the Ledger. When it is off, open the page from the Console page search (Search pages…).

​
Step 1: Basic information

1
From the Accounting Routes page, click New Route.
2
The creation wizard opens on the Transaction Route step.
3
Fill in the basic information:
  • Route Title (required): a descriptive name for this transaction route. You must fill in this field to continue.
  • Description (optional): a description of the route’s purpose. If you leave it empty, the wizard submits and stores an empty description.
4
Click Next to proceed to Step 2.

​
Step 2: Operation Routes

In this step, you add and configure the operation routes. Operation routes define how the ledger validates accounts and records accounting entries.
A Bidirectional operation route acts as both source and destination. When you later create a transaction, the ledger matches a bidirectional route on both the source side and the destination side. A single route can then validate both ends of the flow.
1
Click Add Operation Route to create your first operation route card.
2
Configure the operation route:
  • Title (required): a name for this operation route. The operation route has a single required text field and no separate description field. You cannot advance to the next step until you fill it in.
  • Type: Source, Destination, or Bidirectional.
  • Validation Type: Account Type or @Alias. The wizard requires at least one Account Type or an alias for each operation route.
  • Account Type or Alias: the selected Account Type values or the specific account alias.
3
Configure Accounting Scenarios to define how the ledger records entries. Direct Transaction is always on, and you must fill in its entries. Toggle on the other 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.
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
To adjust anything, click Previous to go back.
3
Click Create Transaction Route to create the Accounting Route.

​
Field guide

​
Basic information

​
Operation route

​
Quick example

Transaction RouteOperation Route 1: BidirectionalDirect Transaction scenario

​
What to do next

After you create the route, create a transaction that matches the same account types, aliases, and scenario in Creating a Transaction.

Create Transaction Route

Create the transaction-level route via API.

Create Operation Route

Create operation-level routing rules via API.