HVAC, Plumbing, and Electrical Customer Sites: Align Salesforce Accounts With NetSuite Billing Hierarchies

What this looks like in commercial HVAC, plumbing and electrical contractors

An MEP contractor services a portfolio of medical offices. A management company coordinates access, separate property entities pay the bills, and one central facilities director approves work. Salesforce groups the relationship under the management company. NetSuite needs the correct payer for each site. When the property manager changes, technicians still need the same equipment and service history, while the account team needs a new contact. Those changes should not create a new physical site.

Records, ownership, and update rules

Work through the process

1. 01
   Separate parties before mapping

   Write down who requests service, who grants access, who approves charges and who pays. A single organization can fill several roles, but the model must also support different parties. Use these roles to choose relationships rather than forcing every contact onto one customer record.
2. 02
   Keep site identity stable

   Assign a site key that survives a property-management change or customer rename. Store the street address as an attribute, not the sole identifier. Several suites, rooftop units or electrical rooms can share an address, so equipment and service history need more precise relationships.
3. 03
   Map the finance hierarchy deliberately

   Connect the Salesforce relationship to one or more NetSuite customers using approved external references. Include subsidiary or branch context where required. The NetSuite Account object is not the equivalent of a Salesforce Account; validate the actual customer and project objects in the selected mapping.
4. 04
   Apply effective-dated changes

   When management or billing responsibility changes, capture the effective date and review open work. Do not automatically move unpaid historical invoices to the new payer. Route contracts, future service requests and unresolved receivables through their respective owners so the transition is commercially accurate.
5. 05
   Test dispatch and billing views

   Ask a dispatcher to locate the correct site and an accounts-receivable user to identify the payer for the same service call. Test a portfolio with multiple legal entities, a renamed site and a management transfer. Confirm connector permissions and object eligibility for every intended update.
6. 06
   Make the site lookup work for field language

   Keep verified aliases such as the customer's building name or local campus label searchable, while the stable site ID remains the actual join key. Dispatchers and technicians often know a location by a name that differs from the legal customer. An alias helps them find the right record without creating another billing account. Have operations review duplicate aliases, especially where several properties use labels such as main office or building one.

Handle the exceptions explicitly

Two buildings share a billing customer

Preserve separate site IDs and route technician instructions by site.

Property manager changes midmonth

Update relationship contacts with effective dates while finance reviews billing responsibility.

Service request arrives without a site

Ask for the location or asset reference rather than guessing from the caller's company.

What to verify before expanding

• A site keeps its service history after a management change.
• The dispatcher and billing clerk see the same service-call reference.
• Different payers under one portfolio remain separate.
• A CRM contact edit cannot rewrite historical invoice ownership.

Technical references

• Stacksync Salesforce connector requirements
• Stacksync NetSuite connector and object support