web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Finance | Project Operations, Human Resources, ...
Suggested Answer

Budget control re-triggered at PO creation from PR, despite prior budget approval and allocation

(3) ShareShare
ReportReport
Posted on by 94
Hello community !

Description:

We are facing a scenario where budget control is enabled across the full procurement process — from Purchase Requisition (PR) to Vendor Invoice.

 

In one particular case, a PR exceeded the available budget. A budget approval request was submitted and subsequently approved. Then, additional budget was allocated, and the PR was successfully approved.

 

However, after a significant delay, when converting this PR into a Purchase Order (PO), we encountered a new budget control blockage.

 

Question:

How can we allocate and reserve budget at the PR level and have that same budget commitment carried forward to the related PO, in order to avoid repeated budget blockages for the same transaction?

 

Any best practices or setup recommendations to maintain the initial budget commitment from PR to PO would be appreciated.

Categories:
I have the same question (0)
  • Suggested answer
    Holly Huffman Profile Picture
    6,554 Super User 2026 Season 1 on at
    Good morning, afternoon, or evening depending on your location!
     
    The issue you're facing occurs because budget reservations at the Purchase Requisition (PR) level don’t always automatically carry forward to the related Purchase Order (PO) in Dynamics 365 Finance and Operations. This can trigger a new budget validation when the PO is created, even though the initial budget was already allocated.
    Here’s how to ensure that the original budget commitment carries forward:
    1. Enable Budget Reservation Carry-Forward
    • Ensure that budget reservations are set to carry forward from PR to PO.
    • In Budget Control Parameters, check if Carry Forward Encumbrances is enabled to maintain commitments across documents.
    • If this setting isn’t active, the budget is validated again when a PO is created, possibly triggering another budget blockage.
    2. Verify Budget Allocation Timing
    • Budget reservations might expire or reset due to:
      • Time-bound budget periods: Ensure that the allocated budget hasn’t expired in a different fiscal year.
      • Reallocation of funds: If funds were moved post-PR approval, they might no longer be available when the PO is created.
    3. Use Encumbrance Accounting for Pre-Encumbered Amounts
    • If budget control is working with encumbrance accounting, confirm that pre-encumbrances at the PR level transition into full encumbrances at PO creation.
    • Verify that the encumbrance entry is not being reset or reversed when the PR transitions to a PO.
    4. Configure Financial Dimensions for Consistency
    • If budget control is applied per financial dimension, the system may trigger a new validation when converting the PR to PO.
    • Ensure that the same funding source, financial dimensions, and budget control parameters are maintained throughout the procurement cycle.
    5. Check Workflow Dependencies
    • Some organizations have workflows or manual approval triggers that require re-validation during PO creation.
    • If there’s an automatic budget check at the PO stage, consider adjusting workflow rules to bypass duplicate validation when a PO originates from an approved PR.
    Best Practices to Prevent Future Issues
    • Enable encumbrance tracking across procurement stages.
    • Monitor budget expiration timelines between PR approval and PO creation.
    • Standardize financial dimensions to avoid budget misalignment.
    • Ensure workflows support budget carry-forward rather than triggering re-validation.
    • Test encumbrance carry-forward behavior in a sandbox before full deployment.
     
    Please note: I teamed up with CoPilot AI to research and craft the best response to your question!
    Hope this helps some!
  • Suggested answer
    KamalKumar365sa Profile Picture
    10 on at
    @Mayouni - In our D365 system, we utilize both pre-encumbrance and encumbrance budgeting controls. When a purchase requisition (PR) line is created and approved, the system automatically reserves the budget amount as a pre-encumbrance. This reservation is immediately visible in pre-encumbrance tracking reports and reduces the available budget balance, while maintaining clear visibility of committed funds before they become formal obligations.
     
    We can add the unapproved line for our budget consume for budget control rules.
     
    Let me know still you have any doubt.
  • Suggested answer
    Abhilash Warrier Profile Picture
    7,585 Super User 2026 Season 1 on at
    Hi Mayouni,

    Have you tried the below options?

    If this helped, please mark it as "Verified" for others facing the same issue.
    Keep in mind that it is possible to mark more than one answer as verified.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > Finance | Project Operations, Human Resources, AX, GP, SL

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 661 Super User 2026 Season 1

#2
Giorgio Bonacorsi Profile Picture

Giorgio Bonacorsi 620

#3
Subra Profile Picture

Subra 473

Last 30 days Overall leaderboard

Product updates

Dynamics 365 release plans