If your company provides payroll services, you may think you are in the business of HR software, payroll administration, employer services, or back-office support.
That may be true.
But if your company receives employer funds, holds those funds, and then disburses them to employees, tax authorities, benefit providers, garnishment recipients, or other third parties, a regulator may see something else as well:
Money transmission.
That is exactly the issue raised in a recent Texas Department of Banking consent order involving Paycor, Inc. The order is not just another regulatory document. It is a useful warning for payroll processors, HR platforms, employer-of-record companies, professional employer organizations, staffing platforms, earned wage access providers, embedded payroll products, and fintechs that move payroll-related funds.
The message is simple:
If you touch client funds and move them for someone else, you need to know whether you are licensed, exempt, or properly covered under someone else’s license.
Assuming that “we are just a payroll company” is not enough.
What Happened?
The Texas Department of Banking issued Consent Order No. 2026-020 against Paycor, Inc., a Delaware corporation headquartered in Rochester, New York.
According to the order, Paycor provides payroll processing services to employers, including small and medium-sized businesses. The Department stated that those services included:
collecting funds from clients through the automated clearinghouse system;
receiving and holding those funds;
disbursing funds to employees;
making payments to tax authorities;
making payments to garnishing entities; and
making payments to employee benefit providers.
Texas concluded that this activity constituted money transmission under both the prior Texas money transmission statute and the current Texas Finance Code Chapter 152.
The result: Paycor agreed to pay a US$275,000 administrative penalty.
Paycor did not admit or deny the factual findings or legal violations. That is normal in many consent orders. But from a compliance and licensing perspective, the practical lesson remains very clear.
Texas treated payroll processing involving the receipt, holding, and disbursement of funds as licensable money transmission activity.
Why Payroll Processing Can Become Money Transmission
The mistake many companies make is assuming that payroll is automatically outside money transmission regulation because it is not a consumer remittance product.
That assumption can be dangerous.
Money transmission laws are not limited to traditional remittance companies, money transfer stores, consumer wallet apps, or cross-border payment platforms. In many states, money transmission can include receiving money from one party and making it available to another party at a later time or different location.
In payroll, that can look like this:
An employer sends funds to the payroll provider.
The payroll provider receives or controls the funds.
The payroll provider holds the funds temporarily.
The payroll provider sends funds to employees, tax authorities, benefits providers, garnishment recipients, or other third parties.
That is a flow of funds.
And once a company is in the flow of funds, the question becomes: under what legal authority is it moving the money?
Is it licensed?
Is it exempt?
Is it acting as an authorized delegate of a licensed money transmitter?
Is a bank or licensed partner actually receiving and transmitting the funds?
Or is the company simply operating on the assumption that payroll is not money transmission?
That last position is where the danger sits.
What Texas Said in the Paycor Order
The Texas order is particularly important because Chapter 152 of the Texas Finance Code expressly includes payroll processing services within the definition of money transmission.
The order explains that “payroll processing services” can include receiving money under a contract to:
deliver wages or salaries;
make payroll tax payments to state and federal agencies;
make payments related to employee benefit plans; or
make distributions of other authorized deductions from wages or salaries.
In other words, the activity does not have to look like a classic remittance transaction.
It can be ordinary payroll processing.
If the provider receives money and moves it to employees or other payroll-related recipients, Texas may view that as money transmission.
The Timeline Matters
According to the order, Texas determined that Paycor had provided payroll processing services in Texas since 2014.
Paycor initially applied for a Texas money transmission license on March 15, 2024. That application was returned because of omissions. Paycor then submitted a new application on July 2, 2024, which was accepted for processing.
During the review, the Department determined that Paycor’s prior Texas payroll activity constituted licensable money transmission.
Then, on April 14, 2025, Paycor was acquired by Paychex Holdings, LLC. Paychex was already licensed to engage in money transmission in Texas. Paychex appointed Paycor as an authorized delegate, and Paycor withdrew its pending application effective June 17, 2026.
This is an important point.
The order did not permanently block Paycor from operating. It recognized that Paycor later came under the umbrella of a licensed money transmitter as an authorized delegate.
That is one of the major commercial lessons here:
If you are not licensed yourself, you may still be able to operate under a properly structured authorized-delegate or sponsorship model, depending on the state, the activity, and the licensed partner.
But you cannot simply assume coverage. It must be structured, documented, and compliant.
Who Should Pay Attention?
This order should not be read as a payroll-only issue. It should be read as a funds-flow issue.
Companies that should pay attention include:
payroll processors;
HR software platforms with embedded payments;
employer-of-record companies;
professional employer organizations;
staffing and contractor payment platforms;
earned wage access providers;
gig economy payout platforms;
benefits administration platforms;
expense reimbursement platforms;
contractor payroll companies;
marketplace payout providers;
fintechs offering payroll APIs;
SaaS platforms that collect and disburse client funds; and
companies using pooled accounts, FBO accounts, custodial accounts, or third-party payment flows.
The key question is not what you call the product.
The key question is what happens to the money.
The Real Test: Do You Touch the Funds?
A payroll software company that only calculates payroll, produces reports, and sends instructions to a bank may have a very different regulatory profile from a company that receives employer funds into its own account and then disburses payroll.
The risk increases when the company:
receives money from clients;
holds money, even briefly;
pools funds from multiple clients;
controls the timing of disbursements;
sends money to employees or third parties;
deducts fees from funds in transit;
operates across multiple states;
uses accounts in its own name;
uses FBO or custodial structures without clear legal coverage;
relies on a processor without understanding who is the licensed party; or
markets itself as handling payroll payments end to end.
If your company is in the middle of the money flow, you need a legal basis for that activity.
“But We Use ACH” Is Not a Complete Answer
Many companies assume that because payroll moves through ACH, the licensing question is solved.
It is not.
ACH is a payment rail. It is not a money transmission license.
Using ACH does not automatically exempt a company from state money transmission laws. The regulatory question is not only how the money moves. The regulatory question is also who receives it, who controls it, who is obligated to transmit it, who owns the customer relationship, and who is legally responsible for the movement of funds.
You can use ACH and still have a money transmission issue.
You can use a bank and still have a licensing issue if the structure does not actually place the regulated funds activity with the bank or licensed entity.
You can use a processor and still have exposure if the processor is not covering your specific activity, in the specific state, under the specific legal structure required.
This is why the flow of funds matters.
The Difference Between Software and Funds Movement
There is a major difference between being a software provider and being a funds movement provider.
Software-only payroll support may include:
calculating gross and net wages;
generating payroll reports;
managing employee data;
producing tax forms;
integrating with accounting systems;
preparing payment files; or
sending instructions to the employer’s bank.
Funds movement activity may include:
receiving employer funds;
holding payroll funds;
debiting employer accounts and controlling disbursement;
transmitting wages to employees;
remitting payroll taxes;
paying benefit providers;
paying garnishment recipients; or
managing pooled payroll accounts.
The closer your company gets to the second list, the more seriously you need to review money transmission licensing.
Why the Penalty Matters
The US$275,000 penalty matters because it shows that this is not theoretical.
For a growing payroll or HR-tech company, a consent order can create several problems at once:
a financial penalty;
reputational damage;
investor concern;
banking partner concern;
licensing delays;
enhanced regulatory scrutiny;
contractual problems with clients;
acquisition due diligence issues; and
difficulty expanding into other states.
The penalty itself may be manageable for a larger company. But the regulatory history can become a much bigger issue.
If you are trying to raise capital, sell the company, acquire another company, become a licensed money transmitter, or partner with banks, a prior consent order can become a serious diligence item.
The Authorized Delegate Lesson
One of the most important parts of the order is that Paycor eventually became an authorized delegate of Paychex, which already held a Texas money transmission license.
This highlights a practical path for companies that do not want to obtain their own license immediately.
In many cases, a company may consider:
becoming an authorized delegate of a licensed money transmitter;
operating under a licensed sponsor;
restructuring funds flow so the licensed party receives and transmits funds;
using a bank-led structure where the bank is genuinely performing the regulated activity;
obtaining its own money transmission license in key states; or
using a staged approach, starting with coverage and moving toward direct licensing later.
The right answer depends on the business model, states, transaction types, ownership of funds, account structure, customer relationship, and regulatory obligations.
There is no universal shortcut.
But there are structured ways to solve the problem.
What Payroll and HR-Tech Companies Should Do Now
If you operate a payroll, HR, EOR, staffing, contractor payout, or embedded payroll product, you should not wait for a regulator to ask questions.
Start with a basic internal review.
Ask these questions:
Do we receive client funds?
Do we hold funds before disbursement?
Do we disburse wages, taxes, benefits, garnishments, or deductions?
Do we operate in Texas or other states with money transmission laws?
Are we licensed in those states?
If not licensed, what exemption are we relying on?
If we rely on a partner, is that partner licensed in the relevant states?
Are we formally appointed as an authorized delegate where required?
Does the partner agreement clearly cover our exact activity?
Does the flow of funds match the legal structure on paper?
Are customer funds ever received into our own corporate operating account?
Are funds pooled, segregated, or held in FBO/custodial accounts?
Who is liable if a payment fails?
Who handles complaints, refunds, errors, and regulatory reporting?
Would our structure survive bank, investor, regulator, or buyer due diligence?
If the answers are unclear, that is the warning sign.
Do Not Wait Until You Are Already in Trouble
Many companies wait too long.
They build the product. They onboard clients. They process volume. They expand across states. They add new payment flows. Then, later, a bank, investor, buyer, regulator, or partner asks a simple question:
What license or exemption allows you to move these funds?
At that point, the company may discover that the commercial product has moved faster than the regulatory structure.
That is expensive to fix.
It is far better to review the structure early and decide whether the company needs:
direct money transmission licensing;
authorized-delegate coverage;
a licensed sponsor;
a banking partner structure;
state-by-state analysis;
revised flow of funds;
revised customer agreements;
custodial or FBO account restructuring; or
a phased licensing roadmap.
The Main Takeaway
The Paycor consent order should be taken seriously by any company that touches payroll funds.
Not every payroll software company is automatically a money transmitter.
But if your company receives, holds, controls, or disburses payroll funds, you need to understand your money transmission exposure.
The label on the product does not control the regulatory answer.
The flow of funds does.
Need Help Reviewing Your Payroll or Funds Flow?
If your company provides payroll processing, HR-tech, employer-of-record, staffing, contractor payout, earned wage access, or embedded payment services, now is the time to review your structure.
We can help you assess whether your activity may require:
money transmission licensing;
authorized-delegate coverage;
a licensed sponsor;
banking or FBO account restructuring;
state-by-state regulatory review;
a Texas-specific licensing review;
a payroll funds-flow analysis; or
a practical path to become compliant before the issue becomes urgent.
If you are already moving funds, do not wait until a bank, investor, buyer, or regulator asks the question first.
Start with the flow of funds.
Then determine whether you are licensed, exempt, or properly covered.
That is how you avoid building a payroll business on a regulatory assumption that may not hold.
Source
Texas Department of Banking, Consent Order No. 2026-020, In the Matter of Paycor, Inc., signed October 6, 2026: https://www.dob.texas.gov/sites/default/files/files/Laws-Regulations/orders/2026-020.pdf
