ERES 2.0 allows you to configure the automatic distribution of settlements created by AOC services
From Wednesday 30/04/2025, The ERES 2.0 service incorporates a new functionality available to users with the service administrator role. that enhances the automation of repetitive tasks and streamlines record management, minimizing the need for daily management of the “AOC pending MUX Inputs/Outputs” tray, which, until now, was necessary for the distribution of automatic settlements received from the AOC services.
The way to take advantage of this automation and save registry users the task of reviewing automatic entries, to complete their classification and distribution, is that the service administrator users, define relationships, based on the entry of automatic records from the MUX Unified Registry service, from the new “MUX Registry Configurations” tray that you will find available in the ERES Administration section.
These rules can be defined for both inputs and outputs, which arrive at the ERES automatically through the MUX and They allow you to predetermine both the area or work unit to which the records will be sent for processing, and the procedure series to which they must be associated.
Thus, for example, if you want to configure all invoice entries to go to a specific work unit existing in the ERES and, in addition, to be associated with a series in the entity's Classification Table, you can create a relationship, similar to the one below, based on the e-FACT submission route, which is the AOC service through which the invoices arrive, and the mux procedure associated with them.
The same can be done for the outputs of the eNOTUM service, to allow them to go to a specific work unit and not have to remain in the MUX's pending records tray.
In the case of procedures that arrive through services such as EACAT or eTRAM, you will be able to define, in addition to the submission method, the procedure and procedure related to the entry records.
It is important to note that the values that from the drop-downs of this functionality, which allows you to define the data that will be automatically added to the records (the submission method, the procedure (mux) and the process), They are living fields that will be nourished by the values of the inputs and outputs that arrive at ERES from the launch of the functionality.That is, to define those relationships in which values must be identified beyond the presentation route (the MUX procedure or the procedure), you will need to wait until you have received an entry in ERES of the type you want to configure, in order to create the predefined data relationship, which will apply to the successive ones.
This new automation will therefore allow for the gradual reduction of the management of the automatic entry distribution tray to the maximum, so that it will only be necessary to review it to identify entries for new services, procedures or formalities, not yet configured in the new functionality, to take into account the creation of the corresponding relationship.
