A new order is waiting on credit. Sales says the customer paid yesterday. AR sees an overdue invoice. The warehouse wants to know whether to ship. Down the hall, someone else is about to refund a $5,000 credit memo to a different customer without noticing that $3,200 of it already paid an invoice last month.
Credit management covers both directions of the same question: how much does this customer owe us, or how much do we owe them, right now? This guide covers how to define exposure, how to make hold decisions quickly without losing control, and how to verify a credit balance before money goes back out.
Define what counts toward the limit
A credit limit is only as good as the exposure figure it is compared with. Write down how your policy treats each component:
| Component | Usual treatment | Decision to document |
|---|---|---|
| Open invoices | Count in full | Whether disputed amounts count |
| Orders not yet billed | Count once approved | At what stage (booked, released, shipped) |
| The new order under review | Count | Whether two orders arriving together are checked together |
| Credits and credit memos | Reduce exposure | Only once applied, or when available |
| Unapplied cash | Varies | Whether it reduces exposure before AR confirms the invoices |
| Payment in transit | Usually does not count | Remittance advice is not cleared funds |
Make clear whether a limit belongs to one billing account or a group under a parent. Two subsidiaries can each appear to have room while their combined exposure exceeds the group limit.
Worked example (illustrative)
A customer has a $250,000 limit. Open invoices are $180,000, approved unbilled orders $45,000, and the new order is $30,000. There is $20,000 of cash received but not yet applied.
- Without unapplied cash: $180,000 + $45,000 + $30,000 = $255,000. Over the limit by $5,000.
- With unapplied cash counted: $255,000 − $20,000 = $235,000. Within the limit by $15,000.
The order’s fate depends entirely on a policy choice about unapplied cash, and on how quickly AR can confirm which invoices the $20,000 covers. That is why the unapplied cash queue is a credit problem as well as an AR one.
Set and review limits on a schedule
A limit set at onboarding and never revisited stops meaning anything. Tie each limit to the evidence it was based on (expected order volume, payment terms, payment history, any financial information the customer provided) and record who approved it and when.
Then decide what triggers a review:
- Calendar. Larger accounts annually, smaller ones less often.
- Behaviour. Payments slipping past terms for two or three cycles in a row, or a rise in disputes.
- Volume. Orders regularly pushing against the limit. If the customer pays on time, the limit may simply be too low for the business you are doing with them.
- Structure. A change of ownership, a new parent, or a new billing entity.
Record each review even when the limit does not change. An auditor or a new credit manager should be able to see why a customer has the limit it has.
Use the controls your ERP already has
Before building a separate hold queue, check what the accounting system does natively. NetSuite, for example, can restrict new credit sales when a customer exceeds its limit or is delinquent, and its manual hold requires a release. Oracle’s NetSuite credit limits and holds documentation. Verify which records and settings govern the specific order your team is looking at; customer-level and transaction-level settings can interact in ways that surprise people.
Give the reviewer everything on one screen
For every hold, show the new order, current exposure, approved limit, overdue invoices, open disputes, and when the balances were last refreshed, with links to the underlying records. An over-limit flag on its own sends the reviewer back to the ledger to rebuild the picture.
| Situation | What to check | Next action |
|---|---|---|
| Sales says the customer paid | Bank activity, remittance, cash application status | AR confirms what cleared and which balance it reduces |
| The overdue invoice is disputed | Disputed amount, reason, person resolving it | Credit applies the dispute policy and records the decision |
| Two orders arrive together | Combined exposure with both orders | Recheck before fulfilment so both cannot use the same headroom |
| Sales requests a one-time release | Order amount, reason, authority, expiry | Credit records the exception on that order only |
| The balance feed is stale | Last successful sync and source | Send for manual review before trusting the figure |
A one-time release needs its own record with the approver, reason, and time. Otherwise the next person treats it as a permanent limit increase.
Test credit recommendations on past holds
Before letting software recommend releases, replay past orders using only the data available when each one arrived. Include a normal release, a payment in transit, a disputed invoice, and a customer with several billing accounts. A later payment can make a historical hold look wrong when the reviewer made the right call at the time.
For each disagreement between the proposed action and the actual decision, find out whether the balance was stale, the rule was wrong, or the policy left room for judgment. Track how long orders wait and whether overrides can be reconstructed. Look at bad debt and DSO alongside aging mix and terms changes; those totals alone will not tell you whether faster hold routing helped.
Where customer credit balances come from
The other half of credit management is money you owe the customer. Before acting on a credit balance, find the transaction that created it.
| What happened | Check before acting |
|---|---|
| Open invoice billed the wrong amount | Compare the invoice line with the contract; document the approved correction |
| Paid invoice needs a price adjustment or return credit | Effective date, approved amount, and how the customer wants it handled |
| Customer paid twice | Both payments settled; neither already applied, returned, or disputed |
| Overpayment on a single invoice | Whether it is an overpayment or an advance for a future invoice |
| Credit should carry to a later invoice | Customer’s instruction on file; credit available when the invoice issues |
Stripe’s credit note workflow shows why the invoice status matters. A credit note on an open invoice reduces the amount due without recording a payment. On a paid invoice, you choose how the credit is allocated, including a refund or a customer balance credit. Stripe’s credit note documentation.
Verify the balance before you refund it
- Find the record that holds the balance. A customer payment, deposit, or credit memo. Check the customer, currency, and available amount.
- Review what has already happened. Look for applications to invoices, prior refunds, and reversals.
- Check the approval and payment method. Give the approver the source record, reason, and proposed amount. Follow your payment release policy, including bank detail verification.
- Tie the result back. Confirm the refund amount, the source it reduced, and what remains for future use.
Oracle’s NetSuite documentation describes refunding eligible payments, deposits, and credit memos, and its credit memo workflow limits a refund to the available amount. Confirm steps and permissions in the NetSuite interface your team uses. Oracle’s customer refund documentation · Oracle’s credit memo refund guide.
Worked example (illustrative)
A $5,000 credit memo was issued for a returned shipment. Last month, $3,200 of it was applied to an open invoice. The customer now asks for “the credit” back.
- Available: $5,000 − $3,200 = $1,800.
- Refund $1,800, recorded as a debit to the customer’s receivable (removing the credit balance) and a credit to cash.
- Afterward the credit memo should show nothing remaining, and the customer’s account should show no credit.
Refunding the full $5,000 would overpay the customer by $3,200, and recovering an overpaid refund is far harder than preventing one.
What goes wrong
- Double refund. A refund is issued from the processor while the same credit is still available to apply in the ERP. Record the processor reference and check that the amount is no longer available.
- Refund during a chargeback. The customer disputes a card payment and also requests a refund. Have the payment owner check the dispute status before releasing anything.
- Stale exposure. The credit check runs on a balance that last synced yesterday. Show the sync time on the hold.
- Permanent exceptions. A one-time release is treated as a new limit.
- Dormant credits. Old credit balances nobody claims. Review them periodically, and confirm any unclaimed property reporting obligations with counsel.
Credit and refund checklist
- Exposure policy written: invoices, unbilled orders, credits, unapplied cash, group limits.
- Holds show exposure, limit, overdue, disputes, and data freshness together.
- Every one-time release recorded with approver, reason, and expiry.
- Recommendations tested against past holds using point-in-time data.
- Every credit balance traced to the transaction that created it.
- Refunds limited to the available amount after prior applications.
- Processor references and chargeback status checked before release.
- Credit balances reviewed monthly by age.
Related: collections aging review, customer deductions and short pays, and SaaS billing accuracy.