NirmaanOne Help
TroubleshootingReviewed 2026-09-29

"Already exists" or "listed twice": the name, code, number or line must be unique

Names, codes and numbers are unique within their scope (the organization, a project, a tower, a set of books) so that records can be told apart, and a line can appear once on a plan, offer or account; rename, reuse the existing record, or remove the duplicate line.

Messages this explains

  • “A project with this name already exists.”
  • “A society with this name already exists.”
  • “An organization with this name already exists.”
  • “An organization with this GSTIN already exists”
  • “An account with this email already exists.”
  • “A company with this name already exists.”
  • “A campaign named <name> already exists”
  • “A tower with this name already exists in this project.”
  • “This floor number already exists in the tower.”
  • “This unit number already exists on the floor.”
  • “A configuration with this name already exists in this project.”
  • “A parking area with this name already exists.”
  • “This parking slot number already exists in the parking area.”
  • “A pricing plan with this name already exists for this unit type.”
  • “A milestone with this code already exists in this project.”
  • “Another <item> already has the code <CODE>; choose a different name.”
  • “Code is required”
  • “Use letters, digits and underscores only”
  • “This code is already in use.”
  • “A template with this code already exists (codes are never reused).”
  • “A letterhead named <X> already exists”
  • “A workflow rule named '<name>' already exists”
  • “An event type with this code already exists.”
  • “This code is reserved for the engine's own event types.”
  • “A role with this name already exists.”
  • “A voucher type with this code already exists in these books.”
  • “A cost centre with this code already exists in these books.”
  • “A group with this code already exists.”
  • “An account with this code already exists in these books”
  • “An account with this name already exists in these books”
  • “Agreement number <no> is already on another booking”
  • “An account with this number and IFSC already exists”
  • “This amenity is already listed for the society.”
  • “This amenity is listed per tower; remove those rows before listing it project-wide”
  • “This amenity is listed project-wide; remove that row before listing it per tower”
  • “This person is already attached to the company.”
  • “This contact is already unsubscribed”
  • “This component is already on the plan”
  • “A component appears more than once.”
  • “This component appears more than once”
  • “This component is already on the offer”
  • “A benefit appears twice”
  • “A benefit appears more than once.”
  • “This milestone is listed twice”
  • “That person is already listed as a holder.”
  • “Already listed”

"Already exists" or "listed twice": the name, code, number or line must be unique

You saved a record and the app answered that its name, code or number is already taken, or that a line on a plan, offer, account or booking appears twice.

What you see

The message sits under the field it concerns (the Name, Code or number box turns red), or in the red banner at the top of the panel or dialog when it concerns the whole record.

Names that must be unique across the organization

  • New project and Edit project: "A project with this name already exists."
  • Societies: "A society with this name already exists."
  • New company and Edit company: "A company with this name already exists."
  • New campaign: "A campaign named <name> already exists".
  • New role (and the role editor): "A role with this name already exists."
  • New rule and Rule (also when cloning): "A workflow rule named '<name>' already exists".
  • Letterheads: "A letterhead named <X> already exists".
  • Create your organization and Organization: "An organization with this name already exists."; on sign-up also "An organization with this GSTIN already exists" under GSTIN, and "An account with this email already exists." under the email. The same email message answers an invitation on Users when that email already has an account anywhere in NirmaanOne.
  • Bank accounts: "An account with this number and IFSC already exists" under Account number.
  • Booking overview, editing the agreement: "Agreement number <no> is already on another booking".

Names and numbers that must be unique inside a project

  • Structure: "A tower with this name already exists in this project.", "This floor number already exists in the tower.", "This unit number already exists on the floor." and, for a unit configuration added from the tab, "A configuration with this name already exists in this project." (configurations are shared by the whole organization, whatever the wording says).
  • Parking: "A parking area with this name already exists." and "This parking slot number already exists in the parking area." (also from the generator).
  • Unit Pricing: "A pricing plan with this name already exists for this unit type." The same wording appears on Tenant Benefits for a duplicate benefit plan name, although the rule there is one name per project, whatever the unit type.
  • Construction Stages: "A milestone with this code already exists in this project."
  • Amenities: "This amenity is already listed for the society." under Amenity when the amenity is already on the project (project-wide, or for that tower); the wording is old and means the project. In the banner: "This amenity is listed per tower; remove those rows before listing it project-wide" or "This amenity is listed project-wide; remove that row before listing it per tower".

