Q1: What is the credit-finance gap, and why is it a credit management problem?

The credit-finance gap is the space between what finance manages — bank statement uploads, journals, suspense accounts, and ERP cash-book reconciliations — and what credit controls: aging reports, collection calls, credit limits, risk flags, and stop-supply decisions. Unresolved allocation issues sit silently in this gap, ageing on nobody's radar.

The consequence is real: overdue balances accumulate on accounts where cash has already been received but not applied. Credit decisions — limit cuts, supply stops, collection calls — get made on bad data. Bank recon is traditionally treated as a finance function, but it has a direct impact on credit risk visibility. Bringing it firmly into the credit conversation is the first step to fixing the gap.

Q2: What are the most common causes of misallocation errors?

Most misallocations trace back to a single root cause: cash applied without a clear remittance advice or explicit client instruction. The specific triggers vary, but the pattern is consistent — incomplete information at the point of payment.

Common causes:

• No remittance advice provided — the client pays without specifying which invoices the payment covers, forcing a guessed allocation.
• Remittance advice errors — the client references incorrect invoice numbers, outdated account codes, or duplicate customer account numbers from ERP migrations.
• Partial payments applied to the wrong invoice — a half-payment is applied to whichever invoice is convenient rather than the one the client intended.
• Credit notes posted to the wrong account — particularly where a debtor trades across multiple accounts; the credit lands on account A while the outstanding invoice sits on account B.
• Unapplied credit notes hiding open invoices — a credit note lies uncleared and masks an outstanding invoice in the same customer's aging summary, making the account appear healthier than it is.
• Foreign currency rounding differences — FX conversion creates small tail balances that accumulate and distort the aging if not cleared promptly with a defined clearing rule.
• One lump payment split across multiple accounts — a group debtor sends a single payment covering 20 or 50 sub-accounts; without a clear remittance, allocation becomes impossible.

Q3: How do allocation errors distort my debtor book and affect credit decisions?

Allocation errors distort your aging in both directions — and both are dangerous. A customer can look more overdue than they are, or considerably better than they are, depending on where the error sits.

Customers appearing more overdue than they are:

• Cash received but sitting in suspense or unallocated — the outstanding balance remains visible in the aging even though the money is already in your account.
• A payment applied to new invoices when the client actually intended to pay old ones — old balances keep ageing into 60- or 90-day buckets unnecessarily.
• Credit notes unapplied — an open invoice looks outstanding while an offsetting credit note sits unclaimed elsewhere on the account.

Customers appearing better than they are (the riskier distortion):

• A large credit note on one account masks an equally large overdue invoice on another — the summarised aging looks clean, but the underlying risk is real.
• Suspense credits sitting against genuinely overdue invoices suppress the overdue flag, so nobody calls the client and nobody reviews the limit.
• When the credit is eventually reallocated to the correct account, a large overdue balance can appear overnight — causing panic and the impression that the credit team dropped the ball.

Q4: Why is remittance advice so critical, and what should I do when clients don't provide one?

The remittance advice is the instruction that makes correct cash application possible. Without it, every allocation is a guess — and guesses compound over time into serious aging distortions. Getting this right starts at onboarding, not when a problem has already appeared.

What to do:

• Set the expectation at onboarding — when you bring on a new debtor, ask upfront: Do you use purchase orders? What reference do you use on EFTs? When do you release your remittance advice — before or after payment? Document the answers.
• Build a reference matching rule — identify the format your client uses (e.g. a PO number, account code, or company abbreviation) and document it so your entire team can recognise it instantly on a bank statement.
• Do not apply cash without a remittance or written instruction — even a clear email from the client stating which invoice they are paying qualifies. A guess does not. This is especially critical where a client pays multiple invoices of similar values.
• If a client repeatedly fails to send remittance advices — escalate to your sales contact and ask them to raise it with the client's creditors clerk or payment team directly. Frame it as a process request, not a complaint.
• For unidentified deposits — contact the bank and ask them to trace the origin of the payment. They can often identify the paying entity from the account number and provide enough detail to allocate correctly.
• Segregate duties — the person who downloads the bank statement and moves cash to the debtor account must not be the same person who allocates it against invoices. Keep these functions separate as a financial control.

Q5: How do I use my bank reconciliation as a credit health check?

Your bank recon is a behavioural report on how your customers pay — not just whether they pay. Recurring patterns in your recon tell you more about a customer's financial position than a single aging snapshot ever will.

Patterns to look for and what they signal:

