Skip to main content
When testing Document Processing, use the sample PDFs below. Upload these documents to test successful parsing, various tax form types, and suspicious document detection.
Test scenarios use the file name to determine results. The sandbox ignores actual file contents. Only the file name matters.
Trigger a suspicious result on any doc upload test scenario. Add the prefix suspicious. to any test file name from this page (for example, rename most.recent.paystub.pdf to suspicious.most.recent.paystub.pdf) and upload it. The doc upload task will return data with is_suspicious: true. This works for every test file listed below — paystubs and tax forms.

​
Pay stubs

​
High income earner

Use these documents to test parsing for a high income earner scenario.

​
Tax documents

For 1099 tax documents, Truv supports parsing formats from any year after 2021. This includes 1099-DIV, 1099-G, 1099-INT, 1099-MISC, 1099-NEC, and 1099-R.

​
Volunteer documents

​
Suspicious document detection

To flag any doc upload test scenario as suspicious, rename the file with the suspicious. prefix before uploading. See the tip at the top of this page for the full rule and examples.

​
Validation failures

Use these files to test the file-level validation flags returned by the Document Collections API. Each file triggers a specific validation failure on the collection retrieve response. In the sandbox, only the file name determines the test scenario — the actual file contents are ignored. You can upload any PDF as long as the filename matches.
The sandbox triggers the duplicate scenario by file name. In production, Truv detects duplicates by file content, not file name — so sandbox results for renamed or same-named files do not reflect production behavior. See How duplicate detection works.

​
Base64 encoding for Document Collections API

The Document Collections API accepts base64-encoded file content when creating or uploading to a collection. To encode a test document for use with the API:
Pass the base64 string as the content field when creating a document collection:
In sandbox mode, the file name determines the test scenario, not the actual content. The base64 content can be from any valid PDF — only the filename matters for sandbox behavior.