Skip to main content

Finity Pension Export (PAPDIS)

Exporting PAPDIS files from Finity for upload to Jarvis

Updated today

Purpose

This guide explains how to export PAPDIS files from Finity for upload to Jarvis. Jarvis requires two file types per payment period: Enrolments (member personal data) and Contributions (contribution values for each member).

Pre-Requisites

Before generating PAPDIS files, ensure:

  1. Payroll completion for target period

    • All payroll runs for the period are complete

    • All corrections and adjustments processed

  2. Two-week arrears timing (strongly recommended)

    • Export files 2 weeks behind current week

    • Example: During week 30, upload files for week 28

    • Prevents uploading incorrect data due to last-minute changes

  3. Payment company details

    • Know which payment companies require file generation

    • Understand payroll frequency for each (Weekly/Fortnightly/FourWeekly/Monthly)

Best Practise

Temporary recruitment and payroll environments experience frequent last-minute changes. Working two weeks in arrears ensures all payroll changes and corrections are processed before file generation.


Understanding PAPDIS File Types

Jarvis requires one PAPDIS file for each tax period and each payment company:

Contributions File

  • Contains personal data for new enrolments and opt-ins

  • Creates or updates member records in Jarvis

  • Contains contribution values for each member

  • Covers the selected pay period

  • Required even when no new enrolments exist


Accessing Pension Data

  1. Navigate to sidebar menu in the Finity Portal

  2. Expand Manage Pensions

  3. Select Pension Data Extract

  4. Locate Jarvis tile (displayed first at top of page)


Configuration Parameters

Extract Mode

  • Contributions: Generate contributions PAPDIS file (includes new enrolments/opt-ins)

Frequency

Select based on payroll cycle:

  • Weekly

  • Fortnightly

  • FourWeekly

  • Monthly

Note

Adjust frequency when exporting for different worker types (e.g., fortnightly, monthly, or four-weekly workers).

Period Selector

  • Select the tax period for file generation

Payment Company

  • Select the specific payment company for file generation


File Generation Workflow

Follow this sequence for each payment company and each tax period:

Step 1: Generate Enrolments File

  1. Set Extract Mode β†’ Contributions

  2. Select appropriate Frequency

  3. Select target Period

  4. Choose Payment Company

  5. Click Run Report to download contributions CSV


Jarvis Upload Guidelines

IMPORTANT

Upload only one file per payment period. If you run multiple payrolls for a single period, wait until all payrolls for that period are completed before uploading.


Handling Corrections

If corrections are made after initial upload:

  1. Re-export files using same settings (Frequency, Period, Payment Company)

  2. Re-upload corrected files to Jarvis

  3. Jarvis will process updated data

Prevention

Working two weeks in arrears significantly reduces the need for post-upload corrections.


Post-Generation Verification

Before uploading to Jarvis, verify:

  1. Contribution file is generated for target period

  2. File corresponds to correct Payment Company

  3. Frequency matches payroll cycle for selected workers

  4. Period matches intended submission (verify 2-week arrears if applicable

  5. Contributions file contains data for all active and expected new members


Troubleshooting Common Issues

Multiple Payrolls in Single Period

  • Wait until all payroll runs complete

  • Generate file only once per period after final payroll

Wrong Frequency Selected

  • Re-generate file with correct frequency setting

  • Verify payroll cycle before export

Missing Data

  • Confirm payroll processing complete for selected period

  • Check Period Selector matches intended tax period

  • Verify Payment Company selection correct


Support

For file generation assistance or technical issues:

  • Contact Finity Support Team

For Jarvis upload queries:

Did this answer your question?