Modern Payroll Infrastructure: From Batch ACH to Real-Time Earned Wage Access

Payroll is the largest recurring money movement in most economies, yet the infrastructure behind it has barely changed in decades. In the United States, 160 million workers receive wages through a system built on batch file processing, ACH settlement cycles, and software stacks designed in the 1990s. The global payroll services market sits at roughly $28 billion in 2025, projected to reach $35 billion by 2030, according to Mordor Intelligence. Despite this scale, most workers still wait two weeks to access money they have already earned.

This article breaks down how payroll actually works: the processing stack, the batch model, earned wage access, global complexity, and the emerging role of stablecoin payment rails in reshaping how workers get paid.

How the Payroll Processing Stack Works

Modern payroll is not a single system. It is a pipeline of four interconnected layers, each handling a distinct responsibility. Data flows from human resources systems through tax calculations and into payment rails that move funds to employee bank accounts.

Layer 1: HRIS (Human Resource Information System)

The HRIS stores employee demographics, contracts, tax codes, leave balances, and benefits elections. It is the system of record for who gets paid, how much, and under what tax jurisdiction. Major platforms include Workday, BambooHR, and Rippling. For payroll to run correctly, every change in employment status, address, or withholding preference must propagate from the HRIS to downstream systems before the pay cycle closes.

Layer 2: Time and Attendance

Time and attendance systems push hours worked, overtime, shift differentials, commissions, and bonuses into the payroll engine. For hourly workers, this layer determines gross pay. For salaried employees, it tracks PTO usage and leave adjustments. Integration quality between timekeeping and payroll is the most common source of payroll errors: disconnected systems lead to manual data entry, which introduces mistakes that compound across pay periods.

Layer 3: Tax Engine and Deductions

The tax engine calculates federal, state, and local withholdings, plus Social Security, Medicare, 401(k) contributions, health insurance premiums, HSA/FSA deductions, garnishments, and union dues. In the United States alone, employers must track withholding rules across 50 states and thousands of local jurisdictions. Multi-state remote workers compound this exponentially: a single employee working from three states in one quarter triggers three sets of state tax obligations.

Layer 4: Payment Rails

Once net pay is calculated, the payment processor generates a batch file in NACHA format and submits it to an originating bank. The bank forwards the file to the ACH operator (either the Federal Reserve or the Electronic Payments Network), which sorts entries and routes them to receiving banks. Funds appear in employee accounts on payday, typically with a T+1 or T+2 settlement lag.

The major payroll processors (ADP at $20.6 billion in annual revenue, Paychex at roughly $5 billion after its $4.1 billion acquisition of Paycor in April 2025, and Paylocity at $1.6 billion) bundle all four layers into integrated platforms. Newer entrants like Gusto (400,000+ businesses) and Rippling ($570 million ARR as of early 2025) compete by offering tighter integrations and better developer APIs.

Why Payroll Still Runs in Batch

Biweekly pay is the most common frequency in the United States: roughly 43% of establishments and 56% of workers operate on a two-week cycle, according to Bureau of Labor Statistics data. The ACH Network processed 35.2 billion payments worth $93 trillion in 2025, averaging 141 million daily transactions. This infrastructure is reliable, well-understood, and deeply embedded in regulatory and accounting systems.

The question is why payroll remains batch when real-time payment rails now exist. The barriers are structural, not technological.

Tax Withholding Assumes Pay Periods

IRS Publication 15-T organizes withholding tables by pay period: weekly, biweekly, semimonthly, monthly. Shifting to continuous payroll would require real-time tax calculation for every micro-payment, across federal, state, and local jurisdictions. The withholding math itself depends on knowing the pay period length to calculate annualized income and apply the correct marginal rates.

Benefits and Deductions Are Periodic

Health insurance premiums, retirement contributions, HSA deductions, garnishments, and union dues are all structured around periodic pay cycles. Restructuring these for continuous settlement would require coordination with insurers, plan administrators, and courts that issue garnishment orders assuming specific pay frequencies.

Overtime Requires a Complete Workweek

