NirmaanOne Help
ScreenReviewed 2026-09-29

Payout runs

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 runs

A payout run pays everything that is due from one set of books in one batch: society members' benefits, channel partners' approved commissions, or the refunds of cancelled bookings. This page lists the runs and is where you draft a new one.

Where to find it

Payout runs in the header of the Payments list. The Runs breadcrumb on a payout run's page brings you back here. The notification sent when payout runs are drafted automatically tells you to "Open Payments > Payout runs to approve and export the bank files." There is no sidebar item for this page.

You need the View permission on Payments. Without it the page shows "No access" and "You do not have permission to view payments. Ask your administrator."

Before you start

  • Member benefits: the member's offer must be Issued, Accepted or Signed, with dated benefit rows such as transit rent, corpus or shifting. Ready-made benefit plans for offers are kept under Tenant Benefits. Each benefit's charge component needs a ledger mapping in the books (see Component mappings).
  • Commissions: the commissions must be approved on their own Commission page.
  • Refunds: the booking must have been cancelled with a refund in the Cancel booking wizard, which creates a pending refund payout.
  • For a bank transfer, the payees need an active bank account on file, and the books need a ledger for the account you pay from.

What you see

The header reads "Payout runs" and "Pay everything due from one books in one action: member benefits (accrued first, one payout per member), approved commissions (one per partner) or the refunds of cancelled bookings. Draft, approve, export the bank file, then clear with the bank's UTRs."

The Books switcher in the header picks which books' runs are listed, as on the Payments list.

  • Kind: Any kind, Member Benefits, Commissions or Refunds.
  • Status: Any status, Draft, Approved, Cleared or Cancelled.
  • Search: by run number (placeholder "Search by run number").

Columns

Column What it shows
Run The run number (PR-, the financial year and a running number), which opens the run, with the books and project underneath.
Kind The kind badge: Member Benefits (purple), Commissions (amber) or Refunds (blue), with the mode and the last four digits of the paying account, or "(cash)".
Dates "paid …", the payment date, and "due up to …", the date the run collected dues up to.
Payouts How many payouts the run holds, with "… skipped, … failed" underneath when some payees were skipped or failed.
Amount The net amount the run pays.
Status Draft (grey), Approved (blue), Cleared (green) or Cancelled (red).
(actions) The eye icon (tooltip "Open").

The newest runs come first. When there are none, the grid reads "No payout runs yet".

Automatic payout runs

