Inquire about purchase orders processed during purchase order year-end

2026 Release Wave 1 · Cash and Bank Management

Score 49/100 · MediumImpact MediumSwiss relevance NoneReleased

Dx365 Analysis

Our interpretation — not a Microsoft statement

What is changing?

Dynamics 365 Finance is adding a separate review page for purchase orders handled by the Purchase order year-end routine. It is expected to provide a consolidated view of the year being closed, the accounting date before and after processing, and the purchase order's post-process state.

Current state today

The standard year-end routine can move eligible open purchase order commitments into the following fiscal year and adjust relevant accounting dates. There is currently no purpose-built inquiry that gives finance teams a single list of the affected orders and their before-and-after dates. Consultants and users typically retain pre-run extracts, review batch output, compare accounting distributions, inspect individual purchase orders, or use custom reporting to establish what changed.

Future state after release

Finance users should be able to review year-end-processed purchase orders from one inquiry rather than reconstructing the result across documents and batch records. This should make exceptions, unexpected date movements, and document outcomes easier to identify. Based on the supplied scope, the underlying year-end calculation and posting behaviour are not expected to change.

Why it matters

The improvement reduces manual evidence gathering around purchasing commitments and gives period-close teams a more usable control point. It is most valuable for organizations that actively use purchase order year-end processing, particularly where open commitments are material or subject to formal audit review. Organizations that do not run this process will see little benefit.

Who is affected?

Finance controllersGeneral ledger accountantsAccounts payable leadsProcurement accounting teamsBudget control specialistsYear-end close coordinatorsInternal and external audit support teamsDynamics 365 Finance functional consultantsSecurity administrators

Consultant impact — Medium

The feature appears reporting-oriented rather than a change to year-end accounting logic, so implementation effort should be limited. Consultants should still verify enablement, security access, legal-entity behaviour, inquiry results, and alignment with established close controls. Customer procedures, training material, and audit evidence packs may need updating. Regression testing is especially relevant for customers using budget control, encumbrance accounting, or customized purchase order year-end reporting.

Likely required work

Confirm whether the customer uses the Purchase order year-end routine and therefore needs the inquiry.
Check availability and the applicable enablement method in the target Finance version.
Review which security roles, duties, or privileges provide access to the inquiry.
Test a representative year-end run containing carried-forward, closed, partially invoiced, and exceptional purchase orders.
Reconcile inquiry results against purchase order accounting distributions and existing year-end control reports.
Determine whether existing custom reports or manual close workbooks can be retired or simplified.
Update year-end procedures, audit evidence instructions, and user documentation where the inquiry is adopted.

Swiss relevance — None

The feature has no identified relationship to Swiss localization, Swiss VAT, payment formats, banking, ISO 20022, statutory reporting, or Swiss-specific compliance. Swiss organizations may benefit from the general audit trail, but that is not Switzerland-specific relevance.

What should customers do now?

Add the inquiry to 2026 year-end testing for customers that carry purchasing commitments between fiscal years.
Run UAT in a sandbox using a copy of realistic open purchase order data.
Validate whether records from year-end runs completed before feature activation are visible or whether only later runs are captured.
Compare the new inquiry with any Power BI reports, data exports, or customizations that currently provide similar evidence.
Avoid changing established close controls until completeness and security have been demonstrated.
Monitor release documentation because the supplied GA status and the future GA date of June 5, 2026 are not fully consistent.

Release Radar score — 49/100 (Medium priority)

This is a useful Finance control and auditability improvement with moderate value for customers using purchase order year-end processing. It should require limited implementation effort but warrants security and regression testing. Its audience is narrower than features affecting routine purchasing or general ledger posting, and it has no Swiss-specific dimension. The planned June 2026 availability keeps it relevant for upcoming release preparation.

Assumptions, not Microsoft-confirmed facts

The inquiry is read-only and does not alter purchase order year-end processing; the supplied description does not explicitly document processing changes.
The exact menu location, filters, export options, cross-company support, security artifacts, and data entities are not specified.
It is unclear whether historical year-end runs performed before activation will populate the inquiry.
The inquiry's behaviour for reversed, rerun, failed, or partially completed year-end jobs is not described.
The supplied status says Generally Available while the supplied general availability date is June 5, 2026; actual tenant availability should therefore be verified.
The practical value is assumed to be concentrated among organizations that use commitment or encumbrance-oriented purchase order year-end processes.

Microsoft information

Quoted from the release plan

Business value

This feature helps finance teams validate the purchase orders carried forward during year-end close without manually tracing each document. A dedicated inquiry shows the closed fiscal year, original and current accounting dates, and resulting document status, giving teams a clearer audit trail for purchasing commitments as they move across fiscal years. Finance users can use the information to support reconciliation, audit evidence, and period-close reviews with less manual investigation.

Feature details

The purchase order year-end process can update purchase order accounting dates and carry purchasing commitments into the next fiscal year. Finance users need a simple way to confirm which purchase orders were included in that process, understand how accounting dates changed, and see the resulting document status after year-end processing. With this feature, Dynamics 365 Finance adds a dedicated inquiry for purchase orders processed through Purchase order year-end. The inquiry is designed to help finance users review the year-end outcome without opening and investigating each purchase order individually. The inquiry shows the fiscal year that was closed, the original accounting date before year-end processing, the current accounting date after processing, and the resulting purchase order document status. Finance teams can use the inquiry during year-end close, reconciliation, audit preparation, and period-close review to confirm that purchasing commitments moved as expected and to investigate exceptions more efficiently.

Change history

Differences detected between scans

status03 Oct 2026
The release status moved from Generally Available to Released.
Previous
Generally Available
Current
Released
added12 Aug 2026
Microsoft added this feature to the Dynamics 365 Finance release plan.
Previous
—
Current
Generally Available

Back to Release Radar³