From IRIS to IDEP

To facilitate the transition from IRIS to IDEP as smoothly as possible, it is important to identify major differences between the two applications:

• You can reuse your PSI commodity codes from IRIS in IDEP.
  Via the IRIS function Print | Tools | PSI product codes | Save as you can export your PSI commodity codes from IRIS to a text-file. You can import this file in IDEP: start import IRIS PSI commodity codes
  For the default screens a similar action can be carried out. There is however no pre-defined import template for these IRIS default screens. You will have to define this format yourself (text, fixed, skip 5 lines).
• Declarations in IDEP are strictly organised by period, flow and declarant.
  In IDEP it is not possible to store records from different flows, periods or declarants in the same declaration. For each flow and period a separate declaration ought to be made. Declarations can only be created for one and the same declarant. In the case of a third-party declarant, another declarant must be made 'active' in order to be able to create declarations for this declarant (see third-party declarants).
  Create declaration, Create declaration help,  PSI declarations, PSI declarations help.
• In IDEP, a null-declaration is a distinct declaration type.
  If you have nothing to declare for a given current period and flow you should create a separate null-declaration.
• In IDEP it is not allowed (nor possible) to send declarations that contain errors.
  The send option is only available if the declaration does not contain any errors and has not yet been sent.
• The send action immediately sends the declaration A soon as the send action is sent, the sent declarations are automatically sent to the CBS. It is not necessary to manually send a file to the CBS. IDEP sends a receipt via e-mail.
  
• A send declaration (and its records) can no longer be edited or sent again.
  Once sent, it is no longer possible to send the declaration again or to edit it.
• The sending and subsequent processing of declarations happens in 'batch mode'.
  As many users could be using IDEP concurrently all actions have to be carried out one at a time. If it is very busy this may take some time. In general it is not necessary to look after the sending and further processing of an sent declaration. See import/sending status.
  Send,  send all, send all help.
• Importing of files is carried out in 'batch mode'.
  Just like the sending of declaration, the importing of files is not 'immediate'. In general, for relatively small files, the import action is carried out swiftly and can be waited upon. See import/sending status.
  Import overview.
• Batches are pending tasks that are/have been carried out later.
  It may sometimes take a while before a batch task has completed but in general it won't take very long.
  Import/sending status, Import/sending status help.
• IDEP supports a limited number of exchange rates.
  In IDEP it is not possible to define ones' own exchange rates.  Exchange rates, exchange rates help, FAQ 11: no own exchange rates.
• In IDEP the declarant can grant rights to a third-party declarant to declare for certain flows.
  It is not possible nor allowed to make oneself a third-party declarant of a declarant. The declarant must grant this right to the third-party declarant. Upon request this can also be done by the CBS.
  Authorise third-party declarant, third-party declarants overview.
• Printing in IDEP is supported in a different manner.
  If you wish to make a printout of a screen, you can do so using the built-in browser print function. Overall, this provides a faithful representation of what is seen on the screen. For lists, it is possible to export the data as a text or PDF file. Such a file can be printed on the user's system in the most appropriate way.
• IDEP does not support 'reports'
  The 'Print/Export' function of the declaration allows you to make an overview or PDF file of a particular declaration.
  Print/Export help.
• 'Control own commodity codes' in IDEP is not necessary
  New PSI commodity codes are validated with respect to the current year. PSI commodity codes of which the CN8 code is no longer valid can still be used in the declarations of the previous year. Therefore such PSI commodity codes are still valid. If a PSI commodity codes is no longer valid, a message will be issued when it is used. IDEP will propose new codes if this is possible.
  PSI commodity codes, PSI commodity codes help.
• There are no e-mail-, print- or font- settings in IDEP
  However, there are other IDEP-specific options.  Options, options help.
• IDEP does not support 'formulas'