At 9:17 on a Monday morning, a small service company sends a customer an invoice for $18,400.
Nothing particularly interesting appears to happen. The job has already been completed, the invoice exists, and the customer has agreed that the amount is correct. From a distance, the final step should be almost automatic: the customer pays and the business gets its money.
In practice, an invoice like this can move through half a company before it becomes usable cash.
That is the more useful context for understanding Helcim. Helcim currently provides online invoicing, ACH bank payments and a Virtual Terminal capable of processing both card and ACH transactions without dedicated payment hardware. Its current U.S. ACH pricing is 0.5% plus $0.25, capped at $6 per transaction, while its core account includes invoicing and the Virtual Terminal without a standard monthly software fee.
Those are the product facts.
The interesting part is what happens to the people around them.
Monday, 9:17 a.m.
The invoice goes out.
The company in this example could be a commercial cleaning operation, equipment-service company, specialty contractor, consulting firm or another small B2B business. The exact industry matters less than its internal structure. There is an owner, somebody responsible for customer relationships, an office employee who sends invoices, and a bookkeeper who eventually has to make the bank deposits agree with the books.
The customer has already received $18,400 worth of value. The seller has already paid employees for doing the work.
That asymmetry is important.
Businesses often discuss accounts receivable as though it were a clerical issue. It is actually a cash-flow issue created by work that has already happened. Payroll did not wait for the client to pay. Fuel, rent, materials and software subscriptions did not wait either. By Monday morning, much of the expense attached to that invoice is history.
The $18,400 sitting in receivables is therefore not theoretical future revenue. It is money the company needs to convert back into cash.
The employee sending the invoice might be an office administrator, billing clerk or bookkeeper. BLS data put the median annual wage for bookkeeping, accounting and auditing clerks at about $49,000 in the latest Occupational Outlook Handbook data, while office and information-clerk roles commonly sit in the low-to-mid-$40,000 annual range.
That employee’s time is not wildly expensive compared with a lawyer, engineer or medical professional.
But repetition changes the calculation.
One invoice takes almost no time.
Two hundred invoices become a department.
Tuesday afternoon: the customer does not pay
This is the part payment-company advertising tends to skip.
The invoice was delivered correctly.
The customer simply has not done anything yet.
At 2:40 Tuesday afternoon, the office employee checks receivables. The invoice is still open. There is no crisis; payment terms may allow plenty of time. But now the invoice has entered the company’s administrative memory.
Someone knows it exists.
Someone will look again.
Someone may eventually follow up.
This is how labor begins attaching itself to an unpaid balance.
If an employee spends only five minutes checking, following up or answering questions around a particular receivable, that is almost irrelevant. Across 500 annual invoices, five minutes per invoice becomes more than forty hours.
One full working week.
This is why payment automation should not be evaluated by asking whether it saves “a few minutes.” Almost every business workflow is made of a few minutes.
The real question is how often those minutes repeat.
Wednesday, 11:06 a.m.: the customer finally responds
The email is short.
Can we pay this from our bank account?
Now Helcim becomes interesting.
Under Helcim’s currently published U.S. ACH pricing, an $18,400 ACH transaction hits the $6 fee cap.
Six dollars.
The same invoice paid by card has completely different economics because card processing remains percentage-based. Helcim’s own current comparison material notes that credit-card costs generally run materially higher than ACH and specifically positions ACH as attractive for large-value transactions.
Even using a simple hypothetical 2.5% card cost, an $18,400 transaction would create $460 in processing fees.
The difference between $460 and $6 is $454.
Suddenly the decision about how the customer pays no longer feels like a tiny feature preference.
Imagine twenty invoices of this size moving through the business in a year.
The theoretical difference becomes more than $9,000.
That is the point where a processor stops being an invisible utility and becomes an operating-cost decision.
There is, however, a catch.
ACH is cheaper because it is not simply another version of instant card authorization. Bank transfers generally take longer to move and settle. Helcim’s own ACH materials describe a multi-business-day process rather than instant availability.
So the owner has a tradeoff.
If the business urgently needs immediate authorization, a card may still make sense.
If the customer is paying a normal commercial invoice under ordinary payment terms, waiting several business days in exchange for potentially hundreds of dollars in lower processing cost can look perfectly reasonable.
The best payment method depends on the business problem being solved.
Wednesday, 11:19 a.m.: nobody wants to explain ACH
This is where software either earns its place or creates another employee task.
If the client has to call the company, ask for banking instructions, receive a PDF, manually configure a vendor in their bank portal and then email somebody afterward saying “sent,” the organization has not eliminated much administrative friction.
It has merely changed the transaction rail.
Helcim allows ACH to be processed through its payment environment, including the Virtual Terminal, and its Virtual Terminal can run from a computer, tablet or phone.
For the office employee, that changes the process from an improvised banking conversation into a defined payment workflow.
That distinction sounds boring.
It is.
Boring is good when somebody is processing business payments all day.
The average employee does not need another flexible system that supports twelve possible ways to solve the same problem. They need to know what they are supposed to do when an $18,400 customer says, “I want to pay from my bank.”
Predictable procedure reduces mistakes.
It also reduces questions.
Thursday morning: the customer changes their mind
Now imagine something more human.
The customer’s accounts-payable employee calls.
Their bank process is taking longer than expected. They have a company card and want the balance paid immediately.
This happens in actual businesses because payment decisions are not always elegant.
Now the office employee has a different tool available.
Helcim’s Virtual Terminal is designed for card-not-present and ACH transactions and can be used directly from an internet-connected device. If a payment does not already have an invoice attached, Helcim says the Virtual Terminal can automatically generate one; its current documentation also supports additional payment options such as partial payments.
Again, the value is not really the Virtual Terminal itself.
The value is that the employee receiving the call does not have to invent a solution.
They do not need to walk to a countertop card machine and pretend the buyer is physically present.
They do not need to send the customer away to figure something out.
They have a documented remote-payment process.
The client can finish the conversation.
The employee can finish the transaction.
Everybody moves on.
What did that phone call actually cost?
Suppose the employee handling receivables earns roughly $45,000-$50,000 per year.
That puts base wage-equivalent time somewhere around the low-$20s per hour before benefits and employer payroll costs, broadly consistent with BLS data for several bookkeeping and administrative occupations.
A ten-minute call therefore appears to cost almost nothing.
Maybe four dollars of labor.
That is the wrong way to look at it.
The employee does not receive only this call.
There may be sixty invoices open.
Twenty customers asking questions.
Three overdue accounts.
Refunds.
Billing corrections.
Bank deposits.
Month-end reconciliation.
A business does not suffer from one ten-minute interruption. It suffers from a workflow composed of hundreds of them.
If payment tools reduce ten hours of repetitive administrative work every month, that can represent 120 hours annually.
At $23 per hour in simple wage terms, that is $2,760 of labor.
Add payroll burden and the actual employer cost is higher.
More importantly, those 120 hours can now be used for something else without immediately hiring another employee.
This is often the forgotten half of software economics.
A payment platform has a transaction price.
It also has a labor price.
Friday: $18,400 is no longer one number
By the time the money arrives, several people inside the company can view the same payment differently.
The salesperson sees a successfully completed customer relationship.
The administrator sees a closed invoice.
The bookkeeper sees a transaction that now needs to reconcile correctly.
The owner sees cash.
Those perspectives are not interchangeable.
This explains why apparently simple payment software accumulates reporting, invoicing and customer-management functions over time. The card authorization is only one moment. Businesses need enough context around the transaction that employees can understand it later.
Helcim’s current pricing page bundles invoicing, customer records, the Virtual Terminal and integrations around its payment-processing account rather than treating the transaction as the only feature.
That broader environment is probably more important for an established business than it is for a person making ten sales a month.
Volume changes what “simple” means.
At low volume, memory works surprisingly well.
At higher volume, memory becomes expensive.
Then the bookkeeper enters the story
The customer paid.
Everyone else believes the story is over.
For the bookkeeper, it may just be beginning.
They need to know what the $18,400 belongs to. If the business processed a card instead, they need to understand why the eventual net deposit may differ from the gross invoice amount. Refunds, processing fees and payment batches all create additional context.
This is why a processor should not be judged solely by whether customers find it easy to pay.
The back-office employee matters just as much.
If the front end saves customers two minutes while the accounting department spends an additional five hours per month untangling the results, the business has not necessarily improved anything.
BLS still shows bookkeeping, accounting and auditing clerks as a major occupational category even though employment is projected to decline as more routine work becomes automated. That decline itself tells an interesting story: businesses increasingly expect software to absorb mechanical accounting tasks while humans concentrate on exceptions and judgment.
A payment processor therefore earns part of its value by making the exceptional cases easier to understand.
The bookkeeper should not be reconstructing every ordinary transaction manually.
Now imagine the invoice was only $85
This is where the entire Helcim analysis changes.
On an $85 transaction, obsessing over ACH’s $6 fee cap makes no sense because the transaction never gets near the cap and the customer’s convenience matters much more.
A card is probably exactly what everybody wants.
Quick.
Familiar.
Done.
The strange thing about payment processors is that the same tool can be economically excellent at one transaction size and unremarkable at another.
That is why a business should not ask:
Which payment method is cheapest?
It should ask:
Which payment method makes sense for this type of payment?
A business with $50 consumer transactions and a business with $20,000 commercial invoices should not have identical payment strategies.
Helcim becomes particularly interesting when a company has both.
Cards for ordinary quick payments.
ACH for large invoices.
Virtual Terminal for the person who phones in.
Online invoices for customers who prefer self-service.
One platform can cover those situations without pretending they are economically identical.
What the owner eventually realizes
The owner initially thought they were comparing payment-processing rates.
They were actually comparing a collection system.
That system includes the obvious fee paid to Helcim or another processor, but it also includes the number of employees involved between invoice creation and clean reconciliation.
That distinction changes the buying decision.
Suppose Processor A costs $4,000 less per year in direct fees but generates enough awkward workflow to consume an additional 200 administrative hours.
At $23 an hour, that is already $4,600 of wage-equivalent labor.
The “cheaper” processor is no longer obviously cheaper.
Now reverse it.
Processor B is easy for staff but costs an additional percentage point on $2 million of annual payments.
That is $20,000.
Convenience is not worth infinity either.
The sensible calculation sits somewhere between the two extremes.
Processing fees + employee time + software expense + error/reconciliation cost.
That is the actual price of getting paid.
Helcim is strongest when there is enough business to make boring things expensive
A one-person company sending four invoices a month probably does not need a complicated optimization project.
If email, bank transfer and the existing card processor work, leave them alone.
The story changes when the business has employees.
A billing employee.
A bookkeeper.
A salesperson whose clients call them with payment questions.
An owner who sees $1 million or $2 million move through processing every year.
Now small differences repeat enough times to become real.
BLS’s latest wage reporting shows office, information-clerk and bookkeeping roles commonly costing employers tens of thousands of dollars annually before benefits and payroll burden. The transaction system these employees use every day is therefore not a trivial purchase.
It is workplace infrastructure.
Helcim’s pitch becomes credible when the company needs several payment paths but does not want a fixed monthly charge for the core processing account. Its current offering includes the Virtual Terminal, online invoicing and integrations, while its ACH pricing remains particularly attractive for large domestic invoices because of the $6 fee cap.
None of that automatically makes it the right processor.
A business should still compare its actual card mix, existing integrations and employee workflow.
But it creates a rational reason to look.
The $18,400 payment finally becomes boring
That is the ideal ending.
Nobody celebrates.
The customer paid.
The administrator can see it.
The bookkeeper knows what it belongs to.
The owner sees the cash.
The salesperson does not receive another call.
The transaction disappears into the company records and everyone gets back to work.
This is what payment technology is supposed to do.
The interesting thing about Helcim is not really that it can process an $18,400 payment. Plenty of companies can.
The interesting question is how much money and employee attention gets burned between “invoice sent” and “invoice done.”
On a large invoice, ACH pricing can change the direct cost dramatically.
On hundreds of invoices, workflow can change the labor cost dramatically.
And once a business has enough employees and enough volume, those two numbers start meeting each other.
That is when choosing a processor stops being about a card reader.
It becomes a decision about how the company wants money to move through the people who work there.
Last reviewed: August 10, 2026
