MSP Billing: Automating Per-Seat IT Contracts With ACH and Card

On this page 7 sections

1. Why MSP Billing Is Hard to Automate
2. Syncing Seat Counts From Your PSA to Recurring Billing
3. Pass-Through Licenses: Card Fees on Low-Margin Resale
4. Requiring ACH Autopay in Your Master Services Agreement
5. Handling Failed Payments Without Cutting off Support
6. Comparing PSA-Native Payments to a Standalone Processor
7. Next Steps for Automating Your MSP Billing

Key takeaways

• Automated MSP billing works only when seat counts are reconciled against one source of truth before each invoice run.
• Card fees are charged on the full invoice, so thin-margin license resale is where ACH autopay protects you most.
• Your master services agreement should require autopay, authorize variable debits, and define what happens when a payment fails.
• PSA-native payments are convenient, but compare their pricing, ACH handling, and portability against a standalone processor.

MSP billing looks simple on paper: a monthly fee per user or device, plus a few extras. In practice, seat counts shift every month, license costs pass through at thin margins, and project work lands on top of the retainer. This guide explains why managed IT invoices resist automation and how to sync seat counts into recurring billing. It also covers several other steps:

• Steering clients to ACH autopay so card fees don't eat your license margin
• Handling failed payments without going dark on a client
• Comparing PSA-native payments to a standalone processor

Why MSP Billing Is Hard to Automate

Most recurring billing tools assume the same customer pays the same amount on the same day. A managed service provider rarely gets that luxury. A single client invoice might include:

• Per-user or per-device support fees that change as the client hires, lays off staff, or retires hardware.
• Pass-through software licenses such as Microsoft 365, backup, and security tools, often resold at a small markup.
• Project or time-and-materials work, like a server migration or office move, billed on top of the agreement.
• Hardware resale, which can be a large, one-off line item.
• Block-hour overages when a client burns through prepaid hours.

Each line has a different margin and a different cost to collect. Some lines also need a different approver on the client side. Many MSPs lose money or goodwill when they automate the whole invoice with one payment method and one rule set.

There is also a vocabulary problem. In payments, "MSP" usually means merchant service provider, the company that sets up your card and ACH processing. In IT, it means managed service provider. This article is written for managed service providers who are choosing a merchant service provider.

Syncing Seat Counts From Your PSA to Recurring Billing

Automation fails quietly when the seat count on the invoice doesn't match reality. Under-billing leaks revenue. Over-billing triggers disputes, and on card payments those disputes can become chargebacks.

Pick One Source of Truth for Per-User IT Support Billing

Your seat count can come from several places:

• Agreement additions in your PSA
• Agent counts in your RMM
• User counts in license portals
• The client's own HR list

These rarely agree on any given day. Decide which system is authoritative for each billable unit:

• Users: often the license portal or directory count, minus shared and service accounts.
• Devices: often the RMM's count of active, managed endpoints.
• Licenses: the vendor portal, since that's what you're billed for.

Set a Count Date and a Proration Rule

Pick a fixed "snapshot" day each month, a few days before your invoice run, and write it into your agreement. Then decide:

1. Do you bill seats in advance, in arrears, or a mix (support in advance, overages in arrears)?
2. Are mid-month adds prorated, rounded to a full month, or billed starting next cycle?
3. Are removals effective immediately or at the next count date?
4. Is there a contract minimum seat count?

Add a Review Step Before the Charge Runs

Automation shouldn't mean nobody looks at the invoice. A simple rule works well: if a client's invoice changes more than a set threshold from last month, flag it for review before the autopay pulls.

Illustrative example: A client goes from 38 to 45 users between snapshots. The flag prompts a quick check, which shows three of the new accounts are shared mailboxes that your contract excludes. You bill 42 users instead of 45 and avoid a dispute.

Good managed service provider billing software should show the client which users or devices they're paying for. Line-level detail is your best defense if a charge is ever questioned.

Pass-Through Licenses: Card Fees on Low-Margin Resale

Card acceptance often costs MSPs the most on this part of the invoice. Processing fees are charged on the full transaction amount, not on your margin. On a support fee, a card fee is a manageable cost of doing business. On resold licenses with a thin markup, it can consume a large share, or all, of your profit on that line.

Illustrative example (numbers are hypothetical, not quoted rates): A client's monthly invoice includes $4,000 in resold licenses that cost you $3,600, for a $400 gross margin. The client pays by card, and your blended processing cost works out to a few percent of the total. Card fees on the license line alone could eat a meaningful slice of that $400. Run the math with your actual statement and your actual license margins.

Commercial and corporate cards can cost more to accept than consumer cards. Card-not-present invoice payments also generally cost more than in-person ones. These guides explain the mechanics:

• Why online and keyed transactions cost more to process
• How interchange fees are set

Ways to Protect License Margin