Codes

  • Lookups: the code is derived from the name as you type, so a clash shows under Name as "Another <item> already has the code <CODE>; choose a different name." A name that yields no code (only symbols or non-Latin letters) shows "Code is required" under Code. Lookup values added from another screen show "This code is already in use."
  • Document templates, message templates (New message template) and Organization templates: "A template with this code already exists (codes are never reused)."; a group template on Organization templates shows "A group with this code already exists." Codes typed by hand on document and message templates also validate as "Code is required" and "Use letters, digits and underscores only".
  • Event types: "An event type with this code already exists." or "This code is reserved for the engine's own event types."
  • Voucher types: "A voucher type with this code already exists in these books."; Cost centres: "A cost centre with this code already exists in these books."; Chart of accounts: Groups: "A group with this code already exists."; Ledgers: "An account with this code already exists in these books" or "An account with this name already exists in these books".

The same line twice

  • Unit Pricing, plan lines: "This component is already on the plan" under the second pick, or "A component appears more than once." on save.
  • Estimate charges (New estimate and the estimate wizard): "This component appears more than once".
  • A member's offer on Society & Tenants: "This component is already on the offer".
  • Tenant Benefits: Save greyed out with the hover reason "A benefit appears twice", or "A benefit appears more than once." on save.
  • Payment plan milestones (estimate wizard and booking wizard): "This milestone is listed twice".
  • Bank accounts holders: "Already listed" under the second row, or "That person is already listed as a holder." on save.
  • Company, People: "This person is already attached to the company."
  • Unsubscribes: "This contact is already unsubscribed".

Why it happens

Each of these is a uniqueness rule, and each has a scope:

  • Organization-wide names (projects, societies, companies, campaigns, roles, workflow rules, letterheads) are how people find records in lists and pickers. Two "Sea Breeze" projects would be picked by mistake on estimates, bookings and reports. The same goes for a bank account (number plus IFSC identifies one real account, and a duplicate would split its ledger) and an agreement number (the registered agreement belongs to one booking).
  • Per-project names and numbers (towers, floors within a tower, units within a floor, parking slots within a parking area, stage codes, pricing plan names per unit type) label the inventory that is sold and billed; a duplicate would make a unit or parking slot ambiguous on every document. A benefit plan name is unique per project for the same reason.
  • Amenities are listed either project-wide or per tower, never both, so the listing on offers and brochures cannot contradict itself.
  • Codes go into reports, integrations and generated documents, so they are unique and, for templates, never reused even after the template is retired: a document generated years ago must still point at one template. Lookup codes are derived from the name, so two names that reduce to the same code (for example "Walk-in" and "Walk In") clash. Event type codes that the workflow engine raises itself are reserved so that a custom type cannot shadow them. Within a set of books a voucher type, cost centre, group and ledger code or name must be unique because vouchers and reports refer to them by code.
  • Organization name, GSTIN and email are unique across all of NirmaanOne: the email is the login, and a GSTIN identifies one registered business.
  • Lines on a pricing plan, estimate, offer, benefit plan, payment plan or bank account name one component, benefit, milestone or holder each; the same one twice would double-count it.

How to fix it

  1. Find the existing record first. Search the list for the name, code or number in the message; remember to include inactive rows (Show inactive on Lookups, the Active filter on Bank accounts and Companies, retired templates on Organization templates). If it is the record you meant, open and edit it instead of creating another. Creating and editing need the Create and Edit permissions on the module concerned (Projects, Societies, Companies, Campaigns, Roles & Permissions, Workflow Rules, Towers, Floors & Units, Parking, Pricing Plans, Construction Stages, Lookups, Document Templates, Message Templates, Books, Chart of Accounts, Bookings, Bank Accounts).
  2. Otherwise choose a different name, code or number. For lookups, change the Name until the derived code differs; for towers, floors, units and parking slots check the numbering scheme before generating a range. Template and event type codes must be new, never a retired one.
  3. For a booking agreement number, open the other booking named by the number from Bookings and correct whichever is wrong (the Edit permission on Bookings).
  4. For an amenity, decide the scope: remove the per-tower rows before adding the project-wide row, or remove the project-wide row before listing it per tower (the Edit permission on Projects).
  5. For a duplicated line, remove the second row and pick another component, benefit, milestone or person; Save goes through once each appears once. On a benefit plan the hover reason on Save tells you why it is greyed out.
  6. For an email already registered, the person already has a NirmaanOne account (possibly in another organization). Ask them to sign in with it, or invite a different address.

