Skip to content

How Should a Small Business Ask Customers to Pay?

Send every payment request from the same trusted system, with the right amount, what it’s for, the due date, and how to pay. Tell customers you’ll never change your bank details by email alone. When money arrives, confirm it cleared, send a receipt, and record it against the right invoice.

A payment request is anything that asks a customer for money: an invoice, a payment link, a deposit request, or a text with a link. Payment confirmation is the step where you check the money actually arrived and tell the customer.

Say Clearview Window Cleaning sends every invoice from its invoicing software, never from a personal email. Each one shows the job date, the services, the amount, the due date, and a payment link. When the payment clears, the software sends a receipt, and the owner marks the invoice paid.

  • Errors cost trust. A wrong amount or a request for a job that was already paid makes customers doubt everything else.
  • Fraud. Criminals send fake invoices or emails pretending to be a business and ask customers to pay a new account. The Federal Bureau of Investigation (FBI) says to verify any change to payment details directly with the person, through a separate channel.
  • Disputes. Without a confirmation record, it’s your word against the customer’s (see 10.7.7 Chargebacks).
  • Messy books. Payments that aren’t matched to invoices make bank reconciliation hard (see 10.5.3 Bank Reconciliation).

Every business that bills customers. It matters most for businesses that take deposits, send invoices by email or text, or accept bank transfers.

  1. Choose one system for sending payment requests, such as your invoicing or payment software (see 10.7.1 Payment Methods).
  2. Use a standard format: business name, invoice number, job date, what it’s for, amount, taxes or fees, due date, and how to pay (see 10.7.5 Invoices).
  3. Send requests from your business email or system, never from a personal account.
  4. Put a short notice on invoices and in your welcome message: “We will never change our payment details by email. Call us at our listed number to confirm.” This gives customers a way to spot fake requests.
  5. Don’t ask customers to email or text full card numbers. Use a secure payment link or payment terminal (see 10.7.6 Payment Security).
  6. When a payment arrives, confirm it cleared in your payment system or bank, not just that the customer said they sent it.
  7. Send a receipt with the amount, date, method, and what it paid for.
  8. Mark the invoice paid and record any deposit against the right job (see 10.7.2 Deposits).
  9. If you ever change your own payment details, tell customers by phone or in person too, not only by email.
  • A copy of each payment request
  • The payment record from your processor or bank
  • The receipt sent to the customer
  • Your bookkeeping entry matching payment to invoice

Keep these in your accounting system and job file (see 10.5.5 Invoice Records).

  • Payment requests from many places. Some from software, some by text, some from a personal email. Customers can’t tell what’s real.
  • Marking jobs paid on a promise. “I sent it” isn’t confirmation. Check that it cleared.
  • Collecting card numbers by email or text. It puts customer data at risk.
  • No warning about payment-detail changes. Customers have no way to spot a fake invoice using your name.
  • No receipt. It leads to “I already paid that” disputes later.

A bookkeeper or certified public accountant (CPA) can help set up invoicing and match payments to your books. Your payment processor can explain fraud tools. Questions to ask:

  • Can my invoicing and payment system send receipts automatically?
  • How do I match deposits and partial payments to the right job?
  • What fraud protection does my processor offer?

[Bill: add a short note. For example, a fake invoice scam you’ve seen aimed at a small business’s customers, or how you keep billing simple for SiteSmarty clients.]

  • [Date I did this:]
  • [What I actually did, step by step: the system SiteSmarty uses for payment requests, the standard format, and how payments get confirmed]
  • [What it cost and how long it took:]
  • [What surprised me or what I’d do differently:]
  • [Screenshot or photo to add, with private info blurred: a payment request and matching receipt]
  • [Result so far:]

What should a payment request include? Your business name, invoice number, job date, what it’s for, the amount, taxes or fees, due date, and how to pay.

How do I protect customers from fake invoices? Send all requests from one system, and tell customers you’ll never change payment details by email alone.

How do I confirm a payment? Check that it cleared in your payment system or bank, then send a receipt and mark the invoice paid.

Do I need to send a receipt every time? It’s a good habit. A receipt prevents disputes and gives the customer a record.

  • Question: Are payment requests sent from one trusted system in a standard format, and is every payment confirmed, receipted, and recorded?
  • Pass looks like: One system, standard invoices, a payment-detail warning, confirmed payments, receipts, and matching entries in the books.
  • Fail looks like: Requests from personal accounts, card numbers collected by email, jobs marked paid without checking, or no receipts.
  • Evidence to collect: Sample payment requests, processor records, receipts, and bookkeeping entries for the same jobs.

Where this fits

Do this first: 10.7.1 Payment Methods, 11.1.6 Payment Terms

Do this next: 16.6.4 Failed Payments

Related pages: 10.7.2 Deposits, 10.7.5 Invoices, 10.7.6 Payment Security, 11.9.5 Payment Fraud, 10.5.3 Bank Reconciliation, 22.6 Payments and Bookkeeping Procedure

Sources

This page explains general rules and Bill's own experience. It is not legal, tax, or insurance advice. Talk to a qualified professional about your situation.

Get free updates

I'll send you a short email when new guide pages and videos go up.

No sales pitches. Unsubscribe any time.