# Bank and manual payments, verified before Paid

For payments outside the online gateway, a customer reports the payment on the invoice's secure page. Staff can also log one reported by phone, email or WhatsApp. A reported payment counts nowhere until a signed-in person verifies it against an authoritative record, such as the bank statement. Large payments then need a second person's approval. Only then is the invoice Paid.

- **Status:** Available
- **Audience:** both
- **In the app:** /apps/crm (Billing › Payments to Verify)
- **Last verified:** 2026-11-02
- **Canonical:** https://connectbyjbrh.com/docs/product/bank-payments/

## Payment instructions

A business saves its bank, IFSC and UPI instructions as a draft. Only a person with approval rights makes them the version customers see. Later edits stay drafts until approved, so a customer is never shown half-finished account details.

## Reporting a payment

Each final invoice has a secure, phone-friendly page with no script. It shows the approved instructions, the balance and the state of anything the customer already reported. The customer gives the amount, the method (bank transfer, NEFT, RTGS, IMPS, UPI or cheque), the purpose, a reference, the date and an optional proof (PNG, JPEG or PDF up to 900 KB).

> **Note** A reported payment is **Awaiting verification**. It does not reduce the balance, change the payment status or count as income.

## Verification, approval and Paid

1. Verify: a signed-in person with approval rights enters the authoritative record's kind (bank statement, the bank's credit alert, a settlement report or a cleared cheque), its reference, the amount and date it shows, and confirms.
   - Result: A screenshot or a customer's word cannot fill these fields. An API key or the assistant cannot verify. A bank reference already used is refused.
2. At or above the business's threshold, a second person approves. It can never be the verifier.
   - Result: Below the threshold, verification alone makes the payment Paid.
3. Connect checks acceptance before Paid.
   - Result: If the invoice comes from an agreement or quote, that must read accepted. Otherwise nothing moves and the screen says why.

Paid writes one payment row, counted up to the balance. Any excess is held as an overpayment and never counted. Dispute, reopen, reject (with a reason the customer sees) and withdraw are all audited, and each invoice reconciles: paid, awaiting, disputed, held over and the balance.

## What is unchanged, and what is not yet verified

- Online gateway payments (signed webhooks, refunds and dispute reversal) and staff's Record Payment work as before.
- Reminders use the existing Send to Customer, held without consent or an approved template.
- No live payment configuration was touched, and Connect sets no price anywhere.
- A real bank payment verified in production is the owner's own check after release.

## Questions

### Why did a verified payment not become Paid?

Either it is at or above the threshold and waits for a second person's approval, or its agreement or quote has not been accepted. The screen names which.

### Can a business with one person approve large payments?

No. The approver can never be the verifier. Set no threshold, or add an approver.

## Related

- [Agreements and formal acceptance](https://connectbyjbrh.com/docs/product/agreements-and-acceptance/)
- [Quotes and sales documents](https://connectbyjbrh.com/docs/sales/quotes-and-documents/)
- [Offerings, plans and trials](https://connectbyjbrh.com/docs/product/offerings-and-trials/)
- [Cashfree Payments](https://connectbyjbrh.com/docs/technology/cashfree/)

## What this page is based on

- `backend/app/manual_payments.py`, `manual_payments_api.py`, `manual_payment_models.py`
- `webapp/apps/crm/screens/billing/payments.js`
- `docs/agents/tasks/s3-payments-20261102.md`
