Processor Payout
What It Is
A payout is the bank movement that finance staff want to explain after a processor settles money collected through a merchant account. Usually the processor sends a deposit. A day with refunds or charges can instead produce a debit, and a net-zero payout can still need an explanation. The payout records that result rather than treating every bank movement as incoming cash.
Staff identify it through its payout number, merchant account, processor reference when available, amount and dates. Those details let them compare the processor’s report with the bank and with earlier entries. Manual entry records what staff know now; it does not establish that either external party has independently confirmed the record. Keeping those facts separate is central to reviewing a deposit confidently.
What It Is Not
The payout is the net bank movement, while a settlement item is an individual financial effect contributing to it. Its reconciliation holds the explanation connecting those two views. It also differs from an operational batch, which organizes accounting work for posting. A saved payout alone does not establish bank agreement, successful reconciliation or completed ledger posting.
How It Is Used
A preparer starts with a processor report or bank deposit and records the payout in the correct merchant context. Readers use the payout list to locate it and inspect its standing. The preparer then opens an explanation, while an approver reviews the completed reconciliation. Staff can correct entry mistakes before the financial record is sealed.
Bank evidence is a separate review task. The service can record agreement or disagreement, but the current console control sends an incomplete request. A product manager evaluating this workflow therefore needs to distinguish available service behavior from a usable bank-verification screen. The published acceptance proposal must not treat a successful mock badge as proof that the live bank review works.
Its Facets
Entry origin explains how the record enters Rhythm and keeps that distinct from processor confirmation. Bank evidence supplies the independent statement and posted day supporting verification.
Reconciliation standing follows the current explanation, while the accounting day places the bank movement in the relevant period. Neither is a substitute for understanding the other.
Duplicate safeguards distinguish a reused processor reference from a deposit that merely looks similar. Supporting documents preserve the material an approver needs to inspect.
Entry cancellation keeps a mistaken payout recognizable without leaving it available for normal work. Reference number and activity support later retrieval and responsibility review.
How It Relates
The merchant and bank accounts come from accounting configuration. Reconciliation connects the payout to settlement money, exceptions describe outstanding concerns, and readiness puts those concerns in a period context. Operational batch posting completes the requested accounting entries. These relationships let staff follow one deposit without assuming that every part belongs to the same workflow.
What It Could Become
The product should provide complete bank-evidence entry and a clear path for acknowledging possible duplicates from the console. Processor imports could provide independently reported payout information later. Any extension should preserve the separate meanings of entry origin, bank agreement and reconciliation approval.