Page tree
Skip to end of metadata
Go to start of metadata


VGM registration according to new SOLAS rule

On July 1, 2016, the new SOLAS rule for Verified Gross Mass (VGM) will come into force. Related messages will be generated and transmitted by Scope 8.2 within the B/L instructions. 

The VGM information will be transmitted via DAKOSY within the B/L. Messages to INTTRA, GT-Nexus and CargoSmart will be delivered in a first step also within B/L instructions. Automated transmission of the VGM will implemented soon. For the time being before the implementation of Scope 8.2, we recommend to create text modules so that the needed information can be filled in the remark field of the form.

The verified weight will be transmitted to the ocean carrier, and by default printed on the B/L instructions. On request, the information can be printed on your own documents. In this case, please contact our Scope support team to tune the adaption for your documents the way you wish.

Under Ocean > Export Shipments > "Goods" Tab, the VGM can be add by ticking the blue actionlink Register Verified Gross Mass (VGM)

Mandatory details to be prompted are:

  • VGM weight
  • Date
  • Person in charge = person responsible for correctness of data

↓ VGM registration according to new SOLAS rule

Specific selection from OAG-Flightschedule

By using the OAG-Fightschedule so far all flight connections were displayed. To get a clearer structure of flights, now it is possible to add transit ports.

In the OAG-Flightschedule overview the new field Transit was added.

By tright mouse click into the field Transit the menu Select Transit Point will be available.

A new window will display all possible transit ports for the selected flights. By clicking the button Add or Remove the desired transit ports can be defined.

The selected transit ports will be displayed in the Transit field. By clicking on the search button again, the overview will renewed. The user can add the flight and use it for the shipment.

↓ Specific selection from OAG-Flightschedule

Templates for RFS-Flights

In Scope Handling templates for Road Feeder Service have been added.

The layout for RFS-Flights can be created under Maintenance > Handling > RFS Templates.

All templates are displayed in the overview. By clicking the button New a new template can be created.

It is mandatory that the fields Airline, Flight, Departure, Destination and Customer are filled out. In addition the fields Message, Operates On and Message Recipients can be used.

A new RFS-Flight can be added under Handling > RFS-Flights. Alternatively, existing flights can be edited.

All available RFS-Flights are displayed in the overview. By clicking the button New, a new flight can be edited.

A new window will appear where the template can be selected. It is also possible to create a new RFS-Flight without a template.

In the following window all shipments and information can be added. Finally, the RFS-Cargo-Manifest can be printed and in case of interface connection data can be sent to SITA.

↓Templates for RFS-Flights

SITA improvements

The SITA-Application has been enhanced by features already implemented in other applications.

Under Air > SITA the user can open the SITA-Application.

The Advanced Filter has been added into the SITA Homeview to make the search more comfortable.

The message can be printed (PDF) directly from the homeview

or via the blue actionlink Print within the message field. All documents will be filed under the Documents tab.

↓ SITA improvements


New base in tariffs

Under Maintenance > Finance > Tariffs the new basis Container TEU is available. The basis can be used in new or in existing tariffs. For the job costing, Scope detects if a 20' or 40' Container is used.

The selection can be done under Basis by a dropdown menu. The basis is depending on the charge type.

For a 20' Container, Scope will calculate the tariff once for job costing and

for a 40' Container, Scope will calculate the tariffs twice. Scope will create only one line in the invoicing for both options.

↓ New base in tariffs

Extension for partner turnover report

The partner turnover report provides new reportfields e.g. Shipper Address, Consignee Address, UNLocode for destination etc. In addition, it is possible to add the Partner Turnover per Chargeline as criteria. To use this function, a layout must be defined under Maintenance > Layouts.

The partner Turnover per Charge Type can be selected by double mouse click or by pressing the button Add from the Available selection to the Chosen selection. The layout can be saved by pressing the button Save.

Under Forwarding > Shipment overview the overview will appear.

By clicking the blue actionlink Partner Turnover the report can be created.

Select the partner and layout in the new window.

After confirmation with OK, the report is created as a xml. file.

↓ Extension for partner turnover report

Exchange Rate updates

A new functionality has been added that compares and detects changes between registered used exchange rates and the current applicable exchange rates, e.g. an updated vessel exchange rate. When opening an invoice or when fixating estimated cost the user will be asked if the exchange rate needs to be updated or the existing exchange rate should be used.


Manual Entry

In the tariff setup one of the basis available is the Manual Entry which allows for a prompt during calculation of the job costing. This prompt question was earlier only shown in Air Exports, within Scope 8.2, the question will be raised whenever the job costing calculation action linked is used.  


NL Customs

AGS Partner positioning and defaulting

To improve the understanding and the logic applicable different roles within AGS declaration, both Imports and Exports re-positioning and default logic have been changed.

NL Custom Partner Role

The previous logic was that the indicator was to show that the partner could be used in Imports, and the Import field was shown next to the indicator. The new logic is 


The Importer field only requires to be populated if the importer for this partner, when used as consignee in the shipment, is a different partner. 
so it can remain empty in most cases, counter to the old behavior where it was defaulted by itself.

Acts as Importer

This indicator now means that this partner is allowed to be used as an importer, in the Importer field of an AGS Import declaration, 
Other fields have remained unchanged. 

AGS Imports

The position of the fields Importer and Declarant have changed to provide a more logic display since the settings of all other fields are depended on the partner entered in the Importer field.

To recap the allowed and defaulted combinations we have included the listed schedule below

From Shipment Defaulting



Has no NL customs Partner Role

The consignee Partner

Has NL customs Partner with "acts as importer" activer

The consignee Partner

Has NL customs Partner with different partner as importer

The Importer Partner from the consignee


Importer Partner setup

RS in the declaration



no NL customs Partner Role




no NL customs Partner Role

2 or 3


Update of the NL customs Partner Role required

NL customs Partner Role without Importer setting, 



Update of the NL customs Partner Role required

NL customs Partner Role with RS 1




NL customs Partner Role with RS 2

1 or 2



NL customs Partner Role with RS 2



RS code in de Partner setting must be equal to the RS code in the declaration

NL customs Partner Role with RS 3



RS code in de Partner setting must be equal to the RS code in the declaration

New PD fields on Customs Partner

For additional defaulting possibilities new fields have been added to the NL Customs Partner Role for Client PD.

These files are: 

Inspection Shed

Previously there was no defaulting available for Inspection Shed, this has been added.


The stakeholder is normally defaulted with the declarant (license holder) of the PD declaration, however, the registration if an inspection is allowed at a certain inspection point is determined by
the stakeholder role and can be different from the declarant, so this field will allow for more correct defaulting.




  • No labels