With carry over enabled, Duco carries forward any unmatched items between reconciliation runs without you having to submit them again. This is important in the case of timing differences.

Consider this scenario: The front office generates a data extract at 6pm everyday, and the back office generates their extract at 7pm. Due to the timing difference, some records will appear in one system and not the other until the following day. 

With carryover enabled, Duco will take all of the unmatched records from one day and attempts to match on them again.

The data might look as follows:

Run 1: 8 Feb 2021

Run 2: 13 Feb 2021

Run 3: 18 Feb 2021

Let's say that you have set up a process to match the data sets above and that you want to run the process multiple times. The first time you use input Data set A1 and B1, the second time A2 and B2, and the third time A3 and B3, etc.

If you look at the data closely you'll see that A1, ..., A3 and B1, .., B3 contain the same trades, but you'll also see that each "A" data set contains 5 trades, whereas the "B" data sets varying number of trades. So, for example, if you run the matching process using A1 and B1 as input, the trade with date "07/02/2021" from Data set A1 will appear in the unmatched result. This is because it's present in Data Set A1, but not in B1. If you then run the matching process using A2 and B2 as inputs, the trades with date "07/02/2021", "13/02/2021", and "14/02/2021" and from Data set B2 will appear in the unmatched result. Because they are present in B2, but not in A2.

To deal with this situation, Duco allows you to "carry over" the records that don't match in one run to the following run.

To carry over records, tracking must also be enabled. The reason for this is, in order to carry over a record from one run to another, Duco needs to identify that record, which is possible only if tracking is enabled.

Set up your process as usual. I.e., set up the data inputs...

... and match the fields

• Click on Settings → Record tracking

• Enable record tracking
• ... and specify a set of key fields for each data set

• Next, select the items you would like to carry over. You can choose to have either Unmatched or both Unmatched and Partially Matched items to carry over. This allows you to ensure that all breaks have been rectified at source. This is particularly appropriate when you are submitting only additional new items with new runs and are not re-loading older data (e.g. for trade reconciliations).. 

• Finally, add a retention period for the records to carry over. You can either select to have items carry over indefinitely or you can set your own specific time limit.  If you set a particular time limit, Duco will mark a carry over expiry date on any records submitted during a run. When the carry over expires (the run date is after the expiry date of the record), it will no longer be moved to the next run. If you do not set a particular time limit, records will not be marked with an expiry date. In this case, records will only stop being carried over if the user accepts, closes or manually matches the record or the record becomes auto-matched.
  
  

How the retention period works

First of all, a retention period of 0 means: "don't carry over any record", which is the default behavior. You can specify a retention period for each data set. The retention period can be expressed in days, hours, or minutes. This example uses a retention period of 7 days. This means that, when you execute a run and the run gives results in an unmatched record, Duco will "hold on" and try to match that record for the next 7 days.

Let's follow, what happens when the 3 runs in this example execute:

Run 1:

• On 8 Feb 2021, the first run executes. The data inputs are A1 and B1.
• Two trades, the trade dated 07/02/2021 (sell GSK) and the trade dated 07/02/2021 (sell BP) are unmatched.
• Duco includes the two unmatched trades among the "unmatched" results, but the two trades are also carried over to the next run. Since the retention period is 7 days, Duco will attempt to match them for 7 more days. I.e., until 15 Feb 2021.
• All other trades match and are included among the "matched" results.

Run 2:

• On 13 Feb 2021, the second run executes. The data inputs are A2 and B2.
• B2 contains a match for the trade dated 07/02/2021 (sell GSK), which was carried over from the A1 in the previous run. Duco will include this trade among the "matched" results.
• The 07/02/2021 (sell BP) still does not have a match. Duco includes the trade among the "unmatched" results, but also carries the trade carried forward again. Duco will attempt to match it until 15 Feb 2021.
• B2 contains two trades, 13/02/2021 (buy HSBA) and 14/02/2015 (sell BATS), for which there is not a match in B2. Duco includes the trade among the "unmatched" results and will attempt to match them for 7 more days. I.e., until 20 Feb 2021.
• All other trades match and are included among the "matched" results.

Run 3:

• On 18 Feb 2021, the third run executes. The data inputs are A3 and B3.
• A3 contains a match for the trades 13/02/2021 (buy HSBA) and 14/02/2021 (sell BATS), which were carried over from B2 in the previous run. Duco will include these two trades among the "matched" results.
• The 07/02/2021 (sell BP) still does not have a match. Duco includes it among the match results. Because more than 7 days have passed since this trade first became unmatched, it's not carried forward any more.
• All other trades match and are included among the "matched" results.

Run with carry over only

We have added the option to perform a run with carry over data only.

This allows you to fix any exceptions due to incorrect rules and reference data tables. You can then re-run the reconciliation with carry over data only to check that the exceptions have indeed been fixed.

To make use of this option, please select the new "Run with carry over only" option from the "Run process" dropdown. This option will only be available if you have carry over switched on and there are items which will be carried over to the next run.