TSS Software for Freight Forwarders: How to Scale Customs Declarations
- John Hall
- Customs Specialist at iCustoms.ai
Freight forwarders scale TSS declaration volume by removing repeat typing, not by adding staff. The Trader Support Service (TSS) itself is free and supports intermediaries through an agent account, but it does not solve multi-client working. Software earns its place by holding client data separately, reusing what repeats and routing only genuine exceptions to a person.
This article is written for the people who file for other businesses: forwarders, customs agents, intermediaries and in-house teams handling several trading entities. It covers how TSS treats intermediaries, where the volume actually goes, and what to insist on when you look at customs software for freight forwarders.
Most searches for TSS software freight forwarders come from operations managers who already know they cannot hire their way out of the volume, and want to understand what is actually being bought. That is the question this answers.
Terms used here An intermediary is anyone who completes customs formalities for someone else. TSS uses the phrase customs agent for the account type. Freight forwarder, customs agent, broker and intermediary are used loosely in the trade, but in TSS the account type is what governs what you can do. |
How TSS treats intermediaries
Before you evaluate any software, it helps to know the constraints the government service imposes, because software cannot remove them. TSS for customs agents runs through a distinct account type with its own rules, and those rules shape everything a supplier can offer you. The detail below comes from the NICTA handbook for customs agents and intermediaries, updated 27 May 2026.
The agent account is a one-way door
An intermediary works in TSS through an agent account. If you already hold a trader account, the primary account contact converts it using Convert Account to Agent Account. That conversion is permanent and cannot be reversed. It is worth pausing on that before anyone clicks it, particularly if your business also moves its own goods.
Authorisation runs in two steps, and the trader starts it
You cannot add clients yourself. The trader raises the request from their account, and you accept or decline it from your Notification tab or by email. Until you accept, nothing can be filed. For onboarding, that means the first task in every new client relationship is chasing an action inside someone else’s TSS account.
A trader can authorise only one customs agent
This is the constraint most forwarders discover late. A trader may authorise a single customs agent to complete declarations and facilitate payments on their behalf. There is no shared or parallel arrangement, so a client cannot split work between two intermediaries inside TSS, and taking on a client who already uses another agent means that authorisation has to be removed first. It also means a client leaving you is a single administrative action on their side.
You work inside the client's account, with limits
Once authorised, you switch into a client using Represent a Trader in the username menu, and a banner confirms you are acting for them. You will not see everything they see. Visibility of their Northern Ireland to Great Britain movements is restricted, and you can only see cases you raised yourself or cases attached to declarations you submitted. Any open case moves back to the trader’s account if your authorisation is removed.
You cannot wear two hats at once
This one catches forwarders who also move the goods. While acting on behalf of another account, you are not authorised to complete declarations as a haulier or freight forwarder. TSS for hauliers is a separate role, and the account you are inside determines which role you are playing. If your business does both the movement and the customs work, that has to be planned around rather than discovered mid-shipment.
Multi-factor authentication on every login
Agent accounts require an authenticator app and a code at every sign-in. It is a small thing until you have several operators working shifts, at which point access management becomes a real process rather than a shared password.
What agents can file covers most of the ground: supplementary declarations, full frontier declarations and Internal Market Movement Information (IMMI) for clients holding UK Internal Market Scheme (UKIMS) authorisation. Northern Ireland to Great Britain exports are outside the scope.
For the wider picture of which declaration applies to which movement, see the declaration types TSS supports and when each is due.
Where a forwarder's declaration time actually goes
Ask anyone handling Northern Ireland declarations for clients where the hours go and the answer is rarely the declaration itself. A supplementary declaration for a client you have filed for fifty times is not intellectually difficult. It is the surrounding work that consumes the day.
| Activity | Why it consumes time at volume | Does it repeat? |
|---|---|---|
| Chasing client paperwork | Invoices arrive late, in different formats, from different contacts at each client. | Every movement |
| Re-keying the same product data | The same commodity codes, descriptions, origins and weights are typed again for regular lines. | Almost always |
| Switching between client accounts | Each client is a separate context, with its own authorisations and payment arrangements. | Every switch |
| Resolving rejections | An error found after submission costs far more than the same error found before it. | Unpredictable |
| Month-end concentration | Supplementary declarations bunch towards the deadline rather than spreading evenly. | Every month |
| Answering status questions | Clients ask where a declaration is, and the answer requires logging in and looking. | Constantly |
Only two of those six are customs expertise. The rest are administration, and administration is what software should be attacking. That distinction matters when you build a business case, because the saving is not in doing declarations faster, it is in doing less of everything around them.
A note on the Assisted Completion Service TSS offers a free Assisted Completion Service where a TSS agent will complete up to twenty supplementary declarations a month on a trader’s behalf, for declarations in Draft or Trader Input Required status with a tax point date less than 330 days old. It is explicitly not available to customs agents, or to traders who use an intermediary in TSS. If you are an intermediary, this safety net does not exist for you, which is precisely why your own throughput has to be engineered. |
What scaling actually means for an intermediary
Scaling customs declarations is not about peak capacity on a good day. It is about what happens to the operation when volume doubles. Three patterns are worth naming.
Linear scaling
Double the movements, double the people. Costs and revenue rise together, margin stays flat, and recruitment becomes the constraint. Most manual operations sit here whether they realise it or not.
Fragile scaling
Volume is absorbed by the same team working harder. It holds until something disrupts it: a busy week, an absence, a client onboarding. Error rates climb quietly before anything visibly breaks. This is the most dangerous pattern because it looks like efficiency.
Structural scaling
Repeat work stops being work. A regular client’s regular product line requires review rather than creation, so volume growth lands mostly on the reusable part of the process. Headcount grows with client count and complexity, not with shipment count.
The third is the only one that survives growth, and it is the only one worth paying for. When you assess a freight forwarder customs workflow, the question is not how fast a single declaration can be produced. It is what proportion of your movements could be handled without a person creating anything from scratch.
Six things intermediary software must handle that single-trader software does not
Plenty of customs software is built for a business filing its own declarations. Multi-client declaration management is a different problem, and these are the six differences that matter.
- Hard separation between clients. Client data, product records and documents must not bleed across accounts. One client’s commodity code appearing on another client’s declaration is a commercial incident, not a bug.
- Per-client reference data. Each client has their own product master, their own suppliers, their own recurring routes. Reuse only works if the system knows whose data it is reusing.
- Correct authorisation handling. UKIMS is held by the trader, not by you. The importer EORI on the declaration must match the EORI on that client’s UKIMS authorisation, and no software should let you file as though the authorisation were yours.
- Payment routing you can see. Agents may use their own duty deferment account (DDA), their own CDS cash account or electronic credit transfer for full frontier declarations, with narrower options for supplementary declarations. Which account paid what, for which client, has to be visible without reconstruction.
- Per-client audit trail. When a client asks what was submitted for a movement eighteen months ago, the answer should take a search, not an archaeology project. Records must be retained for the required period and retrievable per client.
- Exception routing that reaches the right person. An exception is usually a question for a specific contact at a specific client. Software that surfaces exceptions without routing them just moves the queue.
Notice that none of these are features you would think to ask about if you filed only for yourself. They are the reason a general customs product can look impressive in a demonstration and still fail in an intermediary operation.
Connecting your own systems
Most forwarders already run a transport or freight management system holding consignment data. The customs work then happens somewhere else, and the gap between the two is filled by copying. Closing that gap is usually the largest single saving available.
TSS provides an API, and the functional guide confirms that agents can submit for the traders they represent, so programmatic submission is available to intermediaries rather than being a trader-only route. It is not a small undertaking: it assumes development capability and clean source data on your side.
Whether that is the right move depends on your volume and repetition profile. We have compared the two operating models honestly in whether the API or the portal suits your volume, and set out the workflow itself in how TSS declaration automation works step by step.
One limit worth designing around A single declaration submitted through the API is limited to 99 items. Consolidated groupage loads can exceed that, so any high-volume design needs a defined approach to splitting consignments before it meets that limit in production rather than after. |
The data problem is your clients' data problem
A forwarder’s declaration quality is capped by what clients send. You cannot validate your way out of a supplier invoice that describes goods as assorted parts. This is the uncomfortable part of the business case: some of the improvement has to happen on the client side.
What you can do is make the requirement explicit and make compliance easy. A short onboarding data specification per client, agreed once, prevents more rework than any amount of downstream checking. Specify the goods description standard, the commodity code source, origin evidence, incoterms, weights and the UKIMS position.
The full requirement is set out in writing customs-ready goods descriptions, and the failure patterns are catalogued in where manual TSS entry goes wrong. Both are worth sending to clients rather than paraphrasing.
The movement side does not wait for you
For accompanied roll-on roll-off traffic, the customs data has to exist before a goods movement reference can be built, and the vehicle cannot check in without one. That makes late client paperwork a transport problem rather than a paperwork problem, which is a useful thing to be able to demonstrate when you renegotiate cut-off times.
The dependency is explained in how goods movement references are built from declaration data.
Building the business case
Avoid vendor arithmetic. Use your own numbers, measured over a normal month rather than a quiet one.
- Count declarations by client and by type, separating first-time products from repeats.
- Time a repeat declaration end to end, including chasing documents and switching accounts, not just the keying.
- Count rejections and amendments, and estimate the handling time each one costs.
- Identify your month-end peak as a multiple of your average day. That multiple is what forces overtime or agency cover.
- Work out what proportion of your movements are repeat product lines for existing clients. That proportion is roughly the share of work that automation can genuinely take.
- Price the alternative honestly: the licence, the implementation, the integration effort and the internal time to run it.
If repeats are a small share of your volume, or every client sends something different every time, the saving will be smaller than a vendor projects. That is a legitimate finding, and it is better to reach it before you sign.
Questions worth asking a supplier
Ask these as an intermediary, not as a trader, and ask for a demonstration rather than an answer.
- How do you keep client data separated, and can you show me the boundary rather than describe it?
- How does an operator switch between clients, and how many clicks does a routine repeat movement take?
- Which declaration types are supported today, in production, for agent accounts specifically?
- How does the system handle a client whose UKIMS position changes?
- What happens on a rejection, and who is notified?
- Can I see per-client volumes, statuses and outstanding actions without exporting anything?
- What does onboarding a new client involve, in hours?
- What are the retention arrangements, and can I extract everything for one client if they leave?
A fuller set of evaluation criteria, applicable whether or not you file for others, is in evaluating declaration software.
What software cannot change
Three things stay put whatever you buy, and any supplier who implies otherwise is worth treating carefully.
- Accountability. Accuracy and timely submission remain the responsibility of the party the declaration belongs to. Filing on someone’s behalf does not transfer that.
- The commercial agreement. TSS requires a commercial agreement between you and the trader setting out the terms of representation and payment. That is a contract question, not a systems question.
- De minimis visibility. As an agent you cannot see how much of a client’s de minimis state aid allowance remains. The trader has to tell you, and TSS accepts no responsibility if the limit is breached.
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