NirmaanOne Help
How-toReviewed 2026-09-29

Bounce a returned payment or correct a pending one

Mark a cheque or transfer the bank returned as bounced so its voucher is reversed and the demand reopens, and fix, cancel or delete a payment that is still pending.

Bounce a returned payment or correct a pending one

Two different problems, two different actions. When the bank returns a cheque or a transfer fails after you recorded it, bounce the payment: a cleared one has its voucher reversed and the bills it settled reopen, a pending one is simply marked. When you typed something wrong on a payment that is still Pending, edit it, or cancel or delete it and record it again. A cleared payment can only be bounced; its voucher is never edited.

Before you start

  • You need the Edit permission on Payments to bounce, edit or cancel: in the default roles the Administrator, the Finance Lead and the Accountant. Delete needs the Delete permission on Payments, which the same three roles hold. Without the permission the buttons aren't shown.
  • The payment's status decides what is possible: Pending payments can be edited, cleared, bounced, cancelled or deleted; Cleared payments can only be bounced; Bounced and Cancelled payments are final. To recover money after a bounce, record a new receipt (Record and clear a buyer's receipt).
  • The party, booking, books and direction of a payment can never change. If those are wrong, cancel (or delete) the pending payment and record a new one.

Steps

  1. Open the payment (Payment): from Payments in the sidebar (Payments), from the booking's Demands & money tab, or from the demand's Receipts against this demand card. The header shows the number, the Receipt or Payout badge, the clearing status (Pending or Cleared) and the mode; the Allocations card lists the demands or commissions it settles.
  2. For money the bank returned, click Bounce. The dialog "Bounce this payment?" opens. On a Cleared payment it reads "The voucher is reversed, the allocated bills reopen and the paid amounts are recomputed."; on a Pending one "The pending payment is marked bounced; nothing was posted."
  3. Set Bounced on (today by default), type the Reason (required; placeholder "Insufficient funds, signature mismatch…") and click Mark bounced. You see "Payment marked bounced." The badge reads Bounced and a banner shows "Bounced on <date>: <reason>" and, for a payment that had been cleared, "The receipt voucher was reversed and the bills reopened." The reversal voucher is dated the bounce date (or the original voucher's date if that is later). The demand it settled goes back to Issued or Partially Paid with its Outstanding raised again.
  4. To correct a payment that is still Pending, click Edit. The page "Edit <payment no>" opens (Edit payment) with Booking and Books greyed out and the line "Party: <name> (fixed once recorded)".
  5. Change what is wrong: Received on / Paid on, Mode, Gross amount, TDS deducted, Into our account / From our account, the instrument details, Narration, or, on a payout, the Allocate amounts (each allocation shows "<amount> open", counting this payment's own share). A receipt is not allocated by hand: on save its amount settles the payer's open demands again by itself, oldest due first, as the What this receipt settles card shows. Click Save changes. You see "Payment updated." and the payment page opens. Click Save and clear instead to post it in the same step ("<payment no> cleared; voucher <no> posted.").
  6. To drop a pending payment recorded by mistake, click Cancel in the header and confirm with Cancel payment in "Cancel this payment?" ("The pending payment is marked cancelled and its allocations released."). You see "Payment cancelled." and the banner "Cancelled before clearing; nothing was posted." The number stays on record. To remove it altogether, click Delete and confirm with Delete in "Delete this payment?" ("The pending payment is removed for good."). You see "Payment deleted." and land on the booking's Demands & money tab or the Payments list.

What happens next

  • After a bounce, the seeded rule "Payment bounced: recover (system)" (switched on by default) notifies the Accountants and Finance Leads ("Payment <no> bounced: Rs <amount>") and gives an Accountant a high-priority task due in 2 days to recover it; the task shows under Tasks. The rule "Payment bounced: notify the payer (system)" emails the "Payment returned unpaid" template to the payer but ships switched off; an administrator can switch it on under Rules.
  • A bounced receipt that had already been appropriated leaves its split standing: the demand shows "<appropriated> is placed on the lines but only <received> has been received (a receipt bounced or was cancelled). Reduce the appropriation." Open the demand and lower the split: Appropriate a receipt across a demand's charge lines.
  • Cancelling a pending receipt frees the demand's open amount at once (a pending allocation had been holding it), so a replacement receipt can be recorded straight away.
  • Once the receipts against a demand are bounced or cancelled, the demand itself can be cancelled with a credit note if needed: Cancel or correct a demand.

If something goes wrong

  • "A <status> payment cannot be edited. Bounce a cleared one, or record a new payment." on the edit page, or Edit, Cancel and Delete are missing: the payment is no longer Pending. See Payment status locked (trouble.collections.payment-status-locked).
  • "Only a Pending payment can be cancelled; a cleared one is bounced" or "Only a Pending payment can be deleted; bounce or cancel it instead": use Bounce on a cleared payment. Same article (trouble.collections.payment-status-locked).
  • "A <status> payment cannot bounce": the payment is already Bounced or Cancelled; refresh the page. Same article (trouble.collections.payment-status-locked).
  • "Reason is required" in the bounce dialog: type the reason the bank gave.
  • "No fiscal year covers that date. Open the next fiscal year under Books first." or "That fiscal year is closed." when bouncing a cleared payment: the reversal lands in a year that isn't open. Open the next fiscal year, or pick a Bounced on date in an open year. (A Bounced on date earlier than the original voucher is not a problem: the reversal then takes the voucher's date.) See Fiscal year missing (trouble.accounting.fiscal-year-missing).
  • "Direction, party, booking and books cannot change on a payment; cancel it and record a new one." when saving an edit: those fields are fixed. Cancel the payment and record a new one. See Payment status locked (trouble.collections.payment-status-locked).
  • "At most <x> is open on this target" or "demand <no> has <x> open (pending allocations included), allocation is <y>" when saving an edit: another pending payment already earmarks part of the demand. Lower the allocation or cancel that payment. See Payment rejected (trouble.collections.payment-rejected).
  • The buttons are missing on a Pending payment: your role lacks the Edit (or Delete) permission on Payments. See No permission (trouble.common.no-permission).

Related

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

  • Edit paymentScreen

    Change the date, mode, amount, bank details and, on a payout, the allocations of a payment that hasn't cleared yet, and optionally clear it in the same step; a receipt settles the open demands again by itself when saved.

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

  • DemandScreen

    One demand: the installments it bills, its amounts with GST, the expected TDS and what is payable in money, the receipts and TDS credits against it and how the money is placed on the charges, with the actions to edit, issue, cancel or delete it.

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

  • TasksScreen

    Follow-ups for you and your team: add tasks by hand or let workflow rules raise them, link each to the record it is about, assign it, and mark it done.

  • Record and clear a buyer's receiptHow-to

    Record the money a buyer paid against an issued demand as a consideration receipt (and the GST they paid as its own GST receipt), clear it to post the receipt voucher, give the buyer their receipt, and hand the TDS they deducted to a TDS credit.

  • Appropriate a receipt across a demand's charge linesHow-to

    Place the money received against a demand on the charges its instalments cover, in the split you decide, so the booking's schedule rows show what is paid.

  • Cancel or correct a demandHow-to

    Fix or remove a draft demand, or cancel an issued one with a credit note so its installments are free to be billed again.

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

  • Manual appropriation of receiptsConcept

    A receipt settles a demand as a whole; which charges the money was for is decided by you, on the demand, in any split up to each line's billed amount and up to what was received, and that split is what marks the payment schedule's rows paid.

  • Payment cannot be edited, cancelled, deleted or bounced: its status decidesTroubleshooting

    Only a Pending payment can be edited, cleared, cancelled or deleted, and even then its direction, party, booking and books are fixed; a Cleared payment can only be bounced, which reverses its voucher and reopens the bills; Bounced and Cancelled payments are final and a new payment is recorded instead.

  • Record payment refuses to save: the party, books, direction or allocations do not fitTroubleshooting

    A receipt or payout needs exactly one party (or a booking that gives the buyer) and a set of books; a payout also needs TDS no larger than the amount and allocations that name one open target each, add up to no more than the amount, match the direction and belong to the payee. A receipt settles the payer's open demands by itself, so its allocation messages reach the form only when a demand closed between the preview and the save. A receipt refused over the buyer's TDS or over GST has its own article.

  • Posting refused: no open fiscal year or period for the dateTroubleshooting

    Every posting, manual or automatic, needs a fiscal year of the books that covers its date, with the year open and the month's period unlocked; open the next year, unlock the period or reopen the year under Books, or move the document's date.

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

  • CollectGuide

    Map charges to ledgers, raise and issue demands on bookings and member offers (singly or in runs), record and clear receipts, appropriate them, handle bounces, chase overdue demands, mirror the bank's daily RERA sweeps and watch the RERA accounts.