• Persistent unallocated receipts from the same customer — either the client isn't providing clear references, or finance isn't posting their account. Either way, it creates visible aging distortion that needs a process fix, not just a once-off clean-up.
• Recurring small rounding differences — a client consistently taking small unexplained credits. These accumulate and can mask short-payment behaviour if left unchecked. Investigate and clear them promptly.
• Payments landing just after month-end — always within a narrow window. The customer is waiting on their own incoming cash before paying you. Factor this dependency into your limit and collection decisions.
• Payments shifting progressively later each month — 28th, then the 2nd, then the 5th. This staggering is a classic early sign of cash flow strain. Watch the trend across three months.
• Round-number payments instead of invoice-specific amounts — paying R5,000 when the invoice is R9,450.23. They paid what they had available, not what the invoice required. Treat this as a red flag.
• Split payments across a single large invoice or across multiple accounts — complex payment patterns without a clear remittance make allocation impossible and often indicate a debtor in a difficult cash position.

Q6: What is the recon–credit limit–collection triangle, and why does timing matter?

The triangle describes the dependency between three critical monthly events: when finance closes the bank recon, when credit limits are reviewed, and when collection calls begin. If these are out of sync, your team acts on stale or distorted data — with real consequences for customer relationships and credit decisions.

The three points of the triangle:

• Bank recon close — finance should close the recon on the last working day of the month, using the final bank statement of that period. This is the moment your aging becomes trustworthy enough to act on.
• Credit limit review — limits must be reviewed against fully reconciled, post-close data. Reviewing while cash is still unallocated risks cutting the limit of a customer who has already paid — or missing a genuine over-limit situation because credits are masking it.
• Collection calls — credit controllers should not follow up on overdue balances until the recon is closed and all cash is fully applied. Calling a customer about an invoice they have already paid destroys trust and wastes everyone's time.

Synchronise your credit calendar with your recon cycle. Know exactly when finance closes and when the banking clerk finalises uploads — and build your team's monthly workflow around that date, not just the calendar month-end.

Q7: When and how should I escalate unresolved allocation issues?

Escalation is not a sign of failure — it is how you get the rest of the business working with you. Unresolved allocation issues become progressively more expensive the longer they sit, and there are specific triggers that should prompt immediate action.

When to escalate:

• Unallocated receipts outstanding for more than 5 business days — these should be resolved within 5 days as a standing rule. Beyond that, escalate to your supervisor or credit manager.
• The same allocation error recurring across multiple months — a pattern error is a process problem, not a one-off. Escalate to finance and document the recurrence with specific examples.
• Allocation errors that have driven an incorrect credit decision — if a limit was cut, a supply was stopped, or a collection call was made based on misallocated data, escalate immediately. The customer record and the decision both need to be corrected.
• Suspense accounts growing month on month — this is no longer a credit control problem. It requires finance, treasury, and management involvement. Treat it as a systems or process failure.
• Credit notes held up because another department hasn't acted — document the delay, note the date the credit note was requested, and escalate to the relevant manager with a clear timeline and the aging impact.

How to escalate effectively:

• Bring data, not just the problem — show the account, the amount, how long it has been outstanding, and the impact on the aging or on a credit decision already made.
• Bring a proposed solution — even if it needs refining, come with a recommendation. It shows ownership and speeds up resolution.
• Match the escalation level to the severity — a 5-day unallocated receipt goes to a supervisor; a suspense account growing for three consecutive months goes to the finance manager and credit director.

Q8: What payment behaviour patterns should flag concern for me?

Your bank recon is a behavioural dataset. The way a customer pays — not just whether they pay — is one of the earliest indicators of financial stress. Teach your credit team to read these patterns, not just chase outstanding balances.

Patterns that signal concern:

• Round-number payments — paying R5,000 instead of R9,450.23 means the client paid what they had available, not what the invoice required. This is a cash flow signal worth noting.
• Payments arriving progressively later each month — shifting from the 28th, to the 2nd, to the 5th across three months indicates the customer is waiting on their own incoming cash before paying you. Watch the trend.
• Withheld remittance advices — occasionally a deliberate delay tactic. If a customer who previously sent advices without prompting suddenly stops, take note and follow up promptly.
• Payments stopping and then resuming with a lump sum — interrupted payment flow. Ask your sales contact to check in with the customer's management; it often signals a cash flow event.
• A customer claiming to have paid when funds are not in your account — always request proof of payment. The money may be in the wrong account, or the claim may not be accurate. Trace it before acting on either assumption.
• One bulk payment covering multiple sub-accounts — without a detailed remittance, correct allocation is impossible. This is not optional: the remittance advice must accompany any grouped payment before cash is moved.

Need more help?

The support team is ready to assist

support@tradeshield.ai

+27 (0) 10 753 1630

www.tradeshield.ai