Related

  • New projectScreen

    Create a project from its name, type, promoter entity and site address, then carry on in the setup wizard.

  • Edit projectScreen

    Change a project's facts on one page: basics, site address, land survey details and expected possession, and, on a redevelopment, the development agreement date and the fair value of the development rights. The settings the project inherits from the organization live on its Settings tab.

  • SocietiesScreen

    The list of existing housing societies your organization works with, where you add, edit and delete societies and open one to manage its members.

  • Create your organizationScreen

    Start a new organization in NirmaanOne: enter its name, GSTIN, your email and a password, and you become its administrator.

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

  • UsersScreen

    The people in your organization: invite new users, change their role, deactivate or reactivate them, reset a lost two-factor authentication, and resend or revoke pending invitations.

  • New companyScreen

    Register a company: its name and type, legal identity, statutory registrations, contact details and the type-specific fields for promoters, channel partners, vendors and contractors.

  • Edit <company name>Screen

    Change any detail of a company; only the fields you touch are saved, and a change of company type swaps the type-specific section and clears the old type's fields.

  • Company (<company name>)Screen

    One company's registrations, contact details, type-specific details, the people you deal with there and its bank accounts, with shortcuts to edit, delete or read the record's history.

  • New campaignScreen

    Create an email campaign: name it, choose the email template, tag a project, set the reply-to address and define who receives the mail, with a live count of the audience.

  • StructureScreen

    Build and maintain a project's towers (wings), floors and units, generate them in bulk, and see every unit's status and designation at a glance.

  • ParkingScreen

    Set up the project's parking areas (basement, podium, stilt) and their numbered parking slots, see who holds each parking slot, and allocate parking slots to society members.

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

  • Tenant BenefitsScreen

    Keep ready-made benefit plans (corpus, transit rent, shifting…) that a rehab officer applies to an allottee's offer in one go.

  • Construction StagesScreen

    Plan the project's construction stages (plinth, slabs, possession…) with their shares and dates, record commencement and completion, and keep the certificates and photos for each stage.

  • AmenitiesScreen

    List what the new project provides, either once for the whole project (clubhouse, pool) or on particular towers (refuge unit, society office).

  • LookupsScreen

    The dropdown lists every form draws on: contact types, lead sources, activity types, company types, bank account purposes, parking types, amenities, unit types and unit configurations.

  • Document templatesScreen

    The list of your organization's document templates (demand letters, offer letters, termsheets, agreements, allotment letters, receipts, cost sheets), with filters and the actions to create, duplicate, open or delete one.

  • LetterheadsScreen

    Set up the branding wrapped around generated documents: logo, header and footer, page size, orientation, margins and page numbers, for the whole organization or for one project.

  • New ruleScreen

    Build an automation rule on a full page: which records it watches, what starts it, which records qualify, and the ordered actions it carries out.

  • RuleScreen

    One automation rule's page: read or change its basics, trigger, conditions and actions, test it against a record, clone or delete it, and switch a system rule on or off.

  • Event typesScreen

    The named events a rule can listen to: the system events NirmaanOne raises itself and the custom events you add to chain rules or to raise from your own integrations.

  • New message templateScreen

    Write a message template on its own page: code, name, channel, record type, subject, the designed email body and its plain-text version, attachments, and the merge-field reference.

  • New roleScreen

    Name a new role, describe it and tick what it may do in each module, then create it so it can be given to users.

  • Voucher typesScreen

    The voucher numbering series of a set of books, one per kind of voucher: add a series, or change its prefix, suffix, digits and whether it restarts each fiscal year.

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

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

  • Booking overviewScreen

    A booking's home page: the applicant and unit, parking, dates, money summary, termsheet status and possession, with the buttons to edit the booking, see its history, jump to the opportunity or cancel it.

  • Bank accountsScreen

    One register of every bank account you pay from or into: the promoter's collection, RERA separate, operative, GST and operating accounts, and the payout accounts of channel partners, vendors, buyers and society members, with joint holders and verification.

  • UnsubscribesScreen

    The organization's opt-out list: contacts who will not receive campaign email, added by the link in every campaign mail or by hand, with the reason and when.

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

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

  • BookingsScreen

    The list of every booking in your organization, with project, status and date filters and a search by booking number, applicant name or phone, to find a booking and open it.

  • Lookup row or unit configuration cannot be deleted: deactivate it insteadTroubleshooting

    A lookup value that records already use, a system activity type the application writes itself, or a unit configuration that units carry cannot be deleted; untick Active so it stops being offered while existing records keep it.

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

  • Bank account cannot be saved, changed or deleted: IFSC, owner, purpose, holders or payments in the wayTroubleshooting

    The bank account panel refuses to save, the owner cannot be changed, a purpose is not available, or Delete answers that payments reference the account: each message, the rule and what to do instead.