Handling invoice tickets
Checks invoices in support tickets against file data, adds work orders, replies, and closes the ticket.
Overview
Invoices arrive as Zendesk tickets and must match the file in Dynamics before anyone replies. This automation reads the invoice PDF, checks it against the file and work orders, replies with the correct country macro, and resolves the ticket. If something is incorrect, it adds an internal note instead of sending an incorrect reply.
What has changed
- Less manual work
- Invoices undergo the same checks every time
- Tickets are assigned to the right employees
At a glance
In één oogopslag
Overzicht
Invoices arrive as Zendesk tickets and must match the file in Dynamics before anyone replies. This automation reads the invoice PDF, checks it against the file and work orders, replies with the correct country macro, and resolves the ticket. If something is incorrect, it adds an internal note instead of sending an incorrect reply.
Wat er verandert
- Less manual work
- Invoices undergo the same checks every time
- Tickets are assigned to the right employees
How it works.
What it does per ticket
- Retrieves up to 20 invoice tickets from Zendesk
- Downloads the invoice PDF and uses AI to extract the file number, customer, and work order
- Checks the data against the file in Dynamics, including a name comparison
- Downloads and checks the work orders
- Applies the correct country macro and attaches the documents
- Sends the reply and resolves the ticket, or adds an internal note in case of exceptions
Rules
A ticket is only processed if it is accessible, unassigned, and contains one message with a PDF. AI reads the invoice and the name is compared with the file, requiring a full match, and the file number must yield exactly one result with matching work orders. If a check fails, an internal note is added instead of a reply.
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.