Make the next collection call a useful one

At a glance

Frappe ERP's Accounts Receivable reports show outstanding amounts and ageing, while Payment Entry and Payment Reconciliation connect money received to invoices. Use that foundation to prepare useful collection calls. The collector should know what remains unpaid, what the customer disputes and who will resolve the next step before asking for a payment date.

Start before the call

The collector has the invoice open when the customer says it was paid last week. The bank receipt exists, but nobody has matched it to that invoice. A call intended to bring money in now consumes time on both sides and makes the next reminder harder to trust.

Make payment allocation part of collection preparation. Frappe's Payment Entry distinguishes amounts paid from amounts allocated to particular documents. That gives finance a way to investigate the customer's statement before sending another reminder. The immediate benefit is a more accurate conversation, not a promise that every debtor will pay sooner.

The official version 13 sources cited here describe the established accounting records. Check the report filters and matching procedure on your installed release with your accountant. A familiar report name is not enough to confirm that two teams are looking at the same population.

Agree what overdue means

Frappe's Accounts Receivable reporting includes ageing analysis and a payment-terms view. These support different questions. The controller may need the whole customer balance, while the collector needs the amount due under the agreed schedule. Define which view drives the daily worklist and make its cutoff explicit.

A large invoice may contain an instalment that is not yet due. Do not describe the entire invoice as late merely because its earliest payment date has passed. Have finance test the terms-based report against the signed agreement before it becomes the basis of customer communication.

Save the reporting assumptions in the collection procedure. Name the company and currency, and record the date used for review. Someone covering the desk during an absence should be able to reproduce the list without inheriting a private spreadsheet whose filters nobody remembers.

Match the money first

A customer can send one payment covering several invoices. Frappe documents allocating a Payment Entry across outstanding invoices, as well as retaining an unallocated amount for later use. Payment Reconciliation provides a separate route for linking payments and invoices when those connections were not made initially.

Use the customer's remittance advice when deciding which documents to settle. An arbitrary allocation can make one invoice look late while hiding a genuine dispute on another. Where the reference is unclear, assign the investigation to someone and keep the uncertainty visible to the collector.

Worked example, hypothetical and not an ERPNova result: a customer has invoices of USD 8,000 and USD 5,000. A USD 9,000 payment is allocated as USD 8,000 to the first invoice and USD 1,000 to the second. Total outstanding is USD 4,000. The first invoice is settled; only the second belongs in the remaining collection conversation, assuming no other adjustments.

Do not confuse invoice matching with bank reconciliation. Proving which invoice a receipt settles is a different check from confirming the bank statement and the recorded cash movement agree. Give each check an owner.

Separate disputes from delay

An unpaid invoice can require a customer action or an internal correction. If the customer is waiting for a purchase-order reference, another payment reminder will not supply it. If a delivery is disputed, the collector needs somebody in operations to examine the evidence.

Design a short dispute register around the invoice reference. Record the reason in plain words and name the person who owes the next response. This is a process recommendation, not a claim that every required dispute field or escalation is preconfigured. Assess any additional fields and notifications as implementation scope.

Keep the disputed portion separate from the amount the customer accepts. Ask for a payment commitment on the undisputed amount where your agreement permits it. Finance should approve credits and write-offs through its own control procedure; collectors should not erase differences simply to remove an uncomfortable item from the list.

Write a useful commitment

A note saying customer contacted tells the next collector very little. A useful note records what the customer said they will do and when you should check again. If they promise to send remittance advice rather than money, write that distinction down.

Choose a follow-up method staff will actually maintain. It may be an assigned task linked to the invoice, or a scoped collection view built around your chosen fields. Ask the implementer to demonstrate the reminder and access rules on your release instead of assuming a notification will reach the right person.

Review missed commitments without turning every case into an escalation. A payment sent to the wrong reference needs investigation. A customer repeatedly changing the date may need a credit-control decision. Give the collector a clear route to finance leadership, with any supply hold decided under your own policy rather than improvised during a call.

Review the right evidence

Measure the collection process before claiming it has improved cash flow. Start with whether unallocated receipts are being resolved and whether disputed invoices have owners. An ageing balance can change because of new invoices or credits as well as collections, so a falling total does not establish the cause by itself.

Use a sample account to trace the receivable back to the underlying postings; Frappe's General Ledger report provides transaction-level detail and filters. Have finance explain any difference between the report and the collector's worklist using the same cutoff. Correct the definition before judging the person making the calls.

Bring ERPNova an anonymized ageing report and an example of a receipt that was difficult to match to an ERP audit. Ask for a pilot covering allocation, dispute ownership and the next follow-up. If the problem starts before billing, our quote-to-cash guide helps you examine the handoff that produced the invoice.