Payroll controls

Check a severance payment against the approved separation letter

A practical severance payment guide that names the evidence, the approver, and the close condition for the current close cycle.

Check a severance payment against the approved separation letter workflow illustration

Check a severance payment against the approved separation letter

Name the decision and the queue owner

The severance payment note should separate the request, the decision that is still open, and the person who can close it. Separate the request from the decision, because a complete request is not an approval. Write the decision in one sentence so the reviewer knows what would count as an answer. Name the trigger that brought the case into the queue. The severance payment record should let a second reviewer rebuild the decision from the severance calculation and the payroll register.

Give the case a stable identifier before any document is attached. Separate the request from the decision, because a complete request is not an approval. Keep the original request so a later correction does not erase the reason for the work. Record the requester and the promised response time. A sample severance payment review checks the separation letter, the severance calculation, and the surviving value in the payroll system.

State explicitly what is in scope and what is out of scope for the case. Distinguish a new request from a correction to an earlier one. A clean-looking status is not evidence that the underlying work is correct. Say which system of record governs if two sources disagree. Apply the same severance payment test to the payroll register and to the value that survives in the payroll system.

Map the source and the evidence trail

Attach the separation letter and the severance calculation to the case, label their versions, and record the time each was observed. Keep a version label on every file that can change. The record should show the source, the decision, and the surviving value in one place. Keep the original request so a later correction does not erase the reason for the work. The severance payment case note should show what the payroll system held at the time and who reviewed it.

Link each value to the field or page that supports it. A case that moves between owners should keep both owner periods visible. Record the export time beside any value taken from a system. Keep the original request so a later correction does not erase the reason for the work. For severance payment, compare the separation letter with the destination value rather than relying on a status label.

Keep a version label on every file that can change. Use the same case key in the queue and in the evidence extract. Name the repository where sensitive evidence is held. Mark missing evidence as missing, with a reason, rather than leaving a blank. The severance payment close note cites the payroll system, the approver, and the time of the final check.

Set the authority boundary

The payroll manager owns the decision in severance payment; the preparer may compare, label, and route but may not approve the outcome. Preparation, comparison, and follow-up may sit with the assistant. Keep emergency authority narrow and followed by a review note. A role change should trigger a review of queue access. In the severance payment queue, an item without a next action is treated as an exception.

If the team cannot reproduce the result from the record, the control is not finished. The record should show the source, the decision, and the surviving value in one place. If two roles share a queue, mark which one decides each item. A short written rule is easier to test than an unwritten habit. For severance payment, the working file keeps the separation letter and the severance calculation beside the decision note.

A role change should trigger a review of queue access. If the team cannot reproduce the result from the record, the control is not finished. The record should show the source, the decision, and the surviving value in one place. Approval, payment, records disposition, and policy exceptions stay with the named owner. Every severance payment handoff names the payroll manager and the field in the payroll system that will confirm the change.

Run the daily handoff

End the severance payment shift with an owner, a next action, and a due time on every open case. Open the day with a queue pass by age, owner, and missing evidence. Use the same definition across the queue and the review so the counts agree. The next reviewer should not have to ask which document is authoritative. The severance payment reviewer records the approver sign-off, the owner, and the next action in one place.

A case with no next action is an exception even if it says in progress. Keep the queue view readable on one screen. If the team cannot reproduce the result from the record, the control is not finished. Keep the original request so a later correction does not erase the reason for the work. A severance payment exception keeps the approver sign-off attached and routes the question to the payroll manager.

Open the day with a queue pass by age, owner, and missing evidence. Do not let a deadline expand a role beyond its written limit. A case with no next action is an exception even if it says in progress. Do not let a status update stand in for a verified event. In this severance payment case, the record points to the payroll system and names the payroll manager as the decision owner.

Handle exceptions without rewriting history

If the payment exceeds the approved separation amount, stop the dependent action and log the conflict in the payroll system rather than choosing the more convenient value. Keep the failed attempt and the correction in the same history. Preserve both values and the time each was observed. A clean-looking status is not evidence that the underlying work is correct. A sample severance payment review checks the separation letter, the severance calculation, and the surviving value in the payroll system.

Route one bounded question to the owner instead of negotiating in the queue. Check whether the exception came from a form, a rule, or a permission. Separate a data conflict from a policy conflict. The next reviewer should not have to ask which document is authoritative. Apply the same severance payment test to the payroll register and to the value that survives in the payroll system.

Check whether the exception came from a form, a rule, or a permission. The next reviewer should not have to ask which document is authoritative. Preserve both values and the time each was observed. Name the owner for every open item, including items waiting on someone else. The severance payment record should let a second reviewer rebuild the decision from the severance calculation and the payroll register.

Close with a verified destination value

The final severance payment check compares the approver sign-off with the surviving value in the payroll system; a status label alone is not a close. Verify that the surviving record is the one downstream teams will use. A case that moves between owners should keep both owner periods visible. Note the next review date before closing. For severance payment, compare the separation letter with the destination value rather than relying on a status label.

Record the close reason with the same codes used in the exception queue. Use the same definition across the queue and the review so the counts agree. Do not let a deadline expand a role beyond its written limit. Note the next review date before closing. The severance payment close note cites the payroll system, the approver, and the time of the final check.

A short written rule is easier to test than an unwritten habit. Tie the close note to the original request and the final evidence. If the team cannot reproduce the result from the record, the control is not finished. A clean-looking status is not evidence that the underlying work is correct. The severance payment case note should show what the payroll system held at the time and who reviewed it.

Review the pattern, not only the case

Review severance payment with a sample drawn from the queue export before the meeting, so the discussion cannot drift to memorable cases. Record the sample frame, the reviewer, and the criteria. Report a null result as clearly as a positive one. Report age and dependency, not only the total count. For severance payment, the working file keeps the separation letter and the severance calculation beside the decision note.

A clean-looking status is not evidence that the underlying work is correct. Report age and dependency, not only the total count. The next reviewer should not have to ask which document is authoritative. Do not let a deadline expand a role beyond its written limit. Every severance payment handoff names the payroll manager and the field in the payroll system that will confirm the change.

Keep the prior procedure available for comparison. Name the owner for every open item, including items waiting on someone else. Record the sample frame, the reviewer, and the criteria. Choose the sample from the export before the meeting. In the severance payment queue, an item without a next action is treated as an exception.

Keep the record ready for the next reviewer

Store sensitive severance payment evidence in the approved repository and keep only the reference and access path in the analysis note. Keep the source reference and the coded value in the same row. Keep the note short enough to read with the case. Name the owner and the date beside each decision. A severance payment exception keeps the approver sign-off attached and routes the question to the payroll manager.

A clean-looking status is not evidence that the underlying work is correct. Keep the note short enough to read with the case. The next reviewer should not have to ask which document is authoritative. Write the note so a reviewer can reconstruct the decision without a meeting. In this severance payment case, the record points to the payroll system and names the payroll manager as the decision owner.

Keep the source reference and the coded value in the same row. Write the note so a reviewer can reconstruct the decision without a meeting. Record event time separately from entry time. Do not store credentials or unnecessary personal data in the case. The severance payment reviewer records the approver sign-off, the owner, and the next action in one place.

This note is operational guidance, not accounting, tax, legal, or security advice. Use the back office support service and read the GAO Green Book before turning the routine into policy.