Payout Reconciliation
What It Is
A reconciliation is the continuing explanation of what a processor deposit contains. The preparer starts with the payout and connects it to the money effects that support the processor’s reported net amount. When a processor divides a settlement across related transfers, the explanation can include several payouts in the same merchant context.
The workspace brings together candidate effects, selected claims, manually entered deductions and the resulting difference. Evidence strength helps the preparer choose; balance alone does not identify the right money. A fee or reserve entry explains a processor movement that staff can support with a note or document rather than inventing another payment.
Finalization is a separate decision from reaching balance. An eligible approver approves the explanation, and Rhythm creates requests for the transfer and applicable item recognition. Operational batch posting later turns those requests into ledger entries. The retained reconciliation therefore explains both the preparer’s choices and the approval that follows them.
What It Is Not
An operational batch groups accounting documents for posting and can contain work from several explanations. A reconciliation can draw from several original batches without becoming their owner. It also differs from month-end close, which evaluates a whole period. Explaining processor deposits does not establish a complete reconciliation of every movement in a bank account.
How It Is Used
Preparers review why candidates appear, claim those that belong and set aside weak suggestions that do not help. They enter processor deductions, inspect the difference and save the work for review. Concurrent work can fail because another person changed the version or another explanation already holds the money. Staff need to inspect that newer state before continuing.
Approvers finalize prepared explanations and use reversal when an approved explanation is wrong. The console saves local draft differences before finalizing, so an approver who changes holdings during that save may become a preparer. That interaction is material to a usable independent-review journey.
Its Facets
Explained payouts supply the net bank result. Money allocations preserve both the selected effects and their explanation. Manual explanation entries add the documented processor effects missing from payment records.
Set-aside suggestions keep review focused without resolving money. Balance and progress indicate preparation rather than approval. Record lifecycle protects the approved explanation and keeps abandoned drafts historical.
Independent approval connects preparation history to the approval decision. Correction history retains the reason and people behind reversal. Accounting requests carry the financial consequence into operational posting. Activity and original batches give reviewers a trace back through preparation and source documents.
How It Relates
Payouts provide the bank movements, settlement items provide the financial effects and exceptions describe concerns requiring investigation. Accounting configuration supplies posting accounts. Batch Management posts the generated requests, and Close Readiness reports unfinished approval or accounting work for the period.
What It Could Become
The product should define the full set of preparer activities before relying on independent approval as its primary control. A complete waiver administration flow and clearer draft-save review would make that decision visible. Import and evidence-upload extensions should preserve accountable approval and reversal rather than editing the finalized explanation in place.