Five steps to prepare for submitting PTRs

From the 1 November 2017 reporting entities must submit Prescribed Transactions Reports (PTRs) to the Financial Intelligence Unit (FIU).

Be prepared – to be ready to submit PTRs from 1 November reporting entities will need to start preparing now!

The five steps below have been developed as a guide to help reporting entities prepare for submitting PTRs.

View the PDF chart for an overview of the Five Steps to Prepare for Submitting PTRs

 

Step 1. Prepare the information

  • Determine what information needs to be provided in PTRs.
    The following documents outline what information needs to be included in PTRs.
  • Check that you capture the information required.
    If you don’t think you do – you will need to develop a way to start collecting it to meet your PTR obligations.
     
  • Determine where the information is and in how many different places (systems).

     
  • Determine how easy it will be to bring this information together into one system.
    If the information is in many different places and formats determining how easy it is to bring together will help you identify how best to submit PTRs and potentially automate your Prescribed Transactions Reports.
     
  • Estimate how many International Fund Transfers (IFTs) and Large Cash Transactions (LCTs) your organisation you will need to report and how often.

 

Step 2. Determine how to submit PTRs

The information you have collated (prepared) in Step 1 will help you identify which of the following options will be most appropriate for your organisation to submit PTRs.

There are three ways reporting entities will be able to submit PTRs via goAML – the Financial Intelligence Unit reporting tool. Whichever way reporting entities choose to submit PTRs, the data you need to include in the report is the same.
 

Option 1: User manually enters report on website

Involves submitting PTRs by entering data into a goAML online form specifically designed for IFTs and LCTs. This option will be similar to the current Suspicious Transaction Reporting (STR) form.

If the information is stored in many different systems and is not easy to bring together then this may be the most appropriate way to submit PTRs for lower volumes of transactions.

The online goAML web tool does not rely on an automated IT system being developed, but will require users to fill out a form for each prescribed transaction.
 

Option 2: User uploads XML files to goAML (bulk upload)

Involves submitting data relating to more than one IFT/LCT transaction at a time, as part of a single 'report' that can be uploaded on to the goAML web interface. The upload goAML file option will require users to upload data as XML files to goAML.

There may be benefits to this option if a reporting entity expects higher volumes and/or already has an IT system that successfully integrates all information relevant to PTRs.

This option relies on developing a more automated IT system that may need to link multiple databases together if the reporting entity holds the required information in more than one system.
 

Option 3: System-to-system upload (XML files are automatically sent to goAML)

This option will enable PTRs to be sent automatically to the FIU. This system-to-system (B2B) option will not require users to manually upload data files. The information will need to be integrated into XML files to be sent automatically to goAML. This option is most beneficial for reporting entities who expect higher volumes of transactions.

Like option 2, it requires IT investment for automating the reporting.

 

Step 3. Develop your system

Once you have worked through the previous steps please email goamlconsult@police.govt.nz for a copy of the following documents.

Option 1: User manually enters report on website

No IT system development is required for this option as users will be required to manually enter data into a goAML online form specifically designed for International Fund Transfers (IFTs) and Large Cash Transactions (LCTs).

Users will need to fill out an online IFT or a LCT form for each prescribed transaction.

Resources Available

  1. An introduction to submitting PTRs via the goAML website (using the IFT and LCT forms).
     

Option 2: User uploads XML files to goAML (bulk upload)

This option requires reporting entities to invest in developing their IT system bringing together the information into one single ‘report’ for users to then upload to goAML (as XML files).

Resources Available

  1. Introduction to the PTR Data Schema (Dictionary)
    This document provides an overview of the PTR Data Schema (Dictionary), what’s included and how to apply the information.

    The Introduction to the PTR Data Schema (Dictionary) v1.4 is available.
     
  2. PTR Data Schema (Dictionary)
    This document is for reporting entities (Project Managers and other resources working on PTR projects) to understand how the information needs to be formatted for developing system automation.

    Data Dictionary v1.4 is available.
     
  3. goAML XML Schema 4.0 (v1.4)
    The goAML XML Schema 4.0 (v1.4) is relevant for reporting entities (software developers) wishing to submit reports via the bulk upload or B2B interfaces.

    This document specifies the file format for uploading files via the bulk upload and needs to be read in conjunction with the PTR Data Schema (Dictionary) which defines rules that must be adhered to.

    The goAML XML Schema 4.0 (1.4) is available.
     

Option 3: System-to-system upload (XML files are automatically sent to goAML)

Like Option 2, this option requires reporting entities to invest in developing their IT system to fully automate submitting PTRs to the FIU via goAML.

Resources Available

  1. Introduction to the PTR Data Schema (Dictionary)
    This document provides an overview of the PTR Data Schema (Dictionary), what’s included and how to apply the information.

    The Introduction to the PTR Data Schema (Dictionary) v1.4 is available.
     
  2. PTR Data Schema (Dictionary)
    This document is for reporting entities (Project Managers and other resources working on PTR projects) to understand how the information needs to be formatted for developing system automation.

    Data Dictionary v1.4 is available.
     
  3. goAML XML Schema 4.0
    The goAML XML Schema 4.0 (v1.4) is relevant for reporting entities (software developers) wishing to submit reports via the bulk upload or B2B interfaces.

    This document specifies the file format for uploading files via the bulk upload and needs to be read in conjunction with the PTR Data Schema (Dictionary) which defines rules that must be adhered to.

    The goAML XML Schema 4.0 (v1.4) is available.
     
  4. Business-to-Business (B2B) Specifications
    The B2B Specification documents all technical aspects of the B2B interface. It is relevant only for reporting entities wishing to use the B2B interface and should be read by solution architects, technical project leads.

    Business-to-Business (B2B) Specifications v1.4 is available.
     
  5. Developers Guide
    The Developers Guide documents the web services interface to submit reports, query the status of reports, and interact with the goAML message board via the B2B interface. This document is targeted at software developers and relevant only for reporting entities wishing to use the B2B interface.

    The Developers Guide v1.4 is available.

 

Step 4. Testing your system

Whichever way reporting entities choose to submit PTRs a testing environment will be available. Reporting entities will not be able to access the production environment until they have successfully run tests against our test environment. If you are starting to look towards planning your testing or require access to the test environment, please email goamlconsult@police.govt.nz.

A draft of the Test Guide (v1.4) for the bulk upload and B2B options is now available. Please email goamlconsult@police.govt.nz for a copy.

 

Step 5. Prepare your people

The goAML User Guide is for reporting entities using Option 1. User enters report on website and Option 2. User upload goAML file. You will need to email goamlconsult@police.govt.nz for a copy.

Option 3. System-to-system goAML file upload is a fully automated solution and does not require any user intervention to submit PTRs.