Why this is hard
Royalty billing goes wrong in a specific and predictable way. The franchisor computes from a spreadsheet built out of POS exports. The franchisee computes from their own till. The two disagree by a small amount, every month, and the argument is never actually about the money — it is about the fact that neither side can see the other's working.
The fix is structural, not arithmetic. When the royalty is computed from a sales dataset the franchisee can already open, under a policy they can already read, the disagreement has nowhere to live. What remains is a genuine question about a specific day, which is a five-minute conversation rather than a standoff.
The second failure is operational: one person, one spreadsheet, once a month. It works until they are on holiday, and it produces no history you can audit when a location is sold or a network is refinanced.
How to calculate and invoice franchise royalties: step by step
7 steps, in dependency order. Skipping ahead is usually what causes the rework.
- 1
Write the policy before you write the invoice
State the basis, the rate, and the edge cases in a form a franchisee can read: percentage or fixed amount, what sales it applies to, any minimum, any cap.
- Be explicit about the basis. Gross sales is the simplest to compute and the easiest to verify from a till.
- Record minimums and caps as part of the policy, not as a manual adjustment someone remembers to apply.
- 2
Derive the sales figure from the same source everyone sees
Compute from the POS-derived sales the network already reports on. If the invoice cannot be traced back to a dashboard the franchisee can open, expect it to be challenged.
- 3
Handle concessions and relief as recorded exceptions
Refurbishment relief, opening-period discounts and negotiated concessions are normal. Record them against the location with a reason and a date rather than adjusting a total by hand.
- 4
Bill a period as a run, and review it as a draft
Generate the whole period at once, inspect it, then send. A draft stage is what lets you catch a location whose POS did not sync before the franchisee sees an invoice built on a gap.
- 5
Produce one invoice per location
A separate invoice per site means a query about one location does not hold up collection across the network, and a multi-unit franchisee can still see their sites individually.
- 6
Send deliberately, and notify the recipient
Keep generation and sending as two distinct acts. When an invoice is sent, notify the franchisee in the system they already use, and give them somewhere to read it.
- 7
Automate the sweep once the manual run is boring
When a period has run cleanly a few times, put it on a schedule. Automate the routine case only after you have seen what the exceptions look like.
What good looks like
- A franchisee can trace any line on their invoice back to sales they can see themselves.
- The monthly run does not depend on one named person being available.
- Concessions have a reason and a date attached, not just a different number.
- Nothing is sent before someone has looked at the run as a whole.
- Every raised, sent and paid invoice leaves a record you could hand to a buyer or a lender.
Mistakes that make the effort worthless
Billing from a sales figure the franchisee cannot inspect.
Give both sides the same view first. A royalty system built on top of visibility settles disputes; one built on a private spreadsheet creates them.
One combined invoice for a multi-unit franchisee.
Invoice each location. It keeps a query about one site from blocking the whole balance, and it matches how the sites are actually run.
Generating and sending in one irreversible action.
Draft, review, then send. The review step is where a missing POS sync gets caught before it becomes a credit note.
Turning on automatic billing on day one.
Run it by hand until the exceptions are known. Automation should encode a process you already trust.
How Stores360 does this
The method above works with any tooling. This is how it is handled if you run it on Stores360.
- Royalty policies are defined as percentage or fixed, with minimums and caps, and are readable by both sides. Gross sales is the billable basis.
- Concessions and relief are recorded against a location rather than applied as an untraceable adjustment.
- A period is billed as a run that produces a draft; invoices are raised per location and sent as a separate, deliberate act.
- The franchisee is notified when an invoice arrives and has a screen to read the bill they were sent.
- Statements, an invoice history and an automatic monthly sweep sit alongside the manual run, and every raise and send is written to the audit log.
Frequently asked questions
What is a typical franchise royalty structure?
Most are a percentage of gross sales, often with a monthly minimum, sometimes with a cap, and frequently accompanied by a separate marketing-fund levy. The structure matters less than whether both sides can verify the calculation.
How do you handle a location whose sales did not sync?
Catch it at the draft stage. Reviewing a billing run before sending is precisely what stops a sync gap becoming an invoice you have to credit.
Can royalties be billed automatically each month?
Yes, once the manual run is predictable. An automatic monthly sweep is appropriate after you have seen how your exceptions behave, not before.
Should royalties be based on gross or net sales?
Gross is simpler to compute and far easier for a franchisee to verify against their own till, which is why it is the most common basis and the one least likely to be disputed.
Keep reading
How to track sales across multiple store locations
One comparable number per store per day — including the details that quietly break most multi-site sales reports.
How to connect a POS to head-office reporting
What a POS integration has to get right before head office should believe a single number it produces.
How to manage multiple store locations
The full method for running a network you can no longer walk around — from one set of numbers to standards that hold.
Or browse every how-to guide.