ERP Business Analyst in San Francisco

Why a traditional BRD often stalls in a San Francisco company

Many teams in the city build software for a living. Their working rhythm is a backlog, short cycles and acceptance criteria that tell everyone when a piece of work is done. Hand them a long business requirements document in the classic format and the reaction is predictable: a quick skim, a few comments and then silence until a partner starts building against assumptions nobody checked.

I keep the substance of a proper BRD and change its shape. Requirements are grouped by process, from quote to cash, procure to pay and record to report. Within each group, every need is a user story stating who needs what and why, followed by acceptance criteria written with real examples from your business. Priority is agreed with the finance lead, not left to the partner.

This format moves cleanly into the tracking tool your engineers and partner already use, which makes progress visible to founders without extra reporting. The underlying method, including the fit-gap view and scope rules, is described on the ERP BRD consulting page. The national view of US requirements, including sales tax and vendor reporting, sits on the US ERP business analyst page.

Controls written as requirements before a listing or a large raise

Bay Area companies preparing for a public listing, an acquisition or a demanding investor often discover late that their finance systems were set up for speed, not control. Anyone can post a journal, approvals happen in chat, and admin rights were handed out freely when the team was small. Fixing that after go-live is slower and more disruptive than designing it in.

During analysis I treat controls as requirements in their own right. Who can create a vendor and who can pay one. Which journal entries need a second approver. How user access is requested, approved and reviewed. What the system must log when a setting changes. Each item becomes a story with acceptance criteria, so testers can show it works and auditors can see that it was tested.

The actual control framework, including which controls matter and how they are evidenced, is decided by your finance leadership and auditors. My contribution is to make sure the ERP design gives them the features and records they need. The approval workflow page covers how these rules are commonly configured.

Equity, payroll and the data the ERP should not hold

Equity compensation is a normal part of pay at many San Francisco companies. Grants, vesting schedules and exercises usually live in a dedicated equity management platform, while salaries and benefits run through a payroll provider. The finance team still needs the accounting effects in the ledger: compensation expense, payroll liabilities and related entries by department or entity.

A common mistake is to pull too much employee detail into the ERP because it seems convenient. That spreads sensitive data across more systems and more users than necessary. In the requirements I define the boundary clearly: which summarized entries flow into the ledger, at what level of detail, how often, and who in finance can see the supporting reports in the source system.

San Francisco also has employer requirements of its own, such as rules on health care spending, that touch payroll data. Your payroll provider and employment advisor interpret those rules. My job is to make sure the requirements describe where the relevant figures are captured and how they reach the general ledger, so finance can reconcile them without manual rework at month-end.

City business taxes and the data they depend on

San Francisco levies business taxes of its own on top of state and federal obligations, including a tax measured on gross receipts. How receipts are classified, which activities they relate to and how they are allocated to the city are questions for your tax advisor, and the rules can change. What a business analyst can do is make sure the ERP captures the data those calculations require.

In practice that means requirements for revenue to carry the right business activity or product classification, for customer and delivery locations to be recorded consistently, and for payroll and headcount by work location to be available when the advisor asks. Companies with staff split between the city, the Peninsula and remote locations need especially clear location data, because the answer can depend on where work is performed.

I write these as reporting requirements with sample outputs, then check during testing that the reports can be produced without spreadsheet surgery. The tax positions themselves stay with your advisor. Multi-entity structures that often sit behind these questions are discussed on the multi-company ERP page.

Teams abroad, contractors and the requirements they add

Bay Area startups often hire beyond the United States early: an engineering group in another country, a sales team in Europe, contractors scattered across time zones. Some staff are employed through a local subsidiary, others through an employer-of-record service, and others invoice as independent contractors. Each route creates different transactions in the ledger.

Requirements for this part of the business cover intercompany service charges and their settlement, employer-of-record invoices that bundle salary, fees and local costs, contractor onboarding and payment approval, and currency handling for each of those flows. They also cover reporting: headcount cost by function across every route, so leadership sees the real cost of a team regardless of how it is employed.

Transfer pricing and contractor classification are specialist topics for your advisors, and I keep them out of my recommendations. The requirements simply make sure the ERP can record what those advisors decide. When the analysis is done, each story is linked to a test scenario, which is how the work hands over cleanly to UAT. For the wider picture of who does what on the project, see the freelance ERP consultant page for San Francisco.