Billing & Reconciliation
MSP billing reconciliation that ends with a verified fix.
Revtein lines up contracted, delivered and invoiced quantities for every client, service and period, and walks your team through each difference until the source shows it is fixed.
HaloPSAContracted34
NinjaOneDelivered37
XeroInvoiced34Example from a demo MSP
What Revtein catches
What goes wrong, and what Revtein shows you.
Devices, seats or backups in use that no invoice line covers.
Clients paying for retired devices or unused licences.
The invoice and the agreement disagree on how many.
An old rate still on the invoice after a price change.
A product or client matched to the wrong record.
Usage from one month billed in another.
How it works
From the first number to the proof.
Agreement, RMM and accounting compared per client, service and month.
Each difference shows the records, unit, price and when each was read.
Bill what is delivered, keep the contract with a reason, or review later. Apply it in your PSA or by hand.
A new read confirms the change before the case closes.
How a case works
See one case through.
The same four-step checklist every case in Revtein follows.
- Check the numbersNowHaloPSAAgreement34NinjaOneDelivered37XeroInvoiced34
Same client, service and period · read Nov 15, 9:20 · $55 per device
Numbers checked - Decide what to do
- Make the change
- Confirm and close the case
Step 1 of 4 · Check the numbers
- Check the numbersAgreement 34 · delivered 37 · invoiced 34
- Decide what to doNow
- Bill the delivered quantity37 devices from the next invoice
- Keep the contracted 34record the clause as an exception
- Wait and reviewchoose a follow-up date
- Make the change
- Confirm and close the case
Step 2 of 4 · Decide what to do
- Check the numbersAgreement 34 · delivered 37 · invoiced 34
- Decide what to doBill the delivered quantity · approved
- Make the changeNowHaloPSA recurring line
34 × $5537 × $55Let Revtein apply it in HaloPSA, or do it by hand with these values. Issued invoices are never edited.
Apply in HaloPSA - Confirm and close the case
Step 3 of 4 · Make the change
- Check the numbersAgreement 34 · delivered 37 · invoiced 34
- Decide what to doBill the delivered quantity · approved
- Make the changeHaloPSA line 34 → 37
- Confirm and close the caseNowNew read of HaloPSA37 devices
The source now shows the change, so the case can close with proof.
Close the case
Step 4 of 4 · Confirm and close the case
- Check the numbersAgreement 34 · delivered 37 · invoiced 34
- Decide what to doBill the delivered quantity · approved
- Make the changeHaloPSA line 34 → 37
- Confirm and close the caseVerified against HaloPSA
Done · the case is closed with proof and the result is kept
Example case from a demo MSP. Numbers are illustrative.
FAQ
Billing & Reconciliation questions
What is MSP billing reconciliation?
It is the process of checking that what a client's contract promises, what you deliver, what should be billed and what was actually invoiced all agree. Differences are revenue leakage or overbilling.
Does Revtein edit issued invoices?
No. An issued invoice is never edited silently. Revtein updates the recurring billing line where the connector supports it, or records the adjustment on the case.
Is a vendor cost the same as lost revenue?
No. A vendor cost is only treated as rebillable after checking that the contract allows it. Revtein does not count it as lost revenue by default.
Related
Keep exploring
Know what needs to change. See it through.
Reserve your spot for launch. Tell us who you are and what you would use Revtein for, and we will email you the day it opens, with a 7-day free trial of the full platform.