How to Get Paid by Customers Who Still Pay by Bank Transfer
A practical finance guide to receiving customer bank transfers, choosing local rails, matching receipts, resolving exceptions and moving surplus fiat into stablecoin treasury.
To get paid by customers who use bank transfers, provide receiving details for the currency and local rail they already use, place a unique reference on every invoice and reconcile only after funds reach your account. Route missing references, short payments and unexpected currencies into an exception queue. If your treasury uses USDC or USDT, convert only the fiat not needed for near-term operating obligations.
To receive customer bank transfers reliably, give each customer the correct bank details for the invoice currency, require a unique payment reference and match the credited funds to the invoice before closing it. Local rails usually create fewer delays and deductions than international transfers. After reconciliation, keep enough fiat for payroll, tax and suppliers, then consider converting genuine surplus cash into USDC or USDT.
Build the collection process around the customer’s payment rail
Customers are more likely to pay correctly when the invoice uses a familiar domestic or regional rail. A euro customer may expect an IBAN for a SEPA transfer, while a US customer may request ACH details. Asking either customer to send an international SWIFT payment can introduce intermediary banks, additional compliance checks, unexpected deductions and more complicated remittance data.
The receiving account should be held in the correct company name or provided under an arrangement that clearly identifies the legal beneficiary. Confirm that the account can receive the relevant currency and payment type. Some account details accept ACH credits but not domestic wires, for example, even though both payments are denominated in US dollars.
| Currency and rail | Typical processing pattern | Best use | Finance checks |
|---|---|---|---|
| EUR: SEPA Credit Transfer | Commonly received by the next business day | Routine euro invoices | Confirm the IBAN, beneficiary name and payment reference |
| EUR: SEPA Instant | Usually processed within seconds when both institutions participate | Urgent euro collections | Verify participation, transaction limits and availability before promising instant receipt |
| USD: ACH credit | Batch-based; timing depends on submission and processing windows | Routine domestic US collections | Provide the ACH routing number and monitor for returns or reversals |
| USD: Fedwire | Generally processed on the same business day if submitted before cut-off | Large or time-sensitive US payments | Provide wire instructions rather than ACH instructions and check the bank cut-off |
| GBP: Faster Payments | Often received within seconds or minutes | Everyday UK customer payments | Confirm the sort code and account number support the rail |
| GBP: CHAPS | Generally same-day before the sending bank’s cut-off | High-value or urgent UK payments | Check fees, cut-offs and beneficiary details |
| GBP: Bacs | Normally follows a multi-day processing cycle | Planned, non-urgent payments | Allow sufficient time before the invoice due date |
| Multiple currencies: SWIFT | Timing varies with correspondent banks and compliance reviews | Cross-border payments without a suitable local rail | Specify who pays bank charges and investigate intermediary deductions |
These are operating patterns, not guarantees. Weekends, public holidays, cut-off times, bank reviews and incorrect instructions can delay any transfer. Finance teams should confirm current capabilities and limits with their bank or payment provider before publishing details.
Put complete, controlled payment instructions on every invoice
Customers should not have to recover bank details from an old email thread. Each invoice should state the invoice currency, legal beneficiary name, appropriate account details and a unique reference. If the trading name on the invoice differs from the account’s legal name, explain the relationship so the payer does not assume the instructions are fraudulent.
Details commonly required by currency
- EUR: legal beneficiary name, IBAN, BIC where required, bank information if requested and invoice reference.
- USD: legal beneficiary name, account number, the correct ACH or wire routing number, account type where required and reference or memo.
- GBP: legal beneficiary name, sort code, account number, invoice reference and, for relevant international payments, IBAN and BIC.
Do not use the same generic instructions for every currency. If a customer sends US dollars to an account intended for euros, a bank may reject the transfer or convert it at a rate the parties did not approve. The amount credited may then differ from the amount due.
Bank-detail changes require a separate fraud control. Restrict who can edit invoice templates, approve changes through a second person and notify customers through an established contact channel. A request to redirect payment should never be trusted solely because it came from a familiar-looking email address.
Design payment references for dependable matching
A payment reference is the primary link between the bank transaction and the accounts-receivable ledger. Assign one short, unique and stable value to each invoice, such as INV-10482. Avoid relying only on the customer’s name because payment may arrive from a parent company, accounts-payable service or another entity within the customer’s group.
- Keep references within the receiving rail’s permitted length.
- Prefer letters and numbers over punctuation that banks may remove.
- Store both the expected reference and the reference actually received.
- Ask customers not to combine invoices unless they send a remittance breakdown.
- Do not recycle references, even after an invoice is closed.
Virtual account numbers or virtual IBANs can create a second matching signal when supported by the receiving provider. A unique identifier can be assigned to a customer, legal entity or collection stream, allowing finance to identify the likely payer even when the invoice reference is missing. This does not eliminate invoice-level matching when one customer has several open balances.
Separate matched receipts from payment exceptions
Not every transfer should post automatically. Create an exception queue for missing references, partial payments, overpayments, duplicate receipts, unexpected currencies and sender names that do not correspond to the customer record. Each case should retain the amount, currency, sender, value date, bank reference and candidate invoices.
Finance can then request remittance advice, compare open balances or contact the customer using a verified address. Do not mark an invoice as paid based on a screenshot or payment confirmation supplied by the customer. Wait until the funds appear in the receiving account, and consider whether the relevant rail permits returns or reversals before treating the cash as fully settled for operational purposes.
A documented variance policy prevents inconsistent treatment. A short payment may reflect an intermediary fee, a withholding tax, a foreign-exchange conversion or a commercial dispute. Define who may write off a small difference, when the residual balance remains open and when collections staff must ask the customer to settle it. Record the reason rather than silently changing the invoice amount.
Decide whether to retain fiat or convert it to stablecoins
Receiving a bank transfer and converting treasury funds are two separate decisions. Once the receipt has been matched, determine how much of that currency is required for payroll, tax, rent, debt service, refunds and supplier payments. Converting cash that will soon be needed in fiat can create avoidable conversion costs and liquidity risk.
| Decision factor | Reason to retain fiat | Reason to convert surplus |
|---|---|---|
| Near-term obligations | Invoices and operating costs are due in the same currency | Forecast cash exceeds the approved fiat reserve |
| Conversion economics | Quoted fees, spread or market conditions are unattractive | The approved quote and total conversion cost are acceptable |
| Liquidity timing | Funds must remain immediately available for bank payments | Stablecoins will be available before their intended use |
| Network and destination | The required blockchain or approved destination is unclear | The token, network and treasury destination have been independently verified |
| Approval requirements | The transaction has not reached the required signing quorum | Approvers have reviewed the amount, quote and destination |
A practical rule is to maintain an approved fiat reserve based on the cash forecast and convert only the excess. The reserve horizon should reflect the company’s payment cycle rather than an arbitrary industry benchmark. Larger conversions should follow the same segregation of duties and signing quorum used for other treasury movements.
A corporate stablecoin treasury platform such as Stablerail can support fiat conversion, USDC and USDT treasury balances, approvals, signing quorum and exportable audit evidence. Before transferring stablecoins, verify the token, blockchain, destination address and sanctions or address-screening result; the same address on the wrong network may not produce a recoverable payment.
Reconcile from invoice through final treasury balance
The audit trail should connect the customer invoice, bank receipt, any fees or foreign-exchange differences, the conversion record and the resulting stablecoin balance. Use the bank’s credited or value date consistently under the company’s accounting policy, rather than the date shown on a customer’s payment screenshot.
- Review newly credited bank transactions each business day.
- Match by reference, payer, currency and amount.
- Post valid receipts against the correct receivable.
- Move ambiguous items to the exception queue without closing the invoice.
- Record bank fees, conversion costs and foreign-exchange differences separately.
- Link each fiat debit to the corresponding stablecoin credit and blockchain transaction.
- Retain statements, remittance records, quotes, approvals and transaction evidence for period close.
The accounting treatment for gross receipts, bank deductions, foreign-exchange differences and digital assets depends on the entity and reporting framework. Finance should document its policy with its accountant or auditor rather than allowing the operational workflow to determine the accounting by default.
Finance-team implementation checklist
- Confirm the receiving account supports the required currency and rail.
- Test each set of instructions with a low-value transfer before major collections.
- Add legal beneficiary details, currency and a unique reference to invoice templates.
- Apply dual review to bank-detail changes.
- Define matching rules, exception ownership and escalation times.
- Document policies for partial payments, fees, overpayments and write-offs.
- Set the fiat reserve and approval process for USDC or USDT conversion.
- Reconcile invoices, bank balances, conversions and stablecoin balances regularly.
The strongest setup keeps payment conventional for the customer and controlled for finance. Familiar local details reduce payment friction, while unique references, exception handling and complete evidence give treasury a reliable path from accounts receivable to fiat or stablecoin balances.
Frequently asked questions
How can my company accept bank transfers from customers?
Provide receiving details that support the customer’s invoice currency and preferred payment rail, then place the legal beneficiary name and a unique reference on the invoice. Reconcile the invoice only after the transfer is credited to the receiving account.
What bank details should be included on a customer invoice?
Include the legal beneficiary name, invoice currency, account details for the relevant rail and an invoice-specific payment reference. Depending on the currency, this may mean an IBAN and BIC, an account and routing number, or a sort code and account number.
How do you match a bank transfer to an invoice?
Use a unique invoice reference as the primary matching key, then validate the payer, amount and currency. If the reference is missing or the amount differs, place the receipt in an exception queue and obtain remittance information before closing the invoice.
Should customer bank transfers be converted into USDC or USDT?
Convert only after the receipt has been reconciled and the company has retained enough fiat for forecast payroll, tax, suppliers and other obligations. Review the conversion quote, liquidity timing, token, blockchain, destination and required approvals before proceeding.
When should an invoice be marked paid after a bank transfer?
Mark it paid when funds have been credited and matched to the correct invoice, not when the customer sends a screenshot. Finance should also understand any return or reversal risk associated with the payment rail before treating the money as fully settled.
Finance writers covering stablecoin treasury, payments, compliance, and risk controls.
More about the Stablerail team- Stablecoin treasury managementApprovals, limits, yield and reporting on one balance.
- Stablecoin payoutsBatch contractor and vendor payments with screening.
- USDT vs USDCWhich stablecoin your company should settle in.
- Stablecoin finance glossaryMPC, off-ramp, travel rule and the rest, in plain English.
- Product updatesEverything we ship, month by month.

