Customs invoicing
Creates, verifies, prints, and logs invoices for customs files in Softpak.
Overview
Every customs file requires an invoice based on tariff lines. This automation enters the file number into Softpak, creates and prints the invoice, validates the invoice number, and checks that all lines have been invoiced. Complete, partial, and exception cases are logged in Excel.
What has changed
- Less manual work for repetitive invoicing
- Invoices are created consistently
- A clear audit trail of processed, partial, and exception cases
At a glance
In één oogopslag
Overzicht
Every customs file requires an invoice based on tariff lines. This automation enters the file number into Softpak, creates and prints the invoice, validates the invoice number, and checks that all lines have been invoiced. Complete, partial, and exception cases are logged in Excel.
Wat er verandert
- Less manual work for repetitive invoicing
- Invoices are created consistently
- A clear audit trail of processed, partial, and exception cases
How it works.
What it does per customs file
- Collects the data and copies the log file for the run
- Enters each file number into Softpak
- Opens the tariff screen and creates the invoice
- Prints the invoice and validates the invoice number
- Checks if all tariff lines have been invoiced and flags partially invoiced files
- Writes the result per file to the Excel log and emails the logs
Rules
If the tariff screen is unavailable, the file is skipped with a status indicating this. An invoice is considered partially invoiced if only some of the tariff lines match the number. Every run follows the same logic and is logged for review, leaving no room for guesswork.
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.