The Fair Labor Standards Act requires overtime calculation based on a seven-day workweek (40+ hours). Biweekly schedules align cleanly with two full workweeks. Real-time pay would require speculative overtime calculations with potential clawbacks if hours shift late in the week.

Compliance Reporting Is Period-Based

Quarterly 941 filings, annual W-2 generation, state unemployment tax reports, and workers compensation audits all assume periodic pay cycles. The entire reconciliation and reporting apparatus would need restructuring to accommodate continuous flows.

The real blocker: Payroll is not just a payment problem. It is a compliance problem. Every dollar paid triggers tax obligations, benefits calculations, and reporting requirements that are designed around discrete pay periods. Real-time rails solve the money-movement piece, but the regulatory and accounting infrastructure assumes batch processing.

How Earned Wage Access Works

Earned wage access (EWA) is the industry's workaround for the batch problem. Rather than changing the payroll cycle itself, EWA providers advance money to workers against wages they have already earned but not yet been paid. The underlying payroll system remains untouched: EWA sits on top as a financing layer.

The EWA Mechanism

EWA providers integrate with employer HRIS and timekeeping systems (DailyPay integrates with 180+ payroll and workforce management platforms). The provider tracks hours worked in near-real-time and calculates accrued but unpaid wages. When an employee requests an advance, the EWA provider funds the transfer from its own balance sheet or a credit facility. The advance is recouped from the employee's next paycheck via payroll deduction.

This is not real-time payroll. It is a disbursement funded by a third party that gets repaid on the next pay cycle. The employer's payroll run does not change.

Fee Models

EWA providers use two primary models. In the employer-funded model, the company pays a per-employee-per-month fee and workers access earned wages at no cost. In the employee-funded model, workers pay per transaction: DailyPay charges $2.99 for instant transfers (next-business-day transfers are free), while Payactiv charges $1.99 to $2.99 per transaction. Some providers offer free transfers to proprietary debit cards to drive card adoption and earn interchange revenue.

Regulatory Status

In December 2025, the CFPB issued an advisory opinion clarifying that covered EWA products are not credit under Regulation Z, provided they meet four criteria: they must be based on accrued wages using actual payroll data, use payroll-process deductions for repayment, include no recourse against the worker if deductions fall short, and involve no credit-risk assessment of individual workers. Roughly a dozen states now require EWA providers to obtain specific licenses or registrations.

EWA is not streaming pay: Earned wage access is a financing product that bridges the gap between work and payment. The worker still gets paid on a biweekly schedule; EWA just provides an advance against future earnings. The payroll batch model, tax engine, and compliance reporting remain unchanged underneath.

The global EWA market was valued at approximately $7.1 billion in 2025, with North America accounting for 42% of that figure, according to Fortune Business Insights.

Global Payroll: Multi-Currency, Multi-Jurisdiction Complexity

Paying a domestic workforce through ACH is relatively straightforward. Paying an international workforce is an order of magnitude harder. Every country has its own tax withholding rules, statutory benefits requirements, labor laws, and preferred payment rails. A company employing workers in 20 countries faces 20 different compliance regimes, often with penalties for errors.

The Employer of Record Model

The dominant solution is the Employer of Record (EOR). The EOR establishes legal entities in target countries and becomes the formal employer of the worker. The client company retains day-to-day control over work, but the EOR handles payroll tax, statutory benefits, employment law obligations, and local compliance. This eliminates the need for the client to register its own foreign entities, a process that can take months and cost tens of thousands of dollars per jurisdiction.

Deel dominates this space with $1.4 billion in annualized revenue as of early 2026, growing 63% year-over-year, and operating profitably since Q3 2023. Remote, Papaya Global, and Oyster compete but have seen the market consolidate significantly since the remote-work boom of 2021.

FX and Settlement Challenges

International payroll requires converting the employer's base currency to each employee's local currency. This introduces FX spread costs, timing risk (rates fluctuate between payroll calculation and settlement), and correspondent banking fees that can add 2-5% to the cost of each payment. For workers in emerging markets, these costs are even higher due to illiquid currency pairs and limited banking infrastructure.

