NirmaanOne Help
TroubleshootingReviewed 2026-09-29

Escrow, TDS or cancellation rule refused: a rule already starts on that date, or it is the last one

The RERA escrow share, TDS on sales and booking cancellation rules are effective-dated: one rule per start date and scope, and the last rule is never deleted because every sweep, demand and cancellation needs a rule in force; change the figure or add a rule from a later date instead.

Messages this explains

  • “An escrow rule already starts on that date.”
  • “Keep at least one escrow rule; change its percentage instead.”
  • “A 194-IA rule already starts on <date>”
  • “A <section> rule already starts on <date>”
  • “Keep at least one 194-IA rule; set its rate to 0 to stop deducting”
  • “Keep at least one <section> rule; set its rate to 0 to stop deducting”
  • “A rule for this scope already starts on that date.”
  • “Keep at least one organization-level rule; set its percentage to 0 to forfeit nothing.”
  • “Please correct the highlighted fields.”

Escrow, TDS or cancellation rule refused: a rule already starts on that date, or it is the last one

You added, edited or deleted a rule on the Organization settings page (RERA escrow share, TDS on sales (section 194-IA) or Booking cancellation rules) and the app refused.

What you see

On Organization (Settings > Organization):

  • New escrow rule / Edit escrow rule: "An escrow rule already starts on that date." under the form. Delete escrow rule?: "Keep at least one escrow rule; change its percentage instead." (the dialog already warns "The last rule cannot be deleted; change its percentage instead.").
  • New TDS rule / Edit TDS rule: "A 194-IA rule already starts on <date>" (the section you typed, and the date written as year-month-day). Delete TDS rule?: "Keep at least one 194-IA rule; set its rate to 0 to stop deducting" (again with the section of the rule).
  • New cancellation rule / Edit cancellation rule: "A rule for this scope already starts on that date." Delete cancellation rule?: "Keep at least one organization-level rule; set its percentage to 0 to forfeit nothing."
  • New escrow rule / New cancellation rule (and their edit dialogs): "Please correct the highlighted fields." in the red banner when a value is missing or out of range (the Effective from date cleared, a percentage above 100). These two dialogs do not mark the field, so check each value. The TDS dialog shows the reason under the field itself instead.

The Project overview readiness card shows the escrow share in force today ("<n>% of every collection swept to the separate account", with "(the organization's rule)" or "(this project's own share; the organization's rule is <n>%)"), and the cancellation wizard shows the cancellation rule it will apply; neither edits the rules.

Why it happens

The three rules are effective-dated tables rather than single settings, because the law and the company's policy change over time and old documents must keep the figures they were made with:

  • RERA escrow share: the share of every collection the bank sweeps from the project's collection account to its RERA separate account (70% under RERA 2016), the rest going to the operative account. Every RERA sweep is split by the rule in force on its clearing date; the warning on a receipt banked outside the collection account, the RERA accounts statement and the dashboard's RERA accounts card quote the same rule. A project can override it with its own RERA escrow share under Accounting on its Settings tab.
  • TDS on sales (194-IA): what the buyer deducts on each installment once the deal's consideration reaches the threshold. The rule in force on the demand date applies, so older demands are unaffected by a change.
  • Booking cancellation rules: the forfeiture and default charges the cancellation wizard suggests. The organization rule applies everywhere, a rule with a project as its Scope overrides it for that project, and the wizard uses the rule in force on the cancellation date.

"In force on a date" means the rule with the latest Effective from on or before that date. Two rules starting on the same day (for the same TDS section, or the same cancellation scope) would leave the app unable to choose, so the date must be unique within the table, section or scope. And there must always be a rule to find: sweeps, demands and cancellations happen every day, so the last escrow rule, the last rule of a TDS section and the last organization-level cancellation rule are kept. Project-level cancellation rules can be deleted freely; the organization rule stands behind them.

The tables are seeded when the organization is created: escrow 70% from 1 May 2017, TDS 194-IA at 1% on a consideration of ₹50,00,000 or more from 1 June 2013, and a cancellation rule forfeiting 10% of the agreed total with no GST from 1 January 2000.

How to fix it

All three cards need the Edit permission on Organization Settings; in the default roles only the Administrator holds it (see "No access" or "You do not have permission").

  1. "…already starts on that date": the change you want is probably an edit of the rule that already starts that day. Find its row in the card (it is the one with that Effective from) and use its pencil icon to edit it. If you really need two changes on one day, keep one rule with the final figure. Otherwise pick the next day as Effective from.
  2. To stop the rule without deleting it, edit the last rule: set the escrow share percentage to the value you need, set the TDS Rate to 0 (demands then deduct nothing), or set the cancellation Forfeiture to 0 with no default charges (cancellations then forfeit nothing). Documents already raised keep their figures.
  3. To change the figure from a date onwards, add a new rule with Add rule and the new Effective from rather than editing the old one, so that sweeps, demands and cancellations before that date still report under the old rule. Rows dated after today show Upcoming; the current one shows In force. For one project on other terms, set its own RERA escrow share on its Settings tab instead of adding an organization rule.
  4. For a project-specific cancellation policy, add a rule with the project as Scope; it overrides the organization rule for that project from its date and can be deleted later without affecting anything else.
  5. "Please correct the highlighted fields.": check each value in the dialog (an Effective from date, percentages and rates between 0 and 100, a threshold of 0 or more) and press Save again.

Related

  • OrganizationScreen

    Your organization's profile and policies: name and invitation expiry, the two-factor requirement, the AI connectors switch, the help-assistant recording switch, the project defaults every project inherits (RERA gate, estimate validity, the two chargeable areas, carpet area offered, revenue method and trigger) and the effective-dated rules: the RERA escrow share that splits every sweep of a project's collection account, TDS on sales and booking cancellation.

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

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

  • RERA accountsScreen

    The RERA accounts statement for one set of books, or one project: what reached the collection account, what was swept to the separate and operative accounts and at what share, what was withdrawn from the separate account, and the movement on the four accounts' ledgers.

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

  • RERA accounts and the daily sweepConcept

    Every buyer payment enters the project's collection account; the bank sweeps it daily, the escrow share (70% under RERA 2016, or the project's own share) to the RERA separate account and the rest to the operative account. NirmaanOne mirrors the sweep as a Contra voucher per receipt the moment it clears, records certified withdrawals from the separate account, warns on receipts banked elsewhere and reports where the money stands; it never moves the money itself.

  • Receipt saved with a warning: it went outside the collection accountTroubleshooting

    A receipt of a project recorded into an account other than the project's collection account (or a GST receipt banked somewhere other than the GST or operative account, the collection account included) is saved with a warning that never blocks; under RERA every buyer payment enters the collection account, where the bank sweeps it, so the money sits outside the sweep until it is moved, while GST belongs apart from the sweep.

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