Sooner or later you land the account that breaks your billing: a builder with a hundred and twenty houses going up in one subdivision.
It's one company, one contract, one billing address. But their accounts-payable department cannot pay a single invoice covering a hundred and twenty houses, because every house is its own job with its own budget. They need an invoice per lot.
One invoice per site keeps that account as a single customer with many sites, and splits only the invoicing.
When to use it
| Good fit | Not a fit |
|---|---|
| Builders and general contractors doing per-lot job costing | A customer with one or two sites who just wants one bill |
| Property managers rebilling each property to a different owner | Customers who want a single consolidated total |
| Municipalities with per-department or per-park budgets |
The tell is simple: the customer's own accounting needs to split the cost by location. If they're happy with one invoice listing every site, leave it off. The standard cycle invoice already groups its line items by site.
Don't solve this by creating a customer per location. You'd end up with a hundred and twenty profiles sharing one billing address, a hundred and twenty rate cards to maintain, and no combined balance.
Turning it on
Customer profile → Edit → Billing → One invoice per site
That toggle is the only new step. The description under it tells you how many sites that customer currently has, so you can see how many invoices a cycle would produce before you commit. There's also a See an example link showing a live sample of what your customer will receive.
Everything else about the customer is unchanged: same Rate Card, same billing cycle, same payment terms, same grace period.
Setting up the sites
Nothing here is special. It's the standard Sites and Rate Card workflow:
A site with no Rate Card row bills nothing and produces no invoice. A site added mid-cycle bills on the next run: only that site's missing invoice is created, and it joins the same group and the same link.
Tip for large customers: the Sites tab has a search bar that filters Street Addresses, GPS Pins and Rate Card together. On a 120-lot builder it's the fastest way to find one address.
Running the cycle
Exactly as it always runs: automatic pre-close drafts, the Generate Cycle Invoices button, or the arrears batch. There is no separate "per-site run."
The only visible difference is the review step, which shows one draft per site instead of one draft for the customer. Review and approve them the same way.
Two things worth knowing:
What the customer receives
One email. Not one per site. It shows the invoice count, the service period, the total amount due, a list of the invoices, and a button linking to their invoices page.
On that page:
| Action | What it does |
|---|---|
| PDF (per row) | Downloads that single site's invoice |
| Pay (per row) | Pays that one invoice |
| Download ZIP | Every invoice as a separate PDF, plus a summary cover sheet that sorts to the top |
| Print all (PDF) | One combined PDF, summary first, then every invoice |
| Pay all | Pays every open invoice in one payment |
The two download options serve two different jobs: the ZIP is for an AP clerk filing one PDF per lot, the combined PDF is for a bookkeeper printing the whole batch.
The summary cover sheet is not an invoice. It's a remittance summary listing every invoice number, site, date, amount and balance, with a total, so the customer can pay per invoice or write one check against the list. It's labeled as a summary so it can never be mistaken for an additional bill.
How payment works
Two paths, and both keep your books correct:
The customer sees one charge on their statement. You see every invoice marked paid separately. If part of the payment can't be applied, the remainder stays on the account as credit and applies to future invoices automatically. After a combined payment the customer receives a receipt showing which invoices it covered.
Paying by check works as always. The summary sheet gives their AP the invoice numbers they need.
What stays exactly the same
| Behavior | Same as any other invoice? |
|---|---|
| Payment terms and due dates | Yes |
| Grace periods before overdue | Yes, and the customer's page uses the identical rule as your invoice list and the PDF |
| Overdue reminders | Yes, but consolidated into one reminder listing the outstanding invoices |
| Invoice PDFs, branding, cash discount | Yes |
| Statements, payment history, reporting | Yes |
| Late fees | Yes, applied per invoice, so an unpaid batch generates one per unpaid invoice |
Things to watch
Turning it off
Flip the toggle off and the next cycle produces a single consolidated invoice again. Invoices already created keep their existing form, and the customer's existing link keeps working for the cycles it covers.