- A rule you’ve set up, such as “this card always books to Software”.
- A suggestion from the accounting intelligence agent.
- The dimension’s default value.
Create a rule
A rule, called a mapping in the API, sets one dimension for every transaction that involves a given card, merchant, contact or other source. Create one with Create or replace an accounting mapping:applyToExistingEntries
to also recode entries that are still in_review; sending an existing rule
again with it applies that rule to them.
When several rules set the same dimension, the most specific one wins, in
this order:
contactmerchantmerchant_categorycardcard_groupvirtual_account
account rules of account and accounts_payable sources belong to the
connection’s default subsidiary. Every other rule applies to the whole
connection.
Review and remove rules
List accounting mappings shows every rule on the connection, both the ones people wrote (createdBy: user) and the
ones the intelligence agent created (createdBy: ai). Filter by sourceType,
sourceId or dimensionKey.
Delete an accounting mapping
removes a rule. Entries it already coded keep their values.
Accounting intelligence
The accounting intelligence agent codes what no rule covers, based on the merchant, card and past transactions. Its suggestions are saved as rules, so you can correct one by writing your own rule for the same source. Choose which dimensions it codes with Update accounting intelligence settings:
The settings you read report
enabledDimensionKeys as what the agent codes
under the current mode, and you can send that object back unchanged. To pick
dimensions, switch to selected_fields.
Switch dimensions on or off
Update an accounting dimension switches a dimension on or off for coding and renames it.Set a default value
A default is used when no rule or suggestion applies, for example “everything is Operations unless a rule says otherwise”. Set it withdefaultValueId on
Update an accounting dimension.