Fictitious Vendor W-9 Bank Duplicate Detector
Screen vendor master records for duplicate normalized tax IDs or bank accounts and active vendors missing either supplied identifier.
Description
Vendor-master anomalies can include shared tax/account identifiers and active records missing them.
Vendor-master anomalies can include shared tax/account identifiers and active records missing them. Identity duplication is an investigative lead.1
The returned values include Duplicate bank accounts, Duplicate tax IDs, Incomplete active vendors, Vendors checked. The How section below explains the calculation, input rules and interpretation.
When to use Fictitious Vendor W-9 Bank Duplicate Detector
Use Fictitious Vendor W-9 Bank Duplicate Detector when you need to evaluate the supplied records under the calculation and evidence rules below. No W9 authenticity, identifier syntax, vendor existence or fraud is established; vendor IDs themselves need not be unique.
Prepare source-backed observations and the applicable engagement policy before entering facts. Use consistent monetary units and periods. Supply all boolean evidence flags explicitly, and treat a successful screen as a reason to continue professional review.
How to use Fictitious Vendor W-9 Bank Duplicate Detector and understand its results
- Prepare source-backed observations and the applicable engagement policy before entering facts. Use consistent monetary units and periods. Supply all boolean evidence flags explicitly, and treat a successful screen as a reason to continue professional review.
- Enter activeFlags, bankAccounts, taxIds, vendorIds using the field table and calculation rules, then run the tool.
- Read duplicateBankAccounts, duplicateTaxIds, incompleteActiveCount, vendorCount. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| activeFlags | One binary active-vendor flag for each record. | list of number | Required |
| bankAccounts | Bank-account value for each vendor; an empty string means missing. | list of string | Required |
| taxIds | Tax identifier for each vendor; an empty string means missing. | list of string | Required |
| vendorIds | One vendor-master identifier for each row. | list of string | Required |
Require aligned nonempty nonblank vendor IDs, tax/account strings possibly blank and binary flags. Trim/lowercase tax/account keys, omit blanks from duplicate sets and count incomplete active rows once. Return sorted distinct duplicates and vendor count.
incompleteActive=active1 AND (tax blank OR bank blank) Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| duplicateBankAccounts | Duplicate bank accounts | list of string |
| duplicateTaxIds | Duplicate tax IDs | list of string |
| incompleteActiveCount | Incomplete active vendors | integer; minimum: 0 |
| vendorCount | Vendors checked | integer; minimum: 1 |
{
"input": {
"activeFlags": [
1,
1,
0
],
"bankAccounts": [
"BANK-1",
"bank-1",
""
],
"taxIds": [
"TAX-1",
"TAX-2",
""
],
"vendorIds": [
"V-1",
"V-2",
"V-3"
]
},
"output": {
"duplicateBankAccounts": [
"bank-1"
],
"duplicateTaxIds": [],
"incompleteActiveCount": 0,
"vendorCount": 3
}
}Limitations and assumptions
No W9 authenticity, identifier syntax, vendor existence or fraud is established; vendor IDs themselves need not be unique.
Numeric inputs, where present, must be finite. Follow the calculation-specific rules for overflow, underflow and exceptional cases. Core numeric and string lists are limited to 100,000 entries; text entries are subject to the general large-text limit. Follow any smaller calculation limits above. Missing fields without a declared default, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Ghost Employee Payroll Masterfile Match Tester: Payroll masterfile anomalies can include duplicate identities, shared bank accounts and active workers without an account. Each needs investigation in context. For a complementary task, use Kickback Vendor Bid Splitting Invoice Analytics Checker: Bid splitting can involve multiple individually subthreshold amounts whose aggregate reaches an approval limit. Vendor normalization groups text keys for a first screen.
References
Similar or alternative tools
- Ghost Employee Payroll Masterfile Match Tester
Payroll masterfile anomalies can include duplicate identities, shared bank accounts and active workers without an account. Each needs investigation in context.
- Kickback Vendor Bid Splitting Invoice Analytics Checker
Bid splitting can involve multiple individually subthreshold amounts whose aggregate reaches an approval limit. Vendor normalization groups text keys for a first screen.