Revenue controls

Reconcile a merchant settlement to the daily sales summary

A practical merchant settlement reconciliation guide that names the evidence, the approver, and the close condition for the current close cycle.

Reconcile a merchant settlement to the daily sales summary workflow illustration

Reconcile a merchant settlement to the daily sales summary

Name the decision and the queue owner

The merchant settlement reconciliation note should separate the request, the decision that is still open, and the person who can close it. Note the observation window; a case without a period cannot be compared later. Keep the original request so a later correction does not erase the reason for the work. A case that moves between owners should keep both owner periods visible. Apply the same merchant settlement reconciliation test to the fee detail and to the value that survives in the merchant portal.

A clean-looking status is not evidence that the underlying work is correct. Record the requester and the promised response time. A short written rule is easier to test than an unwritten habit. If the team cannot reproduce the result from the record, the control is not finished. The merchant settlement reconciliation record should let a second reviewer rebuild the decision from the daily sales summary and the fee detail.

A clean-looking status is not evidence that the underlying work is correct. Do not let a deadline expand a role beyond its written limit. Name the trigger that brought the case into the queue. Give the case a stable identifier before any document is attached. A sample merchant settlement reconciliation review checks the merchant settlement, the daily sales summary, and the surviving value in the merchant portal.

Map the source and the evidence trail

Attach the merchant settlement and the daily sales summary to the case, label their versions, and record the time each was observed. State whether the evidence is confirmed, inferred, or unavailable. A clean-looking status is not evidence that the underlying work is correct. The next reviewer should not have to ask which document is authoritative. The merchant settlement reconciliation close note cites the merchant portal, the approver, and the time of the final check.

State whether the evidence is confirmed, inferred, or unavailable. A clean-looking status is not evidence that the underlying work is correct. The next reviewer should not have to ask which document is authoritative. Record who supplied each document and when it arrived. The merchant settlement reconciliation case note should show what the merchant portal held at the time and who reviewed it.

Name the repository where sensitive evidence is held. A case that moves between owners should keep both owner periods visible. Keep the original request so a later correction does not erase the reason for the work. Preserve a conflicting value instead of overwriting the first one. For merchant settlement reconciliation, compare the merchant settlement with the destination value rather than relying on a status label.

Set the authority boundary

The controller owns the decision in merchant settlement reconciliation; the preparer may compare, label, and route but may not approve the outcome. If two roles share a queue, mark which one decides each item. Name the backup owner and the coverage window in advance. The record should show the source, the decision, and the surviving value in one place. Every merchant settlement reconciliation handoff names the controller and the field in the merchant portal that will confirm the change.

Name the owner for every open item, including items waiting on someone else. If two roles share a queue, mark which one decides each item. A clean-looking status is not evidence that the underlying work is correct. Use the same definition across the queue and the review so the counts agree. In the merchant settlement reconciliation queue, an item without a next action is treated as an exception.

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. If the team cannot reproduce the result from the record, the control is not finished. A delegation needs a scope, a limit, an end date, and a named backup. For merchant settlement reconciliation, the working file keeps the merchant settlement and the daily sales summary beside the decision note.

Run the daily handoff

End the merchant settlement reconciliation shift with an owner, a next action, and a due time on every open case. Keep the queue view readable on one screen. A case that moves between owners should keep both owner periods visible. A handoff is complete only when the receiver acknowledges it. In this merchant settlement reconciliation case, the record points to the merchant portal and names the controller as the decision owner.

Do not let a status update stand in for a verified event. Log the handoff time when a case crosses a shift. A short written rule is easier to test than an unwritten habit. Check that the owner is actually available before assigning. The merchant settlement reconciliation reviewer records the bank deposit, the owner, and the next action in one place.

Keep the queue view readable on one screen. The record should show the source, the decision, and the surviving value in one place. Leave the next shift a queue that needs no chat history. Check that the owner is actually available before assigning. A merchant settlement reconciliation exception keeps the bank deposit attached and routes the question to the controller.

