The ERES 2.0 allows you to configure the automatic distribution of settlements created by AOC services
Share
This post is over 1 year old. Content may not be up to date.
From Wednesday 30/04/2025, the service ERES 2.0 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 “Inputs/Outputs” tray MUX pending AOC”, 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 Unified Registry service MUX, from the new “Registration Settings” tray MUX” which you will find available in the Administration section of theERES.
These rules can be defined for both inputs and outputs, which arrive at theERES automatically through the MUX i 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.
So, for example, if you want to configure all invoice entries to go to a specific existing work unit in theERES and that, in addition, they are associated with a series of the entity's Classification Table, a relationship, similar to the one below, can be created based on the e-FACT submission route, which is the AOC service through which invoices arrive, and the procedure of mux associated with them.
The same can be done for service departures. eNOTUM, to allow them to go to a specific work unit and not have to remain in the pending records tray of the MUX.
In the case of procedures that arrive through services such asEACAT or l 'eTRAM, you will be able to define, in addition to the submission method, the procedure and formalities related to entry registrations.
It is important to note that the values that from the drop-downs of this functionality, which allow you to define the data that will be automatically added to the records (the submission route, the procedure (mux) and the procedure), They are living fields that will be nourished by the values of the inputs and outputs that arrive at theERES from the launch of the functionalityThat is, to define those relationships in which values must be identified beyond the presentation path (the procedure MUX or the procedure), you will have to wait until you have received some entry in theERES of the type you want to configure, to be able 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.
