The most revealing thing about Viewpost is the file it asks a customer to send. Not a pristine API specification. Not a map for replacing the ERP. A check file - the ordinary output of a process the customer already runs. In the few minutes before those payments become paper, Viewpost takes another swing at making them digital.
That is the Orlando company's current business in one sentence. Its FinalCheck service looks at suppliers due to receive checks, identifies or contacts those willing to take a virtual card, ACH or real-time payment, and routes each eligible payment accordingly. The real holdouts still get checks. The buyer keeps its bank, existing virtual-card program and accounts-payable workflow.
This is enterprise software shaped by scar tissue. Large companies have already bought payment modernization, sometimes several times. The obvious suppliers were enrolled first. What remains is the awkward tail: local contractors, special handling, card limits, portal logins and vendors who ignored last year's campaign. Viewpost does not sell a glorious clean slate. It sells a cleanup pass.
The product lives in an awkward moment
Most vendor-enrollment programs work like campaigns. Somebody exports a supplier list, calls through it, records preferences, and repeats the exercise months later. Viewpost's distinction is timing. It runs the enrollment effort against an actual check run, when a supplier has a concrete reason to answer: money is ready now. It repeats that work each time payments are sent, so a vendor's previous “no” does not become permanent infrastructure.
A successful conversion can produce a single-use virtual card for the exact payment amount, with remittance information attached. A supplier processes it through its merchant setup. ACH is available for vendors that prefer a bank deposit. Viewpost also lists premium ACH, RTP and Image Cash Letter processing for eligible banks. If none fits, the check survives. Even an unprocessed virtual card can be voided and replaced by the original paper payment.
“The remaining challenge is not the ability to process electronic payments; it is reaching and enabling the suppliers.”Max Eliscu, founder and CEO
The company's AI claim is modestly placed inside this machinery. Viewpost says its enrollment and processing tools use decisioning and algorithms to improve conversion. The expertise that appears harder to copy is less cinematic: supplier outreach, payment preferences, exception handling, remittance, fallback logic and the institutional patience to call a vendor when a check is already queued.
The first idea was much bigger
Max Eliscu came to the problem through working capital. He had founded LSQ Funding in the 1990s and saw the gaps between invoices, payment approvals and cash. In 2011 he created Viewpost as an LSQ Holdings subsidiary and funded it with $25 million in equity. By 2014, the public pitch was a broad business network: create and exchange invoices, track payments, connect accounting packages, make electronic or paper payments, and offer early payment in return for a discount.
Eliscu did not begin with the last check. He began with the entire conversation between an invoice and the money behind it.
The ambition was network-sized. A hotel might offer to pay its waste hauler early for a discount. Businesses could connect across Oracle, SAP, PeopleSoft, Microsoft Great Plains or QuickBooks. Viewpost would know what was owed, what had been approved and how the money moved. In 2016 a Bank of America arrangement put enrollment in front of more than three million small-business customers. Partnerships with U.S. Bank and Fifth Third were also public, while Comdata added virtual-card issuance.
The public record does not show one theatrical failure that killed that plan. It shows something more common: the broad network ceased to be the center of the story. The website now speaks mainly to large enterprises, usually those above $250 million in revenue, and to banks, platforms and check printers. The front door is FinalCheck, not a universal invoice network.
What changed their mind: friction won
Viewpost's narrower strategy reads like a response to the toughest competitor in enterprise finance - implementation fatigue. A new AP suite may promise invoice capture, approvals, cards, cross-border transfers and reporting. It can also ask a company to rework integrations, controls, vendor records and banking relationships. Those costs arrive before the promised savings.
FinalCheck flips the proposal. Do not persuade the buyer to abandon a primary payment provider. Take the checks that provider failed to convert. Do not require a new workflow. Use the approved file already headed toward print. Do not force every supplier onto one rail. Offer the rail each supplier will accept, then preserve paper as a release valve.
Typical savings relative to existing check-printing costs, according to Viewpost.
The clever part is commercial as much as technical. A standard AP replacement competes for the whole budget. Viewpost can argue that it is additive. Its site says the long-tail work often triples the conversion results of a customer's primary provider. Again, that is Viewpost's own measure. But the promise is easy for a finance buyer to test against a defined check population.
What it costs - and who pays
Current enterprise pricing is negotiated and not posted. Historical pricing shows how the model evolved. In 2014, Viewpost charged 50 cents to send an electronic check and 75 cents for paper. A later Bank of America pricing sheet listed a possible $14.99 monthly account fee, 50 cents per electronic business payment, $1 per paper check and 30 percent of savings from dynamic discounting. Viewpost's support center says some vendor ACH receipts commonly carry a 1 percent fee. Those figures describe legacy or account-specific plans, not a quote for FinalCheck today.
Virtual cards introduce a different ledger. The supplier pays its merchant-service provider to accept the card. The payer can receive a rebate based on card volume. Viewpost and its issuing or platform partners participate in those economics. Suppliers trade acceptance cost for faster, known-good funds and electronic remittance; payers trade paper expense and fraud exposure for rebates. The arrangement works when both sides prefer that bargain to a check.
Funding gave Viewpost room to search for that model. Public databases disagree on the exact lifetime total. Dealroom identifies $30 million in 2014, $24.5 million in 2015, $31 million of debt in 2017, another $10 million later that year, $3 million of debt in 2020 and $2 million in 2021, alongside the original $25 million. CB Insights reports $131.52 million across nine rounds. No valuation has been publicly disclosed.
A specialist beside the suites
Viewpost sits near Coupa, Tipalti, AvidXchange, BILL, Corpay, Bottomline, MineralTree and Medius, but the overlap can mislead. Those businesses sell broad AP automation, spend control, supplier networks or global payment capabilities. Viewpost's current wedge begins later, after the enterprise has already built much of that stack and still has a check problem.
Capture invoices, manage approvals, procure, pay and report across a broad workflow.
Connect suppliers and deliver ACH, card, wire or cross-border payments at scale.
Take the residual check file, retry enrollment in real time and coexist with both groups.
Print every remainder, pay postage, reconcile exceptions and absorb fraud exposure.
That is why Coupa can be both adjacent alternative and partner. Coupa's 2025 product terms identify Viewpost North America as the provider powering Payment Optimization services. In May 2026, Coupa named it Digital Payments Partner of the Year. Three months later, treasury platform Kyriba announced that it would embed Viewpost Check Optimization, with availability planned later in 2026.
A broad network is funded
Eliscu starts Viewpost with $25 million in equity.
Invoices, banks and virtual cards
The network launches, Bank of America distribution grows and Comdata adds card rails.
The long tail becomes the headline
A refreshed public pitch centers enterprise check optimization and coexistence.
Partners validate the layer
Coupa awards the company and Kyriba embeds its service.
Copy the compatibility, not just the card
The reusable lesson is not “launch a virtual card.” It is to look at the rejected output of an existing system. What does the customer's expensive transformation still dump into a manual queue? Can a new product accept that output unchanged, improve a measurable fraction, and hand back the exceptions safely? Viewpost made the check file an interface and the check printer a fallback mechanism.
Conditions that favor it
- High, recurring enterprise check volume
- Suppliers with mixed payment preferences
- An existing workflow buyers refuse to replace
- Enough card-eligible spend to fund rebates
Conditions that weaken it
- Most suppliers are already electronic
- Vendors reject card fees or paid ACH
- International or complex cross-border rails dominate
- Payment files arrive too late for another decision
It also depends on trust. A supplier receiving an unexpected virtual-card call may reasonably verify the payer, invoice and amount. Some need portal entry, multiple card swipes or a specific remittance format. Others simply prefer a check. Viewpost's support pages are full of these prosaic edges, which is precisely the point. The product is not the card number alone. It is the work required to get the right money to the right supplier without breaking reconciliation.
The boring remainder is the business
Viewpost's site now displays logos from Walmart, Kroger, Albertsons, Orlando Health, Hartford HealthCare, UCLA, RH, Ingram, MSC, BradyPLUS and Restaurant Depot. Its target list spans retail, healthcare, higher education, hospitality, manufacturing, distribution, property management and municipalities - industries with large, messy supplier populations and little appetite for another migration.
That customer set explains the company's survival better than a glossy category label. Viewpost is fintech, software, services and enrollment operations at once. It is not trying to make the check look modern. It is using the moment before printing to ask whether the check needs to exist at all.