TSS Automation Software: What Should Businesses Look For?
- John Hall
- Customs Specialist at iCustoms.ai
Judge TSS automation software on six things: whether it can submit programmatically, what it validates before submitting, how it behaves at your volume, what happens when a submission fails, how it connects to the systems that already hold your data, and whether it leaves an audit trail. Everything else is detail.
This is a buyer’s checklist rather than a recommendation. Choosing TSS software is mostly a matter of asking specific questions and refusing vague answers, so it is written to be handed to a vendor, including us.
First question: do you need software at all?
Worth asking honestly, because the answer is sometimes no.
TSS is free. GOV.UK confirms there is no subscription and no charge per declaration. If you make a handful of movements a month with a stable product range, the portal is adequate and buying software will not pay back.
The economics change when one or more of these is true:
- The same customer and the same products are declared repeatedly, and somebody retypes them each time
- Data arrives as invoices, packing lists and transport documents that a person has to read
- Your ERP, WMS or TMS already holds most of the data, disconnected from the customs process
- Declaration volume is the constraint on how much work you can take on
- Nobody can tell you, right now, how many supplementary declarations are outstanding this month
If none of those apply, save your budget. If three or more do, keep reading.
Do not evaluate software before you fix the data The commonest reason these projects disappoint is that the business bought a tool to solve what was actually a data problem. If your authoritative commodity code lives in three spreadsheets and one person’s memory, no vendor can fix that for you. Sort the product master first, then buy. |
The six areas that matter
Treat these as your declaration software requirements document. Score every vendor against the same six rather than comparing feature lists, which are written to be incomparable.
| Area | The question it answers | Why it matters |
|---|---|---|
| Submission | Can it submit programmatically, and what? | Determines whether people still type into a portal |
| Validation | What does it check before submitting? | This is what turns faster into better |
| Scalability | Does it hold up at your volume and peaks? | Month-end is when it will be tested |
| Exception handling | What happens when something fails? | The most underestimated area by a distance |
| Integration | Can it reach the data you already hold? | Decides how much manual input remains |
| Auditability | Can you prove what was submitted and why? | You still answer for accuracy, not the vendor |
1. Submission
TSS provides an API, so any serious tool should be able to submit programmatically rather than driving a browser.
Ask which declaration types it handles. The API covers entry summary declarations, simplified frontier declarations, supplementary declarations and full frontier declarations. A tool that only does one of those leaves you with two processes.
Questions worth asking:
- Which declaration types can you submit today, in production, for a customer like us?
- Do you handle internal market movement submissions for UKIMS authorised traders?
- Can you create the port movement reference, and what authorisation does that need?
- Can you act on behalf of multiple traders if we are an intermediary?
- How do you handle the item limit per declaration for large consignments?
For the underlying technical picture, including the test environment and what the interface actually accepts, see what the TSS API can and cannot do.
2. Validation
The single most valuable area, and the one most vendors describe vaguely.
Automating submission without validation just produces wrong declarations faster. Push hard here, and make the questions specific enough that a generic answer is obvious:
- Do you check the commodity code exists and is current, and that the digit count matches the goods category? Standard goods take six digits; Category 2 goods take eight.
- Do you flag goods descriptions that fail the plain-language standard, including prohibited terms that would cause a rejection at submission?
- Do you check the document codes the Tariff Requirements call for are present in the right data element?
- Do you reconcile gross mass against net mass, and package counts against the packing list?
- Do you check certificate and licence references match the supporting documents?
- Do you validate that a scheme authorisation number is valid for the date of the movement?
A vendor who answers all six concretely is worth shortlisting. One who says the platform validates your data is not answering.
If you want the list of what actually goes wrong, so you can test against it, reducing manual entry mistakes sets out the errors that cause most rejections.
3. Scalability
Not just total volume. Shape matters more than size.
Customs work is not evenly distributed. Supplementary declarations for a whole month are due by the tenth calendar day of the following month, which produces a spike whatever your average looks like. Ask about the peak, not the mean.
- What is the largest customer you run today, in declarations per month?
- What happens on the eighth, ninth and tenth of the month?
- Can you process in batches, and what are the limits?
- How does performance change as our product catalogue grows, rather than our shipment count?
That last question separates the thoughtful vendors. Item-level effort scales with product variety, not with the number of movements, so a business shipping one pallet of forty different products has more work than one shipping a full load of a single item.
4. Exception handling
The area buyers ask about least and regret most.
Every submission returns an outcome. Accepted ones are easy. What you are buying is how the tool behaves on the others.
- When a submission is rejected, who is told, how quickly, and through what channel?
- Does the error arrive with enough context that somebody can act, or just a code?
- Can we route different error types to different people?
- What stops a rejection sitting unresolved until a deadline turns it into a problem?
- Can we see everything currently unresolved, in one place, without running a report?
Ask to see this in the demo. Vendors will happily show you a clean submission. Ask them to show you a failed one, then ask what happens next.
5. Integration
The data mostly exists already. The question is whether the tool can reach it.
- Which of our systems can you connect to, and has it been done before?
- Can you read trade documents that arrive as PDFs and scans, not just structured feeds?
- How do you handle a supplier who changes their invoice layout?
- What happens to a document you cannot read confidently?
That last one is a quality question dressed as a technical one. A tool that quietly guesses is worse than one that stops and asks.
Most of what makes an integration succeed sits on your side rather than the vendor’s. getting your product data in order covers the groundwork worth doing before anybody demos anything.
6. Auditability
The obligation to declare accurately stays with you. Software does not take it on, and no contract moves it.
- Can we see exactly what was submitted, when, and by which user or process?
- If a value was changed between the document and the declaration, is that visible and attributable?
- How long is history retained, and can we export it? UKIMS conditions require supporting evidence to be kept for five years and accessible in the UK.
- If we leave, what do we get back and in what format?
Ask the exit question early. The answer tells you a lot about the relationship you are entering.
Five questions that separate vendors quickly
- Show me a rejected declaration end to end, from the error arriving to it being fixed.
- Which of your validation checks are specific to Northern Ireland movements, rather than generic customs checks?
- Give me a reference customer with a similar product range and volume, not just a similar logo.
- What do you not do? Where does your responsibility stop and ours begin?
- What is the realistic implementation timeline given our data as it is today, not as it should be?
The fourth question is the most revealing. A vendor with a clear answer has thought about the boundary. A vendor who claims to do everything has not.
What cost actually includes
List price is rarely the number that matters. Build the comparison from:
- Licence or subscription, and how it scales, whether by user, declaration or volume band
- Implementation and data mapping, which is usually the larger first-year figure
- Integration work on your side, including your own IT time
- Training, and retraining when people change
- Ongoing support, and what is included versus chargeable
- The cost of running parallel during the transition
Set against that, be equally disciplined about the benefit. Measure your current position first: how many declarations, how many people, how many rejections, how much time between documents arriving and submission. Without a baseline, any saving claimed later is unprovable, including your own.
A note on percentages Be sceptical of accuracy, time-saving or return-on-investment figures presented without a method. Ask how the number was calculated, over what period, for what kind of customer. A vendor who can explain the method is being straight with you. One who cannot is quoting marketing at you. |
Red flags
| What you hear | Why it should worry you |
|---|---|
| Guaranteed one hundred per cent accuracy | Nobody can guarantee this. The claim itself tells you how the vendor talks about risk. |
| We replace TSS | They do not. TSS is the government route. Anything sitting around it is a layer, not a replacement. |
| Fully automated, no human involvement | The at-risk decision and accountability for accuracy stay with people. Always. |
| A demo using only their own sample data | Ask them to run one of your real invoices, including a messy one. |
| Vague answers on validation | The most valuable area is the one they should be most specific about. |
| No named reference in your sector | Northern Ireland movements have specifics. General customs experience is not the same thing. |
How to run the evaluation
A customs software evaluation works best when it is short, evidence-based and run against your own data rather than a curated demo.
- Write down your current numbers first. Volume, people, rejection rate, time from document to submission.
- Shortlist on the six areas above. Comparing TSS software features line by line tends to reward whoever wrote the longest list, not whoever solves your problem.
- Demo with your own data, including one difficult supplier and one messy document.
- Insist on seeing failure handling, not just the happy path.
- Take references and ask them what went wrong during implementation.
- Pilot on one lane, run parallel, and compare against your baseline before committing further.
Who should be in the room
Customs and operations first, IT second, finance third. The hard decisions here are customs decisions. An evaluation run purely by IT tends to produce something technically sound and operationally wrong.
Where to go next
If you are still working out whether the workflow suits you at all, the document to declaration workflow walks through what automation actually changes, and choosing between API and portal submission compares the two operating models directly.
Intermediaries handling many clients have a different set of requirements again, which we cover in TSS software for freight forwarders.
And if you want to see how the pieces fit together in practice, our overview of Northern Ireland customs automation sets out the layer that sits in front of the government service.
Frequently Asked Questions
You may also like:
Struggling to Extract, Catagorise & Validate Your Documents?
Capture & Upload Data in Seconds with AI & Machine Learning
Subscribe to our Newsletter
About iCustoms
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.
Struggling to Extract, Catagorise & Validate Your Documents?
Capture & Upload Data in Seconds with AI & Machine Learning