Customs brokers and agents have automated a lot of the work of filing declarations. Billing for that work is often still manual: someone exports a list of declarations, looks up each customer’s rates, builds invoices in a separate tool and chases payment by email.
Customs invoice automation closes that gap. Every declaration you file for a customer becomes a priced charge, every charge lands on the right invoice, and the invoice moves through approval and payment without being re-keyed. This guide shows how to get there, step by step, and how iInvoice by iCustoms does it inside the platform where your declarations are made.
This guide covers:
New to the topic? Start with our guide to customs invoice software.
Customs invoice automation is the use of software to bill customers for customs work without manual data entry. When a customs broker or agent files a declaration for a customer, the automation records that usage, applies the customer’s agreed price, adds the charge to the right invoice and tracks the invoice until it is paid.
It is worth separating three things that often get mixed up in search results:
| Stage | Manual | Automated with iInvoice |
|---|---|---|
| Capturing usage | Declarations exported or copied into a spreadsheet | Usage from iCustoms recorded against each customer as declarations are filed |
| Pricing | Each customer’s rates looked up and applied by hand | Rate cards apply the agreed rules automatically |
| Exceptions | Missing rates noticed late, if at all | Unpriced charges flagged as they appear |
| Invoice build | Lines typed into a separate invoicing tool | Priced usage comes in as invoice lines, grouped how you choose |
| Approval | Emails and spreadsheets passed around | Draft, pending approval and approve in one place |
| Sending | PDF saved and attached manually | Approve and email in one step |
| Payment follow-up | Manual chasing from a list | Payment statuses, overdue invoices and reminders |
| Regular customers | Invoices recreated every month | Repeating invoices on a schedule |
Automation is only as good as its starting point. If billing begins with someone exporting declarations into a spreadsheet, every later step inherits that manual work. The goal is for each declaration to be recorded as billable usage against the right customer the moment it is filed.
In iInvoice: declarations and billing sit on the same platform. Your iCustoms modules are already listed as billable products, so their usage arrives ready to price. You add your own products only for extra services you sell, and you can add manual lines for one-off charges.
Most billing errors in customs services come from pricing, not arithmetic. Each customer has its own agreement, and agreements change. Write them down once as rules, and let the software apply them.
In iInvoice: a rate card sets the price for a product for all customers (your default), one customer or a customer group, with optional start and end dates, a tax rate and a linked discount. Pricing rules include a fixed fee on every declaration, a fee for each item, a price per unit or per batch, tiered prices, a set fee per band, an amount that depends on the job, and a fixed fee that applies only when a condition matches. Rules used across many cards can be saved to a shared library, with an override price for any customer who pays differently.
An automated process needs an exceptions queue. A declaration with no matching price shouldn’t quietly disappear from the invoice; it should be flagged so someone can decide what to charge.
In iInvoice: any usage with no matching rate card is marked as unpriced. Add or extend a rate card and the charge is priced automatically. Unbilled usage shows every priced charge not yet invoiced, by customer, and by how long it has been waiting, so nothing ages out of sight.
Once usage is priced, building an invoice should take a choice, not a morning. Choose the customer, and their priced usage comes in as invoice lines.
In iInvoice: group lines per product, per declaration or per item. The total is the same whichever you pick. The Explain view adds a breakdown of each declaration, showing how every amount was reached, which answers most customer queries before they are asked. You can add your own rows, attach supporting files and use the Freight and Customs Invoice template designed for billing declarations and filings.
Automation should remove typing, not judgement. Keep a review step before an invoice is final, especially for large customers or new rate cards.
In iInvoice: save and close keeps an invoice as an editable draft. Submit it for approval if someone else signs invoices off. Approve and email approves the invoice, gives it its number and sends it to the customer, or you can approve only, get a link or print the PDF. Once approved, an invoice is locked, which keeps your records consistent.
Billing isn’t finished until the invoice is paid. Automate the follow-up and the invoices that repeat every month.
In iInvoice: invoices move through draft, pending approval, awaiting payment and paid, with overdue invoices shown in red. Payment reminders can be switched on or off. For regular customers, repeating invoices run on a schedule you set, with payment terms and a choice of saving each one as a draft or approving it. You can also import invoices using a template and export your invoice list. Ask the iCustoms team which accounting connections are available for your account.
Harbourline Customs files import declarations for Northgate Retail, which has three branches. Northgate’s head office pays for all of them. Here is how the month runs in iInvoice:
Nobody re-keyed a declaration, looked up a rate or typed an invoice line. The one decision a person made was what to charge for the EUR1 certificate, which is exactly the kind of judgement that should stay with your team.
Your declarations are already in iCustoms. iInvoice turns them into invoices, so your team spends its time on customs work, not on billing admin.
ย
Your team already does the customs work. iInvoice makes sure every declaration is priced, invoiced and paid.
Customs invoice automation means billing the declarations you file for customers without re-keying them. Declaration usage is captured at the source, priced by rate cards and turned into invoices that go through approval, sending and payment tracking in one workflow.
Declaration automation happens before filing: reading documents, classifying goods and submitting the declaration. Billing automation happens after filing: pricing that work and invoicing the customer for it. iInvoice handles the billing stage inside iCustoms.
Most of it can. Capturing usage, applying agreed rates and building invoice lines can run automatically. Approval should stay with a person, because an approved invoice is numbered and locked. iInvoice lets you choose whether repeating invoices are saved as drafts or approved.
Turn each agreement into a rate card. Rate cards can apply to all customers, one customer or a customer group, between set dates, using rules such as fixed fees per declaration, per-item fees and tiered prices.
In iInvoice they are flagged as unpriced rather than left off the invoice. Once you add or extend a rate card to cover them, they are priced automatically.
Yes. Billing accounts link several contacts to one payer, so a head office can receive one invoice for work done for its branches.
You can import invoices with a template and export your invoice list from iInvoice. Ask the iCustoms team which accounting connections are available for your account.
Start with your rate cards. Put your default prices and your largest customers' agreements into rate cards, check unbilled usage for anything unpriced, then run one billing cycle for a few customers before widening.
Price, invoice and track every declaration automatically.
iCustoms is an all-in-one solution helping businesses automate customs processes more efficiently. With AI-powered and machine-learning capabilities, iCustoms is designed to streamline your all customs procedures in a few minutes, cut additional costs and save time.
Set each customerโs rates once and bill without re-keying.