A clearer decision before money leaves.

The idea in practice.

Tervra is developing a business account for UK B2B businesses using their own funds, with payment understanding and supporting evidence alongside it. Accounts, cards and payments are not available today.

The purpose beside the payment

The proposed review brings together the payee, amount, business purpose and supporting documents so the person approving can inspect them.

Make changed details visible

A new destination may need further checks. The design gives the reviewer space to record what was checked, by whom and when; it does not guarantee fraud prevention.

An uncertain outcome stays uncertain

If the result of a request is unknown, the view asks for its status to be checked before another request is prepared. A missing response is not proof that a payment failed.

Make the decision understandable.

The person approving a payment should not need to reconstruct its purpose from a short reference. Bring the supplier, amount, supporting invoice and any relevant changes together. Keep the person preparing the instruction distinguishable from the person approving it where the policy requires that separation.

When the destination changes.

A previously paid supplier can still require a fresh check. If the details change after a review, the original approval may no longer cover the proposed instruction. Keep the destination version and the check together.

Explore the proposed payment review

Keep a clear record afterwards.

An instruction needs an identifiable result and a history a reviewer can understand. Rejection, a pending result and a confirmed payment should not collapse into one generic success message. That distinction is part of the proposed payment journey.