Vetting Plan Sponsors for Finch Compatibility

Last updated: January 8, 2026

Guide for Recordkeepers using Finch's Relius Integration

Use this guide to determine if an existing plan sponsor who currently sends you manual payroll files would be a good fit for Finch's automated payroll integration.

Step 1: Verify Payroll Provider

Question to ask: "Which payroll provider do you use?"

📄 Relius Compatible Providers -Verify that they use a provider on this list

If they use a different provider: The Finch integration is not currently available.

Step 2: Verify Contribution Processing

Questions to ask:

  1. "Where do you process your employer contributions (match, profit sharing, safe harbor, non-elective)?"

    • ✓ Compatible: "In our payroll system" or "Through [payroll provider name]"

    • ✗ Not compatible: "In a separate benefits system" or "We handle that outside of payroll"

  2. "Do your employer contributions appear on employee pay statements?"

    • ✓ Compatible: "Yes"

    • ✗ Not compatible: "No" or "I'm not sure"

Why This Matters

Finch can only retrieve data that exists in the connected HRIS/payroll system. Since you need complete contribution data for audit files and compliance, missing employer contributions means the integration cannot meet your requirements.

Plan sponsors are not compatible if:

  • Safe harbor contributions are managed outside the payroll system

  • Non-elective contributions are tracked in separate systems

  • Employer match is calculated and recorded independently from payroll

  • Any contribution data doesn't flow through the connected HRIS

Note: In rare cases, the Finch implementation team may identify that the data exists in a different location within the payroll provider's system and can investigate alternative retrieval methods. If contributions don't appear on pay statements, assume the plan sponsor is not compatible with Finch.

Step 3: Confirm Division Setup

Question to ask: "Do you have multiple divisions set up in your payroll system?"


Setting Up Compatible Plan Sponsors for Success

Once you've confirmed the plan sponsor uses a supported provider and all contributions flow through their payroll system, set clear expectations:

Initial Setup Requirements

Plan sponsor will need to:

  • Complete the secure connection process using Finch Connect (takes ~5 minutes)

  • Run a successful payroll with the relevant contribution and deduction codes

  • Review and approve payroll item mappings via a secure link you send

You will need to:

  • Map payroll items based on the plan document (identify excluded compensation, deferrals, contributions, loans)

  • Send mapping confirmation link to plan sponsor

  • Configure integration settings in the Finch dashboard (plan ID, payroll sequence ID)

  • Test initial files (typically 1-2 payroll cycles) - work with your Implementation Engineer to determine the best options for your team for testing.

  • For detailed directions on the steps above, see📄 Sponsor Connection Setup In Finch Dashboard.

Ongoing Maintenance

Plan sponsor must:

  • Keep HRIS data current - names, addresses, hire dates, employment status, and all other census fields must be maintained in their payroll system

  • Notify you when adding new pay codes - new earnings types, deductions, or contribution codes require mapping updates

  • Use clear, descriptive names when adding new pay codes to make mapping easier

You will:

  • Monitor dashboard notifications for new payroll codes OR rely on plan sponsor to notify you

  • Update mappings when plan sponsors add new pay codes

Typical Timeline: Most connection setup is complete within 1-2 weeks from initial connection to live file delivery. If your plan sponsor completes Finch Connect immediately after you send them the link and you complete the payroll mapping as soon as it is available in the dashboard (usually within a couple hours but in some cases up to one day), it is possible to have a file within 2 days depending on the timing between when you complete the payroll mapping and configuration in the dashboard and when the next payroll run occurs.