What's New in Workday 2026R2 for Customer Accounts and Cust Contracts

Workday's 2026R2 release hits production on September 19 and is currently available in preview. The Customer Accounts and Customer Contracts area are receiving sixteen features. Twelve are marked automatically available, which is usually code for "skim it and move on."

Do not skim this one. A rename buried in the Customer Accounts list can break a custom report you have not touched in two years, and Customer Contracts gets its first AI feature: an agent that reads a signed contract PDF and builds the Workday record for you. Here is what is worth your time before the release hits production , and what you can genuinely ignore.

Additionally, platform updates affect users of all areas. The My Tasks (inbox) pages have received a significant make-over that are sure to raise a few questions from end users that are working in the system every day.

Customer Accounts: cash application and collections get sharper

Most of what lands in Customer Accounts this release cleans up friction in write-offs, collections, and cash application rather than adding new capability.

The Customer Accounts Hub picks up a new Collections Overview: quick actions for write-offs, My Follow-Ups Due Now and Due Later, invoices with missing POs, and a performance card grouped by write-off reason. No setup required, but it changes where your collections team works, which makes it worth a fifteen-minute walkthrough before they find it on their own.

Cancel Write-off During Customer Payment Reversal closes a real gap. Today, unapplying a payment that triggered small auto-apply write-offs leaves those write-offs sitting on the invoice, and someone has to track them down and reverse them by hand. A new Cancel Associated Write-offs checkbox on Cancel Customer Payment and Unapply Customer Payment does that automatically. It requires setup and a security domain grant (Process: Customer Writeoff - Cancel), so it will not just appear on Monday.

Maintenance of reason codes has been significantly simplified by bringing them all into one new task called “Maintain Receivables Reasons”.

Tax Recovery on Customer Invoice Write-Offs does something similar for the tax portion of a write-off: opt in on tenant setup and Workday calculates and posts the recoverable tax separately instead of you adjusting the invoice by hand afterward. Read the exclusions before you flip it on. It does not apply when worktag balancing is enabled, when the invoice carries withholding tax, or when a third-party provider calculates your tax.

Then there is the one that will not announce itself: Workday renames the Customer business object within the Customer Accounts functional area to Billable Entity, to stop it colliding with the separate Customer object used elsewhere in the system.

Customer Contracts: this is where the real change is

Two of the four Customer Contracts features are focused on improving the Revenue Recognition capabilities, . The fourth changes how contracts get created.

Dynamic Standalone Selling Price and Revenue Allocation Rules replaces the static Fair Value price list with a configurable, formula-based rule builder for calculating SSP under ASC 606 and IFRS 15, including residual value logic for multiple-element allocation. If you run MEA across license, services, and usage lines with pricing that does not fit one flat list, this is a meaningful upgrade. If you allocate against a single static list today, the setup effort may not be worth it yet.

Non-Distinct Sales Item Indicator lets you flag a sales item as not a separate performance obligation and link it to the parent item it rolls into, which matters if you bundle services that do not stand alone for revenue purposes. Invoice Proposal Narrative Configurability adds dynamic tags that pull contract and invoice fields directly into narrative text, plus the ability to edit narratives during proposal review instead of kicking the whole thing back to draft.

The one to plan for is the Revenue Contract Agent. It reads an uploaded, signed contract document and drafts the customer contract in Workday: header fields, contract lines, a side-by-side annotated view linking each populated field back to the source PDF, plus a chat skill for asking questions about the contract you are viewing. It runs on Workday Flex Credits, needs its own security domain (Set Up: Revenue Contract Agent) configured before anyone can touch it, and Workday flags training as recommended for both end users and super users, which is not something they say lightly. If you already have a Contract integration with a third party system, this will not replace it. If your contract team manually enters contracts today, this is worth a pilot.

What to check before September 19

• Search custom reports, calculated fields, and integrations for the Customer business object inside Customer Accounts. The Billable Entity rename will not throw an error. Make sure that the reports still return what you expected, and that integrations still map to the right field.
• Do not assume "automatically available" means "no impact." The Collections Overview and the flattened remittance advice grid change what your AR team sees the moment the tenant updates, whether or not you configured anything.
• Confirm your tenant has Flex Credits allocated before you promise anyone a Revenue Contract Agent pilot. The agent also skips project, prepaid, and intercompany contract lines entirely, so scope your first test contracts accordingly.
• Check the write-off and tax recovery exclusions against how your team processes exceptions today. A feature that covers 90 percent of your write-offs still leaves the other 10 percent for someone to catch manually.

None of this needs an emergency change freeze. It needs someone to read past the one-line description, sort setup-required from set-and-forget, and clear the naming change before it becomes a support ticket. That review is a few hours of focused work on the tenant, not a project.

Working through your own 2026R2 heat map and want a second opinion on what is worth uptaking now versus later? Let's talk.