Sign payslips and contracts without opening each file.
The HR team at a hundred-person company generates a hundred PDF payslips each month. Before they go out they need to be signed by the director or the head of people. It is a repetitive, deadline-driven gesture: on the 30th they all have to ship.
The problem
The payroll system exports a hundred PDFs with names like
FIRSTNAME_LASTNAME_2026-04.pdf. The team needs them signed by the
authorised person before uploading to the employee portal or sending by email. Doing it
by hand means opening every PDF and placing the signature image a hundred times — a
multi-hour task that repeats every month.
The Fdo. flow
- Load the hundred payslips of the month. Drag the whole folder into the browser.
- Set up the signature once. Image of the responsible person, in the position on the last page where the "Received" box is.
- Download the ZIP. Each PDF keeps its original filename, ready to upload to the employee portal in bulk or to send out from the internal system.
Personal data
A payslip contains salary, bank details, ID and address. Sending it to a SaaS tool to sign means adding a data processor to the chain, with the contract and paperwork that implies. Fdo. avoids that step because it does not receive the files: the signing happens inside the HR person's browser, and the PDF only travels to its usual destination.
The HR team keeps its existing flow (payroll system → folder → employee portal) and slots Fdo. in as a step inside the browser. No new vendor in the data processing chain.
What it isn't
Fdo. places a simple signature on the PDF. It does not replace an electronic signature system for the employee with two-factor and audit trail when the collective agreement or internal policy requires that; those usually need dedicated tools. Fdo. covers the employer's signature that the company adds so that the payslip is validated before delivery.