Before you go live

Use this checklist with PayrollKit before inviting your first employer.

Test the integration

• Production API access works from your servers.
• Your OAuth client secret and webhook signing secret are stored securely.
• Access tokens, session tokens and payroll information do not appear in browser code, URLs, analytics or logs.
• Your product only opens PayrollKit for a signed-in user who can access that employer.
• You have tested the full journey: create an employer and their employees, finish setup in PayrollKit, send pay information, approve a Pay Run and confirm the expected filing, Payslip and file results.
• The embedded component recovers from an expired session and gives the user a clear way to retry after a loading or network error.
• You can find PayrollKit records again using the IDs from your product if a request or local job fails.
• Retries reuse the same idempotency key, and updates handle stale ETag values.
• Your signed webhook handler verifies each notification, saves it before responding and handles duplicates, delays and interruptions.

See Onboard an employer, Run payroll each period and Keep data in sync for the complete workflows.

Check the employers you plan to launch

• You have checked what PayrollKit supports for each employer and will stop setup if their payroll needs are unsupported.
• The employer and employee information from your product appears correctly in PayrollKit, and the employer can complete or confirm anything missing.
• Employee email addresses and PayrollKit-managed Payslip delivery have been tested.
• If an employer will use bank payment files, their file format has been tested with the intended banking service.

Prepare support

• Your team knows which questions it should handle and when to contact PayrollKit.
• Support contacts, incident handling and customer messages are ready.
• Your team and PayrollKit have agreed who will monitor the first live payroll through filing and output creation.

See Security and support for contact details and what to include when reporting a problem.

If you use optional API workflows

Complete these checks only if they apply to your integration:

• If you built your own payroll approval screens, PayrollKit has reviewed the flow and enabled direct API approval.
• Your approval screens confirm that the user can act for the employer and keep evidence of what they approved.
• Your payroll screens show the current status, any required action and employee results that reconcile with PayrollKit's employer totals.
• If Partner-managed Payslip delivery has been agreed, the handoff and employee delivery process have been tested.
• If you show filing or output information in your product, you retrieve the latest state after receiving a signed webhook.

Review this checklist again when you add an integration feature or onboard an employer with payroll needs you have not tested.