Invoice what was agreed, and get paid for it
Every won deal becomes planned billing with dates and owners. The people who look after each customer can see, raise and chase that customer’s invoices, and nobody else’s, while finance keeps the whole view. Chasing stops the moment an invoice is paid.
Joined to your pipeline, this is what larger firms call revenue operations (RevOps). Read the guide.
What Billing takes off your plate
Billing delegated by customer
The people who own a customer see, raise and chase that customer’s billing, within their permissions. Finance keeps the whole picture.
Nothing won goes unbilled
Every milestone has a date and an owner. A billable past its date, or with nobody against it, shows up first.
Chasing that never embarrasses you
Chasers check paid status before every send, never send the same chase twice, and stop when the invoice is paid.
Secured revenue you can forecast on
Planned billing on won work feeds the revenue forecast alongside the pipeline, with planned, invoiced and collected kept apart.
The deal is won. The money is already planned.
Billing starts when the work is agreed, not when someone remembers to raise an invoice.
- Deal won Billing planned
The deal’s value becomes milestones or recurring amounts, each with a date and an owner.
- All the time Gaps flagged
Health checks find the billable past its date with no invoice, or with nobody against it.
- Issue date Invoice raised
From the planned billable, in your accounting system. Automatic raising is off unless you switch it on for that customer and billable.
- Overdue Chased until paid
On the schedule you set, for the invoices you enrol, and never once the invoice is paid.
Hand billing to the people who own the customer
Ownership comes from Delivery: whoever owns a customer or a project can see, raise and chase the billing for it, and nothing else. It uses the same permissions hierarchy as the rest of OpsUPLOOP, so finance sees everything, managers see their teams’, and nobody needs a seat in the accounts package to do their part.
- Scoped by customer and project team, not all or nothing
- Raise and chase for your own accounts, with the same checks as finance
- The same access applies through Claude or ChatGPT over MCP
Other customers’ billing isn’t shown: not your accounts. Finance sees everything.
Billing sits with one person, and so does every question about it
Accounting software is built for the finance team. Letting an account manager see or raise invoices for just their own customers is either impossible or means handing over everything, and CRM add-ons that try it rarely have the right write controls. So raising and chasing stay centralised, the person who knows the customer can’t act, and a delivered milestone goes unbilled because everyone thought someone else had it.
Without Billing
- Only finance can see or raise an invoice, so every question queues for one person
- Milestones tracked in someone’s head or a spreadsheet
- Chasing centralised, by hand, when someone remembers
- The occasional chaser to a customer who has already paid
With OpsUPLOOP Billing
- Account owners act on their own customers’ billing, within their permissions
- Every milestone with a date and an owner, and gaps flagged
- Chasing owned by the person who knows the customer, on your schedule
- A paid-status check before every send
OpsUPLOOP Billing, part by part
Planned billing
What you have agreed to invoice, and when.
- Milestones and recurring amounts, each with a date and an owner
- Access by customer and project team: people see and act on the billing for work they are assigned to
- Health checks that flag a billable past its date, or with nobody against it
- Planned, invoiced and collected kept as three separate numbers
Invoicing
Raised from the plan, in your accounting system.
- Invoices raised from planned billables through Xero
- Recurring templates and customer statements
- Card payment links through Stripe, where that suits the customer
Credit control
Chasing that is polite, persistent and never wrong about who has paid.
- Chase schedules you configure
- A paid-status check before every send, and a guard against sending the same chase twice
- Only the invoices you enrol are chased, never your history
Pipeline to paid
The forecast and the money, side by side.
- Pipeline scenarios alongside the billing you have planned
- Dated snapshots, so you can see how the picture changed
- For firms that host for clients: a read-only AWS inventory, with costs allocated to the customers who pay for them
Waits for a person
- Automatic invoice raising is off unless you switch it on for a customer and a billable
- Billables created by an AI assistant can never raise an invoice on their own
- Only invoices you enrol are chased
Runs on its own, within your rules
- Chasers send on the schedule you set, and stop when an invoice is paid
- Health checks run continuously
What it needs
An accounting connection (Xero today) for invoices, and a CRM connection, or OpsUPLOOP holding deals, for the pipeline. Stripe if you want payment links.
Start with Billing. Add the rest when it helps.
OpsUPLOOP Billing works on its own, on your own instance. The other modules share its records, so each one you add builds on what is already there.
- A campaign agent that builds the target list
- Letters drafted, reviewed, then posted
- LinkedIn follow-up and outcomes
- Lead briefings and scores with reasons
- Call analysis that feeds the score
- Drafted follow-ups and a clear pipeline
- Planned billables with owners and health checks
- Invoices raised through your accounting system
- Chasing with paid-status checks
- Customer records, commitments and feedback
- Ownership map, objectives and 90-day plans
- Check-ins that show drift early
Start with any one module. The others use the same records when you add them.
Won deals arrive with their value, ready to plan. Larger firms call this join revenue operations.
Ownership comes from Delivery: whoever owns the customer owns their billing and chasing, within the same permissions hierarchy.
Ask Claude or ChatGPT what is overdue and why. It sees only the billing your role can see.
Billing as it comes, or extended to fit
Everything above is in the product today, and you’ll see it working in the demo. If your firm works differently, Billing can be configured to your rules, or extended by Scorchsoft with the steps, screens or connections it doesn’t have, on the same records and permissions as the rest of OpsUPLOOP.
- As it comes
The modules you need, on your own instance
- Connected and configured
Joined to your systems, set to your rules
- Made to measure
Extended for you, hosted by us or by you
Asked about OpsUPLOOP Billing
Is this a cash-flow forecast?
No. It shows planned billing, issued invoices and collected money. A full cash-flow forecast also needs costs, payroll, tax and payment timing, which OpsUPLOOP does not model.
Could it chase a customer who has already paid?
Chasers check paid status before every send and stop once an invoice is paid. They also guard against sending the same chase twice.
Which accounting systems does it work with?
Xero today. Each instance is connected to what that business uses, so tell us what you run and we’ll say plainly what that involves.
Do we need a RevOps team to use it?
No. It is built for firms where the founder or an operations lead does this work alongside everything else.
See last month’s billing, planned and chased
Tell us how billing is planned and chased today. We’ll show you how OpsUPLOOP Billing would plan, raise and chase the same work.
30 minutes, with the people who build it. No slides.