AVS Is Your First Line of Defence Against CAD Rejections

The cost of a rejected CAD isn’t just the resubmission time

You file a Commercial Accounting Declaration at 2pm, expect a clean release, and instead get an EDI reject because someone fat-fingered an AIRS code or used a deprecated commodity value. Now you’re scrambling to fix it, resubmit, and explain to your importer why their container is sitting at the terminal racking up per-diem. This is where AVS lives: the unglamorous validation layer that catches bad AIRS coding before CBSA does.

The Automated Import Reference System Verification Service isn’t new, but if you’re not baking it into your workflow — especially post-CARM — you’re leaving rejections on the table that didn’t need to happen. AVS validates multiple AIRS commodity codes in a single request, in minutes, against the live CBSA reference file. It’s a pre-flight check. You send your codes, it tells you what’s wrong, you fix it before the CAD goes out the door.

What actually breaks in AIRS coding

AIRS codes change. Tariff items get split, SIMAs get amended, NTRs shift, and suddenly the commodity code you’ve been using for six months is invalid. The rejection notice doesn’t always tell you why — just that line 14 failed validation. Now you’re digging through the current CBSA tariff trying to figure out if it’s the HS classification, the origin qualifier, or something in the SIMA reference that broke.

Common culprits:

• Stale SIMA codes. If you’re importing subject goods and the case number or NQ reference changed, your AIRS code is toast.
• Wrong origin syntax. CUSMA origin requires specific qualifiers that differ from CETA or CPTPP. If your system is pulling the wrong one, AVS will flag it.
• Deprecated tariff treatment codes. GPT, LDCT, UST — these shift when FTAs are amended. Your internal database might be behind.
• Missing or invalid units of measure. Some AIRS entries require specific UOM declarations. If you’re off by one character, the CAD bounces.

AVS doesn’t fix your classification — that’s still on you or your compliance team — but it does confirm that the code you’re about to file is structurally valid and current.

Where AVS fits in the CARM-era filing workflow

Under CARM, the CAD replaced the B3. Same fundamental purpose, different plumbing. The CAD still requires AIRS coding for every line, and CBSA’s tolerance for sloppy submissions hasn’t improved. If anything, the rejection feedback loop is slower because the CARM Client Portal doesn’t surface granular error detail the way some EDI systems used to.

AVS sits between your internal system and the CBSA gateway. If you’re filing via service bureau or your own EDI connection, you run AVS before transmission. It’s a batch process: you send a file with 50 line items, AVS returns validation status on all 50. If three are bad, you fix those three and resubmit the validation request. Once everything clears, you file the CAD.

This matters most when you’re dealing with high-volume, high-SKU shipments — apparel, electronics, auto parts. One rejected CAD on a 40-line entry means the whole thing sits until you fix it. The cost isn’t just the delay; it’s the terminal storage, the importer’s production line waiting on parts, and the phone call you have to make explaining why a typo in line 22 held up the entire release.

The operational reality: AVS is only as good as your data hygiene

AVS validates structure and currency. It does not validate correctness. If you classify a product as 8517.62.00.90 when it should be 8517.62.00.10, and both are valid AIRS codes, AVS will pass it. CBSA will catch it on post-release verification, and you’ll be dealing with a B2 amendment, potential penalties, and a very annoyed importer.

This is why AVS is not a substitute for real classification work or origin verification. It’s a gatekeeper, not a decision-maker. If your team is relying on AVS to confirm that the tariff treatment is correct, you’re misunderstanding the tool. AVS confirms that the code you chose is valid in CBSA’s current reference system. Whether you chose the right code in the first place is a different question.

When AVS saves you from yourself

The real value shows up in two scenarios:

1. Mass updates after a tariff amendment. When the Customs Tariff or a D-memo changes and you need to update 200 SKUs in your internal database, running AVS on the entire batch before you start filing live entries catches the ones you got wrong. You fix them once, in bulk, instead of one rejected CAD at a time over three weeks.

2. New products from a supplier you don’t know well. Importer sends you a commercial invoice with their internal product codes and a vague description. You classify, build the AIRS code, run AVS. If it bounces, you know immediately that something in your coding logic is off — maybe the NTR doesn’t align with the HS, maybe the origin qualifier is malformed. You fix it before the goods hit the port.

If you’re working with mixed origin cargo — CUSMA, CETA, MFN, CPTPP all in one shipment — AVS becomes non-negotiable. The permutations get messy fast, and one bad origin code on line 8 can hold up an otherwise clean entry.

Integration and access

AVS is available through CBSA’s EDI Gateway. If you’re already submitting CADs via EDI, your service bureau or software provider should have AVS built into the workflow. If they don’t, ask why. If you’re filing through the CARM Client Portal manually, you don’t get AVS — it’s an EDI-only tool. That’s another reason why high-volume importers shouldn’t be filing through the portal.

Some brokerage systems run AVS automatically on every entry before transmission. Others require manual triggering. Know which model you’re using, because if your team thinks it’s automatic and it’s not, you’re flying blind.

The bottom line

AVS is not exciting. It doesn’t save you money on duty, it doesn’t speed up CBSA processing, and it won’t fix a bad classification. But it does prevent a specific, recurring operational failure: filing a CAD with invalid AIRS coding, getting a rejection, and losing a day or two while you figure out what broke. That’s a failure mode you can eliminate entirely by running validation before submission.

If your team is still seeing regular EDI rejections due to AIRS errors, you either don’t have AVS in your workflow, or you’re ignoring what it’s telling you. Both are fixable.

If you’re not sure whether your current EDI setup includes AVS or how to integrate it into your CARM filing process, get in touch. We run this check on every entry, and we’re happy to walk through how it plugs into your operation.

Source: CSCB