A customer asks for the detail of outstanding documents. Your manager wants to know how much is more than a month overdue. Both requests may involve the same records, but you should not send the same report without checking its purpose. A customer statement supports discussion of the relationship; aging organizes receivables by age. Confusing them can turn an uninvoiced proposal into a collection request or label an amount overdue while it remains within agreed terms.
Separate the questions
Customer detail identifies documents, amounts, and individual statuses. It helps locate a reference, inspect an invoice, or explain a payment. Aging describes how balances fall into bands relative to due dates and an evaluation date. It supports prioritization and review of overdue concentration. Neither replaces bank evidence or the commercial agreement behind a disputed amount.
Tario's customer statement exporter combines invoices and estimates, showing document type, number, dates, status, total, and displayed amount due. That mixture deserves attention: an estimate remains a commercial proposal. Do not sum every row as collectible debt. Filter by document type and verify each status before preparing a collection email or management total.
An example of different totals
A customer has a CRC240,000 invoice with a CRC90,000 payment, a CRC180,000 invoice still within terms, and a CRC300,000 estimate. The invoices have CRC330,000 outstanding together. The estimate describes a possible sale but does not add CRC300,000 to collection. Summing every original total gives CRC720,000, which represents neither outstanding invoice balances nor overdue debt.
Suppose the first invoice became due twenty days ago and the second is due next week. The first invoice's remaining CRC150,000 needs overdue follow-up; the CRC180,000 is not yet due. Customer detail explains both documents, while aging assigns balances using its bands and cutoff. A customer can have a large balance without all of it being overdue.
Read bands with their cutoff
Before interpreting aging, check the evaluation date, band definitions, and included population. Do not count days from issue if the report counts days from due date. A document issued forty days ago with sixty-day terms is not overdue for that reason. Likewise, a calendar-month band is not necessarily a thirty-day band. Headings and filters are part of the information, not decoration.
Distinguish evaluation date from the balance being used. To reconstruct August closing receivables, a September payment needs treatment consistent with that question. A list showing current balances does not necessarily reconstruct historical balances simply because you filtered August documents. In Tario, inspect the selected report and cutoff, then use documentary and accounting detail for historical differences. Check how each view selects and calculates before expecting exact agreement.
Compare individual documents
- Use the same company, currency, and evaluation date.
- Separate estimates, drafts, and documents outside the collection population.
- Compare invoice number, due date, original amount, applied payments, and remaining balance.
- Explain adjustments and later payments before sending the file.
When balances differ, start with recently paid invoices. Look for unapplied payments, incorrect links, and corrected documents. Applying CRC150,000 to another invoice can change the aging distribution without changing the customer's combined balance. That matters: you might request the wrong document or assign age to a debt the customer identified as settled. Verify the payment instruction before moving its allocation.
Keep currency and scope visible
A USD500 invoice and a CRC100,000 invoice do not create a meaningful balance of 100,500. Present detail in its original currency or explain the report's conversion. The invoice currency is usually clearer for customer communication. A functional currency may help management compare totals if the method is consistent. Exchange differences and overdue balances are separate questions.
Check temporal scope too. An operational view may focus on recent receivables while accounting retains older movements. A document disappearing from a selection does not establish payment or forgiveness. For historical balances, locate the document and its settlements through the appropriate workflow. Do not dismiss an unexplained difference because it is old; first establish why a report includes or excludes it.
Use each output for a specific action
For the customer, prepare identifiable invoices, checked balances, and a stated cutoff date. For a dispute, ask which document is questioned and why. For the team, use aging to assign priorities, owners, and follow-up dates. A small old balance may need a pending adjustment resolved, while a large newly overdue amount may need a commercial call. Report ordering helps without deciding the whole conversation.
After a reply or payment, update the evidence and record or link the movement through an authorized workflow. Sending a statement does not settle invoices or collect money automatically. Retain the reviewed copy used for follow-up and note the subsequent agreement. The next colleague can then understand what remains outstanding, what the customer promised, and what still requires verification without interpreting an estimate as debt.