A Professional Employer Organization Collects Social Security Numbers Through a Link-Only Files.com Inbox Form

A US professional employer organization runs payroll, benefits, onboarding, and HR compliance on behalf of the businesses it serves. Its family of companies supports thousands of client businesses representing tens of thousands of employees.

That model has a consequence built into it. When one of those businesses hires someone, the hire runs through the company: the paperwork, the payroll setup, the benefits enrollment, the compliance record. Collecting sensitive personal data from other companies' employees is not a side effect of the business. It is the business. And no piece of that data is more sensitive, or more unavoidable, than the Social Security number. Payroll does not run without one.

One Required Field Outside the Applicant System

The company had already moved much of its document intake into governed channels. Client businesses upload new-hire paperwork and benefits documents into a siloed folder per client on the company's own branded Files.com domain, and processing staff pull from there.

A Social Security number, though, is not a document. The applicant tracking software that manages applicants has no field for it. The company wanted one governed path for that number: a place inside a system it controls where an applicant at any client company can supply it, and where staff can process it.

The applicant tracking system is the system of record for applicant management, and nobody replaces a system of record over one field. Building custom software to capture a single sensitive value per hire was a disproportionate project for what is a structural, recurring obligation. And the people supplying the number are outsiders. They are employees of thousands of different client businesses who cannot be provisioned accounts or told to install anything.

A Registration Form Inside a Governed Platform

Whatever collected the number had to be reachable with nothing but a link. It had to capture the value inside a governed system. It had to keep each person's submission invisible to every other person. And it had to give staff a way to review and process submissions in bulk.

The company built it on the platform already carrying its paperwork: a Files.com Inbox.

The company configured a permanent, branded Inbox with required registration and a custom form field for the Social Security number. Applicants need only a link, with no Files.com account or signup. The number is captured as a form field inside Files.com. Each submission remains invisible to every other applicant, while staff can review the registration record and export it to Excel for processing.

Nothing was installed at any client. No accounts were created. The applicant tracking system was not touched.

Every Number on the Record

With the Inbox in production, the company gained a governed intake for the one field its document channels did not cover.

• Social Security number collection runs through a governed form: the per-hire obligation the applicant system has no field for now has a home.
• Applicants need nothing but the link. There is no account, no software, and no visibility into anyone else's submission.
• Every number arrives on the record, in a registration log staff review and export for processing.
• The applicant tracking system stayed exactly where it was. The gap closed with a configured form, not a replacement project or custom code.

A New Field Without a New System

A value the system of record has no field for does not require a new system of record. It requires a governed channel that can ask the question and keep the answer, and for the company that channel was already running its file exchange.