# Intelligent Change Processing

Benefit rules mean that the effective date of a change is one of the most important values passed to the back-office application. In practice this means dealing with multiple changes. This can be complex for a user as they are required to ensure that the changes are placed in chronological order prior to being processed.&#x20;

As you wouldn’t want to mandate to the citizen that they provide things chronologically rather than by type, the eChanges form handles all of the logic to derive the correct order for changes to be passed to and updated in the back-office. For example, a citizen reports:

* Partner moved in on 21/11/2017
* New earnings from 01/11/2017
* A change in rent from 01/09/2017

The change in circumstances form will extrapolate out what needs to happen and will push XMLs to the back-office as follows:\
\
&#x20;XML 1 01/09/2017 Change in rent

XML2 01/11/2017 Change in rent & New earnings

XML3 21/11/2017 Change in rent, New earnings & New partner

This intelligence ensures that the back-office benefit periods are updated in the exact same manner they would have been updated were the changes done manually.
