Skip to main content
Verify client income and employment by processing uploaded documents. Document processing serves as a fallback when clients cannot connect to their payroll provider through Bridge, or as a tool for caseworkers who already have documents on file. It is included as part of the standard orders workflow — no separate implementation is needed when using Customer Portal or Caseworker Portal.

​
Benefits

No Payroll Connection Needed

Verify income from paystubs, W-2s, and 1099s without requiring the client to log in

Document Validation

Automatic detection of manipulated documents and suspicious metadata

Structured Data

Extract employer name, pay period, gross/net pay, and tax withholdings into structured fields

Same Report Format

Returns the same income and employment data structure as a live payroll connection

​
What you get

Income Data

  • Gross and net pay per period
  • Year-to-date earnings
  • Pay frequency and period dates
  • Tax withholdings and deductions

Employment Data

  • Employer name and address
  • Job title and position
  • Employment dates
  • Pay basis (salary, hourly)

Document Validation

  • Document type classification
  • Readability verification
  • Suspicious document flagging
  • Known suspicious template detection

Supported Documents

  • Paystubs
  • W-2 forms
  • 1099 tax forms (DIV, G, INT, MISC, NEC, R)
  • SSA-1099
  • Volunteer/community service letters

​
Government use cases

Clients without traditional payroll (freelancers, gig workers, small business owners) can upload 1099s and bank statements to verify income for benefits eligibility.
Caseworkers who receive documents by mail or in person can upload them through the Document Collections API for automated processing, replacing manual data entry.
When a client’s employer isn’t supported or the payroll connection fails, document upload provides an alternative verification path within the same workflow.

​
Government-specific configuration

​
Government document types

Benefits eligibility determinations commonly use these document types:

​
Case ID tracking

Pass external_user_id when creating the user to link document collections to your agency’s case identifier.

​
Fallback from a payroll connection

When a client can’t connect their payroll provider through Customer Portal or Caseworker Portal, fall back to document upload. Enable document upload in the Truv Dashboard to offer it directly within the Bridge widget.

​
Lenient document intake

Applicants rarely upload exactly what’s required. With intelligent intake, a client uploads any mix of files — including phone photos — and Truv classifies each one and flags unreadable scans up front. If a SNAP determination needs two recent pay stubs and the applicant uploads five files, Truv recognizes the two pay stubs among them; you finalize those and let the applicant proceed.

​
How to implement

For caseworker-driven workflows, use the Document Collections API to upload, validate, finalize, and retrieve structured data. For client-facing portals, enable document upload as a fallback in Truv Bridge by setting data_sources: ["docs"] in the bridge token.

​
API reference

Document Collections

Create collections, upload files, finalize, and retrieve results

Document Collections

Upload and process documents via the Collections API

Parsed Documents

Retrieve parsed and structured data

Bridge Token

Create tokens with document upload enabled

​
Next steps

Implementation Guide

Full Document Collections API walkthrough

Caseworker Portal

Integrate document processing into caseworker workflows

Customer Portal

Client-facing verification with Bridge fallback

Test Documents

Sample PDFs for sandbox testing