Clearly Payments Dark Logo
Payments Research

The Cost of Running Payments at Scale: Staffing, Operations & Transaction Costs

The cost of running payments at scale: staffing, reconciliation, exceptions, automation, fraud and transaction costs, with the original Clearly Payments logo.

Payment operations costs are the staffing, systems and administrative expenses required to run payments beyond interchange and processor fees. Reconciliation, exceptions, fraud reviews, disputes, refunds, reporting and processor management create a second cost layer that can reach millions of dollars at enterprise scale.

$225K

Typical annual payment-operations cost at 1 million transactions

$0.22

Typical operating cost per transaction

50%

Share of staff time spent on reconciliation and exceptions

$2.0M

Annual cost gap between manual and automated operations at 10 million transactions

Clearly Payments estimates that a business processing 1 million transactions a year typically spends about $225,000 annually on payment operations. A highly automated operation is closer to $100,000; a heavily manual one is about $425,000.

The key variable is not transaction volume alone. It is how much human work each transaction creates. This guide explains payment operations costs, staffing requirements, reconciliation workloads and automation savings, with worked examples for building a budget.

Scope and currency: All dollar figures are in US dollars (USD). Operations costs cover labor and operating systems/tools, separate from interchange, processor fees and transaction principal. The general per-transaction comparisons and volume-based budgets use separate scenarios; the methodology below explains how to apply them.

Payment operations costs by transaction volume

As volume grows, automation changes the cost curve. A highly automated team can absorb more transactions without adding staff at the same rate. A manual operation cannot.

Annual transactions

Highly automated

Typical

Highly manual

100,000

$25K

$45K

$75K

500,000

$65K

$125K

$225K

1 million

$100K

$225K

$425K

5 million

$325K

$750K

$1.5M

10 million

$650K

$1.3M

$2.6M

50 million

$1.8M

$4M

$8M

Clearly Payments estimates. Annual costs include labor plus operating systems and tools.

What does payment operations cost per transaction?

Cost per transaction is annual payment-operations expense divided by annual transaction count. The general comparison below uses about $0.22 for a typical operation, $0.08 for a highly automated operation and $0.43 for a heavily manual operation. These figures are a separate comparison from the volume-specific budgets above; they are not the unit costs implied by every row of that table.

$0.08

Highly automated

$0.22

Typical

$0.43

Highly manual

Applying the $0.08 and $0.43 comparison to 10 million transactions gives annual operating costs of $800,000 and $4.3 million, a $3.5 million difference. By contrast, the 10-million-transaction budget elsewhere in this article uses $650,000, $1.3 million and $2.6 million, which imply $0.065, $0.13 and $0.26 per transaction. Choose one scenario and keep its assumptions together.

Where payment operations teams spend their time

Half of payment-operations staff time is concentrated in two functions: reconciliation and exception research. Those are also the areas where automation usually creates the largest operating leverage.

Function

Share of staff time

Reconciliation

28%

Exceptions & payment research

22%

Disputes & chargebacks

18%

Fraud review

14%

Reporting

10%

Processor & bank administration

8%

Estimated share of staff time in a typical large merchant.

Payment reconciliation costs: where the workload comes from

Reconciliation sounds simple: match payments to deposits and make sure the numbers agree. At scale, a business may need to reconcile processor transaction files, bank deposits, refunds, disputes, fees, currencies, locations, legal entities, processors and ERP records.

Clearly Payments estimates reconciliation accounts for about 28% of payment-operations workload in a typical large organization. The cost rises quickly when files are downloaded manually, data formats differ or transactions have to be matched across several systems.

The real operating cost comes from transactions that do not match cleanly.

See how Clearly Payments supports back-office payments operations, including reconciliation reporting and transaction research.

A small number of exceptions create most of the work

Most payments require almost no human attention. An exception is different.

Type of work

Typical staff time

Normal automated payment

Under 10 seconds

Simple reconciliation exception

4 minutes

Fraud review

8 minutes

Settlement discrepancy

12 minutes

Complex reconciliation exception

18 minutes

Chargeback or dispute

25 minutes

Complex processor issue

30+ minutes

Estimated handling time per payment event.