• Make ACH the default. ACH costs are typically far lower than card costs and often don't scale the same way with invoice size. Confirm your processor's ACH pricing structure.
• Set payment method rules by line. Some MSPs accept cards for support and project fees but require ACH for licensing and hardware.
• Price card acceptance in. Where permitted by state law and card network rules, surcharging programs for card payments let you pass some processing cost to clients who choose cards. Rules govern disclosure, card types, and limits, so confirm current requirements before turning it on.
• Look at fee-offset programs. Zero cost processing and similar compliant programs can help eligible merchants offset most or all card fees. Ask which structure fits invoice-based billing rather than counter sales.
• Pass enhanced data on commercial cards. Some business-card transactions may qualify for lower interchange when you send additional invoice data. Ask whether your gateway and processor support it.
• Know your pricing model. Our comparison of interchange-plus vs. flat-rate pricing explains the trade-offs. A transparent model makes it far easier to see what large B2B card payments really cost you.

Requiring ACH Autopay in Your Master Services Agreement

MSP autopay via ACH works best when it's a contract term rather than a favor you request after onboarding. Build it into your master services agreement (MSA) and onboarding packet so every new client starts on autopay.

Clauses to Discuss With Your Attorney

• Required payment method. Make ACH autopay the standard. You can still permit cards, with any lawful card fee or alternative pricing disclosed.
• Authorization for variable amounts. Because seat counts change, the authorization should cover recurring debits of varying amounts. It should also require delivery of the invoice a set number of days before each debit.
• Debit timing. The day of the month the debit runs and what happens when it falls on a weekend or holiday.
• Dispute window. How a client questions an invoice before the debit, so issues come to you instead of going to their bank.
• Failed payment terms. Retry attempts, late fees where lawful, and the steps you'll take before suspending services.
• Bank changes. The client's duty to give you updated account details and a signed new authorization.
• Renewal and termination. Notice periods and final billing for licenses with vendor term commitments you can't cancel mid-term.

ACH debits require proper customer authorization under network rules, so keep signed authorizations on file and retrievable.

Automatic renewal laws mostly target consumer subscriptions. If you serve home users or very small offices, review automatic renewal laws by state with counsel. This is general information, not legal advice; have a qualified attorney review your MSA.

Handling Failed Payments Without Cutting off Support

Treat a failed payment as a billing problem. It is not a reason to leave a client's network unmonitored. Shutting off security tools can create liability and damage the relationship faster than the unpaid invoice ever would.

Know How ACH and Card Failures Differ

• Cards usually decline at the moment of the charge, so you know right away.
• ACH debits can be returned days after you thought the payment succeeded, for reasons like insufficient funds or a closed account. Your books and dunning rules should account for that lag.

Use a Staged Response

Keep monitoring, backups, and security services running as long as your contract and risk tolerance allow. Pause discretionary work first, and document every contact.

If a client disputes a card payment, your signed MSA and invoice detail become your evidence. Our guide on how chargebacks work from start to finish shows the timeline.

Comparing PSA-Native Payments to a Standalone Processor

Many PSA and billing platforms offer built-in payment options. If you run ConnectWise, payments may be available inside or alongside the PSA, and other platforms offer similar features. The convenience is real: invoices, payments, and agreement records stay in one place. Still, the payment terms behind the button deserve the same scrutiny as any merchant account.

Capabilities change, so confirm current features and pricing directly with your PSA vendor.

Questions to Ask Either Option

1. What do ACH and card each cost, including per-transaction, monthly, and return fees?
2. Can it debit variable amounts from one standing authorization?
3. Does it support surcharging or fee-offset programs where permitted?
4. Does it pass enhanced data for commercial cards?
5. How quickly do funds settle, and how are returns reported?
6. Does it sync with your accounting system, such as QuickBooks payment integration?

Many billing tools connect to payment gateways like Authorize.net or NMI. Check whether yours does before assuming you're locked into the native option. Our checklist on how to choose a merchant service provider covers broader questions to ask.

Next Steps for Automating Your MSP Billing

Start with your own statements. Pull the last few months of invoices and processing fees. Then separate support, project, license, and hardware revenue. That shows where card fees hurt and which clients to move to ACH first.

Then tighten the process:

• Use one source of truth for seats.
• Set a fixed snapshot date.
• Require ACH autopay in your MSA.
• Follow a staged response to failed payments that never leaves a client unprotected.

MannyPay works with professional services businesses on online payment acceptance, virtual terminals for keyed invoice payments, and compliant cost programs. To have your current setup reviewed, request a free quote; a MannyPay specialist responds within one business day.

ME

About the author

MannyPay Editorial Team

Beyond the Swipe's editorial desk researches the publication's guides and news and cites its sources in every article. Articles reviewed by a named MannyPay editor carry that editor's byline.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.