Blog

The B2B payment map · Part 1

Where B2B payments break, from purchase to close

A map of the handoffs that slow B2B payments down, from purchase order to month-end close, on both the paying and the getting-paid side, and what changes when it all runs on one system.

The Viacle team6 min read

Where a B2B payment breaks
A handoff where delays, errors or cost creep in
  1. 01

    Buy

    Request, approve, order, receive

    When you pay

    • Spend committed before anyone approves it
    • Goods arrive, but the receipt is never recorded

    When you get paid

    • Orders arrive with no purchase order to bill against
    • Proof of delivery stuck in someone's inbox

    On one system: Approval, order and receipt share one record

  2. 02

    Bill

    Invoice, match, approve

    When you pay

    • Paper and PDF bills keyed in by hand
    • Bills that don't match what was ordered or received

    When you get paid

    • Invoices sent to the wrong person
    • Unclear terms that invite late payment

    On one system: Bills checked against the order before approval

  3. 03

    Pay

    Send and collect money

    When you pay

    • The true cost of a payment unknown until it's sent
    • Cross-border payments and currency hard to arrange
    • Supplier bank details changed by email
    • Checks still in the mix

    When you get paid

    • Customers can't pay the way they prefer
    • No notice when money arrives
    • Fees and short payments shrink what lands

    On one system: Rate, fee and status visible before money moves

  4. 04

    Record

    Match and reconcile

    When you pay

    • Payments matched to bills by hand
    • Exchange differences and fees booked late, or guessed

    When you get paid

    • Remittance arrives separately from the cash
    • Short payments turn into disputes

    On one system: Payments post with their bill, rate and fee attached

  5. 05

    Close

    Ledger and reports

    Both sides

    • Exports and spreadsheets stitch systems together
    • The same number differs from system to system
    • Every close starts from scratch

    On one system: Reports built from the records you ran on

What each stage looks like when it runs on one system

A B2B payment looks like a single event: money leaves one business and arrives at another. In practice it's a chain. Someone asks to buy something, someone approves it, an order goes out, goods arrive, a bill follows, money moves, and the books record what happened. Each link is often handled in a different tool, by a different person, at a different time.

The money rarely goes missing. What goes missing is the context: what was ordered, what was agreed, what it really cost. Every handoff between systems is a chance for that context to fall away, and a finance team pays for it later, usually at month-end.

What are B2B payments?

B2B payments are payments between businesses: paying suppliers for goods and services, and collecting from customers. Unlike a card purchase at a checkout, they usually come with purchase orders, invoices, payment terms, approvals and, for international suppliers and customers, currency conversion. That paperwork is what makes them hard to run well.

Your business sits on both sides

Most discussions of B2B payments look at one side at a time. But a growing company pays suppliers and gets paid by customers every day, through the same five stages. The map above follows both. The top of each stage shows where things slip when you pay; the bottom shows where they slip when you get paid.

Read across the map and three patterns repeat:

  • Re-entry. The same details are typed into one system after another, and each copy is a chance for a mistake.
  • Missing context. A payment arrives or leaves without the order, bill or terms that explain it.
  • Late discovery. Differences surface at month-end, long after the people who could explain them have moved on.

One purchase, three systems

Take one illustrative purchase. A company orders six laptops from a German supplier for €9,000. The bill is booked at that day's exchange rate as $9,720. By the time it's paid, the rate has moved, and a payment fee applies, so $9,780 leaves the bank.

One purchase, three systems
Illustrative
  • Order PO-2087 · 6 laptops × €1,500

    Purchasing tool

    €9,000
  • Bill #A-311 at 1 EUR = 1.0800 USD

    Payables tool

    $9,720
  • Cash out at 1.0850, plus a $15 fee

    Bank statement

    $9,780

Across separate tools

A $60 gap between bill and bank, with no record of why.

On one system

$45 exchange loss and $15 fee posted with the payment in JE-5521. Supplier balance: $0.

When ordering, bills and payments live in separate tools, that $60 shows up as an unexplained difference at close. Someone has to find the bill, look up two exchange rates and locate the fee before the account reconciles. When the payment carries its own context, the books record it as it happens: the bill posts in JE-5520, the payment posts in JE-5521, debits equal credits, and the supplier balance clears to zero.

What to ask of any finance platform

For a CFO or business owner, the question isn't whether each tool works on its own. It's whether the numbers hold together when they meet. A few questions cut through quickly:

  • Can you follow one payment from its purchase order to its journal entry without leaving the system?
  • Are exchange differences and payment fees recorded when the payment settles, not estimated at month-end?
  • Do changes to supplier bank details need approval before money can move? It's one of the simplest ways to prevent B2B payment fraud.
  • When something doesn't match, does the system show the records behind the difference before anyone corrects it?
  • Are your reports built from the same records you used to run the business, or from exports?

What changes on one system

B2B payment automation is usually sold one stage at a time: a tool to capture bills, another to send payments, another to reconcile. Each helps, but every one adds a handoff. Unified finance takes the other route. Purchasing, billing, payments, cash management and accounting run on one system, so each stage starts with everything the one before it knew. The checks at the bottom of the map aren't extra steps. They're what each stage looks like when nothing has to be handed over.

Next in this series

This is the first part of a series. The articles that follow take the map one stage at a time: buying and receiving, billing, paying and getting paid, and recording and close. Each looks at what breaks, what it costs and what to look for in the tools you choose.

See every stage run on one system.

Get a demo