Below is a list of the fields available in Paflink Extended Data: 

Output fields 

• D01 – GeoREsult 

• D02 – Longitude 

• D03 – Latitude 

• D04 – Address Type (‘FP’, ‘G’, ADDRESS_TYPE) 

• D05 – GNAF_DETAIL_PID  

• D21 – LONGITUDE_94

• D22 – LATITUDE_94 

• D23 – GEOCODE_LEVEL 

• D24 – LONGITUDE_94 

• D25 – LATITUDE_94 

• D31 – SUP_DECEASED_DATE 

• D32 – SUP_MOVED_CONSENT_INDICATOR 

• D33 – SUP_MOVED_DATE 

• D34 – SUP_DELIVERY_MAIL_INDICATOR 

• D35 – SUP_NONDELIVERY_REASON_CODE 

• D36 – SUP_ADVERTISING_MAIL_INDICATOR 

• D37 – SUP_RESIDENTIAL_INDICATOR 

• D38 – SUP_NONRESIDENTIAL_INDICATOR 

• D39 – SA1_2021_7Digit 

• D40 – SA1_2021_MainCode 

• D41 – LGA_2021 

• D42 – MESHBLOCK_2021 

• D55 – LONGITUDE_2020 (Extended No.) 

• D56 – LATITUDE 2020  (Extended No.) 

• D57 – LGA_2020 

• D66 – SA1_2011_7Digit 

• D67 – SA1_2011_MainCode 

• D68 – SA1_2016_7Digit 

• D69 – SA1_2016_MainCode 

• D70 – LGA _2011 

• D71 – LGA_2016 

• D72 – MESHBLOCK_2011 

• D73 – MESHBLOCK_2016 

• D74 – DT_GEO_LEVEL 

• D75 – GNAF_SITE_PID 

• D76 – GNAF_STREET_PID 

• D77 – GNAF_LOCALITY_PID 

• D55 – Latitude (Extended No.) 

• D56 – Longitude (Extended No.) 

• 7 = Geocode to House/Building 

• 6 = Geocode to the street 

• 4 = Geocode to the locality 

• P = Point 

• S = Street 

• L = Locality 

Data for both PAFlink and NZPAFlink is released quarterly in March, June, September and December of each year.

When the data is ready – you will receive an email from the DataTools Client Service team to notify you that it is available for download and installation.

IMPORTANT: As DataTools are only delivering an update to the PAFlink &/or NZPAFlink data – you MUST keep a copy of your last install and serial number from Acxiom in case you ever need to reinstall it.

DataTools does not have a copy of this install, nor your serial number, so this is a very important step to note.

Should you have any questions please contact the Client Service Team on (02) 9687 4666, support@datatools.com.au or via the chat on our main website. Our team are based in Sydney and are available between 9am to 5pm Monday to Friday.

Steps to update PAFlink data for Australia

1. Make sure that ALL users have exited any program using the PAFlink data
2. Download the latest data from the link contained in your email and save it onto the desktop of the PC/Server that the PAFLink data is required on.
3. Uncompress the file, then copy and paste the data into the PAFlink folder of your install. Click yes to overwrite existing data.

Steps to update NZPAFlink data for New Zealand

1. Make sure that ALL users have exited any program using the NZPAFlink data
2. Download the latest data from the link contained in your email and save it onto the desktop of the PC/Server that the NZPAFLink data is required on.
3. Uncompress the file, then copy and paste the data into the NZPAFlink folder of your install. Click yes to overwrite existing data.

There are two components to the SOA generation process:
– the certificate which you keep for a minimum of two years, using some detail for the actual lodgement process, and
– an entry in an Audit log.
If you are generating your own certificates then you must maintain the Audit log for at least two years and it has to be provided via email, SOAProdlog@nzpost.co.nz, to NZ Post whenever a new SOA is produced.

Produce an entry in your SOA log file. The entry will contain the same information as your certificate. You are obliged to keep all log files for a minimum of two years and provide the logs via email to New Zealand Post at SOAProdlog@nzpost.co.nz as close to the time the SOA has been produced as possible, and prior to any attempt to use the new SOA to lodge Bulk Mail/VolumePost mail with New Zealand Post. You should not at any time attempt to edit your SOA log file(s) in any way.

When sending your ProdLog through to New Zealand Post, please ensure the following:
i. The email subject line must read “SOA PROD LOG AUTOLOAD FILE”.
ii. There must be only one file attached to any given email.
iii. The attached file must meet the current requirements.
iv. It would be highly desirable if the file did not include expired SOA certificates.
v. It would be desirable if the file included only new SOA certificates that have not been sent before
vi. Remove any signature from the email in which the ProdLog is attached as the system New Zealand Post uses to identify the attachment and automatically upload it picks up the email signature and the SOA ProdLog upload fails.

To be able to print Statement of Accuracy (SOA) certificate in 2017 – customer must have the correct year and data provider company name included in your ‘SOAtemplate.txt’ file in NZPAFlink folder.

To do this you will need to amend your ‘SOAtemplate.txt’ file. There is only ONE small text change to be made.

NOTE: It is VERY important that you make this change ON OR JUST BEFORE January 1, every year to remain compliant.

The instructions on how to do this are:

1. Locate your ‘SOAtemplate.txt’ file
2. Right click on the file and ‘Open With’ a program that allows you to edit the text file, like Notepad.The file should contain similar information to what is shown below (but with your information included – not all details will match below.)  The line highlighted in green is the one that requires changing.STATEMENT OF ACCURACY

   SOA ISSUER|Your Company Name Pty 
   SOFTWARE NAME|NZ PAFlink Batch
   SOFTWARE VERSION|
   PAF VERSION USED|
   SOA UNIQUE REFERENCE|ACX16_XXX

   CUSTOMER NAME|
   CUSTOMER NZP NO|99999999
   CUSTOMER ADDRESS|

   CUSTOMER DATABASE|

   DATE SOA ISSUED|
   DATE SOA EXPIRES|

   NO. OF ADDRESS RECORDS|

4. Save the file by going to File>Save.