Component mappings
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.
Component mappings
Every charge on a demand, every member benefit and every commission is a charge component. This tab says which ledger each component posts to in the chosen set of books. A component with no mapping can't be posted automatically, so this is the tab to check when a demand, accrual, payout or commission is refused for a missing mapping.
Where to find it
Open Accounting > Chart of Accounts in the sidebar and choose the Component mappings tab. Access works as for the whole chart of accounts: any permission on Chart of Accounts, and the View permission on Books to choose the books with the Books switcher at the top right. See Chart of accounts: Groups.
Before you start
- The charge components come from Masters > Charge Components. Add a new component there first.
- The ledgers you map to must exist and be active. Add them on Ledgers.
What you see
The tab opens with: "Sale charges name their revenue ledger and how billing reaches it (the revenue treatment), GST posts to output tax (with the SGST leg), tenant benefits to rehab expense, commission to brokerage with its TDS leg. An unmapped component blocks automatic posting of that charge."
When some components have no ledger, a warning reads "<n> active components have no ledger in these books." (or "1 active component has no ledger in these books.").
The table has one row per active charge component of your organization, plus any inactive component that still has a mapping:
| Column | What it shows |
|---|---|
| Component | The name and code, with Inactive component when the component is inactive. |
| Kind | Sale Charge, Tax, Tenant Benefit, Tenant Charge, Commission or Other. |
| Ledger | The ledger the component posts to, or "Not mapped" in amber. |
| Tax ledger | The second ledger, used for the other half of GST or for TDS, or "—". |
| Revenue | For sale charges and tenant charges only: the revenue treatment badge, With the unit (blue), On billing (amber) or Pass-through (grey). Under With the unit it adds "via <contract liability ledger>" ("via 2100" when none is chosen), and "from the ledger" when no treatment has been set and the app is going by the ledger's nature. Other kinds show "—". |
| Cost centre | The cost centre put on the posted lines, or "—". |
| Actions | The row's icons. |
New books start with these mappings, copied from your organization's templates:
| Components | Ledger | Tax ledger | Revenue |
|---|---|---|---|
| BASE_RATE, FLOOR_RISE, PLC, PARKING | 4100 Sale Revenue - Units | — | With the unit via 2100 |
| CLUB, LEGAL, DEVELOPMENT, AC_PIPING | 4130 Other Charges Recovered - Buyers | — | With the unit via 2100 |
| DEPOSITS | 2150 Utility Deposits Collected from Buyers | — | Pass-through |
| MAINT_DEPOSIT, MAINT_ADVANCE | 2130 CAM / Maintenance Advance Collected | — | Pass-through |
| SOC_SHARE, SOC_FORMATION | 2140 Society Formation Corpus Collected | — | Pass-through |
| GST | 2210 GST Output Payable - CGST | 2220 GST Output Payable - SGST | — |
| CORPUS | 5110 Corpus Expense | — | — |
| RENT | 5100 Displacement Rent Expense | — | — |
| SHIFTING | 5120 Transport Compensation - Tenants | — | — |
| DIFF_AREA | 4110 Revenue - Differential Area (Tenants) | — | With the unit via 2110 |
| TENANT_LEGAL, TENANT_OTHER | 4120 Other Charges Recovered - Tenants | — | With the unit via 2100 |
| CP_COMMISSION | 5200 Brokerage Expense | 2300 TDS Payable | — |
2100 is Contract Liability - Sale of Units and 2110 is Contract Liability - Differential Area.
What you can do
Sync from templates
Copies into these books whatever your organization's templates have that the books still lack: new group templates, active ledger templates marked Auto-create in new books, and template mappings for components these books haven't mapped.
- Who: anyone with the Edit permission on Chart of Accounts. In the default roles that is the Administrator, the Finance Lead and the Accountant. Without it the button isn't shown.
- What happens next: "Synced: <n> groups, <n> ledgers, <n> mappings added." Nothing already in the books is changed.
Edit mapping
The pencil icon on a row (tooltip "Edit mapping of <component>") opens "Map <component>": "Where <code> posts when a demand, benefit or commission is raised."
- Ledger (required): search the books' active ledgers by code or name.
- Tax ledger (optional): placeholder "Second leg, e.g. SGST or TDS payable".
- Cost centre (optional): placeholder "From the voucher"; any cost centre of these books.
For a component of kind Sale Charge or Tenant Charge the dialog adds:
- Revenue treatment: With the unit, On billing or Pass-through. Left blank, the placeholder reads "From the ledger (<treatment>)": an income ledger means With the unit, any other ledger Pass-through. A hint explains the chosen treatment: "Billed to the contract liability; the revenue run recognises it with the unit.", "A separate obligation: revenue as soon as it is billed." or "Money held for others (deposits, maintenance, society): never revenue."
- Contract liability ledger, shown only under With the unit (placeholder "2100 Contract Liability - Sale of Units"): "Where billing waits until the revenue is recognised. Blank: 2100."
Click Save mapping, or Cancel.
- Who: anyone with the Edit permission on Chart of Accounts.
- Greyed out: without that permission the icon is a greyed-out eye (tooltip "View mapping of <component>"), so the mapping can't be opened. In the dialog, Save mapping stays greyed out until a Ledger is picked. No reason is shown on hover.
- What happens next: "<component> mapped." The next posting of that component uses the new ledgers. Postings already made are not changed.
Unmap
The bin icon on a mapped row (tooltip "Unmap <component>") asks "Remove mapping?": "<component> will have no ledger in these books until it is mapped again." Click Unmap, or Cancel.
- Who: anyone with the Edit permission on Chart of Accounts. Without it the icon isn't shown.
- What happens next: "<component> unmapped." Automatic postings of that component are refused until you map it again.
Things to know
- How postings use a mapping:
- Demand issue posts a Sales voucher. The buyer's or member's ledger is debited with the amount payable, and any TDS the buyer deducts goes to 1300 TDS Receivable. Each charge is credited to its component's Ledger, except a charge whose treatment is With the unit: that is credited to the mapping's Contract liability ledger (2100 when none is chosen) and stays there until a revenue run recognises it. The exception doesn't apply when the books' revenue policy in force on the demand date is Revenue on billing; then every charge goes straight to its Ledger.
- GST on a demand: when the party and the project's site are in the same state (or the party's state isn't recorded), the GST is split in half between the GST mapping's Ledger (CGST) and Tax ledger (SGST), or goes wholly to Ledger when there is no tax ledger. Across states, it goes to 2230 GST Output Payable - IGST.
- Commission approval debits the CP_COMMISSION Ledger, takes GST input credit to 1311 and 1312 (or 1313 across states), credits the channel partner, and credits the TDS to the mapping's Tax ledger (2300 TDS Payable when there is none).
- Benefit accrual debits each benefit component's Ledger and credits the member's ledger. A payout of a benefit that was never accrued also debits the component's Ledger.
- Cancellation uses the GST mapping.
- Cost centre: the mapping's cost centre when set, otherwise the project's own cost centre (see Cost centres).
- The revenue treatment decides what counts as the unit's price. Only With the unit charges make up the transaction price a revenue run recognises. On billing charges are separate obligations, earned as soon as they are billed. Pass-through money (deposits, maintenance, society charges) is never revenue. Only sale and tenant charges take a treatment, and the Contract liability ledger must sit under a liability group ("The contract liability ledger must be a liability").
- An unmapped component stops the posting. It is refused with "Charge component <code> has no ledger mapping in books <name>" (or "The CP_COMMISSION component has no ledger mapping in books <name>" for commissions and "The GST component has no ledger mapping in books <name>" for cancellations). Map it here and try again.
- Mapped ledgers must stay active. The app doesn't warn when you retire a mapped ledger; the next posting is refused with "Account <code> <name> is retired". Remap first, then retire.
- Each set of books has its own mappings. A new component has to be mapped in every set of books that will post it. To give future books a default, add a template mapping on Organization templates.
- Sync only adds. It never changes an existing mapping, ledger or group, even if the template has changed since.
- Your organization can rename the tab labels, so your screen may use different words.
Related
Related
- 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.
- 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.
- Chart of accounts: GroupsScreen
The reporting groups of the chosen set of books as a tree under the five classes (asset, liability, equity, income, expense); add your own groups and delete empty ones.
- 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.
- 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.
- 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.
- 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.
- Contract balancesScreen
The Ind AS 115 contract-balances disclosure per project over a period: contract liability, contract asset and contract acquisition costs rolled forward from the ledger, with the revenue recognised in the period and how much of it came out of the opening liability.
- 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.
- Demands, demand runs and the GST splitConcept
A demand is the bill raised on a buyer's installments (or a member's offer charges): numbered by financial year, billing the full total with the buyer's expected 194-IA TDS shown apart, posted as a sales voucher with GST split as CGST + SGST or IGST by place of supply; a demand run raises one demand per buyer for everything due by a date.
- 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.
- Map a charge component to a ledgerHow-to
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.
- 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.