Your questions, answered.

Tervra is a business account in development for UK B2B SMEs using their own funds. We’re designing payments, cards, invoices and supporting context around the account to help people understand their money.

No. Accounts, cards and payment services are not available today. There is no confirmed launch date. Early access is customer discovery, not an account application.

The initial focus is UK businesses that trade with other businesses and manage their own funds. Consumer accounts, client-money accounts, tenant deposits and pooled customer funds are outside the initial scope. Eligibility criteria remain under development.

That is part of the planned business-account experience. Provider arrangements and the precise services available remain under development; account details are not available today.

A separate account has its own balance and activity. A transfer changes the source and destination balances. A budgeting earmark labels money within an existing account; it does not move it or create another balance.

Both are included in the proposed product. Savings rates, access terms and protection have not been specified. The Tax account is a proposed way to organise money you choose to set aside, not a tax-calculation or automatic-payment service.

Yes. The design includes both types, a named cardholder, a funding account and spending controls. Physical cards also have delivery, activation and replacement journeys. Pricing, delivery terms and provider availability are still to be confirmed.

Not yet. Final fees, payment limits, account terms and card charges have not been published. Illustrative figures are not a price list or a service offer.

No. A proposed match relates records to one another. Documentary evidence may explain a difference. The payment record must separately confirm what happened to the money.

The design keeps the question open, shows the records available and identifies what is missing. A similar amount or a plausible story should not be treated as proof.

The intended role is to explain, ask, prepare or recommend. It does not override a person’s authority, payment permissions or system controls. The proposed journey separates preparation, approval and completion.

No. A regulated provider retains its own responsibilities and decisions. Relevant context may help explain activity, but Tervra does not promise to prevent a review or restriction.

No live programme approval is claimed. Provider arrangements are being developed. Read the development-status page for the current service boundaries.

Discovery about your business account needs and current workflows. It is not a reserved place, an eligibility decision or a promise of future access. Any later invitation would explain its own scope.

No. Start with a description or anonymised example. The forms ask for a description and have no document-upload facility. Keep confidential records out of your response.

The product pages explain what we’re building. The worked payment example shows how an invoice, a receipt and supporting evidence can help clarify a difference.

Your details are sent to Tervra to handle your enquiry or discovery introduction. A confirmation is shown only after the service acknowledges receipt. This does not create an account or a marketing subscription.

The website code writes no cookies, form drafts or preferences to browser storage. Unsent answers stay in the open page. No optional analytics or advertising scripts are loaded. Read Cookies & storage for details.

Use the contact page for accessibility enquiries and the partnership page for infrastructure or commercial discussions. For an urgent issue with a live account or payment, contact that service’s provider.