Introduction

This guide is for organizations that have integration solutions they want to market to prospective and mutual Paylocity customers within the Paylocity Integrations Marketplace and do not yet have a formal technology partnership agreement with Paylocity.

• By the end of this document, you will understand:
  • Requirements to become a technology partner and maintain a technology partner status.
  • The steps to begin partnership discussions and whom to contact.
  • Required stakeholders to participate in partnership discussions.

🚧

Customer-specific integrations

If you are a current Paylocity customer and want to build/own an integration just for your company and not advertise it to other Paylocity customers, we don't require a partnership agreement. For details, see our Integration Requirements.

Requirements to become a technology partner

• To be approved to access a test environment, you must sign a partnership agreement, be willing to code to Paylocity APIs, and agree to commercial terms.
• To be shown in the production marketplace for early adopter Paylocity customers, you must complete the first three phases of the Technology Partner Journey.
• To receive a "Paylocity Certified" designation (Phase 4) in the Paylocity Marketplace, you must have at least three (3) mutual Paylocity customer advocates who are active and have accomplished the required early adopter testing scenarios, and your integration must function in production with an error rate of less than 5%
  (Error Rate = # of errors / Total Calls x 100).

❗️

Robotic Process Automation Providers

Paylocity does not allow partners to perform Robotic Process Automation (RPA) to execute actions such as screen scraping & driving.

An example of this would be when a solution provider asks a company admin to login to the Paylocity product suite so that a third-party application can take control of the browser to perform a preconfigured set of navigation clicks & data inputs into fields in order to complete some tasks as if the Admin user had done it (and would be logged as such in the audit trail). These actions bypass the use of Paylocity APIs and prevents appropriately tracking who/what performed data transformative actions.

Technology partner journey

Use this journey map as a guide to understand and track your progress at a high level through the phases and requirements to become a Paylocity technology partner. This is an outline, and Paylocity reserves the right to introduce additional conversations and requirements, if necessary, based on your service and functions.

Phase 1: Discovery & agreement terms

In this phase, you will talk with our Business Development team to explain your solution and how you’d like to work with Paylocity. You will sign a Marketplace Partner Agreement and agree to commercial terms. Once the agreement is signed, you will be given credentials for a sandbox account for testing.

To kick-off these discussions, complete the Marketplace Partner Intake Form.

Phase 2: Build your integration and finalize the solution, scope, and required documentation

In this phase, you will complete process documentation with Paylocity to finalize your supported solutions, services, and scope.

Complete build using sandbox

• Utilize sandbox to build your integration, test, and create integration use case proofs; ensure you are meeting expectations for each business use case and follow best practices for error handling.
• Reach out to your Business Development Manager or [email protected] with questions.

Submit required document & resources

• Contact List - To ensure smooth communications throughout the process, you'll provide Paylocity with a primary contact and general distribution email addresses for each phase: Sales, Implementation, Support, and Escalation. The same contacts can be used for each phase.

• Customer Support Instructions - You will provide services to troubleshoot Tier 1 issues related to your integration. This deliverable will include documentation that outlines integration customer responsibilities and how to contact Support from your organization for data-element issues or maintenance concerns. Links to this documentation may be included on your Paylocity Integration Marketplace page. We will supply you with a Roles & Responsibilities document to help you complete this step.

• Data Element & Directionality Mapping - You will provide a resource to showcase Paylocity endpoints utilized, Paylocity API data elements, and direction of data (e.g., pushed to/pulled from Paylocity).
  For more details, see Data Element & Directionality Mapping

• Integration Use Case Proof(s) - You will provide a use case proof for each of your integration use cases. A template format of how to document these proofs will be provided.

• Demo Video - Provide a step-by-step demo video that highlights the integration and its features.

• Complete Risk Assessment – Your Business Development manager will work with you to kick-off the process, which may include submitting documents like a SOC 2.

Phase 3: Moving into a technology partner role

In this phase, you have completed all the general and partner resource document requirements from Phase 2. You have demonstrated your solution to the Paylocity Web Services Team and have been approved to be a technology partner.

As a new technology partner, you must complete the following onboarding tasks:

• Review the Marketplace Partner Launch Kit and complete the Partner Launch Intake form
• Create a landing page using the Partner Landing Page Requirements Overview
• Agree upon timeline to create and launch your Paylocity Integration Marketplace pages. Your assigned Web Services Business Systems Analyst will review the Partner Launch Intake Form details to complete the creation of your marketplace page. This is typically released on the 15th in monthly cycles but may vary depending on various timings.

🎉Congratulations!🎉
You are a Paylocity technology partner and are listed on our Integrations Marketplace for all customers to see.

• Paylocity customers will have a shortened onboarding process to using your integration. The company admin for that customer may now submit a request directly through the Paylocity Marketplace experience without having to contact an Account Executive.

Phase 4: Gaining your "Paylocity Certified" Designation

In this phase, you have tested your integration with mutual clients and you’re now ready to provide further final documentation and gain a certified designation.

• To receive a “Paylocity Certified” designation in the Paylocity Marketplace, you must:
  • Have at least three (3) mutual Paylocity customer advocates who are active and have accomplished the required early adopter testing scenarios, and the integrations have been active at least 90 days.
  • Your integration must function in production with an error rate of less than 5% (Error Rate = # of Errors / Total API Calls x 100 in the last 90 days)
  • Wireframe or Solution Flowchart/Diagram - Please provide a detailed flowchart or diagram showcasing the intended steps, data flows, and data hierarchy in your integrated solution design. It should clearly illustrate database relationships, iteration patterns, and major components of your Extract, Clean, Transform, Load, and Analyze (ECTLA/ETL) logic & application layers.

Maintaining your technology partner status

Once your integration has launched, you must accommodate the following to maintain a relationship as a technology partner with Paylocity:

• First Level (Tier 1) Support: Scope and filter any low-level customer concerns that can be handled in your processing documentation and support articles.
• Acceptable error rate of API calls:
  5% or less, Error Rate = # of Errors / Total API Calls x 100 in the last 90 days; varies by scope and complexity of integration
• Calls per second and rate limit annual review
• Response time of 48 hours or less on communications from Paylocity Support and Implementation teams.
• Automated annual renewal of API credentials.

Ongoing support and relationship

• Collaborate with Paylocity to maintain updated business and technical contact information for ongoing support and escalations.
• Pass yearly reviews of integration stability and customer-partner relationship states.
• Attend regularly scheduled touchpoint calls with the Paylocity Integration team.
  • Discuss and address identified issues.
  • Discuss planned maintenance and Paylocity product initiatives related to your integration.
  • Address changes needed to support your integration (e.g., expanding endpoint access, changing renewal contacts, updating production webhook URLs or authorization details, process enhancements, partner feedback, etc).