This card lists the scheduled workflow rules that draft payout runs on a timetable: "Workflow rules that create these runs, on a cadence or the moment an event happens. Manual runs stay available; an automatic run is an ordinary run whose notes name the rule." Each rule shows its name (a link to the rule's page, see Rule), Active or Inactive, its schedule, its project or "Every project", when it runs next and how its last run went. With no rules it reads "No schedule yet."

The card shows when you have the View permission on Workflow Rules.

What you can do

New payout run

Opens the New payout run dialog.

  • Who: anyone with the Create permission on Payments. In the default roles that is the Administrator, Finance Lead and Accountant. Without it the button isn't shown.

The dialog explains the kind you choose:

  • Member Benefits: "Transit rent, corpus and shifting rows of live member offers due on or before the as-of date. The run first accrues them (expense against the member's ledger, one bill per row), then drafts one payout per member."
  • Commissions: "Approved channel-partner commissions with an outstanding, one payout per partner."
  • Refunds: "The pending refund payouts that booking cancellations created, collected for one bank transfer."

Fill in:

  • Kind: Member Benefits by default.
  • Books: placeholder "Choose the books"; it starts on the books chosen in the header (your organization's books are listed under Books). The list needs the View permission on Books.
  • Project (optional): leave it on "Every project of the books", or pick one project. It shows with the View permission on Projects.
  • Pay everything due on or before: today by default. Rows and commissions due up to this date are collected.
  • Payment date: today by default.
  • Mode: NEFT by default; any of the nine modes.
  • From our account: the books' company's active bank accounts, shown as bank, last four digits and purpose. Leave it blank to pay from cash (placeholder "Cash"; "Pick the books first" until the books are known). Listing the accounts needs the View permission on Bank Accounts. Hint: "The books need a bank ledger for this account; leave blank to pay from cash."

As you fill it in, a preview shows who would be paid: a badge with the number of payees ("3 payees"), "Total …", and a table of Payee (with "Member …" and the membership number, or the party kind, then the project and booking), Bank account (bank, last four digits and IFSC, or "none on file" in amber), For (the rows or commissions being paid, with due dates, for example "Transit Rent installment 2 (…)") and Amount. If the preview can't be loaded, its error shows in the dialog.

If some payees have no bank account and the mode isn't Cash or Cheque, a warning reads, for example, "3 payees have no active bank account on file and will be skipped for a NEFT run." (or "1 payee has …" for a single payee).

Draft payouts

The main button, Draft … payouts, creates the run as Draft with one Pending payout per payee. The message reads "Run … drafted with … payouts." and the run's page opens.

  • Who: anyone with the Create permission on Payments.
  • Greyed out: when no books are chosen or the preview finds no payees. No reason is shown on hover.
  • What happens next:
    • Member Benefits: before drafting the payouts, the run posts a journal for each member's offer that has due rows not yet accrued: the benefit expense against the member's ledger, one bill per row, dated the "due on or before" date. Then it drafts one payout per member that settles those bills. A member whose benefit component has no ledger mapping is skipped with the reason "Charge component … has no ledger mapping in books …".
    • Commissions: one payout per channel partner for their open approved commissions.
    • Refunds: the pending refund payouts are gathered into the run as they are.
    • Payees that can't be drafted are listed under Skipped payees on the run page with the reason, for example "The payee has no active bank account on file".
  • If it's refused, the reason shows in the dialog, for example "These books are inactive. Reactivate them under Books to post entries.", "That project is not promoted by the company these books belong to." or "A bank ledger must point at a bank account owned by the books' company."

Close

Closes the dialog without drafting anything.

Open

The eye icon on a row, or a click on the run number, opens the Payout run.

  • Who: anyone who can see this list.

Schedule automatic payout runs

On the Automatic payout runs card. Opens the New rule page with a payout run preset, so you can have runs drafted on a timetable.

  • Who: anyone with the Create permission on Workflow Rules. Without it the button isn't shown.

Statuses

  • Draft: drafted; the payouts are Pending and nothing has been paid.
  • Approved: approved for payment; the bank file can be exported.
  • Cleared: every payout has cleared.
  • Cancelled: withdrawn before any payout cleared.

The Payout run article explains each step.

Things to know

  • A run is drafted, approved, exported and then cleared. Drafting needs the Create permission on Payments, but approving needs the separate Approve permission on Payments, held in the default roles by the Administrator and the Finance Lead. That keeps a second person between preparing a batch and releasing the money.
  • Member benefits are booked as an expense only when a run is drafted, dated the "due on or before" date. Until then, a due benefit row is not in the accounts.
  • Cash and cheque runs don't need bank accounts on file. For every other mode, a member or partner without an active bank account is skipped. Add the account and draft another run for them.
  • Refunds runs skip no one for a missing bank account. They pick up every pending payout whose purpose is exactly "Refund" and that isn't in a run yet, and each refund keeps the mode, account and date set in the cancellation wizard.
  • Payout runs don't deduct TDS from member benefits or commissions.
  • A system schedule rule is available. The workflow rule "Daily payout runs (system)", listed under Rules, drafts member benefit, commission and refund runs in each set of books at 09:00 and tells finance. It ships switched off and drafts only; a person still approves.
  • Your organization can rename the grid's column titles, so your screen may use different words.

Related

  • 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.

  • 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.

  • 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.

  • Component mappingsScreen

    Which ledger each charge component posts to in the chosen set of books (a main ledger, an optional second tax ledger, an optional cost centre and, for sale and tenant charges, the revenue treatment and contract liability ledger), and the action to copy template additions into the books.

  • 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.

  • RuleScreen

    One automation rule's page: read or change its basics, trigger, conditions and actions, test it against a record, clone or delete it, and switch a system rule on or off.

  • RulesScreen

    Every automation rule in your organization, system and custom, with filters, the switch that turns each rule on or off, and shortcuts to edit, test, clone, see the run history of or delete a rule.

  • CommissionsScreen

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

  • CommissionScreen

    One channel-partner commission: the partner, the brokerage with GST and TDS, the payouts against it, and the actions to edit, approve, cancel or delete it.

  • BooksScreen

    The list of every set of books in your organization, one per promoter company, with the actions to set up books for a company, open a set or delete 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.

  • Cancel bookingScreen

    The four-step wizard that cancels a booking: it shows the demands and receipts that will be reversed, suggests the forfeiture and charges from the rule in force, sets the refund and posts everything in one go, releasing the unit and parking and marking the opportunity lost.

  • Tenant BenefitsScreen

    Keep ready-made benefit plans (corpus, transit rent, shifting…) that a rehab officer applies to an allottee's offer in one go.

  • 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.

  • Benefit plans and benefit accrualConcept

    A benefit plan is a project's ready-made list of what the developer pays an allottee (corpus, transit rent, shifting), applied to a draft offer in one go; benefit accrual is how a Member Benefits payout run books each due installment as an expense and a bill on the member's ledger before paying it.

  • Books, the active books switcher and cost centresConcept

    A set of books is the ledger of one promoter company: every posting for a project lands in its promoter's books, every accounting screen works on the one set chosen in the Books switcher, and cost centres inside the books (usually one per project with a child per tower) let the ledger and reports be cut by project.

  • Numbers and series: documents, bookings, demands, payments and vouchersConcept

    How NirmaanOne numbers what it creates: generated documents, bookings, demands, demand runs, payments, payout runs and revenue runs take a prefix, the Indian financial year and a five-digit serial (BK-2026-27-00007), while vouchers are numbered on posting from their voucher type's prefix, padded counter and suffix.

  • 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.

  • Pay commissions through a payout runHow-to

    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.

  • Refund a cancelled bookingHow-to

    Pay the refund a booking cancellation created: clear the pending refund payout on its own from the payment page, or collect several refunds in a Refunds payout run that is approved, exported as a bank file and cleared with the UTRs.

  • Put demand, payout and revenue runs on a scheduleHow-to

    Have demand runs, payout runs, revenue runs and RERA sweeps prepared on a timetable instead of by hand: start from the ready-made schedule on each runs page, adjust the day, time and options, save the rule, or simply switch on the matching system rule.

  • 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.

  • "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.

  • Posting stopped: a charge component or standard ledger is missing from these booksTroubleshooting

    A demand, payout, commission, cancellation or revenue run could not post because a charge component has no ledger in the promoter's books, or a template ledger or group the posting needs was never copied into them; map the component or sync the templates, then retry.

  • NotificationsScreen

    Your in-app inbox: every message the workflow rules sent you, newest first, with links to the records they are about and a way to mark them read.

  • DashboardScreen

    The page you land on after signing in: shortcuts to common jobs, a queue of what is waiting on you, the headline figures and one card each for projects, sales, stock, receivables, construction and the RERA accounts.