Handle exceptions without rewriting history

If the settlement excludes a sales day without explanation, stop the dependent action and log the conflict in the merchant portal rather than choosing the more convenient value. Use the same definition across the queue and the review so the counts agree. When access blocks the work, name the system, role, and approver. The record should show the source, the decision, and the surviving value in one place. The merchant settlement reconciliation record should let a second reviewer rebuild the decision from the daily sales summary and the fee detail.

Record the stop reason and the release decision together. Name the owner for every open item, including items waiting on someone else. Do not let a deadline expand a role beyond its written limit. Use the same definition across the queue and the review so the counts agree. A sample merchant settlement reconciliation review checks the merchant settlement, the daily sales summary, and the surviving value in the merchant portal.

An escalation that ends in silence remains open. When access blocks the work, name the system, role, and approver. Use the same definition across the queue and the review so the counts agree. Name the owner for every open item, including items waiting on someone else. Apply the same merchant settlement reconciliation test to the fee detail and to the value that survives in the merchant portal.

Close with a verified destination value

The final merchant settlement reconciliation check compares the bank deposit with the surviving value in the merchant portal; a status label alone is not a close. Record the approximate value, the approver, and the final check time. Tie the close note to the original request and the final evidence. Note the next review date before closing. The merchant settlement reconciliation case note should show what the merchant portal held at the time and who reviewed it.

Test one closed case by rebuilding it from the evidence map. Do not let a deadline expand a role beyond its written limit. Use the same definition across the queue and the review so the counts agree. A short written rule is easier to test than an unwritten habit. For merchant settlement reconciliation, compare the merchant settlement with the destination value rather than relying on a status label.

Tie the close note to the original request and the final evidence. If the destination is another team, require an acknowledgment. If the team cannot reproduce the result from the record, the control is not finished. Record the close reason with the same codes used in the exception queue. The merchant settlement reconciliation close note cites the merchant portal, the approver, and the time of the final check.

Review the pattern, not only the case

Review merchant settlement reconciliation with a sample drawn from the queue export before the meeting, so the discussion cannot drift to memorable cases. The next reviewer should not have to ask which document is authoritative. A clean-looking status is not evidence that the underlying work is correct. A short written rule is easier to test than an unwritten habit. In the merchant settlement reconciliation queue, an item without a next action is treated as an exception.

Separate what was observed from what the team believes caused it. The next reviewer should not have to ask which document is authoritative. Do not let a deadline expand a role beyond its written limit. Report a null result as clearly as a positive one. For merchant settlement reconciliation, the working file keeps the merchant settlement and the daily sales summary beside the decision note.

Keep the original request so a later correction does not erase the reason for the work. Separate what was observed from what the team believes caused it. Check whether the definition changed during the period. Include a routine case, a reopened case, and a cross-owner handoff. Every merchant settlement reconciliation handoff names the controller and the field in the merchant portal that will confirm the change.

Keep the record ready for the next reviewer

Store sensitive merchant settlement reconciliation evidence in the approved repository and keep only the reference and access path in the analysis note. Record event time separately from entry time. The next reviewer should not have to ask which document is authoritative. Keep the source reference and the coded value in the same row. The merchant settlement reconciliation reviewer records the bank deposit, the owner, and the next action in one place.

If the team cannot reproduce the result from the record, the control is not finished. Record event time separately from entry time. Archive the extract with the study so it can be repeated. Name the owner for every open item, including items waiting on someone else. A merchant settlement reconciliation exception keeps the bank deposit attached and routes the question to the controller.

Label the version of every file that can change. Name the owner and the date beside each decision. A clean-looking status is not evidence that the underlying work is correct. Archive the extract with the study so it can be repeated. In this merchant settlement reconciliation case, the record points to the merchant portal and names the controller as the decision owner.

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.