Before You Start
Ensure you have:
Jarvis configured in Kintec
Organisation ID and Scheme ID entered in Company Settings
Pension scheme configured with Jarvis Pension Group
See the "Configuring Jarvis in Kintec" guide for setup instructions
Completed payroll for the period
All payroll runs must be finalised before submission
All corrections and adjustments processed
Overview of Submission Methods
Kintec offers two methods for sending pension contributions to Jarvis:
Manual PAPDIS Export - Generate and upload a CSV file to Jarvis (suitable for all users)
API Submission - Send contributions directly via API integration (recommended for faster processing)
Choose the method that best suits your workflow. API submissions provide real-time processing and eliminate manual file handling.
Method 1: Manual PAPDIS Export
Old UI
Hover over Employees in the main menu
Click Pensions
Click Papdis Export
Enter the date range for the payroll period
Click Export
Upload the generated CSV file to your Jarvis employer portal (https://app.getjarvis.app/employer)
New UI
Click on Company in the main menu
Navigate to the Pensions section
Click the '+' icon in the Papdis Export section
Enter the date range and click Submit
Once the file generation is complete, click 'Download' for the correct file
Upload the downloaded CSV file to your Jarvis employer portal (https://app.getjarvis.app/employer)
Important:
PAPDIS files should include all workers, even those who haven't joined or opted into the pension scheme
Generate the file after each payroll run
Avoid modifying the CSV file after export - make any changes in Kintec and re-export
Method 2: API Submission (Recommended)
Old UI
Navigate to either a calculated or posted payroll batch
Click 'Submit Contributions to Jarvis'
Contributions will be sent directly to Jarvis via API
Wait for confirmation of successful submission
New UI
Navigate to either a calculated or posted payroll batch
Click the 'Actions' button
Select 'Submit Contributions to Jarvis'
Contributions will be sent directly to Jarvis via API
Wait for confirmation of successful submission
Tip: API submissions provide instant confirmation and eliminate the need for manual file uploads. We recommend using this method whenever possible.
Best Practices
Submission Timing
Generate and submit contributions after each payroll run
Submit contributions two weeks in arrears to allow for corrections
Example: During week 30, submit contributions for week 28
File Handling (Manual Export Only)
Do not modify PAPDIS files after export
If corrections are needed, make changes in Kintec and re-export
Keep a record of all exported files for audit purposes
API Submissions
Verify successful submission confirmation before moving to the next payroll period
If an API submission fails, use the manual PAPDIS export as a fallback
Contact support if you experience repeated API submission failures
Troubleshooting
Common Issues
PAPDIS File Generation Fails
Verify that Jarvis is correctly configured in Company Settings
Check that the pension scheme has a valid Jarvis Pension Group assigned
Ensure the date range is correct and covers completed payroll periods only
API Submission Fails
Check your internet connection
Verify that your Kintec instance has API submission enabled
Confirm Organisation ID and Scheme ID are correct in Company Settings
Contact Kintec support if the issue persists
File Upload Rejected by Jarvis
Ensure the PAPDIS file hasn't been manually modified
Check that the file format is CSV
Verify that Organisation ID and Scheme ID match between Kintec and Jarvis
Confirm that all required worker data is present in the file
Workers Missing from Export
Check that workers are assigned to a pension scheme in Kintec
Verify that the Jarvis Pension Group is correctly populated for each worker
Ensure the date range includes the relevant payroll periods
Need Help?
For assistance with contribution submissions:
Kintec Support Team: For platform-related queries
Your Jarvis Relationship Manager: For submission issues
Email: [email protected]