NirmaanOne Help
How-toReviewed 2026-09-29

Map a charge component to a ledger

Tell a set of books which ledger each charge component posts to (with its tax leg, cost centre and, for sale and tenant charges, the revenue treatment), so demands, benefit accruals, payouts and commissions can be posted automatically, and give future books the same default through a template mapping.

Map a charge component to a ledger

Every charge on a demand, every benefit paid to a society member and every channel partner commission is a charge component. Before the app can post one, the promoter's books must say where it goes: its ledger, a second ledger for the tax leg where there is one, an optional cost centre and, for the charges that make up a unit's price, how the revenue is treated. Do this when you add a new charge component, when you open a new set of books that didn't get a template mapping, and whenever a posting is refused with "Charge component <code> has no ledger mapping in books <name>".

Before you start

  • The component exists under Masters > Charge Components (see Configure charge groups and components).
  • The promoter's books exist (Set up the books); without any books the chart area reads "No books yet". You need the View permission on Books to choose the books.
  • The ledger you want must exist in those books and be active. Add it on Ledgers first; a cost centre on Cost centres.
  • You need the Edit permission on Chart of Accounts to save a mapping. In the default roles that is the Administrator, the Finance Lead and the Accountant. Without it the pencil is a greyed-out eye and the dialog can't be opened.
  • Know which ledger each kind takes. New books come with these seeded mappings, which show the pattern: sale charges to an income ledger (4100 Sale Revenue - Units for the unit price, floor rise, PLC and parking; 4130 Other Charges Recovered - Buyers for club, legal, development and AC piping); deposits and maintenance and society charges to their liability ledgers (2150, 2130, 2140); GST to 2210 GST Output Payable - CGST with 2220 GST Output Payable - SGST as the tax ledger; tenant benefits to rehab expense (5100 Displacement Rent Expense, 5110 Corpus Expense, 5120 Transport Compensation - Tenants); tenant charges to 4110 and 4120; and the channel partner commission to 5200 Brokerage Expense with 2300 TDS Payable as the tax ledger.

