Skip to content

Commit 317c982

Browse files
authored
Update purchase-requisitions-cannot-released.md
1 parent 171af28 commit 317c982

1 file changed

Lines changed: 18 additions & 29 deletions

File tree

support/dynamics-365/supply-chain/procurement/purchase-requisitions-cannot-released.md

Lines changed: 18 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -12,43 +12,32 @@ ms.date: 02/25/2025
1212
# Purchase requisitions created before the current fiscal year cannot be released
1313

1414
## Symptoms
15-
In Dynamics 365 Finance & Supply Chain Management (D365 F&SCM), Purchase Requisitions (PRs) that are submitted at the end of one fiscal year and approved in the new fiscal year encounter an issue when converting them into Purchase Orders (POs). The system throws the following error:
16-
"Purchase requisition line was pre-encumbered in a fiscal year that is different from the accounting date of the purchase order. Hence, purchase order cannot be created."
15+
In Dynamics 365 Finance & Supply Chain Management (D365 F&SCM), Purchase Requisitions (PRs) that are submitted at the end of one fiscal year and approved in the new fiscal year encounter an issue when converting them into Purchase Orders (POs). The system throws the following error:
16+
1717
"Purchase requisition line was pre-encumbered in a fiscal year that is different from the accounting date of the purchase order. Hence, purchase order cannot be created."
18-
1. Pre-Encumbrance Issue
19-
When a purchase requisition is approved, it creates a pre-encumbrance in the system to reserve budget funds.
20-
If the requisition was submitted in the previous fiscal year, the pre-encumbrance is tied to that year’s budget.
2118

22-
2. No PR Rollover Functionality
19+
## Cause
20+
1. Pre-Encumbrance Issue
2321
When a purchase requisition is approved, it creates a pre-encumbrance in the system to reserve budget funds.
22+
If the requisition was submitted in the previous fiscal year, the pre-encumbrance is tied to that year’s budget.
23+
However, when attempting to convert the PR into a PO in the new fiscal year, the system detects a mismatch because the pre-encumbrance belongs to the old fiscal year, but the purchase order is being created in the new fiscal year.
2424

25-
If a PR remains open at year-end, it cannot be carried over automatically into the new fiscal year
2625
2. No PR Rollover Functionality
27-
Recommended Solutions & Best Practices
28-
This restriction ensures that budgets and financial commitments remain aligned with fiscal year policies.
29-
30-
## Workarounds
31-
1. Cancel Open Requisitions at Year-End
32-
Before the fiscal year-end closing, identify all open purchase requisitions.
33-
Cancel any unapproved or pending PRs that have not yet been converted into purchase orders.
34-
Create new purchase requisitions in the new fiscal year, ensuring they align with the correct budget year.
35-
This avoids the issue altogether by ensuring that new requisitions are processed within the correct fiscal period.
36-
37-
2. Convert PRs to POs Before Fiscal Year-End & Roll Over POs
38-
39-
## Workarounds
40-
41-
The best practice is to either cancel open PRs at year-end or convert them into POs before the fiscal year closes. This ensures smooth procurement processing without encountering fiscal year mismatches. Since D365 does not support PR rollovers, organizations should proactively manage requisitions as part of their year-end closing procedures.
42-
43-
44-
26+
D365 does not support purchase requisition rollovers across fiscal years.
27+
If a PR remains open at year-end, it cannot be carried over automatically into the new fiscal year.
28+
This restriction ensures that budgets and financial commitments remain aligned with fiscal year policies.
29+
30+
## Workaround
31+
1. Cancel Open Requisitions at Year-End
32+
Before the fiscal year-end closing, identify all open purchase requisitions.
33+
Cancel any unapproved or pending PRs that have not yet been converted into purchase orders.
34+
Create new purchase requisitions in the new fiscal year, ensuring they align with the correct budget year.
35+
This avoids the issue altogether by ensuring that new requisitions are processed within the correct fiscal period.
36+
37+
2. Convert PRs to POs Before Fiscal Year-End & Roll Over POs
4538
Instead of leaving PRs open, convert them into purchase orders before the fiscal year closes.
46-
4739
If the PO needs to be received or invoiced in the new fiscal year, leverage the rollover functionality for purchase orders.
48-
4940
This ensures that financial commitments are properly managed across fiscal years.
5041

51-
52-
5342
The best practice is to either cancel open PRs at year-end or convert them into POs before the fiscal year closes. This ensures smooth procurement processing without encountering fiscal year mismatches. Since D365 does not support PR rollovers, organizations should proactively manage requisitions as part of their year-end closing procedures.
5443

0 commit comments

Comments
 (0)