CFIA NISC Paper-Package Submissions: What Changed, What Brokers Should Watch

NISC Is Not a Fallback Email Address

CFIA’s National Import Service Centre has put out fresh guidance on paper-package submissions for food, feed, and plant imports that need documentation review. The short version: if you’re emailing paper instead of using AIRS or ePermitting, CFIA expects Form 5272 filled out correctly, a valid transaction code typed on the form, and a working contact email that won’t bounce. That sounds basic, but the number of rejected packages and follow-up requests climbing out of NISC suggests brokers and importers are treating the paper path as a catch-all when electronic filing breaks or when they’re not sure which system applies.

Paper submissions go to [email protected]. CFIA wants Form 5272 current version, every field completed, transaction code clearly printed or typed. If the transaction code is missing or illegible, NISC kicks it back. If the email address on file bounces, the response sits in limbo and your shipment sits in sufferance.

The transaction code is the CARM release line identifier that ties the paper request to the CAD. Without it, NISC has no clean way to match the documentation package to the release hold, and the clock keeps running. This is not a soft requirement.

Why Paper Packages Are Still a Thing

Most routine CFIA permits and certificates flow through AIRS (Automated Import Reference System) or the newer ePermitting portal. Paper is the exception, not the rule. You end up on the paper path when:

• The commodity or origin combination isn’t supported in AIRS yet.
• The importer hasn’t registered for ePermitting and the shipment is already at the border.
• CFIA flagged the entry for manual documentation review after automated screening.
• You’re dealing with a residue or contaminant issue that requires lab certificates or third-party test results not captured in standard permit fields.

In every case, paper means delay. NISC processes submissions in order received, and turnaround depends on workload and completeness. A clean package with all attachments, correct transaction code, and legible contact info usually clears within one to two business days. An incomplete package or one with a bounce-back email address can add three to five days, plus whatever time the importer or broker burns chasing status.

What’s Driving the New Guidance

CFIA didn’t publish this out of nowhere. The October 2024 CARM launch moved all commercial releases onto the CAD structure and the CARM Client Portal replaced the old CBSA eManifest release workflow. Transaction codes are now the primary key for every release line, and OGD holds including CFIA now tie back to that code instead of cargo control numbers alone.

Brokers who were used to referencing CCN and B3 line numbers in CFIA correspondence had to retool their submission templates. Some didn’t update fast enough. Some importers are still handing brokers old email templates with pre-CARM references. CFIA is tightening the process because the volume of incomplete or mis-referenced packages spiked in Q4 2024 and hasn’t come down.

The other issue is email hygiene. Corporate spam filters have gotten aggressive, and if the contact email on Form 5272 is a generic catchall or an auto-forwarding alias that fails SPF/DKIM checks, CFIA’s reply ends up in quarantine. The importer doesn’t know CFIA responded, the broker doesn’t know the package cleared, and the shipment sits on hold while everyone assumes someone else dropped the ball.

What Brokers Should Do Before Submission

Double-check the transaction code on the CAD release line before you fill out Form 5272. The code is visible in the CARM Client Portal under the release summary. Type it on the form; don’t rely on a scanned handwritten copy. NISC staff have rejected packages where the transaction code was present but illegible.

Use a direct contact email, not a generic info@ or customs@ alias. If the importer’s compliance team has a dedicated CFIA contact, use that. If you’re the broker of record and you’re handling the submission, use your own work email and copy the importer. Make sure your mail server isn’t on any public blocklists (check MXToolbox if you’re not sure).

Attach all supporting documents referenced in the form. If you’re claiming compliance with a D-memo or citing a CFIA guidance document, include the relevant pages. If lab results or certificates of analysis are required, include them as separate PDFs with clear filenames. NISC won’t chase you for missing attachments; they’ll reject the package and ask you to resubmit complete.

Keep a local copy of the entire submission package including the sent-mail timestamp. If NISC doesn’t respond within 48 hours, follow up. Don’t assume it’s in the queue. Submissions do get lost, and the sooner you catch it the less warehouse time you burn.

When to Escalate

If you submitted a complete package with correct transaction code and working email, and you haven’t heard back in three business days, call the NISC general line (1-800-835-4486) and reference the transaction code and submission timestamp. Have the cargo control number and importer BN ready. CFIA’s phone queue is long, but it’s faster than waiting another two days hoping the email shows up.

If the shipment is time-sensitive (short shelf life, production line dependency, high demurrage or drayage detention risk), flag that in the subject line of the submission email and in the “additional information” field on Form 5272. NISC doesn’t guarantee expedited processing, but they do triage based on risk and perishability.

The Bigger CARM Pattern

This NISC guidance is a small piece of a larger shift. CARM replaced a lot of informal workarounds and ad hoc email correspondence with structured data fields and mandatory identifiers. Transaction codes, CARM client IDs, BN15 references, portal-based document upload instead of email attachments. It’s cleaner in theory, but the transition punished anyone who didn’t update templates, retrain staff, or audit their email infrastructure.

The brokers and importers who adapted quickly are seeing fewer holds and faster OGD releases. The ones still copying and pasting pre-CARM email bodies are the ones getting bounce-backs and rejection notices from NISC, ISED, Health Canada, and every other department that moved to portal-based submission.

If your compliance process still relies on email templates written in 2022, this is the year to rewrite them. CFIA’s guidance is narrow, but the problem it’s solving is not.

If you’re filing CADs and still getting NISC rejections after following the checklist, that’s operator error or a gap in your import registration. Get in touch and we’ll walk the package before it goes out.

Source: CSCB