Validate invoice export
Validates test invoice exports using fixed quality checks and initiates production exports upon approval.
Overview
Before invoices move to production, test exports must be complete and cover the correct period. This automation downloads three test exports, verifies the period, checks that the error and warning sheets are empty, and only then starts the production exports. If a check fails, the file is emailed.
What has changed
- Reduced manual follow-up for invoice preparation
- Exports are complete and period-accurate before release
- Invoice batches are released in a controlled and traceable manner
At a glance
In één oogopslag
Overzicht
Before invoices move to production, test exports must be complete and cover the correct period. This automation downloads three test exports, verifies the period, checks that the error and warning sheets are empty, and only then starts the production exports. If a check fails, the file is emailed.
Wat er verandert
- Reduced manual follow-up for invoice preparation
- Exports are complete and period-accurate before release
- Invoice batches are released in a controlled and traceable manner
How it works.
What it does per export
- Checks if pending exports are ready
- Downloads the test export files
- Verifies that the period runs from January 1st to the end of last month
- Checks that the error and warning sheets are empty
- Emails the file if a check fails
- Starts the production export per invoice period
Rules
Two quality checks determine whether production can start: the export period must run from January 1st to the end of the previous month, and the error and warning sheets must be empty. The run attempts to retry up to 20 times. The same input always leads to the same outcome, and every run leaves an audit trail that can be reviewed.
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.