Posting invoices in Dynamics 365
Prepares and posts purchase invoices in Dynamics 365 from a controlled data source, with an audit trail.
Overview
Purchase invoices must be posted in the correct company with the right settings. This automation prepares them from a controlled data source, stops when that source is empty, posts them, and creates the approval workflow. In the free-text variant, invoice creators also receive an email with the result, including any warnings or errors.
What has changed
- Less manual financial work
- Invoices are posted consistently
- There is an audit trail, and in the free-text variant, creators receive timely feedback
At a glance
In één oogopslag
Overzicht
Purchase invoices must be posted in the correct company with the right settings. This automation prepares them from a controlled data source, stops when that source is empty, posts them, and creates the approval workflow. In the free-text variant, invoice creators also receive an email with the result, including any warnings or errors.
Wat er verandert
- Less manual financial work
- Invoices are posted consistently
- There is an audit trail, and in the free-text variant, creators receive timely feedback
How it works.
What it does per invoice
- Refreshes the source data and stops if the output is empty
- Logs into Dynamics and opens the correct view and company
- Posts the invoices
- Creates the approval workflow
- Cleans up temporary markers
- In the free-text variant, it emails the result to the invoice creator
Rules
The run stops if the source data is empty and checks before posting whether it is in the correct company, ensuring an invoice is never posted to the wrong legal entity. The outcome is classified as posted, posted with warning, or failed. The same input always leads to the same outcome, and every run leaves a log that can be audited.
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.