Skip to Content
User GuideRejection Analysis

Rejection Analysis

The Rejection Analysis dashboard provides comprehensive insights into declaration rejections, helping you identify patterns, reduce rejection rates, and improve compliance.

Overview

Access the Rejection Analysis dashboard via SettingsRejection Analysis.

What You Can Analyze

  • Rejection rates over time
  • Most common error codes
  • Fields frequently causing issues
  • Rejection breakdown by declaration type (import/export/transit)
  • Detailed error information for each rejection

Who Can Access

Rejection analysis is available to:

  • Administrators
  • Managers with declaration access

Dashboard Components

Summary Metrics

Four key performance indicators at the top of the dashboard:

Total Submissions

  • Number of declarations submitted to customs during the selected period
  • Includes accepted, released, and rejected declarations

Rejections

  • Total number of declarations rejected by customs
  • Shown as count and rejection rate percentage

Rejection Rate

  • Percentage of submitted declarations that were rejected
  • Industry benchmark is typically 2-5%

Unique Error Codes

  • Number of distinct error codes encountered
  • Helps identify how widespread issues are

Rejection Rate Over Time

Line or bar chart showing your rejection rate trend:

  • Daily view: Used for periods up to 90 days
  • Weekly view: Used for longer periods
  • Helps identify if rejection rates are improving or worsening
  • Spot patterns related to specific time periods or events

Top Error Codes

Bar chart displaying the most frequent error codes:

  • Error code (e.g., DMS343AA, TMSV0045)
  • Official error description from customs
  • Number of occurrences
  • Percentage of total rejections

Click on an error code to see all affected declarations and detailed information.

Rejections by Type

Pie chart showing rejection distribution:

  • Import declarations: Inward processing, customs warehousing
  • Export declarations: Outward declarations
  • Transit declarations: T1, T2 movements

Helps identify which declaration types need more attention.

Most Affected Fields

Bar chart showing which fields most frequently cause rejections:

  • Field name (e.g., consignee_country, document_code, procedure_code)
  • Number of times this field caused an error
  • Helps focus training and validation efforts

Recent Rejections

Table of the latest rejected declarations:

ColumnDescription
ReferenceDeclaration reference number
CustomerCustomer name
TypeDeclaration type (H1, B1, etc.)
DateWhen the rejection was received
ErrorsNumber of errors in the rejection
StatusPending or Resolved
ActionsView declaration details

Click View to open the full declaration and see rejection details.

Period Filters

Select different time periods to analyze:

  • Today: Rejections from today only
  • This Week: Monday to present
  • This Month: 1st of month to present
  • Last 30 Days: Rolling 30-day window
  • Last 60 Days: Rolling 60-day window
  • Last 90 Days: Rolling 90-day window
  • This Year: January 1st to present

The period filter applies to all dashboard components. Change the period to see how metrics evolve over time.

Error Code Drill-Down

Click on any error code in the Top Error Codes chart to see detailed information:

Error Code Modal

Displays:

  • Error Code: The official customs error code
  • Description: What the error means (from customs codebook)
  • Affected Declarations: List of all declarations with this error

Affected Declarations Table

ColumnDescription
ReferenceDeclaration reference
FieldWhich field caused the error
Original ValueThe incorrect value that was submitted
Line NumberDeclaration line number (or “Header”)
DateWhen the rejection occurred
ActionLink to view the full declaration

Click View to navigate to the declaration and correct the issue.

Exporting Data

Click the Export button to download rejection analysis data as CSV.

CSV Export Contents

The exported file includes:

  • Declaration Reference
  • Customer Name
  • Declaration Type
  • Rejection Date
  • Error Code
  • Error Description
  • Affected Field
  • Original Value
  • Line Number
  • XPath/Error Pointer
  • Resolution Status

Use this data for:

  • Sharing with customers or team members
  • Creating custom reports in Excel
  • Root cause analysis
  • Training materials
  • Compliance audits

Common Error Codes

Some frequently encountered error codes:

CodeCommon MeaningTypical Field
DMS343AAInvalid address or country codeConsignee country
TMSV0045Missing required documentDocument code
DMS548AAInvalid procedure codeProcedure code
DMS372AAMissing destination countryDestination country
DMS653AAInvalid government procedureAdditional procedure
DMS455AAInvalid country codeVarious country fields
DMS869ABDeclarant EORI not authorizedEORI number
DMS255ABTARIC code requiredCommodity code

The actual error descriptions from customs are shown in your dashboard. These examples are for general reference.

Reducing Rejection Rates

Best Practices

  1. Review Top Error Codes Regularly

    • Check the dashboard weekly
    • Focus on the most frequent errors first
    • Update templates and procedures to prevent recurrence
  2. Analyze Field Patterns

    • Identify which fields cause the most issues
    • Improve validation for problematic fields
    • Provide better guidance to declaration staff
  3. Track Trends

    • Monitor if rejection rates improve after process changes
    • Compare periods (this month vs. last month)
    • Set team goals for rejection rate reduction
  4. Customer-Specific Analysis

    • Filter by customer to identify specific training needs
    • Share relevant error data with customers
    • Work together on data quality improvements
  5. Type-Specific Focus

    • If import rejections are high, review import procedures
    • Check if certain declaration types need more training
    • Update checklists for high-risk declaration types

Using the Data for Improvement

For Training:

  • Export error data to create training materials
  • Focus training on most frequent error types
  • Use real examples from recent rejections

For Process Improvement:

  • Add validation rules for frequently incorrect fields
  • Update declaration templates with better defaults
  • Create checklists for error-prone declaration types

For Customer Communication:

  • Share rejection trends with customers
  • Provide guidance on common data issues
  • Collaborate on improving source data quality

API Access

Rejection analysis data is available via the REST API for integration with business intelligence tools or custom reporting.

See the API Reference for endpoint documentation.

Last updated on