Change data input to a Data Prep process

In the March 2023 release, we have enabled the ability to change any existing reconciliation input to a Data Prep process. This will work on all cash, one-sided, and two-sided reconciliations. This will help reduce manual work, react quickly to the market changes, and unblock some key pain points below:

• React quickly to market or counterparty format changes
• Freedom to change upstream sources without losing previous run results
• Change existing inputs without creating a brand new process
• Reduce the number of reconciliations and consolidate into single process fed from data prep
• Support the upcoming SWIFT ISO20022 Cash MT940/MT950 migration

Please note we are continuing to make this complex user journey easier, and appreciate any feedback on how we can make these transitions of inputs easier for our users. Please feel free to contact your Account Director or Success Manager with any inputs.

Before using this feature, please note the impacts below:

Steps:

Go to “Data input” settings page on any process

Click “Delete input” button at bottom of page and complete confirmation dialog. In order to delete a data input, you will need the config admin role on the process in which you are trying to perform this action. We also highly recommend doing this through change control with a staging copy to make sure there is 4-eye approval before this takes place, as it cannot be reversed.

You must confirm the deletion before it takes place. This will temporarily invalidate your process, until you select a new input (must be a Data Prep process).

Check this Help Centre section to learn how to create a Data Prep process.

Assign a Data Prep process to become the new input. You need to configure the Data Prep process ahead of time. If the Data Prep process field names (case sensitive), field type, and field order match exactly, then nothing more needs to be done.

However, if there is a mismatch, then an error message will display with a link to fix the underlying difference. Make sure to inspect the match fields after clicking this link to make sure everything is as expected.

In this case, Account is now Account Identifier, so Duco has detected a mismatch and you will need to reconfigure this in the match fields screen. (Note, fields are case sensitive. So, if Amount is now amount, you will still need to reconfigure).

This next step is important!

Reconfigure this by creating a rule which sets the match field to the corresponding field from the new input.

You must use NRL to complete this step.

DO NOT delete the pairing and re-create the match field. This will break any NRL rules which reference that field, and will result in losing any submitted data related to that match field. The data history will be lost!

Once done, this step is complete. If SFTP is configured to this process, you will need to redirect the data source to route into the Data Prep process.