Skip to content
Bitta Apps
Operations, performance & upgrades

Pause Dunning on Disputed Invoices in Business Central

On this page

Pausing dunning for a disputed invoice in Business Central is one of the most common collections questions, because nothing damages a customer relationship faster than a reminder for an invoice the customer has already said is wrong. This guide explains the native fields involved, the exact steps in standard Business Central, the side effects to watch for, and how Bitta Collections handles disputes on the same fields.

Why a disputed invoice needs its own pause

A disputed invoice is not an overdue invoice in the usual sense. The customer does not refuse to pay the account; they question one document because of a pricing difference, damaged goods, a missing purchase order number or a billing error. Until the question is resolved:

  • reminders for that invoice should stop, so the customer is not chased for something they are waiting on;

  • the rest of the account should keep moving, so a single disputed invoice does not hide other overdue balances;

  • someone should own the dispute, with a date by which it should be resolved.

The native fields: Dispute Status and On Hold

Business Central has two fields on the customer ledger entry that matter here.

  • Dispute Status relates to the Dispute Status table, where each code has a description and an Overwrite on hold setting. The field is synchronized with the posted sales invoice and can be set with Update Document. Microsoft's Finance Agent in Outlook (preview) can also update it, as described in Collect outstanding balances.

  • On Hold is a free three-character code. According to Microsoft Learn, a customer ledger entry with On Hold filled in does not prompt the creation of a reminder, and interest is not calculated on it.

Reminders read On Hold, not Dispute Status. Setting a dispute status therefore pauses reminders only when the code has Overwrite on hold turned on, because that setting writes a value to On Hold on the entry. With a code that leaves Overwrite on hold off, setting a dispute status never fills On Hold, and reminders continue for the invoice.

Pause dunning for a disputed invoice in standard Business Central

  1. Search for Dispute Status and create codes for the reasons your team uses, for example PRICING, DAMAGED and NO PO.

  2. Turn on Overwrite on hold for each code that should stop reminders.

  3. Open Customer Ledger Entries, select the disputed invoice and set Dispute Status to the right code. Business Central fills On Hold on the entry.

  4. Record who owns the dispute and when it is due in a note, because the native fields have no owner or due date.

  5. When the dispute is resolved, clear Dispute Status and check On Hold.

Watch for the On Hold side effect

Step 5 matters, but only for Dispute Status codes that have Overwrite on hold turned on. When such a code filled On Hold, clearing Dispute Status on Customer Ledger Entries leaves the On Hold value in place, because the field's validation stops when the new status is blank. The invoice then stays excluded from reminders after the dispute is over. Check On Hold after every resolved dispute and clear it when the invoice should be collected again.

Also note how reminder runs treat on-hold entries. An on-hold entry does not create a reminder on its own, but when a reminder is created for the customer because of another overdue entry, the on-hold entry can still be listed on that reminder. The Include Entries On Hold option on the reminder batch controls this. See Set up reminder terms and levels and Automate reminders in collections.

Track disputes with Bitta Collections

Bitta Collections uses the native Dispute Status codes as its dispute reasons and writes the native field when a dispute opens, so the dispute is visible to anyone who looks at the ledger, including Microsoft's Finance Agent. On top of the native field, each dispute has:

  • a Reason Code, a Disputed Amount and a description of what the customer says;

  • an Owner Collector Code and a Due Date, the work date plus a set number of days;

  • a number, an activity in the customer's history and an acknowledgment the collector can print or email.

What a dispute pauses

An open dispute pauses only the disputed invoice; the customer's other invoices carry on as normal. Dunning sequences skip the invoice. With Exclude Disputed Entries on, native reminders and finance charge memos skip it as well. The worklist leaves it out of the actionable overdue amount, and credit hold rules do not count it.

The dispute reasons Bitta Collections creates have Overwrite on hold turned off, so resolving a dispute does not leave a stray On Hold value behind. When a dispute is resolved, the invoice gets its previous Dispute Status back and dunning resumes on the next run.

The native field stays in sync

Collectors who prefer the native field can keep using it. Setting a Dispute Status on an open invoice opens a dispute, clearing it resolves the dispute as withdrawn, and changing it changes the dispute reason. Bitta Collections never blocks an edit of the native field.

Follow up and resolve

When a dispute passes its due date, the work item gets the next action Review Dispute, and the role center counts open and past-due disputes. Resolving a dispute records the outcome, such as Credit Memo Issued, Customer Will Pay, Written Off or Withdrawn. When a disputed invoice is closed by a payment or credit memo, the daily job resolves the dispute as Entry Closed. The Open Disputes and Dispute Analysis reports show disputes by reason, age and owner. The full steps are in the Disputes guide.

Short payments often start a dispute

Many disputes start as a short payment: the customer pays an invoice less a deduction they believe is owed. Handling the short-paid remainder as a dispute keeps it out of reminders while the deduction is reviewed. The companion guide on applying short payments in Business Central covers the cash application side.

A dispute process is only as good as its exit. Whatever tooling a team uses, every dispute should have an owner, a due date and a recorded outcome, and every resolved dispute should return the invoice to normal dunning without manual cleanup.

FAQ

Frequently asked questions

How do I stop reminders for a disputed invoice in Business Central?

Fill in On Hold on the customer ledger entry, or set a Dispute Status code that has Overwrite on hold turned on, which fills On Hold for you. An entry with On Hold filled in does not prompt the creation of a reminder.

Does setting a Dispute Status stop reminders?

Only when the Dispute Status code has Overwrite on hold turned on. Reminders read On Hold, not Dispute Status.

Why is an invoice still excluded from reminders after the dispute was resolved?

If the Dispute Status code had Overwrite on hold turned on, setting it filled On Hold, and clearing Dispute Status on Customer Ledger Entries leaves that On Hold value in place. Check On Hold and clear it when the invoice should be collected again. Codes with Overwrite on hold off never set On Hold.

Does a dispute pause the whole customer account?

It should not. In Bitta Collections an open dispute pauses only the disputed invoice; the customer's other invoices carry on through dunning as normal.

Sources

Claims in this article were checked against the following on Nov 17, 2026.

  1. learn.microsoft.com/en-us/dynamics365/business-central/receivables-collect-outstanding-balances
  2. learn.microsoft.com/en-us/dynamics365/business-central/finance-setup-reminders
  3. learn.microsoft.com/en-us/dynamics365/business-central/finance-automate-reminders

Written by

Mohammad Nour Itani

Founder & Senior Business Central Developer

Related services

Work with Bitta Apps on this

Next step

Talk to a senior Business Central consultant, not a sales rep.

Fixed-price proposal in writing within five business days of discovery.