Purchase to Pay in a Small Business: Approval, Receipt, Matching, Payment

In a small business a supplier invoice usually arrives by email, somebody glances at it, and at month end it gets paid. What is missing along the way is not technology but three questions nobody asked: did we order this, did we receive it, and does the price match what was agreed. A purchase-to-pay chain is simply the way to answer those three before the money leaves.

The three control points

Large businesses call this three-way matching, and in a small business it can be three columns in a spreadsheet. What matters is not the tool but that the questions get asked before payment rather than after - once the money has gone, any correction becomes a credit request to a supplier, and that is a far longer conversation.

Where supplier invoices disappear

The first failure is an address: when invoices arrive in the personal mailbox of whoever ordered, there is no way to know what exists. One person on holiday means an invoice nobody saw, and the supplier finds out before you do.

The fix is one dedicated address for supplier invoices, monitored by more than one person, given to every supplier once at onboarding. The logic of capturing supplier documents without losing any is in supplier receipt capture.

An order, even with no system

You do not need a purchasing system to have an order. A structured email to the supplier with four things is enough: what, how many, at what price, and when. It is also what makes matching possible later, because there is something to compare against.

Less important than the format is the consistency: an order placed by phone sometimes and by email other times produces a state where half your purchasing is checkable and half is not. In a small business a phone call ending in a written summary message is an order in every sense.

What gets recorded per supplier invoice

• The supplier and their invoice number, exactly as printed.
• The invoice date and the planned payment date.
• Which order or purchasing event it relates to.
• Status - received, approved, in query, paid.
• Who approved it and when.
• How it was paid - method and execution date.

Six lines that fit in a spreadsheet and hold up to a fair size. The third field is what turns the list from an archive into a control: without it there is no way to answer whether the invoice corresponds to something you requested, which is exactly the question the whole process exists for.

One thing worth adding beyond the six: a short free-text field for anything unusual. "Discount agreed by phone", "includes delivery that was not on the order" - notes like these look redundant in the moment and explain the discrepancy two months later.

Who approves, and where approval starts

A payment approval needs two things: a name and a date. Not a signature and not a process - just a mark that somebody checked. In a two-person business that looks unnecessary until the moment a payment surfaces that nobody remembers approving.

The practical question is where approval begins: above an amount, by expense type, or for a new supplier. All three cuts are legitimate, and the logic of setting limits and who approves what is in approval limits and controls. What does not work is "the owner approves everything" in a business with dozens of invoices a month - that produces automatic approval instead of a check.

What to automate, and what not to

Automate: filing the invoice, identifying the supplier, creating a record, a reminder before the due date, and recording the payment afterwards. All of those involve no judgement.

Do not automate: the approval itself. Automatic approval by amount sounds convenient and removes the entire point of the control - what you can do is route automatically to the right approver and leave the decision with them. The logic of separating duties with two people in a business is in invoice approval with two people.

What to measure in this chain

Three numbers are enough to know whether the process works: how many invoices arrived this month with no matching order, how many showed a price discrepancy, and how many were paid late. All three come from the list itself and require no extra work.

The first is the real health measure. An invoice with no matching order is not necessarily serious as a one-off, but a high rate of it says purchasing is happening outside the process - and none of the other controls will help, because they have nothing to compare against.

The third measure also serves the other side: a supplier consistently paid late becomes a supplier less willing to do you a favour when you need one. That is part of the cost of a disorganised process, and it appears in no report.

A payment run instead of paying one at a time

Paying every time an invoice arrives consumes more time and produces more errors than a fixed weekly run. A run has one list, one approval and one execution - and therefore one record that is easy to check against.

What happens without a fixed run is two things: payments forgotten until the supplier calls, and double payments - the same invoice paid once by one person and once by another. The run mechanism itself, including what gets checked at each stage, is in the weekly supplier payment run, and the Masav file mechanics are in supplier invoice approval through to Masav.

What do you do with an invoice that does not match?

Do not pay it and do not ignore it - mark it in a third state: "in query". The two normal states, approved and not approved, are not enough, and without the third a disputed invoice falls between the cracks and surfaces when the supplier stops delivering.

What gets recorded on it: what the discrepancy is, who contacted the supplier, and when. Three lines that let you answer "what is happening with this" without reconstructing an email thread.

And the important rule: an invoice in query still enters the open-items list and the cash forecast. An unpaid expense will still be paid eventually - if not in full then in part - so hiding it from the forecast produces a surprise exactly when it resolves.

Sources

• Business automation for small businesses in Israel
• Israel Tax Authority - business information