Quote to invoice across locations: connecting your tools

In a services company with several branches, a single account passes through a lot of hands. Sales writes the quote in the CRM. The customer signs. The contract goes into a shared folder. The branch schedules the jobs in its own tool. The technician does the work. Someone prepares the invoice in other software. Everyone does their part well, and yet at month end some completed jobs haven’t been invoiced, and nobody knows exactly which.

The usual reflex is to look for the one system that handles everything from quote to invoice. Sometimes that’s the right answer. But for a multi-location business whose branches each have their own habits, it’s a long and risky project. There’s a lighter route: keep the tools, and get the handoffs between them right.

Where quote to invoice breaks

The problems almost always cluster in the same places:

• The signed quote is never scheduled. The signature lands in the CRM or an inbox, and nobody creates the job in the branch’s scheduling tool.
• The contract doesn’t generate its visits. A maintenance contract includes regular visits, but they’re never created, or not at the right frequency.
• The job is done but never invoiced. It wasn’t marked complete, an extra agreed on site wasn’t recorded, or a multi-day job was billed only once.
• The contract’s price review or renewal is forgotten.
• Branches charge different prices for the same service, and discounts are decided case by case.
• Each tool has its own reference. Quote number, contract number, job number, invoice number: nothing links them without searching by hand.

Why multiple locations make it worse

In a single-site business, these gaps often get caught because everyone talks to each other. Across several branches, that stops being true. Each branch names clients and sites its own way, uses its own statuses (“done”, “complete”, “closed”, “OK”) and sometimes its own scheduling tool. Head office only gets an overall picture by asking each branch for spreadsheets.

There are rules to respect, too. Invoice numbers must be unique: in the UK, for example, an invoice must carry a unique identification number, and in France numbering must be continuous, though separate series are allowed, such as one per billing site. That makes a “one branch, one prefix” scheme workable for invoices as well, as long as no two invoices ever share a number.

One shared reference, not one giant system

The key piece is simple: one reference per account, carried on every document. For instance the branch code followed by the contract number. It appears on the quote, the contract, every job and every invoice line.

With that reference, you can finally ask the question that matters: for each account, what was signed, scheduled, done and invoiced?

Then harmonise a minimum across branches: the same list of statuses, the same service names, the same client record. Each branch can keep its own scheduling software, as long as they all speak the same language.

Handoffs worth automating

Once the shared reference and common statuses are in place, a few handoffs do most of the work:

• Quote signed → contract and jobs created as drafts. Marking the quote as signed creates the contract and the planned jobs in the branch’s tool, for the branch to confirm.
• Job marked done → draft invoice line. Including any extras recorded on site. Never an invoice sent automatically: a person checks it and sends it.
• Contract nearing its end → reminder to the account manager.
• A daily or weekly exceptions report: signed but not scheduled, done but not invoiced, contracts coming up for renewal, clients missing key details.

That exceptions report is often where you get the most return for the least effort. It makes visible what used to slip through; someone still has to fix it.

A note for companies invoicing in France

Since 1 September 2026, every French company must be able to receive electronic invoices. Large and mid-sized companies must also issue them; small businesses will have to from 1 September 2027. On the same timetable, invoices gain four new mandatory details: the customer’s company number (SIREN), the delivery address if it differs, the nature of the transaction (goods, services or both) and, where relevant, the option to pay VAT on debits. For a multi-site business working with other businesses, the message is the same as above: clean client records, entered once, and information that flows correctly from quote to invoice.

What stays human

• special prices, discounts and goodwill gestures;
• disputes and credit notes;
• scheduling trade-offs: emergencies, absences, priorities between clients;
• checking every invoice before it’s sent;
• renegotiating a contract when it comes up for renewal.

When not to connect yet

• One of the tools is about to be replaced. Wait for the new one.
• There’s a single site and few accounts. A shared spreadsheet and a weekly check are often enough.
• Branches don’t share statuses, prices or contract templates. Harmonise first. Otherwise automation just copies the mess faster.
• Nobody owns the exceptions report. A report nobody reads changes nothing.

A weekly “done but not invoiced” check to start with

Take a recent month and one branch. For every completed job, find the quote, the contract and the invoice. Count what’s missing. Done by hand once, this small exercise shows where your chain breaks, and so which handoff to automate first. Then turn it into a weekly report.

We’ve written this scenario up as a use case: Quotes, contracts, scheduling and invoices connected across branches. For a real project that matches what was declared against what actually happened, see sessions checked before payroll: the same logic, applied to coaching sessions.

If you’d like to run this exercise with us on one branch, tell us how you’re organised.

Sources

• GOV.UK, Invoices: what they must include.
• Service Public Entreprendre, Tout savoir sur la facturation (in French; numbering and series per site, e-invoicing timetable, new mandatory details; checked by the publisher on 7 August 2026).
• French Ministry of the Economy, Facturation électronique entre entreprises : coup d’envoi de la réforme (in French), 1 September 2026.