Skip to main content
When recategorizing or renaming a transaction, the user will be asked whether they want the new data to apply to the selected transaction or to all future transactions. If they choose to apply it to all future transactions, it will create a transaction rule which will automatically apply the changes going forward.

​
Transaction Rule Fields

FieldData TypeDescription
category_guidStringA unique identifier for the category. Defined by MX.
created_atStringThe date and time the transaction_rule was created, represented in ISO 8601 format with a timestamp, e.g. 2015-04-13T12:01:23-06:00.
descriptionStringThe matched transaction’s description will be updated to the string provided here.
guidStringA unique identifier for the transaction_rule. Defined by MX.
match_descriptionStringA string used to find a transaction to which the rule will be applied. Transaction matching is based on a comparison of match_description to a transaction’s cleansed description.
updated_atStringThe date and time the transaction_rule was last updated, represented in ISO 8601 format with a timestamp, e.g. 2015-04-13T12:01:23Z.
user_guidStringA unique identifier for the user to which the transaction_rule belongs. Defined by MX.