IID Version 5.01 Goes Live February 2027, Old Version Retires Nine Months Later

What Changed

CBSA IT confirmed the rollout schedule for Integrated Import Declaration version 5.01. Certification lab access for client testing is targeted for the end of January 2027, production implementation in February 2027, and the anticipated retirement date for IID v4.02 is November 2027. That last date is marked subject to change, but the pattern on past CBSA version retirements is that once they publish a target, it usually holds or moves earlier, not later.

The nine-month gap between production launch and forced retirement is shorter than the last major IID version migration. If you transmit IID data through EDI, either directly or through a software provider, that timeline matters. November 2027 is the hard stop. Anything still running v4.02 after that date will start bouncing.

Who Files IID and Why This Affects Them

Integrated Import Declaration is CBSA’s Single Window implementation. It combines the customs import declaration with Canadian Food Inspection Agency requirements in one EDI transmission. If you import regulated food, plant, or animal products, your broker files IID instead of a standalone CBSA release message and a separate CFIA notification. The data goes to both agencies at once, and CBSA holds the release until CFIA clears.

Most small and mid-market importers never touch IID directly. Their customs broker handles the EDI filing through the broker’s own software. But three groups do care about version updates:

1. Importers with in-house customs systems that file IID on their own behalf (usually large food importers or NRI configurations where the foreign supplier uses a Canadian software provider).
2. Customs brokers and freight forwarders whose platforms need to support the new business rules in Addendum v1.7.
3. Third-party logistics and compliance software vendors whose clients depend on them to stay current.

If you fall into any of those buckets, the February 2027 production date is your go-live target, and the November 2027 retirement is your drop-dead date. CBSA does not run dual versions indefinitely. When v4.02 retires, transmissions on that version will reject. You either migrate or stop importing.

The Certification Lab Window and What It Means

CBSA’s certification lab is the test environment where software providers and large importers validate their EDI transactions before pushing to production. Access by the end of January 2027 means you have about one month of testing time before the February production launch. That is tight if your software vendor has not already started development work on the v1.7 business rules.

The smart move: if you rely on a commercial platform (broker software, TMS, ERP customs module), ask your vendor now whether they are on the IID v5.01 development roadmap and what their internal timeline looks like. If the answer is vague or they are waiting for CBSA to finalize the spec, you have a problem. The spec is final enough that CBSA is building it in their internal test environment right now. A vendor that has not started is going to be scrambling in Q4 2026.

For brokers filing on behalf of clients, this is usually transparent. The broker’s software gets updated, the broker tests in the cert lab, and the client’s shipments continue clearing without interruption. But if you are filing IID yourself, either as an importer of record with your own software or as an NRI working through a third-party service, you own the migration timeline. Budget the testing window now, because January 2027 is fourteen months away and enterprise software release cycles are not fast.

What Changed in Addendum v1.7

CBSA has not published the full v1.7 business rules yet, but the pattern on past IID updates is that addendums introduce new data validations, tighter edits on CFIA product codes, and updated tariff treatment flags. The CBSA trade automation programs page will eventually post the technical specs, but those usually land close to the certification lab opening, not months in advance.

The risk is not that v1.7 introduces massive new requirements. The risk is that it tightens validation on fields your current EDI map is leaving blank or filling with default values that technically violate the schema but v4.02 was not rejecting. When CBSA turns on stricter edits in the new version, transmissions that were sailing through start bouncing for missing or malformed data. If that happens in production, your shipments sit at the border until you fix the file and retransmit.

This is why the certification lab window matters. You need time to submit test files, catch the new validation errors, fix your mapping logic, and retest before the production cutover. One month is not a lot of runway if your software has technical debt in the IID module.

The November 2027 Retirement Date Is the Real Deadline

February 2027 is the production launch. November 2027 is the cliff. CBSA will accept v4.02 and v5.01 transmissions in parallel for nine months, then v4.02 goes dark. If you are still on the old version in November 2027, your imports stop clearing. CBSA will not grant extensions. The agency has been running dual PARS versions and dual ACI versions in the past, and the retirement dates hold.

Nine months sounds like a long time until you factor in enterprise change control, testing cycles, user acceptance, and the fact that Q4 is peak season for most importers. A production cutover in October 2027 to beat the November deadline means your testing and UAT work has to finish in Q3 2027. That puts your certification lab access request in Q2 2027, which is only a few months after the lab opens. The window is tighter than it looks.

If your software vendor is not on the v5.01 roadmap yet, or if they are deprioritizing it because they think nine months is plenty of time, you should be asking pointed questions. Software providers that wait until June 2027 to start testing are going to be filing for emergency extensions in October, and CBSA does not hand those out.

What to Do Now

If you file IID through a customs broker and have no in-house software, this is mostly their problem, not yours. Ask your broker whether they are tracking the v5.01 timeline and what their migration plan looks like. If the answer is confident and specific, you are fine. If the answer is vague, that is a yellow flag.

If you file IID yourself, or you work with a third-party software provider, put the November 2027 retirement date in your project tracker now. Confirm your vendor is building to the v1.7 spec, confirm they have a certification lab access plan, and confirm they have a production cutover date that is earlier than November 2027. Do not assume the timeline will slip. It will not.

For importers bringing in CFIA-regulated goods through the Port of Montreal, the IID version update does not change your drayage or sufferance warehouse workflows, but it does change the system your broker uses to request release. If your broker’s IID filing bounces because they are still on v4.02 after the retirement date, your container sits on port until they fix it. That is detention and dwell time you are paying for while the filing gets sorted. The cost is not in the version update itself. The cost is in the delay if the update does not happen on time.

We run IID filings daily for food importers, mostly on the CFIA side for fresh and frozen product. The version update is on our internal roadmap, and we will be in the certification lab in Q1 2027. If your current provider is not saying the same thing, or if you are filing on your own and need a second set of eyes on your EDI map, get in touch.

Source: CSCB