Steps

  1. In the sidebar open Accounting > Chart of Accounts and choose the Component mappings tab. You see the Component mappings table, one row per active charge component (plus inactive ones that still have a mapping), with the columns Component, Kind, Ledger, Tax ledger, Revenue, Cost centre and Actions. When some components have no ledger, a warning reads "N active components have no ledger in these books."

  2. Pick the right set of books in the Books switcher at the top right: a mapping belongs to one set of books, so a component that several promoter companies bill is mapped in each of their books. Unmapped rows show "Not mapped" in amber under Ledger.

  3. Click the pencil on the component's row (hover "Edit mapping of <component>"). The dialog Map <component> opens: "Where <code> posts when a demand, benefit or commission is raised."

  4. Fill in the dialog:

    • Ledger (required): search the books' active ledgers by code or name. The demand credits a sale charge here, a benefit accrual debits a benefit here, a commission approval debits the commission here.
    • Tax ledger (optional) ("Second leg, e.g. SGST or TDS payable"): for the GST component, the SGST ledger (the demand splits the GST in half between Ledger and Tax ledger when the buyer is in the project's state; across states it goes to 2230 IGST); for a commission, the TDS payable ledger (2300 when none is chosen). Leave it blank for ordinary charges.
    • Cost centre (optional) ("From the voucher"): the cost centre stamped on the posted lines; blank means the project's own cost centre when it has one.
    • For a Sale Charge or Tenant Charge, Revenue treatment: With the unit ("Billed to the contract liability; the revenue run recognises it with the unit."), On billing ("A separate obligation: revenue as soon as it is billed.") or Pass-through ("Money held for others (deposits, maintenance, society): never revenue."). Left blank, the treatment follows the ledger: an income ledger means With the unit, any other ledger Pass-through. The placeholder says so: "From the ledger (With the unit for an income ledger)" on a new mapping, "From the ledger (<treatment>)" on a saved one.
    • When the treatment is (or follows the ledger to) With the unit, the Contract liability ledger appears ("Where billing waits until the revenue is recognised. Blank: 2100."), placeholder "2100 Contract Liability - Sale of Units". Pick a liability ledger; the seeded differential-area charge uses 2110.

    Save mapping stays greyed out, with no reason on hover, until a Ledger is picked.

  5. Click Save mapping. You see "<component> mapped." The row shows the ledgers, the revenue badge (With the unit "via 2100", On billing or Pass-through, with "from the ledger" when you left the treatment blank) and the cost centre, and the unmapped count drops by one. The next posting of that component uses the new ledgers; postings already made are unchanged.

  6. Switch the Books switcher to every other set of books that will bill, accrue or pay this component and repeat steps 3 to 5. A component is posted in the books of the project's promoter, so map it wherever that promoter's projects use it.

  7. To give every future set of books the same default, open the Organization templates tab and choose Template mappings ("The default ledger per charge component, copied into every new set of books."). Click the pencil on the component (hover "Edit mapping of <component>"); the dialog Template mapping for <component> takes the Ledger template (required), a Tax ledger template (optional) and, for a sale or tenant charge, the Revenue treatment ("Copied into books that do not have a treatment yet. With the unit: billed to the contract liability until the revenue run recognises it.") with its Contract liability template. Click Save mapping; you see "<component> mapped." See Organization templates.

  8. Optional: for a set of books that has no mapping for the component yet, go back to its Component mappings tab and click Sync from templates. You see "Synced: N groups, N ledgers, N mappings added." Sync adds what the books lack and never re-points an existing mapping, ledger or group, so books that already map the component keep their own ledgers. The one thing it fills in on an existing mapping is a missing revenue treatment, taken from the template.

What happens next

  • Demand issue posts a Sales voucher: the buyer's or member's ledger is debited with the amount payable, any TDS the buyer deducts goes to 1300 TDS Receivable, and each charge is credited to its Ledger, except a With the unit charge, which is credited to its Contract liability ledger and stays there until a revenue run recognises it. (When the books' revenue policy in force on the demand date is Revenue on billing, every charge goes straight to its Ledger.) See Demand.
  • Benefit accruals debit each benefit component's Ledger and credit the member; a payout of a benefit that was never accrued also debits the Ledger. Commission approval debits the commission's Ledger, takes the GST input credit, credits the channel partner and credits the TDS to the Tax ledger. Cancellation uses the GST mapping.
  • Only With the unit charges make up the transaction price a revenue run recognises; On billing charges are earned when billed; Pass-through money is never revenue. The revenue policy of the books decides when and how.
  • To take a mapping away, click the bin on its row (hover "Unmap <component>"), read "Remove mapping?" ("<component> will have no ledger in these books until it is mapped again.") and click Unmap; you see "<component> unmapped." Postings of that component are refused until it is mapped again.

If something goes wrong

  • "Charge component <code> has no ledger mapping in books <name>" (or "The CP_COMMISSION component has no ledger mapping in books <name>", "The GST component has no ledger mapping in books <name>") when a demand is issued, a benefit accrued or paid, a commission approved or a booking cancelled: map the component in those books, then try again. See Component not mapped (trouble.accounting.component-not-mapped).
  • "No books yet" and "Set up books for a promoter company first: that copies the chart of accounts, opens the fiscal year and seeds the voucher types." in place of the chart area: there are no books to map into. See Set up the books and No books yet (trouble.accounting.no-books-yet).
  • "The contract liability ledger must be a liability" on Save mapping with Revenue treatment set to With the unit: the Contract liability ledger sits under an asset, equity, income or expense group. Pick a ledger under a liability group (2100 or 2110), or leave it blank for 2100.
  • "Account <code> <name> is retired" when a posting runs: a mapped ledger was retired afterwards. Nothing on this tab warns you. Map the component to an active ledger, or reactivate the ledger on Ledgers. See Voucher cannot be posted: retired ledger (trouble.accounting.cannot-post-voucher).
  • "These books have no active ledger copied from template <code>; sync templates": a posting needs a standard ledger the books lack or have retired (2100 for a With the unit charge with no contract liability ledger of its own, 1300 for TDS, 2230 for IGST, 2300 for commission TDS). Click Sync from templates, or reactivate the ledger. See Component or standard ledger missing from the books (trouble.accounting.component-not-mapped).
  • The pencil is a greyed-out eye (hover "View mapping of <component>"), or "You do not have permission to view the chart of accounts. Ask your administrator." / "Choosing a set of books needs the Books read permission. Ask your administrator.": your role lacks the Edit (or View) permission on Chart of Accounts, or the View permission on Books. See No permission (trouble.common.no-permission).

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.

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

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

  • Cost centresScreen

    The cost-centre tree of a set of books, usually one per project with a child per tower, so the ledger and the reports can be cut by project; mirror the projects in one click or add cost centres by hand.

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

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

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

  • Revenue policyScreen

    The CA's effective-dated choices on how the books recognise sale revenue and the costs that go with it: framework, method, possession trigger, OC rule, cost treatments and judgement areas.

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

  • Set up the books for a promoter companyHow-to

    Create the set of books a promoter company keeps, mirror its projects as cost centres, check the voucher numbering series and the component mappings, and connect the project's bank accounts to their ledgers so demands, receipts and payouts can be posted.

  • Configure charge groups and componentsHow-to

    Review the standard charge groups and their default GST, add a group of your own, and add or retire the charge components (sale charges, tenant benefits, tenant charges, commissions) that pricing plans, estimates and offers are built from.

  • Component mappings: which ledgers a charge posts toConcept

    A component mapping tells one set of books where a charge component posts: a main ledger, an optional second tax ledger, an optional cost centre and, for sale and tenant charges, the revenue treatment; demands, commissions, benefit accruals, payouts and cancellations all read it, and an unmapped component stops the posting.

  • The chart of accounts: templates, books copies, nature and system rowsConcept

    The organization keeps one master chart (group templates, ledger templates and default mappings) and every set of books holds its own copy of it; each group carries a nature (asset, liability, equity, income, expense) and a Direct flag that feeds gross profit, a few system rows are locked, codes are never reused, and the Consolidated report adds the books up by the template each ledger came from.

  • Contract liability, contract asset and the transaction priceConcept

    A booking's transaction price is the sum of its charges treated "With the unit"; while revenue is deferred, demands for those charges are credited to a contract liability (billed ahead of revenue), a revenue run debits it as revenue is recognised, and revenue recognised ahead of billing sits in the contract asset.

  • Revenue recognition: policy, point in time vs over time, and revenue runsConcept

    Each set of books carries an effective-dated revenue policy (framework, method, possession trigger, cost and brokerage treatments, judgement areas) chosen by the CA; a revenue run is the period close that computes every booking's and member offer's progress under it, recognises the catch-up revenue, cost of sales and brokerage, and posts the journals.

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

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

  • Voucher cannot be posted: unbalanced, missing lines, retired ledgers or bill allocations that do not matchTroubleshooting

    Save and post or Post is greyed out, the draft saves but posting fails, or the form refuses a line: the balance, line, ledger, voucher-type and bill-allocation rules a voucher must meet before it reaches the ledger.

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