ERP Business Analyst in New York

The city layer that generic requirements miss

Most ERP requirement templates are written with federal and state rules in mind. New York City adds its own layer. Partnerships and other unincorporated businesses operating in the city may face a separate city business tax. Certain commercial tenants in Manhattan face a commercial rent tax. Sales tax collected in the city combines state, city and regional components. Employers in the wider metropolitan area may also pay a regional transportation payroll tax.

None of these are things an ERP business analyst should interpret. That is the work of your tax advisor. But each one depends on data the business has to capture somewhere: where work is performed, which leases relate to which premises, which revenue arises in the city, which employees work where. If the ERP is configured without those fields and reports, the finance team ends up rebuilding them at year end from emails and spreadsheets.

So I run a short session with your finance lead, and where useful your advisor, to list every city and state obligation that touches the system. Each becomes a requirement with an owner, the data it needs and the report that supports it. The broader US requirements, such as multi-state sales tax and contractor reporting, are covered on my ERP business analyst page for the USA.

Freelancers, agencies and the payables process

Advertising agencies, publishers, production companies, fashion houses and design studios in New York often rely on freelance writers, photographers, stylists, editors and developers. The city, and more recently the state, have introduced rules on written agreements and timely payment for freelance work. Your counsel will tell you exactly what applies, but the operational consequence is clear: payables needs to know which suppliers are freelancers, what was agreed and when payment is due.

In many firms that information lives in producers' inboxes. A project lead agrees a fee by email, the invoice arrives weeks later, and finance has no record of the agreed payment date. During requirements gathering I map that journey from engagement to payment and write requirements for each step: a supplier category for freelancers, a link from each purchase order or agreement to its job, an approval route that does not stall when a producer is on a shoot, and an aging report sorted by agreed due date rather than invoice date.

I also capture how freelance costs flow into job or campaign profitability, because the same data serves both purposes. These requirements then go into scripted demos, where each vendor shows how a freelance agreement becomes a payable. The method is set out on my ERP requirements gathering page.

Real estate owners, leases and building data

New York companies tend to have complicated relationships with space. An operating business may lease several floors, sublet part of one and charge shared space costs to subsidiaries. A property owner may hold buildings in separate entities with their own lenders, managing agents and reporting needs. For both, the ERP requirements go well beyond rent payments.

I document how each lease is recorded: premises, landlord, term, escalations, sublet income and how occupancy costs are allocated to departments or entities. That record matters for lease accounting, which your auditors will review, and it supports the data your tax advisor may need for city-level rent obligations.

For building owners there is a newer consideration. City rules on building emissions require owners of larger buildings to report energy use and meet limits over time. Specialist energy platforms usually hold the meter data, but finance still needs to budget for compliance work, capital projects and possible penalties by building. I write requirements for how that information reaches the ERP, which dimensions it is tracked against and who approves related spending.

These requirements sit inside a business requirements document structured by process, and they feed directly into the real estate ERP evaluation if a new platform is being chosen.

Nonprofits, foundations and cultural institutions

New York has a large nonprofit sector: foundations, social service providers, hospitals' affiliated charities, museums, performing arts organizations and membership bodies. Their ERP requirements differ sharply from those of a commercial firm, and a business analyst who treats them like a small company produces the wrong document.

The central requirement is fund tracking. Grants arrive with budgets, allowable cost rules, reporting periods and sometimes matching requirements. Program staff need to see what is left in each grant, finance needs to allocate shared costs fairly, and the board needs reports that separate restricted and unrestricted funds. Government contracts, including city-funded programs, add their own invoicing and documentation rules.

I map the cycle from award to final report: how a grant is set up, how costs are coded to it, how time is allocated across programs, and how drawdowns or reimbursement claims are prepared. Each step becomes a requirement with a test case. I also record what stays outside the ERP, such as donor relationship systems or ticketing platforms, and define the interfaces between them.

Charity regulators and auditors have their own expectations, which your accountant will confirm. The requirements simply make sure the system can produce the evidence they ask for without a month of manual work.

Union labor, public works and payroll data boundaries

Construction, building services, hospitality and some healthcare employers in New York work with union agreements, and contractors on public projects may face prevailing wage rules and detailed payroll reporting obligations. Payroll itself is usually run by a specialist provider, not the ERP, but the ERP still needs labor data for job costing, billing and fringe benefit fund remittances.

The requirement work here is mostly about boundaries. I document which system holds employee records, pay rates, classifications and hours; how hours are captured on site or by shift; how labor cost reaches each job or contract; and how benefit fund contributions are reconciled. I also note how work location is recorded, since employees across New York, New Jersey and Connecticut may be taxed differently, a point for your payroll provider and advisor to confirm.

These details are tedious to gather and expensive to fix after go-live. Written down early, they let vendors show precisely how their system handles your labor model, and they become user acceptance tests later, an approach set out on my ERP testing and UAT page. If you want to see how this fits a wider selection, my New York ERP consultant page explains the full engagement, or you can ask about a requirements engagement directly.