Wage record cross-checks
Wage verification works only by triangulation: attendance records, production records, and payroll must tell the same story independently, because any single record type can be prepared while three consistent ones rarely are.
Key takeaways
- Define the audit scope in writing before the visit, because a factory that knows the checkpoints prepares evidence while one kept guessing stages theater.
- Triangulate every important claim across documents, observation, and interviews — a single source of evidence is an anecdote, not a finding.
- Separate system findings from one-off lapses in the report, since only systemic gaps predict how the next order will run.
- Close every corrective action with evidence and a deadline, and verify closure on the next visit rather than accepting paper promises.
- Treat worker interviews as sampling, not interrogation: small, random, private conversations reveal whether procedures live on the floor or only in binders.
Wage-record checking is forensic rather than administrative: the auditor assumes nothing, compares independent traces of the same working weeks, and lets convergence — or its absence — speak. Patience and sampling discipline matter more than accounting skill.
Third-party evaluation matters because the auditor has no order to protect and no relationship to preserve. That independence is what lets uncomfortable findings reach the buyer intact, which is the entire point of paying for the visit.
The buyers who extract most value from audits run them as a program, not events: initial evaluation, corrective closure, periodic re-verification, with each round narrower and sharper than the last.
The three record families
Attendance traces come first: biometric logs, gate records, shift sheets. Auditors look for completeness across the sampled months, weekend and holiday patterns, and whether the records show the maintenance traces of real daily use rather than batch creation.
Production traces constrain the story: piece counts, line output logs, warehouse receipts. A month of high output with low recorded hours — or high hours with no output — breaks plausibility whichever direction it leans, and demands explanation.
Payroll traces close the loop: pay slips, bank transfer records, deduction items, minimum-wage and overtime-rate math. The rates must match statutory requirements for the locality and period, and deductions need documented worker consent. The underlying idea comes from the ISO 9000 family, which treats quality as a managed system of controlled processes rather than a final round of sorting.[1]
How the audit day runs
The day opens with scope confirmation: which areas are in bounds, which records will be pulled, who must be available for interviews, and what happens if access is refused. Factories that agreed all this in writing cooperate; factories meeting it for the first time negotiate, and the audit loses its first hour.
The walkthrough follows the product flow rather than the org chart — incoming material, storage, production lines, testing stations, packing, finished-goods warehouse. Flow-following surfaces handoff gaps that department tours politely skip. In practice, an independent supplier verification checks licenses, capacity, and quality systems before the buyer commits volume.
Document review runs in parallel with observation wherever staffing allows: licenses and certificates, quality manuals, recent production and QC records, corrective logs. Dates, signatures, and consistency across documents matter more than the polish of any single binder. Under the WTO TBT framework, solid conformity evidence is what keeps differing national regulations from becoming shipment-stopping surprises.[2]
Cross-check matrix
| Compare | Against | Mismatch signals |
|---|---|---|
| Biometric attendance | Shift sheets | Edited weekends, missing holidays |
| Recorded hours | Piece output | High output, low hours |
| Overtime hours | Payroll premiums | Flat pay for extra hours |
| Pay slips | Bank transfers | Cash gaps, missing receipts |
Any single mismatch triggers deeper sampling; two independent mismatches in one period constitute a system finding.
After the visit: from report to decision
Conditional approval is the normal outcome for developing factories: specific gaps, named owners, dated evidence of closure. Release order volume in stages tied to closure milestones rather than all at once on promises.
A rejection should name the re-entry path. Factories improve, and a buyer who states exactly what must change — with what evidence, by when — keeps a future option open while protecting the current season.
Share the corrective section with the factory promptly and require a dated response plan. Audit value decays fast: findings delivered weeks later meet changed personnel and faded memory, and closure rates collapse.
Senior factory attendance at the opening meeting predicts cooperation quality all day. When the owner or general manager attends, records appear faster and awkward areas open sooner; when only a junior handler appears, expect a managed tour.
Photograph the mundane, not just the violations: calibration labels, posted procedures, training boards, maintenance logs. Normal-state evidence is what future disputes need, and nobody photographs it twice.
Language discipline matters during interviews. Questions route through the auditor's interpreter, never through factory management, and answers are recorded privately. Relayed interviews through interested parties are not evidence.
Evening factory-dormitory observations, where the scope includes them, reveal working-hour realities that daytime records may disguise. Entry and exit patterns at shift change are hard to stage and easy to read.
Subcontracting discovered mid-audit should be mapped immediately: which processes, where performed, under whose control. Undisclosed outsourcing found by accident usually indicates more undisclosed outsourcing not yet found.
The auditor's independence needs visible protection on site: no gifts beyond courtesy, no factory-arranged transport that creates obligation, findings discussed with the buyer first. Small courtesies accepted casually become leverage later.
Worth remembering
An audit measures the system that will make your next order, not the samples on today's table. Judge the factory by its routines under normal pressure — records, handoffs, discipline — because those routines are what your goods will inherit.
Sources
- Wikipedia: ISO 9000 —— Overview of the ISO 9000 family of quality management standards.
- WTO: Agreement on Technical Barriers to Trade —— WTO portal for the TBT Agreement covering technical regulations, standards and conformity assessment.
Frequently asked questions
Which months should auditors sample?
Peak-season months plus one off-peak month, typically three months spanning the last year. Peak months stress the working-hour limits hardest, which is exactly where compliance systems prove or fail themselves.
How do worker interviews support the check?
Private interviews confirm whether recorded hours match lived experience and whether pay arrives as documented. Small random samples suffice — five to eight workers per visit — because the goal is corroboration, not a census.
What if the factory uses piece rates?
Then output records become the anchor: auditors verify that piece earnings at stated rates reach minimum wage for actual hours, and that overtime premiums apply where hours exceed limits. Piece systems need more checking, not less.
Are bank transfer records required?
They are the strongest payment evidence where available, since cash claims without receipts prove little. Auditors request them routinely; absence does not equal violation but shifts weight onto other corroboration.
Strategy is a craft, not a deliverable. Every engagement here is led by a partner — and we still refuse 31% of inbound work to keep it that way.
— Frog Sink House, Portland & Lisbon