TradVolt › Guides › CN→AU Corridor › r14 EMS User Access — Maintenance & Process
Verdict: Run the periodic access review on a 90-day (quarterly) cadence, with the first review scheduled 90 days after activation. Trigger an RFQ handover to TradVolt only on a corridor-scope change (new goods line, new entity, or regulator change) — not on routine maintenance cycles. Equipment scope: EMS user-account governance only (no CATL / BYD / Sungrow / Huawei / LONGi / Jinko / Trina / Growatt hardware in scope for this guide). Horizon: between onboarding and the next corridor revision. Evidence date: 2026-09-22. Limitation: SLA windows, duty rates, and EMS operator fees in this guide are PENDING pending lookup against the ABF Integrated Cargo System (ICS) operator schedule and the GACC Customs Tariff.
| Decision point | Value |
|---|---|
| Periodic review cadence | Every 90 days (quarterly); first review at D+90 from activation |
| RFQ handover trigger | Event-driven: corridor-scope change only (new goods line / new entity / regulator change) |
| Evidence archive window | Within 5 business days of each change (model assumption pending GACC record-retention guidance) |
| Equipment scope | EMS user accounts only; no hardware models in scope for this maintenance guide |
| Primary RFQ anchor | https://tradvolt.com/rfq/ (site path only) |
Scope: the recurring access-maintenance workflow for trade operators holding an Electronic Manifest System (EMS) account on the China to Australia corridor. This page covers access request intake, role verification, periodic review, evidence retention, and the handover path to a TradVolt RFQ.
Audience: trade lane owners, compliance leads, and EMS account custodians at exporters, freight forwarders, and customs brokers servicing the corridor.
Read first: r14 is a maintenance revision; it does not redefine corridor policy. If you need the corridor introduction, start at the CN→AU landing guide. Numeric checkpoints here are indicative and marked PENDING where the figure has not been sourced from a primary authority.
This guide defines the recurring maintenance process that keeps an EMS user access record on the CN→AU corridor accurate, evidenced, and auditable between the initial onboarding milestone and the next major corridor revision. It addresses who may hold an EMS account, how a change is requested, how the change is verified, and how evidence is retained.
The process covers the operator-side governance only. The underlying statutory framework for the corridor is set by the Australian Border Force (ABF), which operates the Integrated Cargo System (ICS) — the platform on which the Electronic Manifest System (EMS) module runs for inbound and outbound manifests — and by the General Administration of Customs of the People's Republic of China (GACC), which operates the PRC-side manifest counterpart. This guide does not restate their rules and should be read alongside the regulator's own published material (abf.gov.au; customs.gov.cn).
The table below defines the ordered steps for maintaining an EMS user access record on the ABF Integrated Cargo System (ICS). One named owner is assigned per step; the owner is accountable for the done-when state and for the output document produced.
| Step # | Action | Owner | Input doc | Output doc | Done-when |
|---|---|---|---|---|---|
| 1 | Receive access change request from trade lane owner | Access custodian | EMS-Access-Change-Request form | Maintenance register entry (new row) | Request is logged with date, requester, corridor tag CN-AU-r14, and ticket ID |
| 2 | Verify requested role against r14 role matrix | Compliance lead | Maintenance register entry; r14 role matrix | Verification note | Role is mapped to a corridor-approved role and trade lane matches the user's entity |
| 3 | Raise ABF ICS / EMS operator ticket with evidence pack | Access custodian | Verification note; identity attestation | EMS ticket reference | EMS operator ticket is open with all mandatory attachments accepted |
| 4 | Track ticket against ABF ICS SLA window | Access custodian | EMS ticket reference | SLA tracking note | Confirmation ID from EMS operator is captured in the maintenance register |
| 5 | Provision EMS account and run first-login test against ABF ICS | EMS operator liaison | Confirmation ID | Activation record | First-login test passes for the named corridor test case and timestamp is recorded |
| 6 | Schedule the next periodic access review (90-day cadence) | Compliance lead | Activation record | Review calendar entry | Calendar entry exists with cadence from §3 and named reviewer assigned |
| 7 | Run the quarterly access review | Compliance lead | Review calendar entry; EMS account list | Quarterly review report | Findings are recorded (no change, modify, revoke) for every active account |
| 8 | Apply review decision (retain / modify / revoke) | EMS operator liaison | Quarterly review report | Maintenance register update | EMS state matches the review decision and change reference is filed |
| 9 | Archive the evidence pack | Access custodian | All step outputs | Archived evidence bundle in evidence vault | Bundle is hashed, dated, and cross-referenced from the trade lane register |
| 10 | Trigger RFQ handover on corridor-scope change | Trade lane owner | Archived evidence bundle | RFQ submission via TradVolt | RFQ is submitted through the r14 RFQ anchor and evidence is attached |
EMS operator identity: the EMS module referenced here is the Electronic Manifest System component of the ABF Integrated Cargo System (ICS), operated by the Australian Border Force. No third-party EMS vendor is named in this guide; the regulator-published ABF ICS operator schedule is the canonical SLA source (currently PENDING against abf.gov.au).
Every maintenance cycle must be able to produce the following files. Tick each item before closing the cycle.
EMS-Access-Change-Request-v3.pdf — the original request formr14-EMS-Role-Matrix.xlsx — the r14 role matrix referenceMaintenance-Register-CN-AU.xlsx — the central maintenance registerEMS-Ticket-Evidence-Pack.zip — the EMS operator evidence bundleIdentity-Attestation-CN-AU.pdf — identity attestation for the named userSLA-Tracking-Note.md — the SLA tracking note from Step 4Activation-Record-CN-AU.csv — the activation record from Step 5Review-Calendar-CN-AU.ics — the review calendar fileQuarterly-Review-Report-Qn.pdf — the quarterly review reportEvidence-Vault-Index-CN-AU.json — the evidence vault index entryRFQ-Handover-Cover-CN-AU.pdf — the RFQ handover cover sheetThe timeline below defines indicative windows for each phase. Durations are indicative and must be reconciled with the ABF ICS operator schedule (see abf.gov.au).
| Phase | Day offset | Indicative window | Source basis |
|---|---|---|---|
| Intake & register | D0 | PENDING — ABF ICS operator schedule | abf.gov.au (ABF ICS operator schedule — PENDING lookup) |
| Role verification | D0–D+2 | PENDING | Internal compliance window (model assumption) |
| EMS ticket raising | D+2–D+3 | PENDING | ABF ICS operator schedule |
| EMS operator confirmation | D+3–D+10 | PENDING | ABF ICS operator SLA |
| Provisioning & first-login test | D+10–D+12 | PENDING | Internal provisioning window (model assumption) |
| First periodic review | D+12 + 90 days | Quarterly | r14 review cadence (model assumption) |
| Subsequent periodic reviews | Every 90 days | Quarterly | r14 review cadence (model assumption) |
| Evidence archive | Within 5 business days of each change | PENDING | Model assumption; no primary regulator record-retention rule identified for this workflow |
| RFQ handover (on scope change) | As triggered | Event-driven | tradvolt.com/rfq/ |
The figures below are slots only and are explicitly indicative. No hard price is provided in this guide. The ABF ICS does not publish a fee schedule for EMS user-access changes in publicly available material; treat all cost rows as PENDING.
| Slot | Indicative range | Status | Source basis |
|---|---|---|---|
| Internal custodian effort per change | PENDING | Indicative | Internal time-recording basis (model assumption) |
| ABF ICS / EMS operator fee per ticket | PENDING | Indicative | abf.gov.au ICS fee schedule — PENDING |
| Compliance lead effort per quarterly review | PENDING | Indicative | Internal time-recording basis (model assumption) |
| Evidence vault storage per cycle | PENDING | Indicative | Vault vendor schedule (model assumption) |
| External audit support (if invoked) | PENDING | Indicative | Audit firm proposal basis (model assumption) |
Disclaimer: TradVolt does not publish hard prices for third-party services. Confirm every figure in this table against the named source before use.
This guide is a process guide and does not by itself assign a tariff classification. If the maintenance cycle is triggered by a change in the goods profile on the corridor, use the block below as a starting point only, and reconcile against the named customs authorities.
| Field | Value | Source |
|---|---|---|
| AU import lookup source | Australian Border Force — Working Tariff (home) | https://www.abf.gov.au/ |
| PRC export lookup source | General Administration of Customs of the PRC — Customs Tariff | https://www.customs.gov.cn/ |
| Duty rate (indicative) | PENDING | AU Working Tariff (Home — do not cite removed deep /tariff-classification URLs) |
| GST / VAT treatment | PENDING | ABF / GACC (PENDING lookup) |
| Concession screen check | PENDING | ABF Concession Instruments (PENDING lookup) |
| Free Trade Agreement path | China–Australia FTA (ChAFTA) — verify current status | DFAT ChAFTA page (page lives under dfat.gov.au/trade) |
Disclaimer: HS classification and duty outcomes are governed by the customs authority of import. The rates above are placeholders pending lookup against the named sources. Do not rely on this block for clearance decisions. Note: ABF deep /tariff-classification URLs moved during 2024-25; cite the ABF home page and run the live Working Tariff search rather than a fixed deep path.
This guide is a process guide and does not itself certify equipment. If the maintenance cycle intersects with a hardware change on the corridor (e.g., a new battery, PV, or EV-charging SKU), the following adjacent standards apply for reference; always confirm the exact edition at the RFQ stage.
| Standard | Title | Source |
|---|---|---|
| IEC 61851-1:2017 | Electric vehicle conductive charging system — Part 1: General requirements | webstore.iec.ch/en/publication/33644 |
| UL 1973 | Batteries for Use in Stationary and Motive Auxiliary Power Applications | shopulstandards.com — UL 1973 |
| UL 61730-1 | Photovoltaic (PV) Module Safety Qualification — Part 1 | shopulstandards.com — UL 61730-1 |
| UN 38.3 (UN ST/SG/AC.10/11/Rev.7) | Lithium battery test provisions within the UN Manual of Tests and Criteria | unece.org — UN Manual of Tests and Criteria |
| Regulation (EU) 2023/1542 | EU Battery Regulation | eur-lex.europa.eu — Reg (EU) 2023/1542 |
| IATA DGR | IATA Dangerous Goods Regulations (cargo) | iata.org — DGR |
| ICC Incoterms 2020 | Incoterms 2020 rules | iccwbo.org — Incoterms 2020 |
| ISPM 15 | Wood packaging (international standards for phytosanitary measures) | ippc.int — ISPMs list |
| OCPP | Open Charge Point Protocol (EV charging) | openchargealliance.org (home; deep protocol URLs unguessable — cite home + protocol name/version in text) |
No specific CATL, BYD, EVE, Sungrow, Huawei, LONGi, Jinko, Trina, or Growatt model is named in this guide, because no hardware model is in scope. If a model is later added to the corridor's goods profile, name the exact model from the OEM's product page (e.g. catl.com/en/ess/, sungrowpower.com/en, solar.huawei.com/en, longi.com/en/, jinkosolar.com/en/, trinasolar.com/us-en, growatt.com, evebattery.com/en) and confirm the OEM manual revision at RFQ.
r14 is the corridor-specific revision tag for this maintenance guide. It indicates the fourteenth revision of the CN→AU EMS user-access maintenance process. Major policy is unchanged from r13; r14 adds explicit evidence-retention and RFQ-handover steps.
Each step in §2 has exactly one named owner. The owner is accountable for the done-when state and for the output document. If a step requires multiple participants, the additional participants are contributors, not co-owners.
The default cadence is quarterly (every 90 days), with the first review scheduled ninety days after activation. If a regulator or your internal policy requires a shorter cadence, override Step 6 accordingly and note the override in the maintenance register. This cadence is a model assumption; no ABF ICS-published quarterly-review rule was located in public material at the evidence date.
Trigger the RFQ handover when the corridor scope changes — for example, a new goods line, a new entity on the trade lane, or a regulator change. Do not trigger on a routine maintenance cycle. Use the primary RFQ anchor at the top of this page and attach the latest archived evidence bundle.
No. This guide is an internal maintenance process. Statutory obligations sit with the Australian Border Force (abf.gov.au) and the General Administration of Customs of the People's Republic of China (customs.gov.cn); consult their published material before acting on any clause here.
If at any point in this process you identify a gap that requires external support — an access audit, a role-matrix rebuild, or a regulator-readiness check — raise it through the primary RFQ anchor below. Attach the archived evidence bundle so TradVolt can scope from your actual state, not from a generic brief.