Quick answer
Use the records created during ordinary operations to test whether the claimed balance can be reproduced. A legal pack may contain the contract and invoices, while the business-record review explains how the customer, orders, work, credits, allocations and disputes moved through the company's systems.
How to use this guide
Use ordinary-course business systems to reproduce the claimed balance and explain every adjustment. The customer master, order, fulfilment, ledger, bank and dispute records perform a different job from the formal legal bundle: they show how the account moved through the business and where identity, allocation or performance inconsistencies arose.
Reconstruct the account from source systems
Operational systems explain how a customer balance moved through the business. Start with the customer master and note changes to legal name, registration number, billing entity, contacts, credit terms and account ownership. Then connect orders, fulfilment, invoicing, credits, receipts and disputes across the same cut-off date. This helps expose wrong-entity and allocation problems before legal conclusions are drawn.
Check the operational record chain
Follow the account through each ordinary-course system:
- Export the customer master showing legal identity, account changes, credit terms, contacts and approval history.
- Trace quotations, orders, fulfilment, delivery, acceptance, returns and service tickets through their source systems.
- Reconcile the aged debtor ledger to the general ledger, bank receipts, remittances and allocation history.
- Preserve credit notes, rebates, refunds, write-offs and manual journals with approval and audit information.
- Extract CRM notes, complaint logs, dispute codes and collection activity without deleting inconvenient entries.
- Record system migrations, data corrections and access logs that explain any inconsistency in dates or balances.
Preserve audit history
Preserve audit history when systems disagree. An order platform may record a return that has not reached the ledger; a bank receipt may sit in suspense; a customer-management note may promise a credit. Export the relevant reports with their names, filters, timezone, generation date and custodian. Keep manual journals, write-offs and corrections with the approval trail instead of overwriting the earlier entry.
Explain ledger differences
The reconciliation should explain differences, not force every system to show the claimed total. Mark which figure is a live accounting balance, which is a legal claim calculation and which remains disputed. A litigation schedule can cite the underlying records while staying separate from the books. Escalate unexplained changes or missing history before a formal demand presents the balance as final.
Avoid changing the live record
Protect the audit trail while the balance is being reconstructed:
- Do not treat a manually updated age analysis as independent proof of the underlying transactions.
- Do not overwrite the live ledger to make it match a litigation schedule.
- Do not export excessive unrelated customer or employee personal information into the recovery bundle.
- Do not ignore a payment allocation or credit simply because it was posted to the wrong account.
Build the reconciliation file
Package the reconciliation so another reviewer can reproduce it:
- Reproduce the balance from transaction-level records and record every reconciliation difference.
- Map each order to fulfilment, invoice, payment, credit and current dispute status.
- Preserve read-only exports with report parameters, generation date and system source.
- Separate normal operational records from notes created specifically for the dispute.
- Escalate unexplained manual changes, missing audit trails and customer-identity mismatches before demand.
Deeper analysis: business-debt operational reconciliation
Start with the customer master and account history. Record changes to legal name, registration number, billing entity, contacts, credit terms and account ownership. A debt can be misdirected when a group company, franchise, branch or trading name was used inconsistently, so connect each source transaction to the entity that actually contracted and received performance.
Reconcile operational and financial systems across the same cut-off date. An order-management platform may show returns or rejected work that the aged ledger does not yet reflect; the bank may show a receipt posted to a suspense account; the CRM may record a promised credit. Preserve each discrepancy and its correction history rather than overwriting one system to match another.
Make exports reviewable. Record the system, report name, filters, timezone, generation date and person who produced the file. Keep manual journals, write-offs, rebates and allocation changes with approval and audit trails. A later litigation schedule should cite these sources and remain visibly separate from the live accounting record.
Accounting records become more persuasive when their changes can be explained. Keep the original invoice entries, allocation history, credit notes, reversals, write-offs and user audit logs, together with the bank transactions used in the reconciliation. If the customer relationship system records a complaint or promised adjustment, preserve that too. A clean explanation of each movement is more useful than a fresh spreadsheet that reproduces only the balance the business now wants to recover.
Limits of internal business records
Internal records can establish a reliable reconciliation without independently proving legal liability. Their weight depends on source integrity, ordinary use, authority and consistency with the agreement and performance evidence. Restrict unrelated customer and employee information, preserve adverse entries and escalate unexplained manual changes before a demand states a final balance.
FAQs
Is the aged ledger enough to prove the debt?
No. It is a useful accounting view, but the source transactions, performance, allocations, credits and disputes must support the balance.
Why keep CRM and ticket records?
They may show acceptance, complaints, promised corrections, dispute timing and the business's response to alleged non-performance.
Should bank records be included?
Include relevant receipts and remittances so payments and allocations can be checked, while limiting unrelated financial and personal information.
What if two systems show different balances?
Preserve both exports, document parameters and migration or adjustment history, and resolve the difference before presenting a final amount.
Related Lexuno paths
Related articles
Source notes
Legal note
This article is general legal information for South African readers. It is not legal advice. Speak to a qualified legal professional about your specific facts before taking action.