Set credit limits before the sale
A credit limit is a decision, not a suggestion. Set it per customer, review it before large orders and stop supply when it is consistently exceeded.
- Limit based on payment history and order size.
- Warning at 80% of the limit.
- Owner approval for exceptions.
- Review limits quarterly.
What a useful statement contains
| Field | Why |
|---|---|
| Document number | Lets the customer match their records |
| Document date | Establishes ageing |
| Amount and paid amount | Shows the open balance per document |
| Total balance | Summary for approval |
| Payment terms and due date | Removes ambiguity |
| Contact and bank details | Makes payment easy |
Apply payments to documents, not totals
A lump-sum payment hides which invoices remain open. Apply each receipt to specific documents so the statement reflects reality and disputes can be traced.
- Partial payments against one document.
- Prepayments held as credit and applied later.
- Write-off approval for small residual amounts.
- Separate cash, bank transfer and cheque references.
A weekly collection routine
- Review the ageing report every Monday.
- Send statements before the due date, not after.
- Call accounts that are 7 days late, not 30.
- Record every promise-to-pay date.
- Escalate consistently: call, email, owner call, stop supply.
Frequently asked questions
How often should statements be sent?
Monthly at minimum. For fast-moving credit accounts, weekly statements reduce disputes and speed collection.
Should we show every historical document?
Show open documents plus recent paid ones for context. A statement with years of history is harder to check.
What if a customer disputes a line?
Trace the original document and delivery signature. Resolve the specific line and issue a credit note if justified rather than adjusting a total.
Can 小企业简单进销存软件 generate statements?
Yes. Statements can be generated by customer and date range, exported or printed, and show document-level balances.