How a CRM Should Handle Property-Management Billing and Service Locations
The company paying the invoice and the property receiving the work are often different records. A CRM should preserve both without duplicating the customer.
Founder of LeadFlow · Owner of JMB Business Solutions
One account can represent many physical job sites
A property-management company may approve work, receive invoices, and maintain the business relationship while the actual work occurs at an apartment, community, motel, commercial building, or resident address.
Treating every site as an unrelated customer creates duplicates. Treating every site as the parent’s office address destroys job-level accuracy. The CRM needs a parent billing account and reusable service locations beneath it.
What belongs on the parent account
The parent should hold the management company’s name, billing contact, billing address, email, phone, account-level notes, and standing commercial terms. It is the relationship and billing identity—not a substitute for the work location.
- ✓Management-company identity and billing contact
- ✓Primary billing address and communication preferences
- ✓Account-level agreement or standing contract context
- ✓Authorized users and overall relationship notes
What belongs on the service location
Each service location should preserve the property or community name, street address, city, state, ZIP, unit, resident or site contact, access instructions, and location-specific notes. The location can be reused for future estimates and jobs without becoming another parent customer.
When a unit matters, it must follow the estimate into the sale, production job, invoice, document, and expense record. Otherwise two jobs at one complex can reduce the wrong balance or absorb the wrong receipt.
Billing remains centralized while profitability stays local
The parent company can remain the invoice recipient while every contract and expense stays scoped to the individual site job. That separation supports consolidated relationships without mixing money between properties.
A receipt for materials used at Blue Spruce Motel, for example, belongs to the Blue Spruce production job. It does not belong to the Green Springs Capital parent record merely because Green Springs controls billing.
Historical data needs careful restructuring
Older systems often contain each address as a separate customer because parent-account support did not exist. Migration should not blindly merge records. Create the true parent, create verified service locations, move current estimates and jobs deliberately, and preserve historical links until ownership is confirmed.
The key rule is factual correction without changing unrelated money. Reassign the service location while preserving contract amount, invoice status, and payment history unless there is separate evidence those values are wrong.
Frequently asked questions
Quick answers
Should a property-management company be duplicated for every address?
No. Use one parent billing account with multiple service locations so the relationship remains centralized and each job retains the correct physical address.
Can each property have separate estimates, invoices, and profit?
Yes. Each estimate, sale, production job, invoice, payment balance, and expense should remain scoped to the exact service location and job.