Feronix ATLAS Customer Portal

Summary Declaration (SumA)

Generates a CUSPRL/SCPRLK file for the Summary Declaration for temporary storage — validated against the official XSD.

Customs clearance by Feronix. Customs clearance is handled under Feronix's own EORI and deferment accounts. You as a customer do not need your own customs authorization, EORI registration, or deferment account. Feronix acts as declarant and representative.

When you need a SumA

The Summary Declaration (SumA) is the advance declaration of a goods import for temporary storage. It is mandatory when a shipment enters the customs territory and (yet) no complete import declaration is available. Feronix generates the appropriate SCPRLK file according to EDI-IHB ATLAS 10.1.17, message SCPRLK, version K.1.5.

What SumA is not

  • SumA is not an IMPOST — it does not replace an import declaration
  • SumA is not an ENS/ICS2 — it does not replace an entry summary declaration
  • SumA is not an ASumA — it does not replace a detailed SumA

How to create a SumA

  1. Open SumA — open "SumA XML" in the client portal.
  2. Select EORI and customs office — the EORI of Feronix and the customs office configured by Feronix are used here, not the customer's. Select an EORI and a customs office configured for it.
  3. Enter header data — LRN, declaration type, presentation, parties, transport and previous document. Delivery and package data can be adopted.
  4. Create goods items — at least one item, add more dynamically.
  5. Preview or download — successful exports are automatically archived in the DMS.

Supported are presentation, transport, holder, previous document, transport document, container and item details.

Mandatory fields per goods item

  • Goods description
  • Gross mass (gross weight)
  • Country of dispatch
  • Type of packaging
  • Number of pieces

What Feronix checks automatically

  • EORI and establishment (those of Feronix as declarant)
  • Customs office assignment
  • BIN (Participant Identification Number)
  • LRN and date/field formats
  • Previous document dependencies
  • Entry SumA MRN with item
  • Transport document type with number

Feronix then validates against the official SCPRLK.xsd. Errors return HTTP 422 with SUMA_XML_INVALID.

What you receive

  • SCPRLK file according to EDI-IHB ATLAS 10.1.17, version K.1.5
  • Validation report with XML and schema checksum, XSD version and all code lists referenced by the schema
  • Automatic DMS archiving of the export

Transmission to ATLAS

The SumA is transmitted automatically via the ATLAS FTAM interface. Available functions include draft, correction, submission, status history, SCPRLK, allocation, consolidation, amendments, re-export/dispatch reference as well as FTAM inbox, XSD validation, assignment and quarantine.

Additionally, the SCPRLK XML file can be generated and downloaded. It is intended for manual upload to ATLAS or for transfer to a compatible ATLAS participant software. File generation does not send anything automatically to ATLAS.

Also available via API

POST /customer/suma/declarations       # Create SumA declaration
POST /customer/suma/xml                 # Export SumA XML
POST /customer/customs-xml/validate     # Validate XML against original XSD
→ Transit and T1 Open account