Pre-funding vs actuals for Italian payroll: what each does to your cash flow

Every platform that runs payroll in Italy has to decide when the money moves. The choice sounds like a finance detail. It is not. It shapes your working capital, your exposure to client credit risk and the amount of reconciliation work your operations team carries each month.

This article compares the main funding models and what each means for platform cash flow.

The models in plain terms  

Pre-funding. The client sends the full payroll cost to the local provider before payment runs. Net pay, social contributions and withholding taxes are covered by cash already in the account. The provider pays employees and authorities from those funds.

Actuals. The provider pays employees and authorities first, using its own liquidity or the platform’s. It then invoices the client for what was actually paid. The client reimburses after the fact.

Most real arrangements sit somewhere between these. Some platforms pre-fund net pay only and settle contributions and taxes on actuals. Others pre-fund for new or higher-risk clients and move trusted clients to actuals.

What pre-funding does for cash flow  

Pre-funding removes the gap between paying out and getting paid. The platform does not finance the client’s payroll. Cash arrives before it leaves.

The benefits are clear:

• No working capital tied up in client payroll.
• No credit exposure if a client stops paying.
• Simple risk story for finance and audit teams.

The costs are less visible:

• Clients feel the cash drag. They must fund earlier than they would with their own payroll.
• Late client transfers delay pay runs, so cut-off discipline becomes a client-facing issue.
• Estimates must be right. If the funded amount is short, someone has to chase a top-up before the run.
• Excess funds must be tracked and returned or credited, which adds a reconciliation step.

What actuals does for cash flow  

Actuals feels easier for the client. They pay for what happened, after it happened. Variances such as late hires, unpaid leave and corrections flow through naturally, because the invoice follows the real payroll.

The platform pays for that convenience:

• Someone must fund the payroll in advance. That is usually the provider or the platform.
• Credit risk sits with the platform. A client that disputes an invoice or goes insolvent leaves a hole.
• Employee pay and statutory payments cannot wait for a slow client, so the platform carries the timing gap in full.
• Growth makes it worse. More clients means more cash tied up, at the same time.

For a platform with a thin balance sheet, actuals at scale is a financing problem disguised as a payroll product.

Where Italy adds friction  

Italian payroll has several moving parts that each follow their own timing. Net pay, social contributions, withholding taxes and other periodic items do not all settle on the same day. A funding model has to cover each stream, not only net salary.

This matters for the hybrid designs. If you pre-fund net pay but run contributions on actuals, you still carry a timing gap on the statutory side. Define which items are covered by which model, and write it down in the contract and in the data flow.

Corrections also matter. Retroactive changes, adjustments and late data change the real cost after the run. Under pre-funding they create a true-up. Under actuals they create a supplementary invoice. Both need a clear owner.

How to choose  

Use these questions to decide per client segment:

• Who carries credit risk? If you cannot absorb a client default, do not offer actuals without security or limits.
• How predictable is the payroll? Stable headcount suits pre-funding with small true-ups. Volatile headcount creates frequent shortfalls and refunds.
• How strong is your liquidity? Actuals needs a funding line or reserves sized to your growth plan, not to today’s client count.
• What does the client expect? Enterprise buyers often push for actuals. Smaller companies usually accept pre-funding if the cut-off is clear.

A practical pattern is pre-funding by default, with actuals as a earned status. Move a client only after a track record of on-time payment, and keep the right to revert.

Operations that make either model work  

The model matters less than the data behind it. Three things keep cash flow predictable:

• A fixed cut-off calendar. Funding deadlines, data deadlines and payment dates should be agreed per client and shared with everyone.
• Early cost estimates. Send the expected total before the run, so the client can fund the right amount the first time.
• Clean reconciliation. Match every payment to a payroll line, every refund to a funding event and every adjustment to its cause.

When these are in place, the choice between pre-funding and actuals becomes a risk and pricing decision. When they are missing, both models produce disputes.

What this means for partnership teams  

If you are adding Italy to your platform, agree the funding model before you agree the integration. The model decides what data you need to exchange, how often and in which format. It also decides who sees a shortfall first and who has to fix it.

Partnership teams that settle this early avoid the common failure: a technically live integration with an unresolved cash question.

Partnership teams can request the data-exchange specification to see how funding, cut-off and reconciliation data are structured.