Billing cloud licences by hand: the quiet margin killer

Why licence billing eats so much time

The effort does not come from one difficult task but from many small ones repeating every month. Licences sit in several systems: Microsoft licences with the CSP distributor, email security with one vendor, backup with the next, plus your own services. Every portal has its own export format, its own name for the same product and its own cut-off date.

On top of that, the numbers change constantly between two billing runs. A customer hires someone, a mailbox is added, a project ends and ten licences fall away. Tracking that monthly in a spreadsheet means running a second set of books alongside the real one.

• Download an export per portal and bring it into one format
• Map product names to your own items - often by hand, often from memory
• Hold quantities against the stored contract quantities and chase the differences
• Calculate mid-period additions and removals pro rata
• Produce, check and send the invoices
• Answer the queries when a customer does not recognise a line

Five mistakes that regularly cost money

The following patterns show up in almost every business billing by hand. What they have in common is that they do not stand out: no document is missing, no gap appears - the number is simply quietly wrong.

• Quantity drift: the portal says 42 licences, the invoice says 38. Nobody did anything wrong, the customer simply added some themselves. The old quantity gets billed anyway - month after month.
• A confused billing cycle: the same licence billed monthly and annually is commercially not the same product. A quantity query that ignores the cycle adds both together and creates lines with the quantity of every cycle - with a backdated contract start and a corresponding billing backlog.
• A forgotten pro-rata charge: the addition on the 12th is only billed from the first of the following month. For one customer that is bearable; across a year and the whole estate it adds up to a respectable number.
• A cancellation that carries on: ended in the portal, not in the billing. That does stand out - to the customer, not to you. A refund plus the loss of trust costs more than the amount ever did.
• A term change counted as a new purchase: when a subscription changes cycle or is renumbered, many reports read it as an addition. Then both get billed - the old line and the supposedly new one.

The purchase price moves too

A second point, often overlooked: it is not only the quantities that change but the purchase prices. Distributors adjust terms, vendors change list prices, exchange rates shift. Calculate a sales price once and carry it forward for years, and at some point you are selling at cost without noticing.

So it makes sense to check the purchase price against the catalogue automatically on a regular basis and get a warning when the margin falls below a threshold you set - not first at the annual review.

What the effort really costs

Work it out for yourself rather than estimating. The formula is simple: time per customer per month, times the number of customers, times twelve. Look after 60 customers and spend just ten minutes each on reconciliation and clarification, and you spend 120 hours a year on licence billing - three full working weeks in which nobody solves a ticket.

The bigger item is rarely the time, though, but what never got billed. Even one per cent of quantity drift across the entire licence estate usually exceeds the cost of any automation. Only businesses that once put portal quantities and billed quantities side by side know that number - a comparison that is always worth doing as a first step, even without a new system.

How you notice it has become too much

• The billing depends on one person, and it slips when they are on holiday
• There is a spreadsheet nobody but its author understands and everybody needs
• Customers regularly query individual lines
• You cannot say offhand how many licences of a certain type are running in total
• A cancellation triggers a discussion instead of a posting
• You check the figures once a year and find something every time

What an automation has to do

An export button is not an automation. For billing to genuinely leave your to-do list, a system has to do more than copy numbers - it has to cope with the untidiness of reality.

• Quantities come from the source, not from a maintained copy - and the key is precise enough: customer, specific product variant, term and billing cycle. One field fewer and two different products become one.
• Additions are charged pro rata, cancellations run cleanly out to zero instead of quietly billing on.
• Lines changed manually are reported, not overwritten. Otherwise the nightly run undoes what somebody decided deliberately.
• If a source does not answer, the reconciliation pauses instead of calculating with the last known state. Better an invoice late than an invoice too low.
• Every source runs onto one contract and one invoice. The customer does not care which distributor you buy from.
• Every run leaves a log: what was reconciled, what was skipped, what stood out.

How to get there - in three steps

The move rarely fails on technology but on being started too big. The practical order is: clean up, automate one source, then roll out.

• Reconcile the estate: portal quantities against billed quantities, customer by customer. The result is uncomfortable and at the same time the best justification for everything that follows.
• Automate one source - the one with the most lines. Run it in parallel for a month and look at the differences instead of switching immediately.
• Bring the remaining sources across and abolish the spreadsheet. As long as it exists, it will be maintained.