TroubleshootingReviewed 2026-09-29

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

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.

Messages this explains

  • “Saved as pending, but clearing failed: <message>”
  • “These books have no ledger for that bank account. Add a bank ledger under Chart of accounts first.”
  • “Books <name> have no ledger for bank account <account number>; create a bank ledger (account with bank_account_id) first”
  • “<n> payouts could not be cleared; see the failures below.”
  • “1 payout could not be cleared; see the failures below.”
  • “<n> payouts failed on the last attempt”
  • “1 payout failed on the last attempt”
  • “Fix the cause (a missing ledger mapping, inactive books) and run the action again; documents already posted are not touched.”

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

You pressed Save and clear, Clear and post or a payout run's Clear <n> payouts, and the money was recorded but its voucher did not post. The payment (or those payouts) stays Pending; nothing reached the ledger.

What you see

  • On Record receipt / Record payout and Edit payment, after Save and clear, a red toast "Saved as pending, but clearing failed: <message>" and the payment opens as Pending.
  • On the Payment page, the Mark as cleared? dialog shows the reason in its banner, most often "These books have no ledger for that bank account. Add a bank ledger under Chart of accounts first."
  • On the Payout run page, after Clear <n> payouts: the toast "<n> payouts could not be cleared; see the failures below." ("1 payout could not be cleared; …" for a single one), and a red card "<n> payouts failed on the last attempt" listing each payout number with its reason, followed by "Fix the cause (a missing ledger mapping, inactive books) and run the action again; documents already posted are not touched." The card shows the server's own wording, for example "Books <name> have no ledger for bank account <account number>; create a bank ledger (account with bank_account_id) first". The run stays Approved until every payout is cleared.

The message tells you which cause you hit. This article covers the missing bank ledger; the other causes have their own articles:

Message Article
"Charge component <code> has no ledger mapping in books <name>", "These books have no active ledger copied from template <code>; sync templates" Posting stopped: a charge component or standard ledger is missing
"No fiscal year covers that date. Open the next fiscal year under Books first.", "No fiscal year of these books covers <date>; open it first", "That fiscal year is closed.", "Fiscal year <name> is closed", "Period <n> of <FY> is locked" No fiscal year covers that date
"These books are inactive. Reactivate them under Books to post entries.", "Books <name> are inactive" These books are inactive

Why it happens

Recording a payment only stores it. Clearing is what posts the Receipt or Payment voucher: the bank side is debited or credited, the party's ledger is settled against the allocated bills, and the demand or commission moves to Partially Paid or Paid. For the bank side the promoter's books need a ledger linked to the bank account you picked under Into our account / From our account. A payment with no account goes to 1000 Cash in Hand, which always exists.

The app creates that bank ledger by itself only when a collection, RERA separate, operative or GST bank account is saved for a company whose books already exist and are active. Accounts saved before the books were set up, or while they were inactive, have no ledger until someone syncs them. Because clearing is refused before anything posts, the payment simply stays Pending; clearing it again once the ledger exists posts the voucher exactly as if it had worked the first time. In a payout run each payout clears in its own step, so the ones that worked are cleared and only the failures are listed.

How to fix it

  1. Create the missing bank ledgers in one go. Open the project (Projects > the project) and on the Ready to sell and collect? card of the Project overview press Sync bank ledgers. It creates a ledger in the promoter's books for the project's collection, RERA separate, operative and GST accounts and confirms with "Bank ledgers created: <codes>." (or "Every bank account already has its ledger."). You need the Edit permission on Projects; in the default roles that is the Administrator, the Project Manager and the Compliance Officer.
  2. Or add the ledger by hand for any other account of the promoter: Accounting > Chart of Accounts > Ledgers > New ledger, group Bank, a code and name, and the account under Bank account; Add ledger. This needs the Create permission on Chart of Accounts and the View permission on Bank Accounts to see the account list.
  3. Check the ledger is active. If it exists but is Retired, open it, tick Active and Save changes (Edit on Chart of Accounts). A retired bank ledger counts as missing.
  4. Clear the payment again. On the Payment page press Mark cleared, set Cleared on and Clear and post (Edit on Payments). On a payout run press Clear <n> payouts again; the dialog lists only the payouts still Pending, with a UTR box each, and only those are attempted.
  5. If the message names another cause, follow the article in the table above, then clear again.

Related

  • Record receipt / Record payoutScreen

    Record money received from a buyer or society member, or paid to a channel partner or society member: who, how and how much. A receipt settles the payer's open demands by itself, oldest due first; a payout is allocated to commissions or benefit rows by hand. A buyer's consideration and GST are two separate receipts; the TDS they deducted is a TDS credit.

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

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

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

  • LedgersScreen

    Every ledger of the chosen set of books, as a grouped tree or a flat list, with the actions to add ledgers and party ledgers, edit or retire them, and open a ledger's report.

  • Project overviewScreen

    A project's home page: its details, site, land, RERA registration, inventory summary, whether it is ready to sell and collect, where its money stands across its RERA accounts, and the setup checklist.

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

  • 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 books yet" or "has no books": set up books for the promoter company firstTroubleshooting

    Every posting follows the project's promoter company into its set of books; until that Promoter Entity company has books, the accounting screens show an empty state and demands, receipts, commissions and cancellations cannot post.

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