Downloads declaration ZIP files from ONS for a list of items and saves them to a shared folder.
Declaration files must be retrieved from ONS for each processing item. This automation finds the correct ZIP file for the month, downloads it to the shared folder with a fixed filename, and removes the item from the list so it is not processed twice.
Declaration files must be retrieved from ONS for each processing item. This automation finds the correct ZIP file for the month, downloads it to the shared folder with a fixed filename, and removes the item from the list so it is not processed twice.
The end date of the month determines which ZIP file is selected, and once an item is downloaded, it is removed from the list to prevent duplicate processing. Because the logic is fixed, the same input always yields the same result, and every run is logged.
No. The digital colleague works in the screens and systems your team already uses, whether they are legacy applications without an API or modern ones, so there is nothing to replace.
Yarado builds it, runs it and monitors it. When a screen or a system changes, we adjust the automation, so your team needs no developer or automation skills of its own.
Yes. Every run is recorded in the Yarado portal, where you can see which processes ran, when they last ran, what they produced and what went wrong. Depending on the automation, the processing log is also emailed to the team that needs it.
Yarado monitors every run and is alerted automatically when one fails, so a problem is picked up on our side. Cases that need a person are reported to your team with the reason, in the portal or by email.
Yes. Automations are built around your own steps and systems, and this page is just one example of what is possible. A first automation is typically live in weeks, not months.