Financial export from ONS to AFAS
Retrieves a financial export from ONS, uploads it to AFAS, checks for completeness, and reports the result.
Overview
Financial transactions from ONS must be fully integrated into the AFAS general ledger. This automation retrieves the export, waits and retries if it is not yet ready, uploads it using the correct import profile, and performs a completeness check. The result is emailed to stakeholders.
What has changed
- Reduced manual processing of financial files
- Improved traceability
- Delayed exports are automatically retried in a controlled manner
At a glance
In één oogopslag
Overzicht
Financial transactions from ONS must be fully integrated into the AFAS general ledger. This automation retrieves the export, waits and retries if it is not yet ready, uploads it using the correct import profile, and performs a completeness check. The result is emailed to stakeholders.
Wat er verandert
- Reduced manual processing of financial files
- Improved traceability
- Delayed exports are automatically retried in a controlled manner
How it works.
What it does per export
- Logs in to ONS
- Starts the export and downloads it once it is ready
- Restarts itself an hour later if the export is not ready
- Uploads the file to AFAS using the correct import profile
- Performs a completeness check
- Emails the result
Rules
The process retries up to 20 times, restarting an hour later if the export is not ready. The import profile follows the general ledger name, and a completeness check determines which log route is followed. Because the logic is fixed, the same input always yields the same result, and every run is logged.
Check out other automations.
Frequently asked questions.
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.