For a deeper look at how cross-border payment infrastructure creates friction, see our research on B2B payment challenges.

Real-Time Payment Rails: Capability vs Adoption

The technology for real-time payroll exists. FedNow, launched in July 2023, now has 1,600 participating financial institutions and processed $853 billion in 2025 with 460% year-over-year volume growth. The RTP Network from The Clearing House processed over $1.3 trillion in 2025, averaging 1.36 million daily transactions in Q4.

But context matters. FedNow averages roughly 30,000 daily transactions compared to ACH's 141 million. Only about 40% of U.S. demand deposit accounts can currently receive FedNow payments. The infrastructure is growing rapidly but remains a fraction of legacy rail volume.

International Real-Time Rails

Other countries are far ahead. India's UPI processed 228.3 billion transactions in 2025 (up 33% year-over-year), handling roughly 698 million daily transactions. The IMF recognizes UPI as the world's largest retail fast-payment system, accounting for nearly 49% of global real-time payment volume. Brazil's PIX reaches 174 million individual consumers, roughly 82% of the population.

For a comprehensive comparison of these systems, see our global real-time payments analysis.

Why Real-Time Rails Alone Do Not Fix Payroll

Even where real-time rails have near-universal coverage, payroll remains largely periodic. Real-time rails solve the money-movement problem: funds arrive instantly instead of in one to two business days. But they do not solve the calculation problem. Gross-to-net computation, tax withholding, benefits deduction, overtime compliance, and regulatory reporting all still require a discrete pay cycle to execute correctly.

Same-Day ACH has seen strong adoption (1.4 billion payments worth $3.9 trillion in 2025, up 16.7% year-over-year), but primarily for direct debit and B2B use cases, not payroll frequency changes.

Crypto Payroll: Stablecoins Enter the Stack

A growing segment of the payroll market now uses fiat-backed stablecoins for wage payments. This is not about paying employees in volatile cryptocurrencies: it is about using dollar-denominated tokens on blockchain rails to move money faster and cheaper, especially across borders.

How Stablecoin Payroll Works Today

Bitwage, founded in 2014 and acquired by Paystand in November 2025, pioneered the model. It processed over $400 million in wages for 90,000 workers across 4,500 businesses before the acquisition. The mechanism is straightforward: Bitwage integrates with existing payroll systems and allows workers to allocate a percentage of wages to stablecoins (USDC, USDT) or cryptocurrency, supporting 80+ local fiat currencies across roughly 200 countries.

Deel has scaled this further. Eligible employees can allocate 10-25% of net salary (after taxes and deductions) to stablecoins. The conversion is handled by BVNK, Deel's payments partner: an API call converts fiat to the specified stablecoin and sends it to the worker's blockchain wallet. Settlement occurs in minutes. Deel processed $250 million in crypto payouts in 2025, with 225+ businesses integrating stablecoins for payroll or operational payments.

What Changes and What Does Not

Stablecoin payroll changes the last mile of payment delivery. It does not change the upstream calculation. Tax withholding, benefits deductions, and compliance reporting still happen through the traditional payroll engine. The stablecoin conversion occurs after gross-to-net calculation, replacing the ACH transfer with a blockchain transaction.

The advantages concentrate in cross-border payments: stablecoin transfers eliminate correspondent banking chains, reduce FX costs, and settle in minutes rather than days. For a contractor in Nigeria or the Philippines receiving payment from a U.S. company, the difference between a 3-5 day SWIFT transfer with 3-5% in fees and a 10-minute stablecoin transfer at near-zero cost is transformative.

From Batch to Streaming: What Would It Take?

The real question is not whether real-time payment rails can deliver funds instantly. They can. The question is whether the entire payroll stack (from tax calculation through compliance reporting) can be restructured for continuous operation. This requires solving three hard problems simultaneously.

Real-Time Tax Computation

Streaming payroll requires a tax engine that can calculate withholding on every micro-payment, adjust for cumulative year-to-date income, handle multi-state apportionment, and produce correct results across thousands of tax jurisdictions. The computational challenge is manageable. The regulatory challenge is harder: the IRS withholding tables assume pay periods, and state agencies expect quarterly filings based on periodic data.

