One remittance. Several questions answered.

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.

A customer may pay a statement spanning several invoices, returns and agreed discounts. The amount received may match none of the individual invoice totals.

The context worth keeping

Review the remittance against the invoice list and supporting credit notes. Separate an agreed adjustment from a deduction that still needs evidence, and retain the links used in the explanation.

A statement includes returns and credits.

A fictional wholesaler receives £8,400 against a £9,000 statement. A £400 credit note supports part of the difference; another £200 remains to investigate. Keep both facts visible instead of labelling the whole statement matched.

The questions worth exploring.

How are invoice lists, returns and credit notes shared? Who resolves deductions that appear on the customer’s remittance but not in your records?

The account is being designed around these workflows. Early access is discovery, not confirmation that a business is eligible or that a particular service will be available.

Keep the boundaries clear

A plausible allocation is a proposal for review. It should not silently close a disputed balance or turn an explained difference into confirmed settlement.

Shape it around your workflow

What matters most in your business account? Tell us about the account, payments and administrative work you handle today. Please describe your workflow without sharing confidential customer records.