A discussion in a small business
A conversation on the shop floor.

A customer pays. The money moves. Somewhere in the business, a person still has to establish what the payment was for. That gap between moving funds and understanding them is where many payment projects should begin.

Start with the reference

An invoice has a customer, an amount and a reason for payment. If the reference survives the journey, a finance team has a useful connection between its commercial records and the money received. If that connection is missing, faster payment can still lead to manual work.

A business reviewing its process should follow one transaction from the first request to the final record. Who creates the reference? Can it be changed? Where does it appear on the receipt? What happens if a customer pays twice or sends a different amount?

Open banking in the wider picture

Open banking supports services that help people and businesses use financial information and make payments through regulated providers. Open Banking Limited explains the model and its uses. The practical question for a business is how a particular service fits its own workflow.

A new payment route needs a clear place in reconciliation, support and reporting. The person who raises an invoice should understand how the payment will be identified. The person responsible for customer support should know where to look if the expected record does not arrive.

Design for the awkward transactions

The routine payment is only one part of the story. A short payment, duplicate payment or unfamiliar reference tests the quality of a process. Good operational design gives each exception an owner and preserves enough information for that person to investigate.

The same applies to supplier payments. Approval, payment initiation and confirmation are different moments. Keeping them distinguishable makes a business record more useful than a single status labelled complete.

A better starting brief

Before selecting tools, describe the current process in plain language. Name the people involved, list the systems they use and identify the points where they have to re-enter information. Then define the record you want to see at the end.

CapitalPay’s payment-operations software starts with this connection between the customer, the payment and the business record. A useful product conversation begins with the work your team needs to do.