Benefits Decoupling

Health insurance premiums, retirement contributions, and garnishments would need to shift from per-paycheck deductions to either continuous micro-deductions or separately scheduled periodic payments. This requires coordination with insurers, 401(k) administrators, and court systems that issue garnishment orders specifying per-pay-period amounts.

Programmable Payment Rails

The payment rail itself needs to support conditional logic: split a payment stream across multiple destinations (employee account, tax authority, benefits provider, garnishment recipient) with each receiving the correct fraction at the correct time. This is where stablecoin rails offer a structural advantage over traditional banking infrastructure. Programmable money on blockchain rails can encode splitting logic directly into the payment flow.

Stablecoin Payroll on Spark: Toward Continuous Salary

Spark, a Bitcoin Layer 2 built on statechains, enables instant transfers with near-zero fees and self-custodial ownership. USDB, a dollar-denominated stablecoin on Spark issued through Brale, provides the unit of account that makes payroll denominations practical.

The combination creates an infrastructure layer where payroll does not need to be a periodic event. Rather than accumulating wages over two weeks and releasing them in a single ACH batch, an employer could stream USDB payments continuously as work is performed. This is structurally different from both traditional payroll and earned wage access.

Streaming vs Advancing

EWA providers like DailyPay solve the timing problem by introducing a third-party lender. The worker borrows against future earnings, the lender funds the advance, and the next paycheck repays the loan. This adds a financial intermediary and a fee to what is fundamentally a delivery timing problem.

Streaming payroll eliminates the intermediary entirely. If wages flow continuously from employer to employee, there is no gap to bridge. The worker has access to earned income as it accrues, not because a lender advanced it, but because the payment rail delivers it in real time. No advance, no repayment, no per-transaction fee.

For a detailed analysis of how Bitcoin-native streaming payments work, see our research on Bitcoin payroll and streaming payments.

International Payroll via USDB

For global payroll, USDB on Spark eliminates the most expensive friction points. Correspondent banking chains that add days of delay and 2-5% in costs are replaced by direct stablecoin transfers that settle in seconds. There is no FX spread on the payment rail itself: the employer sends USDB, and the worker receives USDB. Local currency conversion, if needed, happens at the recipient's discretion through local off-ramps rather than being forced through the correspondent banking system at unfavorable rates.

This model is particularly powerful for the 73 million freelancers and contractors who work across borders. An EOR like Deel charges $300-700 per month per employee in part because of the compliance and banking infrastructure required to move money internationally. Stablecoin rails compress the cost of the money-movement layer toward zero, even as tax and compliance costs remain.

What Still Needs Solving

Streaming stablecoin payroll solves the payment delivery problem but does not automatically solve tax withholding, benefits administration, or regulatory reporting. These layers require purpose-built infrastructure that can operate continuously:

• Tax engines that compute withholding on micro-payments and produce correct quarterly/annual reporting
• Benefits platforms that deduct premiums from continuous flows rather than periodic lump sums
• KYC/AML compliance infrastructure for on-chain payroll at scale
• Money transmitter licensing for entities facilitating stablecoin wage payments

The payments layer is ready. The compliance layer is not, yet. But the direction is clear: payroll infrastructure is moving from periodic batch processing toward continuous, programmable flows.

Building on the Payroll Stack

For developers interested in building payroll or payment streaming applications, the Spark SDK provides the primitives for instant USDB transfers, including programmatic splitting and streaming capabilities. The SDK handles wallet creation, transfer execution, and balance management through a straightforward API. For an example of a Spark-powered wallet that supports USDB, General Bread demonstrates how stablecoin payments work in practice.

For more context on embedded finance and how banking-as-a-service platforms are integrating crypto rails, see our research on the convergence of traditional and blockchain-based financial infrastructure.

This article is for educational purposes only. It does not constitute financial or investment advice. Bitcoin and Layer 2 protocols involve technical and financial risk. Always do your own research and understand the tradeoffs before using any protocol.