ZAMBO.

Direct answer

A bounced check is not a payment. It is a dated event.

A returned check feels worse than no check at all, because for a few days you believed the invoice was settled. The calm way through it: the payment did not happen, the debt is exactly where it was, and the bounce itself is now a documented event with a date, a reason, and a bank notice. Here is the sequence that turns a bad check into a cleared payment without burning the relationship or your leverage.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated October 24, 2026. The two delivery records quoted below are real and public, with their client decision states read back from the live service on publication day.

Step 1. Confirm the facts from the bank notice before contacting the client

Read the return notice first: the date the check was returned, the stated reason, and any fee your bank charged you. Returned usually means insufficient funds, but it can also mean a closed account or a stopped payment, and those are different situations that deserve different tones. Save the notice itself. Until you have it, you know only that money left your account again; after it, you hold the one document in the whole story that neither side wrote, which is exactly why it anchors every message that follows.

Step 2. Put the invoice back to unpaid on the record, with the sequence dated

An attempted payment is not a payment, and your records should say so in order: invoice issued on this date, check received on this date, check returned on this date, balance unpaid from the return date. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show how delivery states stay readable the same way:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

An accepted record, 4 of 4 steps checked, decided_by client, release_hint ok_to_release, is the delivery the bounced check was paying for: finished, checked, and accepted, which matters because a returned check reopens the money question only, never the work question. A pending record, 5 of 5 checked and release_hint hold, shows the honest alternative state. Keep your payment sequence in that same spirit: four dated lines anyone could follow, with the balance restated as open from the return date, so no later conversation starts from the false premise that you were paid.

Step 3. Tell the client once, plainly, with the notice attached

One short message, no accusation in it: the check dated this day was returned unpaid for this reason, the invoice balance is open again at this amount plus the bank fee of this amount, and here is how to replace the payment. Attach the bank notice. Most bounced checks are cash flow embarrassment, not fraud, and a factual message lets an embarrassed client fix it fast without a story. A stopped payment or a closed account is different: the same plain message still goes first, but you hold everything undelivered from that moment and treat any reply against the record, not against promises.

Step 4. Take the replacement in a form that clears before you release anything

The replacement payment should not be a second personal check into the same uncertainty. Ask for a bank transfer, a cashier's check, or another method that confirms as final, and name a date inside the same week. Anything not yet delivered stays undelivered until the replacement clears, stated as a simple sequence rather than a punishment: cleared payment, then release. If work is mid stage, pause it under the same rule and say the stage resumes the day the balance clears. Clients who meant to pay accept this instantly, because it costs an honest client nothing.

Step 5. Add the costs the bounce created, itemized and small

Your bank's return fee, and any fee your agreement or local rules allow for a returned payment, goes on the restated balance as its own named line, with the notice as its evidence. Keep it exact and modest. The point is not to profit from the bounce; it is to make the sequence whole, so accepting a check next time does not quietly make you the insurer of the client's account. If the client replaces the payment promptly and covers the fee without argument, that is the relationship telling you the bounce was an accident. File it and move on.

Step 6. Change the payment terms this bounce just rewrote

Whatever happens next, this client has new terms, set now while the lesson is fresh: deposits and stage payments by methods that clear before work starts or files move, checks only from clients with a clean record, and final delivery after final clearance rather than after final promise. State the new terms in one friendly line in the closing message of this episode, not as a grudge but as your standard setup from here. A second bounce from the same client is not bad luck; it is a pattern you were shown once and chose to underwrite.

What a record does not settle

A verifiable receipt proves the saved result was not changed since it was saved; it does not prove why a check bounced, does not collect the balance, and does not decide what fees or remedies your agreement or local law allows. The bank notice, the dated sequence, and the delivery record are what you would show anyone asked to judge the debt. This page is general information, not legal or financial advice.

Frequently asked questions

My client paid me with a check that bounced. What do I do?

Treat the payment as never made and run a dated sequence. First read the bank return notice for the date, the reason, and your bank's fee, and save it. Restate the invoice as unpaid from the return date, with the sequence written in order: invoiced, check received, check returned, balance open. Send the client one plain message with the notice attached, the restated balance including the return fee as its own line, and a request for a replacement payment by a method that clears, dated inside the same week. Hold anything undelivered until the replacement clears. Most bounces are cash flow accidents that a factual message fixes quickly; a stopped payment or closed account means hold everything and judge replies against the record.

Is a bounced check the same as the client refusing to pay?

Not yet, and treating it as a refusal too early can turn an accident into a fight. Insufficient funds on a given day is a timing failure; the client's response to your message is what tells you which situation you are in. A prompt apology, a clearing replacement payment, and the fee covered means accident. Silence, a second bad check, or a stopped payment with no honest explanation means the payment method was the message. Judge the response, keep the sequence dated either way, and let the record, not the first shock, decide your next step.

Can I charge the client for the fees a bounced check cost me?

Generally you can pass through the fee your bank charged you, shown as its own itemized line with the bank notice as evidence, and many agreements and local rules allow a set returned payment charge on top. Keep whatever you add exact, documented, and modest, and check your agreement's wording before adding anything beyond the bank fee itself. The goal is to be made whole for a cost the client's payment created, not to turn the bounce into a profit line. This page is general information, not legal or financial advice.

Should I keep working or deliver files while the replacement payment is pending?

Hold the line the sequence gives you: undelivered work stays undelivered until the replacement clears, and a mid flight stage pauses and resumes the day the balance clears. State it as a neutral order of events, not a threat: cleared payment, then release. You already delivered once against a payment that reversed; delivering more against a second promise doubles the exposure for no benefit. If the client needs something urgently, the fastest route runs through their bank, not through your files.

How do I keep attempted and cleared payments separate on the record?

Log payments the way delivery is logged: each event dated, in order, with its state named, attempted, returned, cleared, never a single paid stamp that a reversal quietly falsifies. When the underlying work runs through Zambo, the delivery side already works that way: every step saved with a verifiable receipt under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, and the client acceptance recorded with its date and decider. New users get 20 free calls per day, then they upgrade when the job needs more. For $0.99, run the next job on records that cannot be rewritten by a bad week at the bank: get the Day Pass. A Day Pass covers 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 for 30 days (one payment) or $290 for 365 days, and $19 for 30 days for $ZAMBO holders, which adds private handover links, your branding, and the approval record as PDF and JSON files.

Related