ERP Business Analyst in Gurugram

Developers: payment plans, demands and project accounts

Gurugram's residential launches stretch from towers along Golf Course Extension Road and the Dwarka Expressway to the newer sectors toward Sohna and Manesar. Whatever the segment, a developer's finance side is defined by how money arrives. A buyer books with an initial amount, signs the agreement and then pays against a plan, whether construction-linked, possession-linked or largely upfront. Each construction milestone triggers a demand letter, often copied to the buyer's lender.

The requirements I write for a developer cover:

• payment plans as configurable schedules, with milestones that site engineering must sign off before demands go out
• interest on delayed payments and any waivers, following the terms in your agreements
• tax that buyers deduct at source on installments, matched to their payments so accounts are not shown short
• charges passed on at possession, such as state development charges, maintenance deposits or power backup connections, where your agreements include them
• channel partner commissions, payable at an agreed collection stage and reversed if a booking cancels
• cancellations, refunds and the transfer of a unit to a new buyer
• collections routed to the designated project account and withdrawals tracked against verified progress, as your advisors interpret the regulator's rules

Construction in the NCR can also pause when pollution-control restrictions apply, which shifts milestone dates, so the requirement should state how demand schedules respond. The wider system picture sits on my page for property developers.

Office towers: rent, maintenance and recharged power

Cyber City, Golf Course Road, Udyog Vihar and the newer business parks along the expressways are full of towers leased floor by floor to corporate tenants. For the owner, or the company managing the building, billing is far more than monthly rent. A typical lease carries a rent-free period for fit-out, scheduled escalations, a security deposit, a separate charge for common-area maintenance and services, car parking, and electricity recharged from sub-meters, with diesel backup power often metered and billed apart from grid supply.

The requirements I write for a landlord cover:

• a lease abstract for each tenant, holding start dates, escalation rules, lock-in, notice and deposit terms as structured data rather than a scanned agreement
• how maintenance charges are budgeted, recovered from tenants and reconciled against actual cost, where your leases allow a true-up
• meter readings for grid and backup power by floor or unit, with the agreed tariff and loss rules applied
• tax that tenants deduct at source from rent and charges, tracked so their ledgers match yours
• invoicing and e-invoicing requirements, confirmed by your chartered accountant for each type of charge

Fit-out approvals, service requests and access cards usually live in facility tools. The requirement defines what those tools send to the ERP, how often and who checks it. The wider operating model is described under managing let property.

Employee transport operators: rosters, trips and attached cars

Gurugram's offices, contact centers and campuses run around the clock, and many employees travel in cabs that the employer arranges through a transport operator. These operators work from rosters that change daily: the client sends shift-wise pickup and drop lists, routes are planned, cars are assigned and trips run, often late at night. Many of the cars belong to individual owners who attach them to the operator's fleet and are paid monthly.

Each side of that arrangement needs clear requirements:

• Client billing by trip, by kilometer with rules for dead mileage, by a fixed monthly package per car or a mix, with no-shows, cancellations and waiting time treated as the contract says
• Pass-through charges such as tolls, parking and escort guards on night routes, recovered with evidence
• Owner payouts for attached cars, net of the operator's margin, fuel advances and penalties for missed trips
• Driver records, including licenses, verification status and training, held where your safety and legal advisors require them

The trip data usually comes from a routing or tracking app rather than from the ERP. I specify which system is the source for trips and distances, when the month is frozen for billing, and how disputes with the client are logged and settled before invoices go out. Safety obligations for night travel, especially for women employees, come from state rules and your contracts; the requirement makes sure the system records whatever your advisors say must be recorded.

Serviced apartments: corporate long stays and owner payouts

Around Cyber City, Golf Course Road and Sohna Road, serviced apartment operators host project teams, transferees and visiting executives for stays of weeks or months. Many of these operators do not own the flats. They lease or manage apartments from individual owners inside residential societies and pay each owner a fixed rent or a share of income.

That model creates requirements a hotel template misses:

• corporate agreements with negotiated rates, billing instructions and approval of extras, invoiced to the company while personal charges go to the guest
• monthly billing for long stays, with the tax treatment at each tariff level confirmed by your chartered accountant
• an owner statement per flat showing income, society maintenance, utilities, repairs and the operator's share under each agreement
• owner deposits, lock-in periods and condition checks when a flat is handed back
• reporting of foreign guests to the authorities, using the details your compliance team says must be captured and stored under your data protection policy

Bookings, check-ins and housekeeping normally run in a property management system, which stays. The ERP receives revenue summaries, guest ledgers for corporate accounts and the data needed for owner statements. I define that boundary, the reconciliation between the two systems and who resolves differences, so owner statements are no longer assembled in a spreadsheet each month. Related operating patterns appear on my hotel systems page.

Collecting evidence from sales galleries, building managers and dispatch desks

Requirement work in Gurugram involves people who are rarely in one room. Sales gallery staff sit at project sites, building managers handle tenants floor by floor, transport dispatchers work night rosters and finance teams answer to a promoter or a parent company. Long workshops suit none of them, so I build the requirement set from evidence first and use short sessions to confirm it.

The evidence differs by business:

• for developers, booking forms, payment plans, demand letters, receipts and possession offers, including a few awkward cases such as a cancellation or a transfer
• for landlords, lease abstracts, meter reading sheets, the maintenance budget and a recent tenant invoice set
• for transport operators, a week of client rosters, trip sheets, toll receipts and an owner payout calculation
• for serviced apartments, corporate and owner agreements and the property management system's revenue reports

Dispatch supervisors on night shifts can record a short walkthrough instead of joining a live call. Where staff explain more comfortably in Hindi, a bilingual colleague helps; the engagement itself runs in English. Each requirement is then numbered, tied to an example and later turned into an acceptance test.

The resulting document follows how I structure a BRD, and the city context is set out in the Gurugram ERP overview. All of it is delivered remotely, with visits by arrangement.