How-toReviewed 2026-09-29

Pay commissions through a payout run

Pay every approved channel-partner commission of a set of books in one batch: draft a Commissions payout run (one payout per partner), have it approved, export the bank file for net banking, then clear the run with the bank's UTRs.

Pay commissions through a payout run

A Commissions payout run gathers every approved commission of a set of books that still has something to pay, and drafts one payout per partner. A Finance Lead approves the batch, you export one bank file for net banking, and then clear the whole run with the UTRs the bank gives back.

Before you start

  • The commissions are Approved or Partially Paid (Approve a commission). Accrued ones are not picked.
  • Each partner has an active bank account on file, marked Primary if they have several (Record a buyer's or member's payout account). For any mode other than Cash or Cheque, a partner without one is skipped.
  • The books are active and have a bank ledger for the paying account.
  • Permissions, as the role editor names them:
    • to draft: the Create permission on Payments (and the View permission on Books to pick the books);
    • to approve: the Approve permission on Payments (the Administrator and the Finance Lead in the default roles; the Accountant can't);
    • to clear or cancel: the Edit permission on Payments.

Steps

  1. In the sidebar open Accounting > Payments and click Payout runs. The page lists the runs of the books chosen in the header's books switcher, with Run, Kind, Dates, Payouts, Amount and Status. See Payout runs.
  2. Click New payout run and set Kind to Commissions. The dialog "New payout run" reads "Approved channel-partner commissions with an outstanding, one payout per partner."
  3. Choose Books (the header's books by default) and, to pay one project's commissions only, a Project (optional). Set Payment date, Mode (NEFT by default) and From our account ("The books need a bank ledger for this account; leave blank to pay from cash."). The preview shows "<n> payee(s)", "Total <amount>" and a table of Payee, Bank account ("<bank> ····<last 4> · <IFSC>" or "none on file"), For ("Commission on <booking no>" for each commission) and Amount. A warning such as "2 payees have no active bank account on file and will be skipped for a NEFT run." names the partners who won't be paid.
  4. Click Draft <n> payout(s). You see "Run <run no> drafted with <n> payout(s)." and the run's page opens in Draft: Payouts in this run lists one Pending payout per partner, and Skipped payees lists anyone left out, with the reason. See Payout run.
  5. Click Approve. The confirmation "Approve the run?" reads "<n> payout(s) totalling <net> are approved for payment. Export the bank file next, upload it to net banking, then clear the run with the UTRs." Click Approve. You see "Run <run no> approved; export the bank file next." The status reads Approved and the Run card shows who approved it and when.
  6. Click Bank file (CSV) (shown once the run is Approved). The browser downloads "<run no>.csv" with the columns Payment no, Payee, Bank, Account number, IFSC, Amount, Mode, Narration, UTR and Status. Upload it to your net banking; that part happens outside the app.
  7. Once the bank has paid, click Clear <n> payout(s). The dialog "Clear the run" reads "Each payout posts its Payment voucher (member or partner ledger debited against its bills, bank credited). Enter the bank's UTR per payout; a payout that fails to post is reported and the others still clear." Set Cleared on, type each payout's UTR, and click Clear <n> payout(s). You see "Run <run no> cleared: <n> voucher(s) posted." The status reads Cleared.

What happens next

  • Each payout posts its own payment voucher: Dr the partner's ledger against each commission's bill, Cr the bank. The UTRs are stored in capitals.
  • Each commission moves to Paid, or Partially Paid if something is still open.
  • A payout the bank rejects is bounced on its own page (Bounce or correct a payment); the commission's bill reopens and the next Commissions run picks it up again.
  • Cancel run (Draft or Approved, nothing cleared yet) cancels every pending payout of the run: "Every pending payout of the run is cancelled; nothing was posted."
  • To draft runs on a schedule, Schedule automatic payout runs on the Payout runs page opens the rule builder, or switch on the seeded "Daily payout runs (system)" rule. Automatic runs are drafts unless the rule approves them.

If something goes wrong

  • A partner appears under Skipped payees with "The payee has no active bank account on file": record the account and draft another run. See Payee skipped from the payout run (trouble.accounting.payee-skipped-no-bank-account).
  • "<n> payout(s) could not be cleared; see the failures below." with a red card "<n> payout(s) failed on the last attempt" (for example "These books have no ledger for that bank account…"): fix the cause and click Clear again; payouts already cleared are not touched. See Payment saved but clearing failed (trouble.accounting.clearing-failed).
  • "The run holds no pending payout to approve.", "Some payouts of this run are already cleared; bounce them individually instead." or "That project is not promoted by the company these books belong to.": see Payout run cannot be approved, cleared or cancelled (trouble.accounting.payout-run-stuck).
  • "These books are inactive. Reactivate them under Books to post entries.": see These books are inactive (trouble.accounting.books-inactive).
  • The run page shows a note that a Finance Lead approves the run before the bank file is exported, and no Approve button: your role lacks the Approve permission on Payments. Ask a Finance Lead. See No access or no permission (trouble.admin.no-access).

Things to know

  • Pay everything due on or before doesn't narrow a Commissions run: commissions carry no due date, so every approved commission of the books with something outstanding is picked.
  • A run pays one partner once, however many bookings they earned on: their commissions become allocations of one payout.
  • An amount already held by another Pending payout is left out, so the same commission is not paid twice.
  • No TDS is taken on the run's payouts: the brokerage TDS was booked when each commission was approved.
  • Clear the run's payouts from the run, not one by one from their payment pages. Clearing them singly works but bypasses the approval, and if every payout is cleared that way the run stays Approved: its Clear button disappears and it can no longer be cancelled.

Related

  • Payout runsScreen

    Every payout run of the chosen books, the dialog that drafts a new run of member benefits, commissions or refunds, and the scheduled rules that draft runs automatically.

  • Payout runScreen

    One payout run: its payouts, skipped payees and failures, and the steps to approve it, export the bank file, clear it with the bank's UTRs or cancel it.

  • PaymentScreen

    One receipt or payout: its details, amounts and allocations, and the actions to clear it, bounce it, cancel it, edit it or delete it.

  • CommissionsScreen

    Every channel-partner commission accrued on bookings, with filters for status, payable state, project and books, and a shortcut to open each one.

  • Bank accountsScreen

    One register of every bank account you pay from or into: the promoter's collection, RERA separate, operative, GST and operating accounts, and the payout accounts of channel partners, vendors, buyers and society members, with joint holders and verification.

  • New ruleScreen

    Build an automation rule on a full page: which records it watches, what starts it, which records qualify, and the ordered actions it carries out.

  • Approve a commissionHow-to

    Approve an Accrued channel-partner commission so its accrual journal is posted (brokerage and GST input debited, the partner credited net of TDS, TDS payable credited) and it becomes payable.

  • Pay a commission on its ownHow-to

    Pay one approved channel-partner commission straight from its page: record the payout against the commission, then clear it so the payment voucher posts and the commission moves to Partially Paid or Paid.

  • Pay member benefits through a payout runHow-to

    Pay the transit rent, corpus and shifting charges due to society members and other allottees in one batch: a Member Benefits payout run accrues each due benefit row and drafts one payout per member, which is approved, exported as a bank file and cleared with the UTRs.

  • Record a buyer's or member's payout accountHow-to

    Add the bank account a buyer, channel partner or society member is paid into, on the Bank accounts register (or from a company's or allottee's page), so payout runs can pay them and the bank file carries their account number and IFSC.

  • Payout runs: member benefits, commissions and refundsConcept

    A payout run pays everything due from one set of books in one batch: the transit rent, corpus and shifting rows of live member offers (accrued first, one payout per member), approved channel-partner commissions (one per partner) or the refunds of cancelled bookings; it is drafted, approved, exported as a bank file and cleared with the bank's UTRs.

  • Receipts and payouts: allocation, clearing and the UTRConcept

    A receipt is recorded as Pending and settles the payer's open demands by itself, oldest due first; a payout is allocated to commissions or member rows by hand. Both post their voucher only when cleared and can be bounced afterwards; the UTR is the bank's transfer reference, typed on NEFT-style payments and per payout when a payout run is cleared.

  • Channel partner commissionsConcept

    Brokerage owed to the channel partner who sourced a booking: accrued from the booking with a basis percent or a gross amount, GST and TDS under 194H, approved to post the accrual journal, and paid out singly or through a Commissions payout run.

  • Payee skipped from the payout run: no active bank account on fileTroubleshooting

    A NEFT, RTGS or other bank-mode payout run drafts nothing for a member or channel partner who has no active bank account, lists them under Skipped payees, and picks them up in a later run once an account is added.

  • Payment saved but clearing failed, or payouts in a run could not be clearedTroubleshooting

    The payment was recorded as Pending but its voucher could not be posted, most often because the books have no bank ledger for the account the money went through; fix the cause and clear it again.

  • Payout run cannot be approved, cleared or cancelled: nothing pending, partly cleared, or the wrong booksTroubleshooting

    A payout run moves Draft to Approved to Cleared and can be cancelled only while some payout is still pending; a run whose payouts were handled one by one, or a run drafted against books that do not promote the project, refuses the action with the messages listed here.

  • "These books are inactive": nothing posts until the books are reactivatedTroubleshooting

    Posting a voucher, issuing a demand, recording a payment, starting a run or cancelling a booking is refused because the promoter's books are inactive; what is blocked and how to reactivate them.

  • "No access" or "You do not have permission": your role lacks a permissionTroubleshooting

    Every screen, button and picker is gated by a permission on a module; your role decides which you hold, so a missing one shows as a No access card, a refused action, a greyed-out button with a hover reason, or a picker that explains which permission it needs.

  • PaymentsScreen

    Every receipt and payout of the chosen books, with filters and search, and the buttons to record a receipt, record a payout or open the payout runs, the RERA sweeps, the TDS credits and the escrow withdrawals.

  • Pay outGuide

    Accrue, approve and pay channel-partner commissions, singly or in a payout run, pay member benefits (transit rent, corpus, shifting) in batches, and draw certified land and construction cost from the RERA separate account.