How to Track Promises to Pay in Business Central Online
On this page
- What a promise to pay is, in accounts receivable terms
- The native Promised Pay Date field
- Record a promise with standard Business Central
- Keep reminders away from promised invoices
- Check promises by hand
- Track promises to pay with Bitta Collections
- Promises that check themselves
- Report on promise performance
- Choosing an approach
Tracking promises to pay in Business Central starts with one native field, Promised Pay Date, and a clear understanding of what that field does and does not do. This guide explains how the native field works, how to run a dependable promise-to-pay process with standard Business Central, and where an app such as Bitta Collections adds amounts, checks and follow-up.
What a promise to pay is, in accounts receivable terms
A promise to pay is a customer's commitment to pay a stated amount on a stated date, usually given on a collection call or by email. It matters for three reasons:
Collectors stop chasing invoices the customer has already committed to pay, which keeps the relationship intact.
The promise becomes a follow-up date. If the money does not arrive, the collector calls again with a specific broken commitment to discuss.
Finance gets an early cash signal. Promised amounts and dates are a better short-term forecast than due dates alone.
A promise process only works when each promise records the amount, the date and the invoices it covers, and when someone checks it against the payments that actually arrive.
The native Promised Pay Date field
Business Central has a Promised Pay Date field on each customer ledger entry. It is synchronized with the posted sales invoice, so it can also be set with Update Document on a posted sales invoice. Microsoft's Finance Agent in Outlook (preview) reads and updates the same field when a collector works from email, as described in Collect outstanding balances.
The field is informational. It holds one date per invoice. It has no amount, no history of earlier promises and no status. Standard reminders, finance charge memos, statements and credit checks do not read it, so setting a promise date on its own does not stop a reminder from going out for that invoice.
Record a promise with standard Business Central
Search for Customer Ledger Entries and filter on the customer.
Select the invoice the customer promised to pay.
Enter the date in Promised Pay Date. If the column is not visible, add it with Personalize.
Add a note or a comment with the promised amount and the contact who made the promise, because the field holds only the date.
Repeat for each invoice the promise covers.
Keep reminders away from promised invoices
Because reminders ignore Promised Pay Date, the standard way to keep a promised invoice out of the next reminder run is the On Hold field on the same customer ledger entry. According to Microsoft Learn, an entry with On Hold filled in does not prompt the creation of a reminder, and no interest is calculated on it. If a reminder is created for the customer because of another overdue entry, the on-hold entry can still appear on that reminder. See Set up reminder terms and levels and Automate reminders in collections for how reminder runs select entries.
On Hold is a free three-character code with no reason table, so agree on a value such as PTP for promises and clear it when the promise ends.
Check promises by hand
With standard Business Central, checking a promise is a manual review:
Filter Customer Ledger Entries on entries with a Promised Pay Date on or before today.
For each one, check Remaining Amount. If it is zero, the promise was kept.
If an amount remains, decide whether the promise was partly kept or broken, clear On Hold so dunning resumes, and schedule a follow-up call.
Clear Promised Pay Date or set a new one if the customer makes a new promise.
This works for a small number of promises. It becomes unreliable when collectors manage dozens of promises a week, because the check depends on someone remembering to run the filter, and the history of earlier promises is lost each time the date is overwritten.
Track promises to pay with Bitta Collections
Bitta Collections builds on the same native field instead of replacing it. A collector records a promise from the collections worklist, the customer card or Customer Ledger Entries, and the app keeps a promise record with:
the Promise Date, the contact who made the promise and an optional payment method;
a Promised Amount per invoice, so one promise can cover several invoices with partial amounts;
a promise number and an activity in the customer's collection history.
While the promise is open, Bitta Collections writes the promise date to the native Promised Pay Date of each promised invoice. Its dunning sequences pause those invoices, and with the Exclude Promised Entries setting on, native reminders and finance charge memos skip them too. The promised amount also leaves the actionable overdue amount on the worklist.
Promises that check themselves
The main difference from the manual process is the check. Each time a payment or credit memo is applied to a promised invoice, Bitta Collections marks the promise for checking and sets its status from the applications:
Status | When |
|---|---|
Kept | Everything promised was received, or every promised invoice is closed. |
Partly Kept | The grace days have passed and part of the promised amount was received. |
Broken | The grace days have passed and nothing was received. |
When a promise is broken or partly kept, the native Promised Pay Date gets its previous value back, dunning resumes on the next run, and the work item gets the next action Follow Up Broken Promise. The full steps are in the Promises to pay guide.
Report on promise performance
Promise history is kept, so the Promises to Pay and Promise Performance reports show the kept rate by collector and period. A kept rate is a practical measure of collection quality: a falling rate is an early sign that a customer, or a collector's approach, needs attention.
Choosing an approach
Standard Business Central is enough when a few promises a month are tracked by one person. A dedicated collections app is worth evaluating when promises cover several invoices, when more than one collector works the ledger, or when finance needs a kept rate it can trust. The buyer's checklist for collections apps lists the questions to ask any vendor, and the Bitta Collections guide shows each step in Business Central.
Whichever route a team chooses, the principle is the same: record the amount and the invoices, pause dunning for exactly what was promised, and check every promise against the payments that arrive.
FAQ
Frequently asked questions
Does Business Central have a promise to pay field?
Yes. Each customer ledger entry has a Promised Pay Date field, synchronized with the posted sales invoice. It holds one date per invoice and is informational: reminders, statements and credit checks do not read it.
Do Business Central reminders skip invoices with a promised pay date?
No. Reminders do not read Promised Pay Date. To keep a promised invoice from prompting a reminder, use the On Hold field on the customer ledger entry, or a collections app that pauses dunning for promised invoices.
How do I know if a customer kept a promise to pay?
In standard Business Central, filter Customer Ledger Entries on promise dates that have passed and check the remaining amount of each invoice. Bitta Collections does this check automatically each time a payment or credit memo is applied to a promised invoice.
Does Microsoft's Finance Agent update the promised pay date?
Yes. Microsoft's Finance Agent in Outlook (preview) can access and update the Dispute Status and promise to pay date on invoices, according to Microsoft Learn.
Sources
Claims in this article were checked against the following on Nov 17, 2026.