What PoolBoss Says
Keep one customer record for the party that pays, and attach a separate service location for each address you service. One invoice can then cover every site, or each site can bill on its own. Every location holds its own pools, gate code, and service history, and reporting still shows you which property is profitable.
A property manager calls and hands you nine houses. Or a customer mentions the second home across town, or an HOA wants the clubhouse pool plus the two spas at the gate. The work itself is straightforward. The record-keeping is the part that goes wrong, and it goes wrong in the first ten minutes, when someone decides whether that is one customer or nine.
Get it wrong and you find out in month two, when the accounts-payable contact asks why she received nine invoices and you cannot tell her which property costs you the most to service. What follows is the structure that avoids that, what belongs at the site level rather than the account level, how the invoice split actually works, and what to name each site.
At a glance
Key takeaways
- One customer record per paying party, one service location per address - that structure is what makes a single invoice and a per-property profit number possible.
- Entering the same property manager once per address is the mistake; it produces one invoice per site forever and no account-level view of anything.
- Put the address, gate code, and access notes on the location, not on the customer, so the work order shows the tech where they are actually going.
- A site with a pool and a spa is one location with two bodies of water, and each gets its own readings and history.
- One combined invoice is the default; billing locations separately is a per-customer setting you can turn on or off without touching the records.
- Each location can carry its own recurring rate, so a hotel rooftop pool and a clubhouse lap pool under one account can be priced differently.
- Record the customer's own code for each site alongside your name for it, and archive rather than delete a property that drops off the account.
How do I manage a customer with pools at more than one property?
Give the paying party one customer record, then create a service location under it for every address you service. The location is the site: it owns its own address, gate code, and access notes, and the pools at that address attach to it. That single structural choice decides whether the account bills on one invoice or eleven, and whether you can ever answer which of the properties is making you money.
The alternative - entering the same property manager once per address - looks identical on day one and costs you every month after. Set it up the other way and you hold a customer's properties, pools and access details in one record, which is what makes a single invoice and an account-level profit number possible at all.
- Create the customer as the party that pays, not the property. For a property management company that is the company; for a homeowner with two houses it is the homeowner. If the invoice goes to one accounts-payable email, that is one customer.
- Add a service location for every address. Give each one its own street address, gate code, and access notes. A ten-property account is one customer and ten locations, not ten customers.
- Attach each body of water to its location. A site with a pool and a spa is one location with two bodies of water, so both get their own readings and their own service history under the same address.
- Put the site-specific access details on the location, never on the customer. A gate code stored at account level is correct for one property and wrong for the other nine.
- Decide the invoice shape once, at setup: one combined invoice for the whole account, or one per site. It is a per-customer setting you can change later, not a structural decision you are stuck with.
One customer per payer, one location per address
The mistake that costs the most is entering the same paying customer once per address, because every consequence of it arrives later and none of them are reversible cheaply. An operator in Scottsdale, Arizona signs a property manager running nine rental homes plus a small 12-unit complex with one pool and one spa. Entered as ten separate customers, the manager gets ten invoices a month, ten records to update when her billing email changes, and there is no view anywhere that answers "which of these properties is losing me money."
Entered as one customer with eleven service locations, the same book is one invoice at $1,485/month, each site keeps its own gate code and pool record, and the report shows that the complex - two bodies of water on one $220 line - is carrying more chemical cost than the three farthest rentals combined. Same work, same money in, completely different ability to manage it.
| One customer, many service locations | A separate customer per address | |
|---|---|---|
| Invoices the customer receives | One covering every site, or one per site if you turn the split on | One per address, always |
| Service history | Per site, all under one account | Split across records that never join up |
| Profit by property | Revenue and chemical cost per location | Per record only, with no account-level total |
| Updating the billing contact | Once | Once per address, and one gets missed |
| Adding an eleventh property | Add a location | Create another customer and re-enter the contact |
The technician needs the site, not the billing address
Everything a tech needs to get in and do the work belongs on the location, because it is true of that address and no other. The street address, the gate code, the access notes about the dog or the side entrance, which building the equipment room is in - all of it is site-level fact. The customer's own address, meanwhile, is often just where the bill goes, and on a property-management account it is an office nobody services.
This is the practical difference between a multi-property account that runs and one that generates a phone call a week. A tech who opens a stop and reads the billing address for a management company 15 miles away has to call the office to find out where they are actually going. Put the detail on the site and the work order carries the right address and the right gate code on every visit, which is the same reason it matters when you route a multi-site HOA account - the stop is the location, not the customer.
One deliberate limit worth knowing: changes to a site's name and address are written to the account's activity log, but gate codes and access notes are not. That is on purpose. An activity log is append-only and readable by everyone at the company, so copying a door code into it would publish a credential into a record nothing can redact - and access details usually change precisely because the old ones should stop circulating.
One invoice or nine is a setting, not a system limit
By default a multi-location customer gets one combined invoice covering every site, which is what most property managers want: one bill, one payment, one reference. Turn on billing locations separately for that customer and the automatic run emits one invoice per service location instead, each labelled with the site it covers. Nothing about the underlying records changes - it is the same eleven locations either way, and you can switch it back.
Both shapes are common and the choice is the customer's, not yours. A management company reconciling against eleven separate property ledgers usually wants eleven invoices; an HOA board treasurer wants one. Ask at signup rather than assuming, because changing it after three months of statements means explaining why the paperwork looks different. The mechanics of the account itself - terms, PO numbers, who signs - are the same ones you use to bill a commercial pool account.
Price can vary by site too. Each location can carry its own recurring rate that overrides the customer's default, which matters because the properties under one commercial account are rarely worth the same money - a rooftop pool at a hotel and a lap pool at the clubhouse are different jobs. Where no site rate is set, the location inherits the customer rate, so an account where every property is worth $135/month needs no per-site setup at all.
Name each location the way the customer names it
Give every site the name the customer uses out loud, then record the customer's own internal code alongside it. Your name for a site ("Building A", "Clubhouse") is what your techs read on a work order. The customer's code ("Store #4412", "Bldg A-2") is the only identifier that appears on their work order, their ledger, and the email they send your office. A location holds both, and the code shows up on work orders, quotes, and per-location invoices.
The cost of skipping this is small and constant. A property manager phones about "Store #4412", your tech is looking at "Building C", and every one of those calls takes a few minutes that nobody bills. On a twelve-site account that is a standing tax on the relationship. The related failure - the same property entered twice under slightly different names - is worth fixing at the same time, and the fix is the same one you would use to clean up duplicate customer records.
When a customer drops a property but keeps the rest, archive that location rather than deleting it. An archived site disappears from the customer's list and from the pickers, but its address, access history, pools, and every visit logged there are preserved and can be restored if the property comes back - which on a management account it often does. The one site you cannot archive is the customer's default location, because losing a customer's primary property means archiving the customer, not the site.
FAQ
Frequently asked questions
Should I bill each property separately or send one invoice?
Ask the customer, because both are normal and the answer depends entirely on how their books work. A property management company that reconciles each property against its own ledger usually needs one invoice per site, with the property identified on it, or their accounts-payable clerk has to split your total by hand every month. An HOA board or a homeowner with two houses almost always prefers one invoice and one payment. The default worth starting from is one combined invoice, because it is less paperwork for both of you and easier to chase when it goes unpaid. What matters more than the choice is that it stays consistent: switching a customer from one invoice to nine after six months generates questions about every line, and the first month of the new format usually gets queried in full. Decide it at signup, write it in the agreement, and revisit it only if they ask.
How do I handle a customer whose second home is on a different route?
Keep both properties on the one customer record and let each site sit on whichever route serves its geography. The account structure and the route structure are separate: a customer is a billing relationship, a route is a driving problem, and nothing requires them to line up. A homeowner in Phoenix with a cabin in Prescott is one customer, two locations, two routes, and one invoice that covers both. The mistake is creating a second customer just because the second property falls on a different day - it works fine right up to the point where the customer asks for one bill or you try to work out what the account is worth. Where the two properties differ in what the work is worth, set a rate on the location so the distant site is not priced like the one five minutes from your yard.
What do I do when a property manager changes companies?
Change the contact, not the structure, as long as the party paying you is the same. If the management company is still the customer and only the individual has changed, update the contact details on the existing customer record and every property stays exactly where it is, with all its history intact. It is a five-minute job. The harder case is when the owner switches management companies entirely: the new company is a different paying party, so it is a new customer record, and the properties move to it. Do not delete the old record - archive it, so the prior year of service history and invoices remains attached to the entity that was actually billed for them. Ask the new manager for their internal code for each property on the first call, because it will not match the last company's.
Can I price each property differently under one customer?
Yes. Each service location can carry its own recurring rate that overrides the customer-level rate, and any location without one simply inherits the account rate. This matters on almost every commercial account, because the properties under a single payer are rarely equivalent work: a 12-unit complex with a pool and a spa is not the same job as a small rental-house pool, and pricing them identically means one of them subsidizes the other invisibly. Set the rate where the work differs and leave the rest inheriting, so a nine-house account where every pool is worth $135/month needs no per-site setup at all. The practical test is whether you would quote the two properties differently as separate accounts. If yes, price them differently here, or your per-property profit numbers will show a difference in cost with no matching difference in revenue.
How do I see which of a customer's properties is actually profitable?
Compare revenue against chemical cost per location, which only works if each property is its own location under one customer rather than its own customer. Revenue per site comes from the rate attached to that location; cost comes from what your techs actually dose there, visit by visit. The gap between them is where the surprises live. A single complex with two bodies of water can quietly consume more chemical than three rental-house pools combined while billing as one line, and nothing about the monthly total tells you that. Check it once a quarter rather than monthly, since one hot month or one algae recovery will distort any single period. When a property is consistently underwater, you have two honest options - reprice that site at renewal, or hand it back - and both conversations are far easier with a per-property number than with a feeling about the account.
What happens to the history if a customer drops one property but keeps the others?
Archive that location instead of deleting it, and everything is preserved. An archived site is hidden from the customer's location list and from pickers, so nobody schedules it by accident, but its address, access details, pools, and every visit and reading logged there stay attached to the account and can be restored if the property comes back. On a management account that happens often enough to matter - properties rotate in and out as their contracts turn over. Deleting is the option to avoid: it strands the bodies of water that were under the site and loses the address and access history irrecoverably, which is exactly what you want two years later when the same property returns and someone asks what the equipment looked like last time. The one site that cannot be archived is the account's default location, since losing the primary property means closing the customer, not the site.
Should a homeowner with a pool and a spa at one address be one location or two?
One location with two bodies of water. The location is the address you drive to; the pool and the spa are the two things you service once you are there. Structuring it that way means one set of access details, one stop on the route, and one arrival, while the spa still keeps its own chemistry history separate from the pool's - which you need, because a 400-gallon spa and a 20,000-gallon pool do not behave alike and their readings should never be averaged together. Create a second location only when there is genuinely a second address to drive to. The signal is simple: if your tech parks once and services both, it is one location. If they get back in the truck, it is two.
