-
Regional Sales Director, Catalis PaymentsView all postsFrank has decades of expertise in government payments, specializing in secure, modernized payment ecosystems that streamline operations for state, county, and local agencies.
Of all the questions a Massachusetts collector fields about online payments, the one with the most legal weight is also the one most often misunderstood: who pays the convenience fee, and on which bills? It sounds like a customer-service detail. In Massachusetts it’s a compliance matter, and getting it wrong — in either direction — creates exposure the office would rather avoid. Before choosing or configuring any online payment platform, a collector needs to be clear on what the rules actually require.
What Municipalities Can and Cannot Absorb
The central rule is one many residents don’t expect: for real estate and personal property taxes, Massachusetts municipalities generally cannot absorb the credit and debit card convenience fees on online payments — the fee has to be passed through to the payer. That constraint is specific and consequential. A platform configured to quietly absorb those fees, or a well-meaning decision to “make it easier” by covering them, can put a community offside on its most important bill types. For other receivables, such as water and sewer or excise, communities have made different choices, and some do absorb fees — but the real estate and personal property rule is the one that leaves the least room for interpretation.
Practically, that means the payment platform itself has to handle the distinction. It needs to apply the right fee treatment to the right bill type automatically, rather than relying on staff to remember which category absorbs and which passes through. When the rule is enforced in software, compliance stops being a thing the office has to police transaction by transaction and becomes a property of the system.
Disclosure Before the Payment, Not After
The second requirement is about transparency. The convenience fee has to be calculated and shown to the payer before they commit to the transaction — a clear, separate figure presented on the payment screen, not a surprise that appears on a statement later. Massachusetts communities are consistent on this point: the fee is disclosed up front, identified as a charge from the service provider rather than the town, and the municipality receives only the bill amount itself. A compliant platform makes that disclosure unmissable and accurate, every time, across every channel.
The ACH Alternative Has to Be Real
There’s a fairness dimension built into how Massachusetts communities have approached this. Because card fees fall on the taxpayer for real estate and personal property, an accessible lower-cost option matters — and in practice that’s ACH, the electronic check. Most communities offer e-check payment for free or for a small flat fee well below the percentage-based card charge. A platform that buries the ACH option, or makes it harder to use than paying by card, undercuts the whole point: residents should be able to pay online without a percentage-based fee if they choose. When you evaluate a platform, the ACH path should be as visible and as smooth as the card path.
MLC and Other Fees Have Rules Too
Convenience-fee compliance doesn’t stop at tax bills. Municipal lien certificate fees, set under the authority of Chapter 40, Section 22F and capped accordingly, flow through the same online channel and need the same clean separation between the statutory fee, the service-provider charge, and what the municipality actually receives. The same is true for the various municipal charges a city or town collector handles under its expanded authority. A platform that treats fee handling as a per-bill-type rule, rather than a single global setting, is the one that keeps all of these straight without staff intervention.
Why This Is a Platform Decision, Not a Policy Memo
It’s tempting to treat convenience-fee compliance as something a written policy can solve. But a policy only describes what should happen; the platform determines what does happen on every transaction, including the ones processed at 11 p.m. by a resident the office never speaks to. The right question for a vendor isn’t “Can your system charge a convenience fee?” — every system can. It’s whether the system applies Massachusetts fee rules by bill type, discloses the fee before payment, surfaces a genuine ACH alternative, and reports it all cleanly enough to reconcile. Those are configuration realities, and they should be demonstrated, not promised.
Compliance That Reconciles Itself
The final piece ties back to the collector’s core duty. When fees are handled correctly at the point of payment, the downstream record is clean: the municipality’s books show the bill amount it’s entitled to, the service-provider fee is clearly separated, and the weekly turnover and monthly reconciliation reflect exactly what the office collected. Fee compliance and reconciliation accuracy turn out to be the same problem viewed from two angles — and a platform built around Massachusetts rules solves both at once, which is precisely what an audit-conscious collector’s office should expect.
None of this is exotic; it’s the daily reality of accepting payments in a Massachusetts municipality. But it is specific, and it is the kind of specificity a general-purpose national payment vendor tends to flatten into a single fee setting. The collectors who avoid trouble are the ones who treat convenience-fee handling as a Massachusetts compliance requirement from the start — and choose a platform that does the same.
A Quick Test for Any Vendor
You can turn all of this into a short, concrete vendor test. Ask a prospective platform to show, live, how it treats a real estate payment versus a water payment: does it apply the correct convenience-fee rule to each bill type automatically? Ask it to walk through the payer’s screen and confirm the fee is disclosed, separated, and identified as a service-provider charge before the payment is committed. Ask where the ACH option appears and how its cost compares to the card path. And ask for a sample report and confirm the municipality’s share and the service-provider fee are cleanly separated for reconciliation. A vendor built for Massachusetts answers each specifically; a general-purpose processor reaches for a single global fee setting.
It’s worth being precise about what “absorbing” means in practice, because the nuance trips up well-meaning offices. Communities have latitude on some receivables — water, sewer, and excise among them — and some do choose to cover the fee there as a service to residents. The real estate and personal property rule is the one with the least latitude. A platform that lets a community make different, compliant choices by bill type, rather than forcing one setting across everything, is the one that fits how Massachusetts actually works.
CTA → Download the Massachusetts Online Payment Vendor Evaluation Checklist — including the convenience-fee questions to ask.