Stop Chasing Customers Who Already Paid.

Posted on: October 7, 2026 | By: Heather Zhu | Microsoft Dynamics AX/365|Microsoft Dynamics Manufacturing, Microsoft Dynamics AX/365

WORKING CAPITAL / THE COLLECTIONS ISSUE / N05

Your D365 aging report tells you how old an invoice is. It does not tell you what is keeping it open.

By Logan ConsultingOctober 7, 20264–5 minute read

THE SCAN READ. A collection call is one possible action, not the automatic answer to every open invoice. Conceptual workspace illustration.

Consider an illustrative Monday collections meeting. Three invoices sit in the same overdue bucket. The first customer paid on Friday, but the payment has not been settled against the invoice. The second is waiting for proof of delivery. The third genuinely cannot pay on time.

The spreadsheet gives them the same color. The business needs three different conversations. Sending everyone a sterner reminder would be wonderfully efficient, in the way that watering every houseplant twice a day is efficient. The routine is consistent. The diagnosis is not.

This is the uncomfortable starting point for better collections in Dynamics 365 Finance: an open invoice is not, by itself, proof that a customer has failed to send the money. Microsoft explicitly provides a view of posted payments that have not been settled against invoices. Check that evidence before drafting the next demand.³

01 / SEPARATE THE STORIES

One bucket. Three stories.

There is a timely reason to look harder. In its September 2026 US Payment Practices Barometer, Atradius reported that late payments affected an average of 22% of B2B receivables among surveyed businesses. Its findings describe liquidity problems alongside delivery issues, payment-system difficulties and slow approvals. This is survey evidence, not a measurement of your D365 ledger.

The distinction matters because each cause points to a different owner. For the paid-but-unmatched invoice, ask cash application to verify the remittance and settle the correct transactions. An offsetting payment may already be reflected in the customer’s net balance; do not mistake the open invoice line for the whole account.

For the missing-document invoice, the next useful action may belong to shipping or customer service. Obtain the evidence, confirm that the customer received it, and agree on the next payment checkpoint. For a genuine liquidity problem, collections and the credit owner need a direct conversation about the commitment and exposure, not an internal paperwork scavenger hunt.

Age and amount still matter. This is not an argument for ignoring old balances. It is an argument for pairing urgency with a reason, then directing the work to whoever can remove the obstacle.

ILLUSTRATIVE WORKING CATEGORIES. These are recommended routes for investigation, not native D365 status names.

02 / MAKE THE SYSTEM TELL THE WHOLE STORY

D365 already holds several of the clues.

The Collections coordinator workspace brings together open transactions, disputed invoices, promises to pay and unsettled payments. Its customer timeline adds posted invoices, received payments, collection letters and activities. Enable the relevant workspace feature and confirm the user’s access and customer-pool scope before relying on the view.

Do not confuse a status with an explanation. “Disputed” says the customer reported a problem. It does not tell the next person whether the problem is a short shipment, an incorrect price or a missing delivery document. Record that evidence and the responsible person in the appropriate activity or case process. The categories in our decision card are suggested working labels, not new native D365 statuses.

There is also a consequential automation detail. Microsoft’s FAQ says collections process automation skips an invoice marked Disputed or Promised to pay; an overdue invoice can be picked up again after a qualifying status change. That concerns the invoice, not a blanket guarantee that every communication to that customer stops.⁵

A pause therefore needs a review date and an owner. Otherwise, an invoice can disappear from the automated chase while the underlying problem remains. Before enabling or changing a sequence, test a disputed item, a valid promise, a broken promise and a customer with multiple open invoices. Verify the actual output, not just the setup screen.

A status is not a diagnosis.

Native status examples [4], paired with Logan’s recommended investigation questions. Not a product screenshot.

03 / TURN THE AGING REVIEW INTO A WORKLIST

The best next action may not be an email.

Try this in the next AR review: select ten overdue invoice lines across different customers. For each, establish the remaining amount, supporting evidence, likely cause, next action and named owner. Keep “unknown” as a temporary investigation state, not a permanent filing cabinet. Start with the largest or most urgent exposures, but investigate before assuming.

Then measure time to remove the blocker, not only reminders sent. Track newly received cash separately from payments already received and subsequently applied. Both improvements matter, but only one is new cash. That distinction can turn a celebratory dashboard into a more useful management conversation.

Our point of view: collections should be the business’s feedback loop, not its apology department. Repeated requests for the same delivery document are a reason to examine the shipping-to-billing handoff. Repeated unapplied payments are a reason to improve remittance capture and settlement. Fixing either upstream is more valuable than perfecting the fifth reminder.

Logan’s collections-automation guide covers the scheduling and monitoring side. This article asks the question that comes first: what should happen to this invoice next? Bring our D365 team a small, anonymized sample of overdue items. We can help connect the evidence, ownership and system behavior before you automate the wrong conversation.

---

---