"Not a charge the buyer pays": the component's kind does not belong on this record
Every charge component has a kind that decides where it may appear: Sale Charge on pricing plans and estimates, Tenant Benefit and Tenant Charge (with Tax) on member offers, Tenant Benefit alone on benefit plans, Commission on commissions; GST is never a line you add, and a benefit paid to the member can never be demanded.
Messages this explains
- “Not a charge the buyer pays: <name> (<kind>). GST is worked out for each charge from its own rate, so it is never a line you add.”
- “Not a charge the buyer pays: <name> (<kind>). Member benefits and charges go on a member offer; commissions on the booking.”
- “<component> is a <kind> component; a member offer takes Tenant Benefit, Tenant Charge and Tax lines”
- “<name> is a <kind> component; a benefit plan takes Tenant Benefit components”
- “<component> is a benefit paid to the member, not a charge; it cannot be demanded”
"Not a charge the buyer pays": the component's kind does not belong on this record
You saved a pricing plan, an estimate, a member offer or a benefit plan, or raised a demand, and the app refused a line because the charge component on it is of a kind that does not belong there.
What you see
On the project's Unit Pricing tab (Save charges, Import) and on the estimate wizard's pricing step (New estimate, Edit estimate), the save is refused with one of:
- "Not a charge the buyer pays: <name> (<kind>). GST is worked out for each charge from its own rate, so it is never a line you add." when a line carries a Tax component.
- "Not a charge the buyer pays: <name> (<kind>). Member benefits and charges go on a member offer; commissions on the booking." when a line carries a Tenant Benefit, Tenant Charge, Commission or Other component.
The pickers on those screens only offer Sale Charge components, so you meet these messages on lines that came in by sheet import (Import on the Unit Pricing tab), on lines whose component had its Kind changed after it was added, or from outside the screens.
In the offer drawer on Society & Tenants (and on the allottee's page), Draft offer / Save changes fails with "<component> is a <kind> component; a member offer takes Tenant Benefit, Tenant Charge and Tax lines".
On Tenant Benefits, Save fails with "<name> is a <kind> component; a benefit plan takes Tenant Benefit components".
When a demand is raised on an offer, a benefit row is refused with "<component> is a benefit paid to the member, not a charge; it cannot be demanded". The Raise demand dialog lists only the charge and tax rows, so this appears only when the rows changed after the dialog opened.
Why it happens
A charge component is a kind of money line, and its Kind says whose money it is:
| Kind | Whose money | Where it belongs |
|---|---|---|
| Sale Charge | The buyer pays the developer | Pricing plans, estimates, bookings |
| Tax | GST worked out on other lines | On a member offer, as the GST line on its charges (Add tax); never on a buyer's price |
| Tenant Benefit | The developer pays the member (corpus, rent, shifting…) | Member offers, benefit plans |
| Tenant Charge | The member pays the developer (differential area, legal fees…) | Member offers, with GST as a Tax line |
| Commission | The developer pays the channel partner | Commissions on a booking |
| Other | Anything else | Not priced anywhere |
A buyer's price carries what the buyer pays; transit rent or corpus on it would bill the buyer for money owed to a member, and a commission would bill them the broker's fee. GST is never a line of its own because it is worked out per line from that line's rate (the plan line's, the component's or the group's), so adding a Tax line would tax it twice. A member offer keeps the two directions apart on purpose: benefits are paid out and charges are collected, never netted, so only those kinds (and Tax on the charges) fit. A benefit plan is a list of benefits, so only Tenant Benefit goes on it. A demand bills money coming in; a benefit row is money going out and is settled by payout runs instead.
How to fix it
- Replace the line. Remove the refused line and add the right kind: on Unit Pricing Add charge with a Sale Charge component, then Save charges (the Edit permission on Pricing Plans); on an estimate Add a charge with a sale charge (the Create or Edit permission on Estimates); on an offer Add benefit, Add charge or Add tax (the Create or Edit permission on Termsheets); on a benefit plan Add benefit (the Edit permission on Pricing Plans).
- Drop the GST line. GST does not need a line: check the rate on the component or its group under Charge Components (or the plan line's own GST rate), and the estimate shows the tax per group.
- Create the component you need if none of the right kind exists: New component on Charge Components, choosing the Kind (the Create permission on Charge Components; in the default roles the Administrator and the Finance Lead). The offer drawer's New benefit type… and New charge type… create a Tenant Benefit or Tenant Charge component without leaving the offer, with the same permission.
- Fix a sheet before importing again. In the Excel sheet pick the component from the Lists sheet dropdown; the plan sheet accepts sale charges only.
- Do not change the component's kind to get past the message unless you mean it: the kind can be edited (the Edit permission on Charge Components), but it changes where the component may appear everywhere it is used.
- For the demand, close the dialog, reopen Raise demand and tick charge or tax rows only.
Related
Related
- 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.
- Unit PricingScreen
Keep the project's pricing plans, one per unit type: the sale charges by charge group with GST per line, how each charge group is collected, and a preview of the price and payment schedule on a real unit.
- New estimateScreen
Price a unit for a buyer: pick the unit and optional parking slots, load a unit pricing plan or add charges by hand, override rates with a reason, set the validity, and save the draft before moving on to the payment plan.
- Edit estimate (estimate wizard)Screen
Continue an estimate in three steps: edit the draft pricing, draft or re-version the payment plan (lumpsum, installments, custom dates or construction-linked), then review and finalize, which locks price and plan and requests approval.
- Society & TenantsScreen
On a redevelopment project, link the society being redeveloped, keep its members and the project's landowners and PAP tenants, and give each of them an offer that allots new units and sets the benefits the developer pays.
- Tenant BenefitsScreen
Keep ready-made benefit plans (corpus, transit rent, shifting…) that a rehab officer applies to an allottee's offer in one go.
- 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.
- Unit Pricing: no plan for the unit type, or the stage links refuse to saveTroubleshooting
An estimate loads a pricing plan only when the project has an active plan for the unit's type; otherwise price by hand, giving each manual line an amount and every override a reason; on the Unit Pricing tab the stage links save only once the plan has charges and something changed, and the Unit Base Price group always stays on the payment plan.
- Benefit plan cannot be saved or applied to the offerTroubleshooting
A benefit plan needs a name, and each of its lines a Tenant Benefit component, a calendar cadence, an amount and (for a repeating cadence) the number of installments; applying one to an offer needs a plan with lines and, when a line is per sq ft, the allottee's existing carpet on the offer.
- Charge group cannot be deleted or recoded: seeded, or still holding componentsTroubleshooting
The four standard charge groups your organization starts with keep their code and are deactivated rather than deleted; any other group is deleted only once its components have moved to another group; a component still in use is deactivated, not deleted.