A Customer Asked To Pay in Installments. Should You Say Yes?

The email lands in your inbox: "Cash flow is tight this quarter. Can we split the overdue balance into three installments?"

Your gut produces two reactions at once. Relief, because a customer proposing a plan is a customer intending to pay, and irritation, because the money was due six weeks ago and now you are being asked to finance it further. Both reactions are correct, which is exactly why this decision deserves a framework rather than a mood.

I have approved and refused hundreds of these requests across twelve years in finance. Here is how I actually decide, and the exact words for each answer.

First, understand what the request is telling you

An installment request is information before it is a negotiation. It tells you three things: the customer has a cash constraint, the customer is engaged rather than hiding, and the customer values the relationship enough to propose structure instead of going silent. Silent debtors are your dangerous ones. Talking debtors are workable.

But it also tells you to check something immediately: is this a one-off squeeze or a pattern forming? A first-ever request from a customer with a clean history is a completely different animal from a third request in a year, and your accounting system knows which one you are holding.

The three-question decision

1. What does their history say? This is the strongest predictor and the one founders most often decide on vibes instead of data. Pull the record: have they done a plan before, and did they keep it? A customer who has honored two prior schedules is a low-risk yes; kept promises predict kept promises. A customer who broke their last plan is asking you to finance a repeat experiment. (Tracking kept-versus-broken promises per customer is the single most useful piece of AR intelligence you can keep.)

2. What is the relationship worth? A $41,000 balance from a customer who has paid you $186,000 over two years and will likely pay you more deserves flexibility; you are protecting a stream, not just collecting a puddle. The same balance from a one-project customer with no future value should be structured much more tightly, because your only asset in that relationship is leverage, and long timelines burn it.

3. Is the constraint credible and temporary? Seasonal squeeze, a large receivable of their own landing next month, a known industry cycle: credible. Vague "things are tight" with no timeline, or a request arriving alongside other signals (staff departures, slow replies, shrinking orders): that is not a payment plan situation, that is early-warning insolvency, and shorter, front-loaded terms protect you if the ship goes down.

Structuring the plan (where the money is actually won or lost)

Say yes carefully. The structure rules I never bend:

Shorter than they asked. They propose six weeks; you counter with four. Not as machismo, but because plan length is risk exposure, and the customer's opening ask always contains padding. Almost everyone accepts the counter.

Front-loaded. First installment largest and due within ten business days. A customer who can pay nothing now cannot pay a plan either; the first payment is your test of good faith, scheduled while intent is highest.

In writing, with exact dates and amounts. Not "monthly," but "$15,000 by June 11, $15,000 by July 11, $11,200 by August 11." Ambiguity is where plans dissolve.

With a consequence clause. One line: "If an installment is missed, the full remaining balance becomes due immediately." You may never enforce it, but it converts the plan from a favor into an agreement.

Watched like three separate promises. Each installment date gets a next-morning follow-up if missed. A plan is only as strong as its enforcement, and most plans fail not at signing but at the second installment nobody chased. (This is, honestly, why we built promise-tracking into RevCollect: it treats every installment as a tracked commitment and drafts the follow-up the morning one slips, with the customer's full plan history attached for the next decision.)

The exact words

Saying yes:

"Hi Tom, thanks for being upfront about the timing. Given our history, happy to structure this. Here is what works on our side for the $41,200: $15,000 by June 11, $15,000 by July 11, $11,200 by August 11. If any installment is missed, the remaining balance falls due immediately. Reply to confirm and I will send it in writing today."

Counter-offering:

"Hi Mike, we can accommodate a schedule, though six weeks is longer than we can carry. Here is what I can do: $12,000 within ten days, $12,000 at week three, $10,500 at week five. Does that work for your cash cycle?"

Saying no (rare, but sometimes right):

"Hi Sam, I appreciate you raising it directly. Given where the account stands, including the plan from January that was not completed, I cannot extend further structure. I need payment in full by the 28th. If that is genuinely impossible, call me today and we will find the least bad option together, but it needs to be this week."

Even the no keeps a door open. Doors are cheap; silence is expensive. If the no is refused and the account goes quiet, you are into final-notice territory, and the fact that you offered structure first will matter, both to your conscience and, occasionally, to a court.

The summary I would put on a sticky note: an installment request from a talking customer with a clean history is good news wearing inconvenient clothes. Say yes to the structure, on your terms, in writing, front-loaded, and watched. Say no to open-ended patience, which is not a plan at all.

FAQ

Should I charge interest on a payment plan? For plans under 90 days, most SMBs skip interest and instead shorten the timeline; simplicity gets signed. Past 90 days, or for repeat requesters, adding your contractual late-fee rate is reasonable and clarifying.

What if the customer misses the first installment? Treat it as the test it was: full balance becomes due per your clause, follow up the next morning, and move to final-notice footing. A missed first installment predicts a failed plan with depressing reliability.

Should the payment plan be a formal contract? An email with exact amounts, dates, and the acceleration clause, confirmed by the customer in writing, is sufficient for most SMB situations and vastly better than nothing. For five-figure-plus balances, a signed one-page agreement is worth the extra day.

Does offering a plan make me look weak? Structured flexibility on your terms reads as professional, not weak. What reads as weak is unenforced deadlines, unwatched promises, and silence.