What CARM supports

• Importer registration and business account setup.
• Delegation of authority between importer and customs broker.
• Viewing account balances, transaction history, statements, and invoices.
• Managing duties and taxes on commercial goods imported into Canada.
• Supporting Release Prior to Payment and financial security processes.

Operational habit

• Confirm the importer has registered and delegated authority where required.
• Do not assume broker access exists without confirming delegation.
• Escalate account, access, payment, or statement issues before they delay clearance.

What EDI supports

• Advance commercial information and pre-arrival cargo data.
• Release documents for imported goods.
• Integrated Import Declaration and PARS release requests.
• Transmission into ACROSS where applicable.
• Electronic notices and release-related communications from CBSA.

Operational habit

• Understand whether a process is handled through system transmission, portal access, or internal follow-up.
• Watch for CBSA notices, rejection messages, release decisions, or system outage impacts.
• Do not resubmit data repeatedly during outage or delay situations unless directed by the correct process.

Key terms

• ACROSS: CBSA system connected to electronic release request processing.
• PARS: Pre-Arrival Review System release document used for pre-arrival clearance workflows.
• IID: Integrated Import Declaration for submitting information that can include CBSA and participating government agency requirements.
• RNS: Release Notification System used for release decisions and related notices.

Operational habit

• Confirm the release pathway before assuming which system action is required.
• Check rejection messages and missing data before escalating.
• Confirm importer, carrier, cargo, invoice, PGA, and classification details before transmission.

What it supports

• Visual Importer access and system navigation.
• PARS setup and shipment manager workflows.
• Shipment header, invoice, and line item entry.
• ACROSS transmission and common reject review.
• Trade partner setup and release manager workflows.

Training habit

• Use the full MSR / Visual Importer page for step-by-step training.
• Review the MSR Manual before troubleshooting complex system issues.
• Use the video modules and quizzes where available.

Common document types

• Power of Attorney and General Agency Agreement documents.
• Credit applications and bond applications.
• CUSMA / USMCA certification forms.
• Certificate of origin templates.
• CARM, ACElynk, and client instruction documents where applicable.

Operational habit

• Never delete a document link when rebuilding a page.
• If a document appears outdated or broken, keep it visible until a replacement is confirmed.
• Use the Client Toolkit as the main document routing page when employees need a form.

When this comes up

• Importer needs to register in the CARM Client Portal.
• Importer has not delegated authority to Frontier.
• Importer has account balance, statement, payment, or financial security questions.
• Importer does not understand why CARM affects commercial imports.

How to position it

• Use CARM as a compliance and account management conversation, not just a login issue.
• Keep explanations practical and tied to clearance, payment, authority, and recordkeeping.
• Escalate account-specific CBSA issues instead of guessing.

Check before action

• Importer and business number details.
• Carrier, cargo control, shipment, and invoice information.
• Tariff classification, valuation, origin, and duty treatment.
• PGA indicators, permits, certificates, or regulated goods concerns.
• Supporting documents and client instructions.
• System messages, release status, rejects, and escalation notes.

When to escalate

• CARM access or delegation does not match expected account setup.
• EDI messages, release notices, or transmission results are delayed or unclear.
• System outage notices affect timing or shipment status.
• A rejection or system error cannot be resolved with available documentation.

Support habit

• Check official CBSA system information before assuming a local data issue.
• Document the issue, shipment, time, system, and any message text.
• Do not repeatedly resubmit during known system delays unless instructed by the proper procedure.