Turn an overdue balance into an approved installment schedule without confusing promised cash with received cash. Keep each receipt, shortfall and schedule change tied to the decision finance actually authorized.
A business customer asks to pay an overdue invoice in three installments. The account owner wants to keep the relationship, the collector needs dates, and the controller needs to know whether anyone has approved the concession. A note saying “payment plan agreed” does not answer those questions.
A B2B customer payment plan approval workflow should produce three connected records: the approved balance and schedule, the customer’s confirmed arrangement, and the receipts applied against it. This guide sets out a recommended internal-control design for undisputed commercial invoices. Your authority policy determines approvals; your contract and applicable law determine the effect of changed terms. Consumer credit, insolvency and formal debt enforcement are outside this workflow.
Decide whether installments solve the actual problem
Begin with the reason the invoice remains unpaid. A missing purchase order, an invoice dispute and a temporary cash constraint need different actions. If the customer says it already paid, investigate the receipt before negotiating a schedule for the same amount.
- Administrative blocker: correct delivery, portal or supporting-document problems, then confirm the payment expectation.
- Disputed balance: assign a dispute owner and establish the amount being reviewed. Do not represent an unresolved amount as mutually agreed.
- Request for more time: assess a specific installment proposal against the customer’s history, the exposure and your approval policy.
- Unclear authority or material risk: route to the designated credit, legal or finance reviewer before communicating acceptance.
The broader dunning process handles ordinary reminders and escalation. The payment-plan workflow begins when a proposed series of payments needs its own approval and monitoring record.
Build one approval packet with a reconciled balance
The AR owner prepares the packet; the authorized finance reviewer decides. Sales can provide customer context without becoming the default credit authority. Define a substitute reviewer in advance rather than letting an urgent request bypass the authority policy.
Identify what the plan covers
Record the customer legal entity, account, currency, invoice IDs, original due dates, current unpaid amounts, approved credits and receipts already applied. State the balance timestamp and retain links to the accounting records. Separate invoices outside the proposal so that new sales do not quietly enlarge it.
Use a simple control total: covered invoice balances after posted credits and applied receipts = total proposed installments. Investigate a mismatch before submission. An expected credit or a customer’s transfer screenshot is an unresolved item until the relevant owner verifies it.
Make the requested concession explicit
List each installment amount, full due date, currency and intended invoice allocation. Include the customer’s proposed payment route, the reason for the request, the reviewer, and any conditions on new work. Record whether charges or other contractual terms would change, and send consequential changes for the appropriate review.
Business Queensland’s credit-assessment guidance recommends financial review and a written response specifying credit terms. It is Australian business guidance, not a universal rule for your arrangement. Here, the practical control is to make the proposed terms reviewable before anyone treats them as accepted.
Use an approval-and-evidence matrix
Adapt these suggested roles and states to your policy. Keep the plan’s operational state separate from the receivable’s accounting status: approval of more time is not evidence of payment.
| Stage and trigger | Owner | Required evidence | Permitted next state |
|---|---|---|---|
| Request received | AR owner | Customer request, covered invoices, dated balance and reason | Draft; incomplete requests stay in preparation |
| Proposal ready | Finance reviewer under delegated authority | Installment total matches balance; risk, terms and new-work conditions reviewed | Approved for communication, rejected, or returned for evidence |
| Customer confirmation received | AR owner | Confirmed schedule and terms, named customer representative, matching approved version | Active once applicable approval and acceptance conditions are met |
| Installment due | Cash-application owner | Verified receipt, allocation reference and remaining invoice balance | Installment satisfied, partially satisfied, or exception open |
| Amount, date or condition changes | Authorized reviewer | Change request, receipts to date, remaining balance and revised schedule | Revision pending; no silent replacement of the active version |
| Final payment appears complete | AR owner and designated reviewer | Applied receipts and approved adjustments reconcile; no unresolved reversal or variance | Reconciled and closed, or returned for investigation |
Give each plan a reference and version, for example PLAN-042 version 1. Retain the approved version and customer confirmation together. If a customer replies with different dates, record a counterproposal rather than marking the approved proposal accepted.
Monitor installments without rewriting the receivable
Maintain an installment register linked to the accounting system. Useful fields are plan reference/version, installment ID, due date, expected amount, received amount, applied amount, receipt reference, open difference, owner and next review date. A pending transfer can be noted without counting it as applied cash.
System behavior varies. IFS’s B2B installment-plan documentation distinguishes due, overdue, partially paid and paid installments. Stripe’s partial-payment documentation distinguishes a partial receipt from a fully paid invoice. These are examples from those systems, not claims about Workhint or instructions to change your ledger.
Ask the accounting-system owner how approved term changes should be represented and how aging will behave. Do not create fresh sales invoices merely to make a collection schedule visible, or assume that a new schedule removes an impairment concern. The controller should determine any accounting consequences under the applicable policy.
Worked example: the second installment is short
Illustrative example, not a customer result: a service business has a verified USD 12,000 unpaid balance. Finance approves version 1 with USD 3,000 due December 1, USD 4,000 due December 15 and USD 5,000 due December 29. No fees or credits are assumed.
- The USD 3,000 first receipt is verified and applied. The remaining balance is USD 9,000.
- The second receipt is USD 3,500, verified and applied on December 15. Total applied cash is USD 6,500; the remaining balance is USD 5,500.
- The second installment has a USD 500 shortfall. The final scheduled USD 5,000 does not cover the whole remaining balance. Record the shortfall separately rather than labelling the second installment complete.
- The customer asks to pay the USD 500 on January 5. AR submits version 2 for review, showing USD 5,000 on December 29 and USD 500 on January 5. That proposal totals the remaining USD 5,500 but is not active merely because its arithmetic works.
Preserve the original missed expectation, the proposed change, the finance decision and the customer’s confirmation. If the revision is approved and confirmed under your process, make version 2 active while retaining version 1 as history. If declined, keep the exception open and take the authorized next action; do not invent a grace period.
Route exceptions and reapprove material changes
For a missing receipt, first check timing, bank evidence, the payment reference and unapplied cash. Assign a next review date and one customer-contact owner. Coordinate reminder settings so the customer does not receive conflicting demands from a standard sequence and a collector administering the plan.
- Short or unallocated payment: retain the expected amount, investigate the difference, and document the approved allocation or resolution.
- Returned or reversed payment: have the cash/accounting owner verify the reversal and update the outstanding amount through the normal record system. Reopen the affected installment for review.
- Changed amount, date, invoice scope or concession: recalculate the remaining schedule, obtain the required review, and retain a fresh confirmed version.
- New order requested: assess it separately. A payment plan does not itself authorize a customer credit hold release.
Set the escalation owner and review timing in company policy. Do not assume a missed installment automatically accelerates the debt, adds penalties or permits service termination. The permitted action depends on the actual arrangement and applicable requirements.
Where Workhint fits
Workhint’s Workflow Engine supports defining request steps, routing approvals to roles, and requiring details, files or notes before progress. Those are relevant building blocks for collecting a payment-plan packet and routing a proposed amendment to finance.
The workflow automation software solution describes structured forms, review stages, owners and next actions. Use those capabilities to design the coordination layer around your approved process. Confirm the exact configuration and system handoffs before relying on it; these pages do not establish native installment collection, automatic bank matching, ledger posting or legal validation of an arrangement.
Close the plan only after the records agree
Compare the covered balance, applied receipts and approved adjustments with the accounting record. Reconcile every installment and explain any residual amount. A customer’s final payment message is not the completion criterion.
Retain the invoice list, approved versions, confirmations, receipt/allocation evidence, exception decisions and closing review under your retention policy. Record whether ordinary follow-up resumes and whether a separate credit decision remains outstanding. Closing the collection plan should not silently lift a hold or approve future credit.
FAQ
Who should approve a B2B payment plan?
The person authorized by the company’s credit or finance authority policy. AR prepares the evidence; the account team supplies context. The required reviewer can vary with exposure, duration and the concession requested.
Does a payment-plan approval mark an invoice paid?
No. Track the approved arrangement separately from verified receipts and the accounting status. The accounting-system owner must determine how the arrangement is represented in that system.
What happens when a customer asks to move one date?
Record the proposed date, the unpaid balance and the reason. Route the change through the required approval and confirmation process, retaining the previous version and the original expectation.

Leave a Reply