MSP payment terms: the MSA clauses and late-fee rules that get you paid

Most MSPs invoice on net 30. The MSPs that get paid on time bill recurring services in advance, due on receipt with autopay, keep net 15 to 30 for projects and hardware, and enforce a late fee clause from the first overdue day. This guide gives you the exact terms by revenue type, the clause wording to put in your MSA, and the statutory interest rules by country that most US-centric advice never mentions.

Key takeaways

• Net 30 is the most common MSP payment term, and it is also why so many MSPs wait 50 days for money. Common is not the same as good.
• Bill recurring services in advance, due on receipt, collected by autopay. Keep traditional terms for projects and hardware, with deposits.
• Put a late fee clause in the MSA and apply it every time. In the UK, statutory interest of 8% plus the Bank of England base rate applies even without a clause. In Australia and New Zealand, no clause means no late fees at all.
• Enforcement only works if it is automatic. A clause nobody applies trains clients to ignore your due date.

The terms MSPs actually use

Net 30 in arrears is the industry default: deliver the month's service, invoice at month end, wait 30 days. It is the first term every template MSA reaches for, and nobody ever got questioned for choosing it.

The problem is what net 30 turns into. Atradius' payment practices research puts roughly half of all B2B invoices overdue in the US, with the average overdue invoice paid 20 days past due. Apply that to net 30 arrears billing and the realistic cycle for a March service month is: work delivered through March, invoiced 31 March, due 30 April, actually paid around 20 May. You financed seven weeks of someone else's IT operation.

So treat net 30 as the ceiling you negotiate away from, not the standard you adopt by default. The rest of this guide is the away-from.

Bill recurring services in advance

Managed services should be billed in advance: the invoice for March goes out in the last week of February and is due on 1 March, before the work is delivered. Your agreement is a subscription; bill it like one. Nobody expects Microsoft to collect for M365 a month after use, and your seat-based agreement is no different.

Mechanically this means invoicing on a fixed calendar date (the 25th for the following month works well), prorating mid-month starts to the next full cycle, and moving existing clients across at renewal with a plain one-line explanation: "From July, invoices cover the month ahead, like every other subscription you run." I have yet to hear of a client worth keeping who left over it.

Terms by revenue type

One set of terms for everything is how MSPs end up financing hardware. Different revenue carries different risk, so the terms should differ too.

Late fee clauses that hold up

A late fee exists to make the due date real. For it to work it has to be written into the agreement, quoted on the invoice, and applied without ceremony the day the invoice goes overdue. The legal footing is different in each of the markets MSPs sell into, and this is the part almost every US-written guide skips.

The UK figures and the £40 to £100 compensation tiers are set by the Late Payment of Commercial Debts (Interest) Act. To make them concrete: on a £10,000 invoice paid 60 days late, statutory interest at July 2026 rates comes to roughly £193, plus £100 fixed compensation, about £293 you are legally owed for that one invoice. Paidnice tracks the Bank of England base rate automatically, so UK late fees stay compliant without anyone re-reading the legislation. That auto-indexing does not exist in any PSA or payment portal we know of.

Clause wording to adapt with your lawyer:

Invoices unpaid after the due date accrue a late payment charge of 1.5% per month (18% per annum), or the maximum permitted by law if lower, calculated daily from the due date until payment. [Provider] may suspend performance under clause [X] while any invoice remains overdue.

[Provider] will exercise its statutory right to interest and compensation under the Late Payment of Commercial Debts (Interest) Act 1998 on any invoice unpaid after the due date, at 8% per annum above the Bank of England base rate, together with the fixed sum applicable to the debt.

Autopay as a condition of service

New managed services clients sign an ACH or direct debit authority with the MSA. Card autopay with a surcharge where your region allows it is the fallback, and paying invoices manually is the exception, not a preference you cater to. That single onboarding decision removes the collection problem for every client who signs it, which is why it belongs in the contract rather than in a polite email two years later.

For existing clients, use a three-strikes conversion: the third late payment in six months triggers a written requirement to move to autopay for continued service. It is a fair rule, it is easy to communicate, and it turns your worst payers into your best ones. The rails are commodity at this point: GoCardless or direct debit in the UK, ACH in the US, and Stripe or Pinch behind your Paidnice payment portal all do the job.

Deposits, prepayment and credit checks

Any client whose monthly agreement would hurt if it went unpaid for 90 days deserves five minutes of credit checking before you offer terms. For project work, 30 to 50% up front is standard and uncontroversial: a client who resists a deposit is telling you something about how they intend to treat the final invoice. Annual prepay in exchange for a modest discount can work for stable clients, though plenty of MSPs skip discounts entirely and simply hold the line on advance billing. Both positions are defensible; undiscounted arrears billing is not.

The suspension clause you hope to never use

Suspension is the consequence that makes everything else credible, so the clause has to be precise. Four elements: a trigger (any invoice more than a stated number of days past due), written notice with a cure period (five business days is common), carve-outs (security monitoring, backups and licence continuity stay on, so a payment dispute never becomes a data-loss incident), and a reinstatement condition (account brought current, and for repeat cases, autopay).

If any invoice remains unpaid [30] days after its due date, [Provider] may, on [5] business days' written notice, suspend the Services other than [security monitoring, managed backup and third-party licence continuity] until all overdue amounts are paid. Suspension does not relieve the Client of its payment obligations, and time under suspension counts as service delivered for billing purposes.

The process that should happen long before this clause fires, including the credit-hold step that pauses projects while support carries on, is mapped day by day in the MSP collections process.

Put the terms to work automatically

Terms only change behaviour if they are enforced on every invoice, and no owner has the appetite to hand-apply a late fee to a client they had a beer with last month. That is the actual job Paidnice does: it reads every invoice in Xero or QuickBooks Online, checks it against your rules, and runs the consequences, late fees and interest, reminders from your own domain, statements and escalations, without anyone having to be firm in person. Customers cut their average wait for payment in half within 30 days of turning that on. The policy is the bad guy, which is precisely the point.

Common questions

What payment terms do MSPs use?

Net 30 billed in arrears is the most common arrangement, but the trend among well-run MSPs is advance billing for recurring services, due on receipt with mandatory autopay, with net 15 to 30 reserved for project milestones and prepayment for hardware and licences.

Can an MSP charge late fees?

Yes, with regional differences. In the UK, statutory interest of 8% plus the Bank of England base rate applies to B2B debts automatically. In the US it is contractual, typically 1 to 2% per month, with some state caps. In Australia and New Zealand a late fee is only enforceable if it is in your signed terms before supply.

Should MSPs require autopay?

For recurring agreements, yes. Make ACH or direct debit authority part of onboarding for every new client, and convert existing clients after repeated late payment. MSPs that mandate autopay for new business stop having a collections problem on the recurring side of the book almost immediately.

Can an MSP legally suspend service for non-payment?

Yes, if the MSA says so. The clause needs a clear trigger, written notice with a cure period, and carve-outs for security and backups so suspension never creates disproportionate harm. Suspend without the contractual right and you trade a payment dispute for a liability one.

See how enforcement runs hands-off: Paidnice pricing starts at US$69 a month flat, with local pricing in seven currencies, and most MSPs are live in about 15 minutes.

More on getting MSPs paid

This guide is part of a set on MSP credit control. Each piece stands alone; together they cover the whole system.

• MSP credit control: the complete guide: the five levers, the benchmarks and the one-week fix.
• The MSP collections process: the day-by-day ladder with nine copy-paste templates.
• MSP billing: models compared and the accuracy failures that cause disputes.
• MSP billing and AR software: the three-layer stack and an honest buyer's guide.