Argyle offers uploaded document processing through Ocrolus’ optical character recognition (OCR) service. The text within uploaded documents is scanned, and the authenticity of the document is evaluated. The results are made available to view directly in Console or retrieve via Argyle’s API.
Ocrolus can be purchased through Argyle directly, and is available for W-2, 1099, and paystub document uploads.

Uploading documents
Documents can be uploaded via Argyle’s API or directly by users through Argyle Link.Refer to our Document Processing Guide for more information on setting up document uploads.
Document classification
After documents are uploaded, you can optionally choose to classify the documents. This classification pre-processing step will return:- The document type (e.g. paystubs or W-2)
- Key data fields (e.g. pay date or year)
If you are interested in document classification, reach out to your Argyle customer success manager.
Retrieving OCR data
Console

- Select an individual user within the Connections section of Console.
- When viewing Uploaded documents:
- An
OCRtag is shown when OCR data is available. - The Authenticity column will display the document’s Authenticity score.
- An
- Click the
{} JSONtoggle to view OCR data and detailed Authenticity information.- The
ocr_dataobject within the JSON will contain the OCR data. - The
ocr_authenticityobject will contain details on individual instances of tampering or other authenticity-related edits.
Refer to Ocrolus’ documentation for data field descriptions and how document authenticity is evaluated. - The
- Click the
View summarybutton to view a summary of authenticity information for the uploaded document.Additional OCR data including employee, employer, and income details will also be shown for paystubs.

API
Uploaded documents can be retrieved through Argyle’s/user-uploads endpoint.
Example JSON — Uploaded document with OCR and Authenticity data
Example JSON — Uploaded document with OCR and Authenticity data
ocr_data— Object. Contains OCR data.ocr_authenticity— Object. Contains details on individual instances of tampering or other authenticity-related edits made to the uploaded document that were detected.ocr_authenticity_score— Integer. Single score that captures the likelihood the uploaded document is authentic.
Refer to Ocrolus’ documentation for data field descriptions and how document authenticity is evaluated.
Argyle does not return HTTP or Ocrolus-specific status codes returned by the Ocrolus API.
Authenticity scores
Authenticity scores are determined by Ocrolus.| Score range | Authenticity level | Examples |
|---|---|---|
| 0-29 | Very low authenticity | Identity information (SSN, employee name, address) tampering |
| 30-49 | Low authenticity | Created as a template, income tampering |
| 50-79 | Medium authenticity | Editing software detected, dates tampering, fields misaligned |
| 80+ | High authenticity | Document is an image (80 score) |
Currently available only for paystub and W-2 document types.
OCR webhooks
Subscribe to the following webhooks to be notified of OCR updates:OCR errors
If an uploaded document cannot be processed by Ocrolus, anerror object will be returned within the ocr_data object.
This error object will contain:
- A
statusfield listing the Ocrolus document status. For errors, the value will either beFAILEDorREJECTED. - A
rejection_reasonfield listing the Ocrolus rejection reason forREJECTEDdocuments.
DOCUMENT TYPE NOT SUPPORTED— For example, a bank statement was submitted when a paystub was expected.DOCUMENT IS UNREADABLE— The document was too blurry to read and could not be processed.