1. Cross-border Trade SCM
  2. Features
  3. Customs declarations
Feature · Customs declarations

Customs declarations

Keep filing and release details with the purchase they concern.

OverviewSubmitted declarations
Cross-border Trade SCM · Customs declarations

Submitted declarations

Approval conditions

New
Entry numberParentHS codeFiled atDuty USDRevision
CD-91547PR-46390HSC-45910 Oct710360
CD-96376PR-79309HSC-31203 Oct800850
CD-53480PR-73302HSC-85604 Oct700770
CD-13062PR-58757HSC-97517 Oct960580
CD-69678PR-27641HSC-79421 Oct130510
6 of 6 records
HSC-459Customs declarations · CD-91547
ParentPR-46390
Filed at10 Oct
Duty USD710
Revision360
Example screen with sample data

What you can do

Open the declaration

A customs declaration links a purchase request and an organization. The Customs Coordinator enters the entry number, HS code, duty in USD and filing date, then follows the declaration status from Draft to Submitted. The purchase context supplies the supplier, order reference and goods description for the human filing review.

How the work is organized

  • Entry context. Link the declaration to the purchase and organization whose goods the entry covers.
  • Filing detail. Keep the entry number, HS code, duty in USD and filing date on the declaration.
  • Recorded outcome. Change the declaration status and decision date only after checking the external filing or release evidence.

Agree how the team receives entry numbers and classification decisions from its filing process. Record the HS code and duty on the declaration itself, so a reviewer can look at the value that was used. The decision date and revision help the coordinator identify the declaration that received a decision. The approved and rejected paths should have clear owners.

What to agree during setup

Agree which filing source supplies the entry number, classification, duty and outcome. Name the Customs Coordinator who records those values and the Trade Operations Lead who checks the purchase link. A declaration status records the team’s case state; it does not itself issue customs release. Decide where supporting external evidence belongs and who may see an attachment marked Shared.

Check the handoff on an actual case

Take a purchase with an order reference and one declared entry. Enter the HS code and duty, mark the declaration Submitted after filing, and ask the Customs Coordinator to compare the entry number with the external filing evidence. On approval, record the decision date; on rejection, leave a clear follow-up trail with the linked purchase evidence.

Ask the Customs Coordinator to open the actual filing result and compare its entry number with the declaration linked to the purchase. Record the date and approved or rejected status that correspond to the external outcome. If the entry is rejected, keep its evidence with the same purchase while the coordinator determines the next filing action.

Before moving an entry to Completed, compare the decision date with the filing record and reopen the linked purchase. The coordinator should be able to identify which entry belongs to which order without guessing from a supplier name alone.

What your team sees

  • Submitted declarations — Filed entries awaiting a decision, with classification and duty visible.
  • Declaration status board — Draft, submitted, approved and rejected entries grouped by status.

Follow the work through

See the first handoff and the next decision for a case-level rehearsal.

What it keeps track of

Data model
Customs declarations
Customs declarations supporting record verified customs release.
Purchase requests
Cross-border purchase demand with lifecycle, owner, counterparty and revision.
Organizations
Trading organizations that own cross-border purchase and customs operations.
Record attachments
Evidence files attached to a purchase request with visibility scope.

Who uses it

Permissions
Customs Coordinator
Maintains the declaration and records the decision.
Trade Operations Lead
Monitors the linked purchase.

Set up Cross-border Trade SCM your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started