Introducing Disputes

Not every overdue invoice is a simple reminder problem.

Sometimes the customer says the amount is wrong. Sometimes they claim the work was different from what was billed. Sometimes they say they already paid and do not believe anything is owed.

Until now, those moments often lived inside email threads, Slack messages, notes, or someone’s memory. That makes disputes hard to triage, hard to assign, and easy to lose track of.

And the delay is expensive: across industries, it takes an average of 38 days to resolve a customer deduction. This means weeks of cash are sitting uncollected while the issue drifts between inboxes.

Today we’re introducing Disputes in Monk: a dedicated way to track customer invoice objections.

When Monk detects a dispute in a collection conversation, it can create a structured dispute case linked to the customer, invoice, and original conversation. Each dispute includes a summary, reason, status, owner, amount context, target invoice, and activity history, so finance teams can see what happened and what needs to happen next.

‍

‍

‍

Disputes are built for monetary and commercial disagreements. The objections that should not stay buried in a thread:

• A customer says the invoice amount is incorrect
• A customer claims the service or deliverable does not match the invoice
• A payment was applied to the wrong invoice
• A customer says they already paid

Non-commercial requests like asking for new payment terms, asking to speak with someone, or asking you to resend an invoice or a missing document are not disputes. Those keep flowing through collections as escalations, the same as before.

From the new Disputes view, teams can triage open items, assign ownership, update status, add comments, and jump back to the linked collection conversation. Resolving a dispute can also dismiss the linked collection review when there are no other active disputes remaining.

‍

‍

This is an early foundation. We are starting with the operational rail: detect the exception, preserve the context, and make the work visible. Over time, Disputes will connect more deeply into cash application, deductions, ERP context, supporting documents, and resolution workflows.

The goal is simple: routine collections should keep moving automatically, while true exceptions get the structure and attention they deserve.