Automation library
>
Healthcare Administration
>
Downloading declaration files

Downloading declaration files

Downloads declaration ZIP files from ONS for a list of items and saves them to a shared folder.

Overview

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.

What has changed

  • No more manual downloading of recurring files
  • Files are given the same name every time
  • Files are ready for the next step

At a glance

SECTOR:
VVT
System:
Nedap ONS, shared drive
RUNS:
On demand
Technique:
Rule-based

In één oogopslag

SECTOR:
VVT
Systeem:
Nedap ONS, shared drive
RUNS:
On demand
Techniek:
Rule-based

Overzicht

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.

Wat er verandert

  • No more manual downloading of recurring files
  • Files are given the same name every time
  • Files are ready for the next step

How it works.

Item list to download
Item 1 · team Northdone
Item 2 · team Eastdone
Item 3 · team Westrunning
End of month calculated
On demand
Y
Yara finds
the right ZIP
Shared folder structured names
2026-09 North.zipsaved
2026-09 East.zipsaved
2026-09 West.zipsaved
Items removed from the list
Nothing gets downloaded twice.

What it does per item

  1. Logs in to ONS
  2. Loads the list of items to be processed
  3. Calculates the end date of the month
  4. Finds the correct ZIP file in the billing section
  5. Downloads it to the shared folder with a fixed filename
  6. Removes the item from the list so it is not processed again

Rules

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.

Frequently asked questions.

Do we need to change our system?

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.

Who builds and maintains the automation?

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.

Can we see what it did?

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.

What happens if something goes wrong?

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.

Can it work for our process, even if it differs from this example?

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.

Process not found?

Don't see your process listed? Let us know. We'll start with an automation scan to see what can be automated.