Document retention for Italian payroll: what to keep and who keeps it

Retention is a shared job in Italian payroll. A global platform, a local partner and the employer each hold part of the record. Problems start when nobody knows which part is theirs.

This FAQ covers what to keep and who keeps it. It does not state retention periods. Periods depend on the document type and on the authority asking. Confirm them with your local payroll provider and put them in writing.

What documents make up the payroll file?  

Think in groups.

• Hiring records. Employment contract, the notice of hiring sent to the authorities, identity and tax code details, and any signed policies.
• Pay records. Payslips, the monthly calculation, adjustments, bonuses, expense reimbursements and final settlement.
• Contribution and tax records. Social security filings, withholding calculations, payment receipts and year-end certifications.
• Time records. Attendance, leave, sick leave notices, overtime and any collective agreement rules that drive them.
• Compliance records. Health and safety training, medical fitness certificates where required, and data protection consents or notices.
• Termination records. Resignation or dismissal letters, final pay calculation and exit paperwork.

Who keeps the legal payroll record?  

In Italy the employer carries the legal duty to keep the mandatory employment record. In an Employer of Record model, the EOR is the legal employer. So the EOR, or its local payroll provider acting for it, holds the official record.

Your platform may be the contract holder with the end client. That does not move the legal duty. You can hold copies. You are not the system of record unless the contract says so.

What should the platform keep?  

Keep what you need to run the service and answer your customers.

• Copies of payslips and summaries for display in your portal.
• The inputs you sent to the local provider and the date you sent them.
• Approval trails: who approved a change, when, and on what basis.
• The data-exchange logs between your systems and the partner’s.
• Customer contracts and the scope of service for each worker.

These copies support disputes and audits on your side. They do not replace the original record.

What should the local partner keep?  

The local payroll provider usually holds the working file.

• The full set of payslips and calculations.
• Filings made to social security and tax authorities, with proof of submission.
• Payment confirmations.
• The reasoning behind any manual correction.
• The collective agreement version applied to each worker.

Ask for this to be listed in your service agreement. A vague promise to keep records is not enough.

What should the end client keep?  

The client does not hold the legal record, but it holds facts the payroll depends on. These include worker schedules, approved leave, overtime instructions and workplace safety records for the site where the worker operates. If the client does not keep these, your payroll inputs have no source.

Write this into the client contract. Say what the client must keep, and that it must hand it over on request.

Can records be kept only in electronic form?  

Often yes, but do not assume it. Some documents need a proper signature or a certified format to be reliable as evidence. Ask your local provider which documents are safe to hold as digital files only, and which need a specific format or storage method. Record the answer.

How should access work?  

Set access by role. Payroll staff see pay data. Customer success staff see status and summaries. Partnership teams see aggregate and process data, not individual salaries unless needed.

Personal data in a payroll file is sensitive in practice and regulated by data protection law. Keep access logs. Review them on a schedule you can defend.

What happens when a partner relationship ends?  

This is where records get lost. Before you sign, agree on three points.

• The partner returns the full file in a usable format.
• The partner keeps its own copy for as long as the law requires it to.
• Both sides know who answers an authority request after the handover.

Test the return process before you need it. Ask for a sample export during onboarding.

What should the data exchange include?  

A clean exchange makes retention easier. Each record should carry a worker reference, a document type, an issue date, a version and a source system. Corrections should be new versions, not overwrites. That gives you a history that matches what the partner holds.

A short checklist  

• List each document type and name the keeper.
• Put retention periods in the contract, confirmed by the local provider.
• Define what the client must keep and hand over.
• Agree on format, access and deletion rules.
• Plan the return of records at exit.
• Test the export before go-live.

Partnership teams that want to align on a shared record model can request the data-exchange specification.