Payment-link collection status
Track link delivery, customer action and verified payment separately. Use a collection-status worksheet to keep staff follow-up accurate.
No signup. Enter reference codes, add records and download a CSV. Entries stay in the browser tab. Filled fields do not establish completion, approval or compliance.
| Invoice reference | Link sent date | Delivery evidence | Provider payment status | Remaining approved balance | Next staff action |
|---|---|---|---|---|---|
| Invoice-example-5 | Example Monday | Sent only | No verified capture | Confirm from invoice | Review before reminder |
- Starting values are fictional examples, not customer records.
- Keep confidential evidence in your approved business systems. Record only a reference here.
- Complete each row from observed evidence. A completed worksheet does not certify legal compliance or provider compatibility.
- Export your CSV to approved storage before leaving this page.

Sending a payment link finishes a staff task, not the customer's payment. Keep the invoice open until the provider's actual record supports the right status. Sounds obvious, right? But shared inboxes and rushed shift changes often turn “link sent” into “payment handled,” and leave the next employee unsure whether to remind, collect, or release the work.
Use with this guide
online payment tools
Continue with online payment tools.
business dashboard
Continue with business dashboard.
Auto repair duplicate payments: payment links and counter charges
Prevent duplicate repair payments when a customer uses a payment link before pickup. Use the reconciliation register to compare captures, holds and refunds.
Define the collection stages
Track each stage separately: link prepared, sent, delivered if known, opened if measured, attempted, and successfully paid. Your setup may not catch every step. Leave those events unknown. Don’t assume. “Sent” doesn’t prove the customer received or read the message. And a page view doesn’t mean you captured payment.
Stripe separates payment-link views, sales, and payment records in its documentation. That’s a reason to define each metric separately, not proof that BlueFinch offers the same analytics. Check which observations your account actually shows and how current they are. Don’t build a collection process around a metric the provider doesn’t supply.
Sources for this section: Stripe: payment-link confirmations, receipts and payment records · BlueFinch: online payments
Match every action to the invoice
Use the approved invoice reference and current balance as the organizing record. The customer may have paid another authorized way after getting the link. Before sending a reminder, check the relevant payment history and any approved adjustments. The online payment tools provide a destination, not permission to ignore other collections.
Here’s a simple example. A repair shop emails a payment link in the morning, and the customer pays at the counter at noon. If an afternoon reminder checks only the sent-link list, it wrongly says the bill is unpaid. A reconciliation check catches the payment, avoiding an unnecessary reminder and reducing the chance of collecting twice.
Sources for this section: BlueFinch: online payments
Write reminders from verified facts
Use a calm tone, state the remaining approved balance clearly, and give them a way to ask questions. Don’t accuse the customer of ignoring a link if you don’t know it arrived. And don’t add urgency or a late charge unless the agreement and applicable requirements back it up. Keep the message honest about the account’s actual status.
Keep transactional collection communications separate from promotional content. The FTC says an email’s main purpose affects which commercial-email rules apply. Add a loyalty offer to an invoice reminder, and you can change the message’s character. Use the approved process. An existing customer email isn’t automatic permission to send unrestricted marketing.
Sources for this section: FTC: commercial email requirements
Give staff one current status
The worksheet tracks the invoice, send date, delivery evidence, payment status, balance, and next step. Keep personal contacts and payment credentials in the approved system. Give uncertain cases one owner. Employees should be able to see why a reminder is paused without digging through private email threads.
The business dashboard is a useful place to start when reviewing outstanding work. But the original invoice and provider records are still the evidence. Missing or delayed data doesn’t automatically mean a customer hasn’t paid. If a connection is stale, check the appropriate source before taking action with a customer.
Include the time of the last balance check in your internal reminder process. Yesterday’s reminder could be wrong after an overnight payment or approved adjustment. Recheck the balance immediately before the customer-facing action, especially when several employees handle collections. That verification protects the relationship and is usually easier than explaining an incorrect demand afterward.
At the weekly review, compare sample reminders with actual invoice balances. Look for repeat mismatches from alternate payments, stale links, or staff handoffs. Fix the process before adding more automatic reminders. A reliable collection workflow tracks the money and the approved obligation, not how many messages the office sent on a busy day.
Primary sources
BlueFinch last reviewed these sources on October 23, 2026. Check the linked sources for current requirements and product details.
- Stripe: payment-link confirmations, receipts and payment records
- FTC: commercial email requirements
- BlueFinch: online payments
Use this page for general business information. It is not legal, tax, or accounting advice.