NirmaanOne Help
TroubleshootingReviewed 2026-09-29

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

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.

Messages this explains

  • “<n> active components have no ledger in these books.”
  • “Charge component <code> has no ledger mapping in books <name>”
  • “The CP_COMMISSION component has no ledger mapping in books <name>”
  • “The GST component has no ledger mapping in books <name>”
  • “These books have no active ledger copied from template <code>; sync templates”
  • “These books have no ledger <code>; sync templates”
  • “The group a party ledger needs is missing from these books. Sync the templates first.”

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

An automatic posting stopped because the promoter's books don't say where a charge should go. Every charge component (Unit Base Price, floor rise, GST, transit rent, brokerage and so on) needs a ledger in each set of books it posts to, and some postings also need standard ledgers copied from the organization's templates.

What you see

  • On Component mappings, the amber warning "<n> active components have no ledger in these books." (for one: "1 active component has no ledger in these books."), and "Not mapped" in the Ledger column of those rows.
  • Issuing a demand on the Demand page (Issue this demand?): "Charge component <code> has no ledger mapping in books <name>". On a Demand run the same text sits beside each affected demand in the red "<n> demands failed on the last attempt" card.
  • Approving a commission on the Commission page (Approve this commission?): "The CP_COMMISSION component has no ledger mapping in books <name>".
  • Clearing a payout that settles a member benefit row no run has accrued, on the Payment page (Mark as cleared?): "Charge component <code> has no ledger mapping in books <name>". On a Payout run the text appears under Skipped payees when a Member Benefits run could not accrue a member's rows, or in the "<n> payouts failed on the last attempt" card.
  • On the Cancel booking wizard, as the page's error or in the alert after Cancel booking: "The GST component has no ledger mapping in books <name>". The credit notes and the forfeiture GST need the GST mapping.
  • When a standard ledger is missing rather than a mapping: "These books have no active ledger copied from template <code>; sync templates". For example, demand issue needs 1300 (TDS Receivable) when the buyer deducts TDS, 2230 (IGST) across states and 2100 (Contract Liability) when the revenue policy defers the charge; commission approval needs 1311, 1312 or 1313 (GST input), 2300 (TDS Payable) when the mapping names no tax ledger, and 1270 when the revenue policy capitalises brokerage; cash payments need 1000; the year-end close needs 3200.
  • On a Revenue run (New revenue run, Recompute or Post run): "These books have no ledger <code>; sync templates", where the code is 1500 or 1600, the inventory ledgers the cost moves need.
  • Opening a party ledger, either from the Party ledger dialog on Ledgers or the first time a posting creates one: "The group a party ledger needs is missing from these books. Sync the templates first." Customers go under Receivables, members under Compensation, channel partners and vendors under Payables.

Why it happens

Each set of books is a copy of the organization's templates: its groups, its auto-create ledgers and one default ledger per charge component. Postings never guess a ledger. When a demand is issued, each line is credited to the ledger its component is mapped to in the promoter's books; a commission's brokerage is debited to the CP_COMMISSION mapping; benefit accruals and direct benefit payouts debit the benefit component's mapping; GST legs use the GST mapping's Ledger and Tax ledger. A component with no mapping stops the posting rather than post to a wrong ledger.

A mapping goes missing when a charge component was added after the books were set up, when a template mapping was left empty or pointed at a template that is not auto-created, or when someone removed the mapping with Unmap. A template ledger or group goes missing when it was added to the organization's templates after the books existed, when the ledger was retired in the books, or when a set of books was created before that template was seeded. Sync from templates only adds what the books still lack; it never renames or reactivates existing rows, and it skips a template whose code or name a ledger in the books already uses.

How to fix it

  1. Open Accounting > Chart of Accounts > Component mappings and pick the books named in the message in the Books switcher (the View permission on Books).
  2. For a missing mapping, press the pencil on the "Not mapped" row. In Map <component> pick the Ledger (for GST also the Tax ledger (optional) for the SGST leg; for CP_COMMISSION the TDS payable ledger) and Save mapping. You need the Edit permission on Chart of Accounts; in the default roles that is the Administrator, the Finance Lead and the Accountant. Repeat for every row until the warning disappears.
  3. For a missing template ledger or group, press Sync from templates on the same tab (Edit on Chart of Accounts). The toast "Synced: <n> groups, <n> ledgers, <n> mappings added." confirms what was copied.
  4. If the sync adds nothing, the ledger usually exists but is retired: on Ledgers set Active to "Retired only", open the ledger, tick Active and Save changes (Edit on Chart of Accounts). If instead a ledger you added by hand already has that template's name, rename your ledger and sync again.
  5. If the template itself is missing or not auto-created, fix it on Organization templates: tick Auto-create in new books on the ledger template, or map the component under Template mappings; then sync again. Existing books keep their own mappings.
  6. Retry the action that failed: Issue on the demand (the Issue permission on Demands), Issue <n> demands on the run, Approve and post on the commission (Edit on Commissions), Mark cleared on the payment or Clear <n> payouts on the run (Edit on Payments), Recompute or Post run on the revenue run (Create or Approve on Revenue Recognition), or Cancel booking in the wizard. Documents that already posted are not touched. A Member Benefits run that skipped a member needs a new run.

Related

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

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

  • Organization templates (Chart templates)Screen

    Your organization's master chart of accounts, from which every new set of books is copied: group templates, ledger templates and the default ledger per charge component.

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

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

  • Demand runScreen

    One demand run: its dates and totals, the demands it drafted, the subjects it skipped and the demands that failed to issue, with the actions to issue or cancel the run.

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

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

  • Revenue runScreen

    One period close: what each booking and member offer recognises, the journals and cost moves it posts, the subjects it left out, and the actions to recompute, post, reverse or delete it.

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

  • Charge ComponentsScreen

    The organization's catalogue of money lines (unit price, floor rise, PLC, legal charges, tenant benefits, commissions) and the charge groups that section a buyer's cost sheet, each with its GST rate.

  • Chart of accounts: a seeded group, ledger, template, cost centre or voucher type refuses the change or the deleteTroubleshooting

    Rows the app seeded or that postings already use are protected: seeded groups, system ledgers and system templates keep their name and place, and anything with postings, mappings or vouchers behind it is retired rather than deleted.

  • Demand run: some demands could not be issued, or the run holds nothingTroubleshooting

    A demand run issues each demand on its own, so one that cannot post is listed under "failed on the last attempt" while the others go through; a run whose demands were all cancelled or deleted, or a subject with nothing due, is reported rather than issued.

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