Ghost Employee Payroll Masterfile Match Tester

Screen payroll employee IDs and bank accounts for duplicate identities or accounts and active employees without supplied bank-account data.

Description

Payroll masterfile anomalies can include duplicate identities, shared bank accounts and active workers without an account.

Payroll masterfile anomalies can include duplicate identities, shared bank accounts and active workers without an account. Each needs investigation in context.^[1]

The returned values include Active without bank account, Duplicate bank accounts, Duplicate employee IDs. The How section below explains the calculation, input rules and interpretation.

When to use Ghost Employee Payroll Masterfile Match Tester

Use Ghost Employee Payroll Masterfile Match Tester when you need to evaluate the supplied records under the calculation and evidence rules below. No worker existence, bank verification or fraud conclusion is established. Shared accounts may be legitimate.

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 Ghost Employee Payroll Masterfile Match Tester 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 activePayrollFlags, bankAccounts, employeeIds using the field table and calculation rules, then run the tool.
Read activeWithoutBankAccountCount, duplicateBankAccounts, duplicateEmployeeIds. 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
activePayrollFlags	One binary active-payroll flag for each employee.	list of number	Required
bankAccounts	Bank-account value for each employee; an empty string means missing.	list of string	Required
employeeIds	One payroll employee ID for each row.	list of string	Required

Require aligned nonempty nonblank employee IDs, account strings possibly blank and binary active flags. Trim/lowercase keys; collect all employee duplicates and nonblank account duplicates regardless of active status. Return sorted distinct duplicates and active-with-blank count.

duplicates=second normalized occurrence; missing=active1 AND bank blank

Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.

Output field	Meaning	Value type
activeWithoutBankAccountCount	Active without bank account	integer; minimum: 0
duplicateBankAccounts	Duplicate bank accounts	list of string
duplicateEmployeeIds	Duplicate employee IDs	list of string

json

{
  "input": {
    "activePayrollFlags": [
      1,
      1,
      0
    ],
    "bankAccounts": [
      "ACCT-1",
      "acct-1",
      ""
    ],
    "employeeIds": [
      "E-1",
      "E-2",
      "E-3"
    ]
  },
  "output": {
    "activeWithoutBankAccountCount": 0,
    "duplicateBankAccounts": [
      "acct-1"
    ],
    "duplicateEmployeeIds": []
  }
}

Limitations and assumptions

No worker existence, bank verification or fraud conclusion is established. Shared accounts may be legitimate.

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 Fictitious Vendor W-9 Bank Duplicate Detector: Vendor-master anomalies can include shared tax/account identifiers and active records missing them. Identity duplication is an investigative lead. For a complementary task, use Lapping Receipt Delay Pattern Detector: Possible lapping patterns can involve equal amounts applied across different customers. A matching pair is an investigative lead.

References

Ghost Employee Payroll Masterfile Match Tester — tool.io

Similar or alternative tools

Fictitious Vendor W-9 Bank Duplicate Detector
Vendor-master anomalies can include shared tax/account identifiers and active records missing them. Identity duplication is an investigative lead.
Lapping Receipt Delay Pattern Detector
Possible lapping patterns can involve equal amounts applied across different customers. A matching pair is an investigative lead.