Skip to main content

TazWorks Integration Overview

Overview of the Payscore TazWorks integration, including dispatch workflow, report placement, global settings, and key platform limitations.

Written by Stephen Arifin
Updated over 2 months ago

Payscore integrates with TazWorks via API to allow income verification requests to be dispatched from within TazWorks and automatically return income data and reports to the applicant’s file.

Unlike property management system integrations (such as Yardi, RealPage, or Entrata), the TazWorks integration follows a vendor search workflow and does not function as a fully automated application-triggered integration.


How the TazWorks Integration Works

Payscore is configured as a vendor under the Employment Verification category in TazWorks.

When the configured search is dispatched:

  • An verification request is sent to the applicant

  • The applicant completes the verification through Payscore

  • The PDF report is automatically pushed back into TazWorks

  • Income data is inserted into the Employment Verification comments section

This allows the income data to appear directly inside the CRA’s full report when viewed in TazWorks or InstaScreen.


Where Reports and Income Data Appear

PDF Report

  • Automatically uploaded to the applicant’s file in TazWorks

  • May require visibility toggling by the CRA for client viewing

Income Data

  • Stored under the Comments section of the Employment Verification search

  • Included in the final TazWorks report output

This design ensures the verification results are embedded within the standard TazWorks reporting structure.


Important Platform Differences (vs Direct Integrations)

Individual Screenings Only

The TazWorks integration:

  • Supports individual screenings only

  • Does not support group or household screenings

Each applicant must be processed separately.


No Income Criteria

TazWorks does not pass monthly rent data to Payscore.

Because of this:

  • The income criteria is not calculated

  • Reports focus on verified income data rather than rent-based qualification metrics


Re-Opened Screenings Do Not Auto-Update

If an applicant re-opens and updates their verification:

  • The applicant’s file in TazWorks will not automatically update

  • The CRA must manually resend or upload the updated income report PDF if needed


Dispatch Behavior & Global Settings

TazWorks has a global configuration that controls whether non-database searches are automatically dispatched.

Important:

  • Database searches (credit/criminal) are instant

  • Income verification is considered a non-database search

If Automatic Dispatch is Enabled

  • The Payscore income verification request will be sent automatically when the search is ordered

If Automatic Dispatch is Disabled

  • The search must be dispatched manually

  • The verification invite will not be sent until manual dispatch occurs

Customers should confirm their automatic dispatch settings during onboarding.


Recommended Search Configuration

Payscore’s solution should be configured under:

  • Employment Verification → Additional Searches

Best practice:

  • Create a new search

  • Rename it to Automated Income Verification

  • Route the search to the configured Payscore vendor

This ensures clear internal workflows and proper routing.


Special TazWorks Behavior to Be Aware Of

“Not Employed” Application Responses

If an applicant selects “Not Employed” in the rental application:

  • TazWorks may automatically complete the search

  • The income verification invite will not be dispatched

Workaround:

  • Manually submit or assign an employer to dispatch the verification request

This limitation is due to TazWorks platform behavior, not the Payscore workflow.


Summary

  • Payscore integrates with TazWorks through the Employment Verification search category

  • Income verification requests are dispatched via vendor search workflows

  • PDF reports are uploaded to the applicant’s file and income data appears in Comments

  • Only individual screenings are supported (no group screenings)

  • Automatic dispatch depends on TazWorks non-database search settings

  • Re-opened verifications do not automatically update the applicant’s file

Did this answer your question?