If your company is using the Document Upload option for income verification, applicants will be presented with an option to upload financial documents as a method to verify their employment and income. Only Financial Documents (W-2, 1099, Paystubs, and Bank Statements) can be reviewed for fraud indicators and will be Excluded from income verification if any fraud indicators are found. You can read more about this feature here.
Note that the ability to see details of fraud signals is an additional feature. If you do not have this option available to you and would like to explore more, reach out to your CSM.
When financial documents are uploaded they are scanned for fraud signals, which generates an authenticity score based on the context of what was tampered with and the confidence in the fraud signal which VERO uses to exclude or denote a document as fraudulent in the Manager Portal.
You'll find a list of the possible fraud signal types, the signals themselves, and what they mean below.
File Origin Signals
These signals are applied to all supported form types (bank statements, pay stubs, and W-2s). They indicate the presence of tampering that isn't specific to any one type of document.
Signal |
Meaning |
Editing software detected |
The form has been edited with a recognized software package. |
Suspicious document origin |
The form was created by a recognized software package. |
W-2 File Tampering Signals
These signals indicate tampering that's specific to W-2s.
Signal |
Meaning |
Employee taxpayer ID edits |
The employee's social security number has been changed. |
Employee name edits |
The employee's name has been changed. |
Employee address edits |
The employee's address has been changed. |
Employee ID edits |
The employer's identification information has been changed. This signal indicates that one or more of the following values have been altered: |
Employer name edits |
The employer's name has been changed. |
Employer address edits |
The employer's address has been changed. |
Earning edits |
The employee's earnings have been changed. |
Withholding edits |
The employee's withholdings have been changed. |
Date edits |
Dates have been changed. |
Other edits |
Certain other fields have been changed. |
Misaligned Text |
The field or text does not match the expected alignment compared to the rest of the document. |
Invalid Social Security Tax Wage Base |
Stated Social Security Tax Wage Base exceeds the limit for the year. |
Invalid Social Security Taxes Paid |
Stated Social Security Taxes withheld does not match expected 6.2%. |
Invalid Medicare Taxes Paid |
Stated Medicare Tax Withholdings do not match the expected amount. |
Invalid Medicare Tax Wage Base |
Stated Medicare Wages and Tips are below expected amount based on Total Taxable Wages, Total Tips, and Wages Subject to Social Security Tax. |
Invalid Medicare Wages |
Stated Medicare Wages are below expected amount based on Total Taxable Wages and Wages Subject to Social Security Tax. |
Invalid Federal Income Tax for Statutory Employee |
Statutory Employee should not have reportable Federal Income Tax. |
State Taxes Paid in Non-Collecting State |
State taxes being paid in a state that doesn't collect state taxes. |
State Taxes not Paid |
States taxes not being paid in a state that does collect state taxes. |
Invalid State Tax Wage Base |
State income taxes paid do not reconcile with state income tax wage base. |
Social Security Tax Wage Base is Blank |
Social Security Tax Wage Base is blank. Verify applicant is religious worker or H-2A visa worker. |
Medicare Wage Tax Base is Blank |
Medicare Tax Wage Base is blank. Verify applicant is religious worker or H-2A visa worker. |
Invalid State Income Taxes Paid |
State income taxes paid do not match the expected amount based on the state tax rate and state income tax wage base. |
Future Date |
The captured date is in the future. For instance, having a date like January 1 on a W-2 form from next year. |
Invalid Date |
The date that was captured is not valid. For example, mentioning February 31st, which is not a valid date. |
Future Year |
The captured date is in the future. For example, having the year 2025 on a document of 2021. |
Invalid Year |
The captured year is invalid. For example, having the year 2023 on a document that should have been prepared for the year 2021. |
Paystubs Tampering Signals
These signals indicate tampering that's specific to pay stubs.
Signal |
Meaning |
Employee taxpayer ID edits |
The employee's social security number has been changed. |
Employee details edit |
The employee's marital status has been changed. |
Employee name edits |
Employee name has been changed. |
Employee address edits |
The employee's address has been changed. |
Employer name edits |
The employer's name has been changed. |
Employer address edits |
The employer's address has been changed. |
Earnings edits |
The listed earnings have been changed. |
Deductions edits |
Current or YTD deductions (including taxes) have been changed. |
Date edits |
One or more of the following dates have been changed: |
Pay frequency edits |
Pay frequency has been changed. |
Misaligned Text |
The field or text does not match the expected alignment compared to the rest of the document. |
Online generated pay stub |
The pay stub format matches a template from sites known to create paystubs for a fee. |
Dollar Amount Edits |
One or more of the following fields has been changed: |
Future Date |
The captured date is in the future. For instance, having a date like August 1 on a pay stub meant for the period of June 1 to June 30. |
Invalid Date |
The date that was captured is not valid. For example, mentioning February 31st, which is not a real date. |
Future Year |
The date that has been captured is in the future. For example, having the year 2025 on a document of 2021. |
Invalid Year |
The captured year is not valid. For example, having the year 2023 on a document that was supposed to be prepared for 2021. |
Bank Statement Tampering Signals
These signals indicate tampering that's specific to bank statements.
Signal |
Meaning |
Account Number Edits |
The account number has been changed. |
Account Holder Edits |
The account holder has been changed. |
Account Holder Address Edits |
The account holder's address has been changed. |
Account Type Edits |
The account type has been changed. This could refer to account type (e.g. savings or checking) or its branding, among other things. |
Dollar Amount Edits |
One or more of the following dollar amounts have been changed: |
Date Edits |
One or more of the following dates have been changed: |
Transaction Description Edits |
Transaction descriptions have been altered from their original state. |
Misaligned Text |
The field or text does not match the expected alignment compared to the rest of the document. |
Unreconciled Balance |
A bank statement's beginning and ending balances are invalid and don't reconcile based on the transactions available on the bank statement for the given period. |
Invalid Transaction Dates |
The date of the given transaction does not fall within the statement period dates. |
No Transactions Present |
There are no records of transactions or transaction pages present in the bank statement. |
Future Date |
The date that's been captured is in the future. For example, having a date like August 1 on a bank statement that's supposed to cover the period of June 1 to June 30. |
Invalid Date |
The captured date is not valid. For example, February 31st, which doesn't exist on the calendar. |
Future Year |
The year that's been captured is in the future. For example, in the 2023 bank statement year is captured as 2025. |
Invalid Year |
The year that was captured is not valid. For example, having the year 2023 on a document that was supposed to be prepared for 2021. |