About 5% of transactions can create more than half of the operational workload.
A business processing 10 million transactions with a 1% exception rate can be easier to operate than one processing 5 million with an 8% exception rate.

What does one payment exception cost?

Handling time is only part of the picture. More complex payment events can involve several teams, tools and outside providers, making each intervention materially more expensive than a normal automated payment.

Payment event

Estimated operating cost

Normal automated transaction

$0.03

Simple exception

$4

Complex exception

$15

Fraud investigation

$20

Chargeback

$128+

Clearly Payments estimated operating cost per event; chargeback costs exclude transaction principal.

The largest opportunity is therefore not simply processing transactions more cheaply. It is reducing the number that require people.

How payment exception rates change operating costs

At 10 million transactions per year, a 1% exception rate creates 100,000 manual interventions. At 5%, that becomes 500,000. At 10%, it becomes 1 million. The staffing-hour comparison below assumes eight minutes of handling time per exception; it measures exception work only, rather than the entire payment-operations department.

1% exception rate: ~13,300 staff hours
5% exception rate: ~66,700 staff hours
10% exception rate: ~133,300 staff hours
At 2,000 hours/FTE: 10% equals more than 66 FTE-years

Payment operations staffing: how many people do you need?

Headcount depends heavily on automation. At 10 million annual transactions, Clearly Payments estimates roughly 7 FTE in a highly automated operation, 15 FTE in a typical one and 30 FTE in a heavily manual one.

Annual transactions

Highly automated

Typical

Highly manual

100,000

0.3

0.6

1

1 million

1.2

2.8

5.5

5 million

4

9

18

10 million

7

15

30

50 million

22

48

95

Clearly Payments estimated full-time-equivalent staffing by operating model.

The 10-million-transaction gap between highly automated and highly manual operations is about 23 FTE, representing more than $1.8 million in annual staffing cost before software, contractors and other operating expenses.

Transactions per payment-operations employee

330K

Highly manual

670K

Typical

1.4M

Highly automated

If headcount rises nearly one-for-one with transaction volume, the underlying payment workflows are probably not scaling.

Chargebacks and fraud reviews create expensive manual work

Disputes and fraud alerts often sit outside the straight-through payment flow. Their operating cost depends on how much evidence gathering, investigation and follow-up each case needs.

Chargebacks

A chargeback requires investigation, evidence gathering, response preparation, submission, monitoring and reconciliation. Clearly Payments estimates a typical chargeback creates about $128 in internal and third-party operating cost before the value of the transaction itself.

10,000 chargebacks × $128 operating cost = $1.28 million in operational expense.

Fraud review

An ecommerce merchant processing 1 million transactions annually and sending 5% to manual fraud review creates 50,000 reviews. At eight minutes each, that is about 6,667 staff hours, or roughly 3.3 FTE. At $80,000 fully loaded per employee, that equals about $264,000 per year in fraud-review labor.

Cutting the manual-review rate from 5% to 2% removes about 30,000 reviews and saves roughly 4,000 staff hours annually.

For online merchants, the balance between automated risk controls and manual review is part of the eCommerce payments operating model.

Complexity can matter as much as transaction volume

More processors, currencies, legal entities, ecommerce exposure, cross-border activity and disputes all add work even when transaction count does not change.

Complexity factor

Estimated workload increase

Additional processor or acquirer

20%

Multiple currencies

15%

Multiple legal entities

20%

High ecommerce mix

25%

High cross-border mix

15%

High dispute rate

30%

Manual reconciliation

50%

Clearly Payments estimated workload increases; factors are illustrative and should not be added mechanically.

Using multiple processors can improve redundancy, routing and commercial leverage, but Clearly Payments estimates a second processor can increase payment-operations workload by about 20% even at the same transaction volume.

For larger organizations, enterprise payment processing needs to account for this complexity alongside commercial pricing.

Transaction count matters more than payment volume

A company processing one million $20 transactions usually has more operating work than one processing 100,000 $200 transactions. Both process $20 million, but the first company has ten times as many authorizations, settlements, potential exceptions, refunds, fraud decisions and reconciliation records.

That is why cost per transaction is usually a better operating metric than payment-operations cost as a percentage of payment volume.

