Trade credit means a wholesale distributor is always carrying debt — invoices raised and stock already shipped, waiting on payment that might be 7 days, 20th-of-the-month, or whatever's been agreed. That's normal. What isn't normal is finding out how much of it is actually overdue by exporting a report nobody's looked at in a week, or building a customer's statement from scratch in a spreadsheet every time their accounts team asks for one.
Two different problems that get lumped together
Credit control and aged receivables sound similar but solve different problems. Credit control — covered in our guide on credit limits and accounts receivable — stops a new order going out to an account that's already over its limit. Aged receivables is what happens after that: invoices that have already gone out and haven't been paid, aged into current, 30, 60 and 90+ day buckets so your office can see at a glance who's genuinely overdue versus who's simply on longer terms. Get the first one wrong and you're shipping into bad debt. Get the second one wrong and debt that's already there just sits, uncollected, because nobody has an accurate list of who to chase.
Where it usually goes wrong
In a lot of distribution businesses, the aged debtor list is a report someone runs periodically out of the accounting package — useful on the day it's run, stale a few days later once more invoices and part-payments have gone through. Chasing debt off that list means chasing the wrong number half the time. And when a customer's accounts payable team rings up asking for a statement before they'll process payment — which larger accounts do routinely — someone has to stop and build one: pull the open invoices, check what's actually still outstanding, format it into something that looks like it came from a real business rather than a spreadsheet export.
What this should actually look like
The fix isn't a better spreadsheet — it's the aged position and the statement both coming straight off the same ledger that raised the invoice in the first place:
- An aged receivables report — debtor aging buckets, current/30/60/90+ — that reflects invoices and payments as they actually happen, not a snapshot from last week
- A statement of account for any customer who owes money, built in seconds rather than assembled by hand — their open invoices aged into the same buckets
- A date-range activity statement with a running balance for the customer whose own accounts team wants to reconcile a period rather than just see the current balance
- A branded PDF, or the statement emailed straight to the customer, instead of a plain export that doesn't look like it came from your business
Done that way, whoever's chasing debt is working from a number that's actually current, and a customer who asks for a statement gets one immediately instead of waiting for someone to build it.
Why Xero on its own doesn't cover this cleanly
If orders, invoicing and customer records live in a separate ordering or ERP system and only the invoice itself gets pushed through to Xero, your aged receivables position is only as current as the last sync — and it's a one-way trip. Cognit sends invoices and credit notes to Xero; nothing about payment status or ageing comes back automatically. Running aged receivables and statements off the system where the invoice was actually raised, alongside your own general ledger, closes that gap rather than leaving your debtor position split across two systems that don't fully talk to each other.
It compounds with returns and credit notes
An aged balance is only accurate if credit notes are reflected against it as soon as they're raised, not weeks later once someone's caught up on data entry. That's the same discipline behind our guide on returns and credit notes — a damaged pallet or a short-shipped line that's been credited should drop straight off a customer's outstanding balance, so the statement you send them isn't asking for money they don't actually owe.
Built around how your business actually collects debt
Whether your customers expect a monthly statement as standard, only ask for one when they're reconciling their own books, or you mostly work off an aged debtor list internally, tell us how collections actually run in your business and we build the reporting and statement flow to match — on top of the same invoicing and customer records everything else in Cognit already runs on, rather than a bolt-on that only half reflects what's really outstanding.
Stop chasing debt off a stale number
If your aged debtor position is only ever as current as the last time someone ran a report, or building a customer statement still means a spreadsheet, it's worth seeing what an aged receivables view and statement run straight off your live ledger actually looks like. See what's included or book a demo to walk through it against your own customers.
Frequently asked questions
What's the difference between credit limits and aged receivables?
Credit limits stop a new order going out to a customer who's already over their limit or overdue — it's prevention, enforced at the point of sale. Aged receivables is the other side: it's about what's already been invoiced and hasn't been paid, sorted by how overdue it is (current, 30, 60, 90+ days), so your office knows exactly who to chase and how hard.
What is a customer statement, and why would a customer want one?
A statement of account is the document you send a customer showing what they currently owe you — either every open invoice aged into current/30/60/90+ buckets, or a date-range activity statement with a running balance. Customers on trade terms often ask for one before they'll pay, especially larger accounts whose own accounts payable team reconciles against a statement rather than chasing individual invoices.
Why not just run this out of Xero or MYOB?
You can, if that's where your ledger genuinely lives. But if a distributor's real day-to-day picture of what a customer owes is built from orders and invoices raised in a separate ordering or ERP system, the accounting package is only ever as current as the last sync — and Cognit only sends invoices and credit notes to Xero, it doesn't pull anything back. Aged receivables and statements built off the same system that raised the invoice in the first place don't have that lag.
Can a statement cover a date range instead of just open invoices?
Yes — sometimes a customer's own accounts team wants to reconcile a specific period rather than just see what's currently outstanding. A date-range activity statement with a running balance covers that, alongside the standard aged-balance statement for a customer who just wants to know what they owe right now.
Does this replace someone in the office chasing debt by phone?
No — someone still has to make the call or send the reminder. What it removes is the manual work of pulling together which invoices are actually overdue and building a statement from scratch each time a customer asks for one, so whoever's chasing debt is working from an accurate list instead of guessing or exporting a spreadsheet first.
