# How payroll should connect to cash planning and accounting

> Map the evidence and ownership between an approved payroll, the funding required, payment outcomes and the accounting record.

- **Source:** https://www.runproper.com/resources/payroll/payroll-to-cash-and-accounting-handoffs
- **Publisher:** Proper Technologies Inc.
- **Format:** Article · Payroll
- **Reading time:** 2 min

Connect payroll to cash and accounting through explicit handoffs: the approved calculation, required funding, authorized payment instructions, confirmed processing and reconciled records. Give each handoff an owner, a status and evidence of completion.

## Separate amounts that answer different questions

The payroll team, treasury or cash owner, and accounting team may look at the same run for different reasons. One needs to explain employee calculations, another needs to prepare funding, and another needs to record the cost and related obligations. A single total rarely answers all three questions.

Define the amounts each team receives and the period they describe. Include employer costs and other required obligations where they belong in the configured process. Have the responsible specialists establish the actual treatment; a workflow diagram should not invent jurisdiction-specific rules.

## Make the approved run the starting reference

Proper’s Payroll Table Stakes film introduces the connection between pay, what remains owed and the full cost of the team. Its purpose is to show the broader workflow. Confirm which functions the available product and connected providers actually perform.

For implementation, associate the cash and accounting handoffs with the particular approved run. If a correction changes that run, the receiving teams need to know which figures changed and whether an earlier instruction has already proceeded. Sending another spreadsheet without that context can create ambiguity.

## Use status words that describe real events

“Ready” should mean something specific. It might mean the calculation is complete, the reviewer approved it, funding is available or the provider accepted an instruction. Those events happen at different points and can fail independently.

Define your operating states in plain language and retain the relevant acknowledgment. A submitted instruction is evidence of submission; it is not by itself evidence that every payment completed. Likewise, an accounting export is not proof that the receiving ledger accepted and reconciled it.

-   Calculation prepared: supported inputs and unresolved questions are visible.
-   Approved: the authorized reviewer accepted the identified version.
-   Submitted or processed: the responsible provider confirms the actual state.
-   Recorded and reconciled: the accounting owner verifies the receiving result.

## Design the exception route before the first live run

Ask what happens if funding is insufficient, a handoff is rejected or accounting receives a different amount. Assign an owner and a next step for each case. Avoid automatic retries that could create duplicate instructions when the previous outcome is uncertain.

Use a synthetic correction to test the complete route. Start with an approved run, add a late change, obtain the required review, then inspect cash and accounting results. The value of the exercise is the evidence it produces about your actual configuration, including any manual work.

## Questions & answers

### Does payroll approval authorize every downstream action?

That depends on the organization’s authority model. Define calculation approval, payment release and accounting review explicitly rather than assuming one approval covers all of them.

### What should a failed handoff show?

Show the affected run and version, the last confirmed state, the failure or unresolved outcome, a responsible owner and the next permitted action.
