Match fields are configured using point and click, per a generic two-sided process. However, when configuring match fields for a cash process, certain requirements exist.
Match fields in a cash process must at a minimum include fields named Account, Amount, Currency and Value Date in all instances. Other additional fields can use any name.
The values that are processed into the Account field will be looked-up against the accounts configured in the Settings, to define which account group transactions belong to.
See our Best Practice Guide for more detail around configuring your match fields.
If the fields used to create a match field already adhere to the naming convention listed under Field name in the table, then Duco will use this. If your input file is using a different naming convention, then you will be presented with a drop-down where you must select the appropriate Field name.
When Duco extracts transaction amounts from SWIFT messages, it extracts the debit/credit mark and amount value separately. So you should use a transformation rule to set your amount to positive (if credit) or negative (if debit) accordingly.
*Transformation rules are applied at the point of data submission. As such, if you adjust your rules and then Re-match transactions, any new or adjusted transformation rules will not be applied.
Updating a cash process in production
Please be mindful when updating the settings of live cash processes with Megadata enabled, especially those receiving thousands of transactions on a daily basis.
Updating the match fields requires the backend changes which may cause latency in the entire platform if the process is receiving submissions at the same time.
In case if changes need to be made to the match fields, including adding or removing fields, plan this action for the end of a workday or the beginning of the weekend to avoid slowing down the system. We also suggest to do the changes via a staging copy and raising a change request.