How we use coding
Rho enables you to code transactions efficiently, by combining mapping rules, manual coding and default settings to automate coding tasks, while still allowing for user intervention for customization and fine-tuning.
There are three ways that coding gets applied to transactions in Rho.
- Mapping rules
- Line-level coding (manually overriding)
- Default settings (Only for some areas of the product, such as Default Income, Default Expense and Default Accounts Payable accounts)
Mapping rules
Rho applies mapping rules in a hierarchical fashion, checking for rules which exist in the following order.
Mapping hierarchy:
1. Label
2. Vendor
3. Merchant
4. MerchantCategory
5. Card
6. Budget
Here’s an example of how this functions. If there are 2 mapping rules:
- When Vendor = Cindy’s Cookies -> assign GL = Meals and Entertainment
- When Card = *1234 -> assign GL = Miscellaneous
A transaction on Card *1234 at Cindy’s Cookies would bear the coding Meals and Entertainment
Line-level coding
While Mapping rules automate coding tasks, users may opt to override those values. To change a mapping rule-determined coding in Rho, simply modify the assigned mapping on the transaction or via the drawer.
Rho respects user-selected codings and won't update them with new mapping rules or when the Apply Mappings feature is used.
Default settings
When using Rho, you need to choose default GL Income and Expense accounts. If a transaction doesn't have any mapping rules or manual codings, Rho will automatically assign the default GL accounts to the transaction.
.avif)
.avif)