Skip to content

Payouts

A payout is how you pay an account representative for what they’ve earned — the commissions, credits, and deductions that have accumulated in their ledger. This guide explains how you assemble and issue a payout, what a payout statement shows, and how corrections keep everyone whole when something changes after the fact.

Everything a rep is owed but hasn’t been paid yet sits as outstanding items — commissions from their merchant portfolio, plus any credits and deductions you’ve recorded. Issuing a payout is the act of choosing which of those items to pay now and freezing them into a single record.

You start a payout from a rep’s ledger using Issue Payout. That opens the payout builder for that specific rep. Reps can’t issue payouts to themselves — only owners and admins can create them.

The builder has two parts:

  1. The setup card at the top, where you set:

    • Effective date — when this payout occurred. If you backdate it, a short note reminds you how far back you’ve set it. The effective date is the payout’s period attribution; it sits alongside a separate Created date (the moment you actually issue it) everywhere the payout appears.
    • Memo (optional) — a free-text note like “Q1 2026 commission payout — paid by check #4421”. It appears on the statement and on the rep’s ledger entry.
  2. The Outstanding items table, listing everything payable, grouped for easy scanning. Each item carries a colored type pill:

    • Commission (green)
    • Credit (teal)
    • Deduction (red)

    Every item starts checked. Uncheck anything you don’t want to include in this run — for example, an item you’d rather hold for a later payout. You can search by MID, DBA, or memo, and filter by type using the pills above the table.

As you check and uncheck items, a Payout summary panel on the right keeps a running tally: a subtotal for commissions, credits, and deductions, and the Net Payout at the bottom. Deductions reduce the net; credits add to it.

When you’re happy with the selection, choose Issue. The button shows the exact net you’re about to pay.

Once issued, the payout’s contents are frozen — the individual line items are a permanent snapshot of exactly what was paid, and they never change. If something changes after a payout is issued, MySplitPay reconciles it through corrections rather than by rewriting the payout — see Corrections and drift below.

The Payouts page lists every payout you’ve issued. Across the top, a summary strip gives you the shape of things at a glance:

  • Paid This Month — the total paid out this month, across your reps.
  • Outstanding — what’s still owed but not yet paid, drawn from rep ledger balances.
  • Last Payout Run — when you most recently issued payouts.
  • Pending Corrections — corrections waiting to be paid on a future payout (more on these below).

Below the strip, each row shows the payout’s effective date and payout number, its created date, the rep, how many line items it contains, the amount, and a status badge. You can search by rep or payout number, filter by status, and narrow to a date range. Select any row to open its detail. Export downloads the current, filtered list as a CSV.

Account reps see a version of this page scoped to their own payouts only.

Opening a payout shows its statement — the full detail of what was paid. Think of it as a pay stub for the rep.

At the top you’ll find the payout amount, its effective and created dates, who issued it, and the memo if one was entered. A Composition card breaks the total into its commission, credit, and deduction subtotals so the makeup of the payout is clear at a glance.

Below that is the Line Items table — the frozen snapshot of every item the payout paid. Each line shows its type, a description, its effective and created dates, and its amount. Commission lines also show the rate they were paid at and the amount it was applied to — for example, 40% of $2,500 — so the math behind each commission is transparent. A small lock indicator marks that these values are fixed and can’t be edited. You can search, filter by type, sort, and page through the line items just like any other table.

Every payout statement can be downloaded with Statement, which produces a CSV covering the payout’s details, its line items, and any corrections attached to it. Both you and the rep can download it.

Account reps see the same statement for their own payouts, as a read-only pay stub.

Issued payouts never change — but the world behind them sometimes does. If you edit something after a payout was issued that would have changed what it paid, MySplitPay flags the difference and helps you make it right on the rep’s next payout. This keeps the historical record honest (the original payout stays exactly as paid) while making sure nobody stays over- or under-paid.

Outstanding items commissions, credits, deductions Payout issued line items freeze A change lands rate edits, revised reports Correction created posted as credit or deduction corrections ride the rep's next payout
Issued payouts never change — later differences become corrections on the next payout.

A payout can end up out of step with current data when, after it was issued, you:

  • Change a commission rate — for example, correcting a rep’s rate on a merchant from 40% to 30%.
  • Change which rep covers a merchant — adding, removing, or re-dating an assignment that affects a period already paid.
  • Edit the amount of a credit or deduction that was included in a payout.
  • Delete a transaction that a payout had paid.

When that edited item is genuinely new — a period that was never paid — nothing needs correcting; it simply becomes payable on the next payout. A difference only arises when the change touches money a payout already froze.

When you make an edit that affects an already-issued payout, MySplitPay pauses before saving and shows a correction prompt. It spells out the impact in plain terms — for example, that the change leaves a rep overpaid or underpaid by a specific amount across one or more issued payouts — and lists each affected payout side by side: what it paid at payout, what it would be as of now, the difference, and whether that’s an overpayment or an underpayment.

You then choose how to proceed:

  • Create correction (recommended) — MySplitPay posts a correction that will settle the difference on the rep’s next payout. Underpayments become a credit; overpayments become a deduction. The issued payout stays exactly as it was.
  • Save without correction — your edit is applied, but the affected payout is marked as drifted until someone corrects it later.
  • Cancel — nothing is saved; your pending edit stays in the form.

Corrections don’t rewrite the original payout. Instead they wait as outstanding items and ride the rep’s next payout automatically — so the next time you issue a payout for that rep, the correction is already there to include.

On a payout’s statement, corrections show up in two places:

  • A Corrections section lists each correction attached to the payout — its type (credit or deduction), the reason it was created, its dates, its amount, and a status. Assigned (shown in payout blue) means the correction has already been paid on a later payout, and links to it; Unassigned means it’s still waiting to be paid. Both you and the rep can see this section, because it explains what’s coming on the next payout.
  • If a payout still has an unresolved difference, its statement shows a drift banner at the top and flags the specific line items affected — Needs correction while it’s outstanding, then Correction pending or Corrected once a correction has been created to cover it. These flags are visible to you as the ISO, not to the rep.

On the payouts list, a payout with an unresolved difference shows a Has drift status (with the outstanding amount, such as Drift −$145.00); everything else reads Settled. Once corrections cover the difference, the payout returns to Settled. You can filter the list to just drifted payouts to see what still needs attention, and the Pending Corrections figure on the summary strip tracks corrections that haven’t been paid yet.