For budgeting, Clearly Payments estimates a typical enterprise can spend about $750,000 to $1.5 million in payment operations for every $1 billion processed, depending on average ticket size, transaction count, automation and exception rate.

Manual vs. automated payment operations at 10 million transactions

The following budget brings staffing and systems together for the same annual transaction volume. It shows why reducing manual work can have a larger effect on total operating expense than a small change in processing fees.

Operating model

FTE

Labor

Systems & tools

Total annual cost

Highly manual

30

$2.4M

$200K

$2.6M

Typical

15

$1.2M

$100K

$1.3M

Highly automated

7

$560K

$90K

$650K

Clearly Payments estimates; annual labor modeled at $80,000 fully loaded per FTE.

Moving from a highly manual payment operation to a highly automated one can reduce annual operating cost by about $2 million at 10 million transactions.

How embedded payments change operating costs

Embedded payments can simplify operations because payments become part of the software already used to manage customers, orders, invoices or bookings. But the operational work changes rather than disappears.

  • Merchant and sub-merchant onboarding
  • Settlement and payouts
  • Reconciliation across many merchants
  • Fraud and risk
  • Disputes and merchant support
  • Reporting and processor relationships

A five-minute workflow applied to 10,000 merchants creates more than 830 staff hours every time it runs across the portfolio. Embedded payments scale when onboarding, reporting, reconciliation and support scale with software rather than headcount.

Payment operations automation ROI: where the time savings come from

Common manual tasks include downloading processor reports, matching deposits, investigating settlement differences, moving data between systems, compiling management reports, gathering dispute evidence, checking failed payouts, reconciling processor fees and reviewing fraud alerts.

For 100,000 payment exceptions per year, an average 12-minute handling time consumes 20,000 staff hours. Reducing average handling time to five minutes cuts that to 8,333 hours, saving about 11,667 staff hours—nearly six FTE-years.

Worked examples: payment operations costs and automation savings

The following calculations show how to move from staffing and transaction assumptions to an annual budget. Each example answers a different question; exception workload should not be added to a staffing budget that already includes those employees.

1. Build an annual budget and cost per transaction

At 10 million annual transactions, the typical budget uses 15 FTE at $80,000 fully loaded per employee, plus $100,000 for systems and tools.
Annual operations cost: (15 × $80,000) + $100,000 = $1,300,000.
Cost per transaction: $1,300,000 ÷ 10,000,000 = $0.13.
The highly automated and highly manual budgets at the same volume are $650,000 and $2.6 million. Their difference is $1.95 million, rounded to about $2 million elsewhere in this article.

2. Convert payment exceptions into staff hours

Start with 10 million transactions, a 1% exception rate and eight minutes of handling time per exception.
Manual interventions: 10,000,000 × 1% = 100,000.
Handling hours: 100,000 × 8 ÷ 60 = about 13,333 hours.
FTE workload: 13,333 ÷ 2,000 = about 6.7 FTE-years.
This is the capacity required for those exceptions alone. It excludes other reconciliation, reporting, processor administration and operational duties.

3. Separate released capacity from cash savings

For 100,000 exceptions a year, reducing average handling time from 12 minutes to five minutes releases about 11,667 hours. At 2,000 hours per FTE-year, that is about 5.8 FTE-years. An $80,000 fully loaded annual labor cost implies $40 per hour, so the released time represents about $467,000 of annual labor capacity.
That amount becomes a cash saving only when the business avoids costs such as hiring, overtime or external support. Otherwise, the benefit is capacity for other work. Allow for implementation costs and any additional software or support expense before describing the result as automation ROI.

First-year net benefit: realizable annual savings − additional annual operating costs − one-time implementation costs.
First-year ROI: first-year net benefit ÷ one-time implementation costs × 100, where the implementation investment is greater than zero. Use the same time period and avoid counting the same labor saving twice. The article does not assume a particular implementation price or guaranteed cash saving.

The payment-operations metrics worth tracking

A useful payment-operations dashboard connects cost, throughput and exception handling. Track these measures together so a lower headline processing rate does not hide growing manual work.

Cost per transaction

Total payment-operations expense ÷ transactions processed.

Transactions per FTE

How much volume each operations employee supports.

Exception rate

Share of transactions requiring manual work.

Cost per exception

Average labor and system cost to resolve an exception.

Exception handling time

Time to investigate and close payment problems.

Reconciliation automation rate

Share reconciled without human intervention.

Manual fraud review rate

Share requiring human fraud review.

Chargeback handling cost

Operating cost per dispute.

Time to reconcile

Speed of matching transactions, deposits and fees.

Processor complexity

Processors, accounts, currencies and data sources managed.

Payment operations statistics: Clearly Payments estimates

These estimates summarize the operating models and workload assumptions discussed above.

  • $0.22 typical payment-operations cost per transaction
  • $0.08 highly automated cost per transaction
  • $0.43 highly manual cost per transaction
  • $225,000 typical annual cost at 1 million transactions
  • $1.3 million typical annual cost at 10 million transactions
  • $650,000 highly automated cost at 10 million transactions
  • $2.6 million highly manual cost at 10 million transactions
  • 28% of staff time spent on reconciliation
  • 22% spent researching exceptions
  • $128+ estimated operating cost of a chargeback
  • 1.4 million transactions per FTE in a highly automated environment
  • 20% estimated workload increase from adding another processor
  • 50% estimated workload increase from heavily manual reconciliation

Methodology and planning assumptions

Model and calculations: Clearly Payments. Methodology explanation updated November 16, 2026. This article uses merchant payment-operations planning scenarios to explain workload and budgeting. It is not a country-specific salary survey or a measured average across all merchants.

Scope, currency and Canadian use

All dollar amounts are USD. The operating models cover merchant reconciliation, exceptions, disputes, fraud review, refunds, reporting and processor/bank administration. They do not represent the full cost of building a bank, payment network or payment platform.
Canadian businesses can apply the same framework using CAD-denominated labor and system costs; the USD figures should not be read as equivalent CAD amounts. Use local compensation, employer costs, software pricing and the business’s actual workflow mix when preparing a Canadian budget.

What the operating budget includes

Annual payment-operations cost combines allocated labor with operating systems and tools. Interchange, processor transaction fees and the principal value of disputed transactions are outside that operating-cost measure. It is not an all-in merchant processing rate. Chargeback and fraud examples discuss the work involved; do not add transaction principal or fraud losses to an operating-cost comparison without identifying that broader scope.

Labor and handling-time assumptions

The detailed 10-million-transaction budget uses $80,000 of fully loaded annual labor cost per FTE. When adapting it, include the salary, employer taxes, benefits and other labor overhead your own budget allocates to the role. Staffing conversions use 2,000 working hours per FTE-year; this is a planning convention, not a promise that every paid hour is available for case handling.
The exception-rate illustration uses an eight-minute average intervention. The automation example separately compares 12 minutes with five minutes. Other event-handling times are scenario inputs for their respective workflows, rather than a single average to apply to every payment.

Keep the scenario assumptions together

The volume budgets, staffing ranges, general unit-cost comparison and individual-event costs are separate planning views. The $80,000 labor assumption reconciles the detailed 10-million-transaction budget; it is not a universal multiplier that reproduces every row of the separate staffing and volume tables.
For an actual business case, use one consistent set of transaction counts, staff costs, exception rates, handling times and system costs. Calculate its cost per transaction from that budget. Complexity percentages describe individual workload sensitivities and should not be added together mechanically. Rounded figures can differ from calculations made with unrounded inputs.

The biggest payment-operations cost is manual work

Processing fees are easy to see because they appear on statements. Operational costs are harder to see because they are spread across finance, accounting, fraud, customer support, treasury and payment teams.

At scale, the goal is to make normal transactions disappear into automated workflows so employees spend their time only on the exceptions that require judgment. Organizations that do this well can process far more transactions without building equally large payment-operations teams.

Find the cost hiding behind your payment stack

Clearly Payments can review your processing setup, processor mix, reconciliation workflow and payment costs to identify where complexity and manual work are creating unnecessary expense.

Explore payments consulting → Talk to Clearly Payments →

Related resources: Payment Processing FAQ · How payment processing works · Payment Systems Architecture

Have a question about your payment setup?

Clearly Payments can review your processing setup, pricing or payment technology.

Talk to Clearly →
Facebook
Twitter
LinkedIn
Email

Related payments research