@CU21051339-0
this is a budget control configuration issue rather than a bug. the double-counting happens because purchase requisitions are mapped as a source document for both commitments and consumed budget simultaneously in your budget control setup.
three steps to fix it:
first go to budgeting → setup → budget control → budget control configuration → documents and journals section. check if purchase requisitions is selected as a source document for consumed budget — if it is, uncheck it. prs should only update commitments at approval stage. consumed should only update when the vendor invoice is posted as an actual cost.
second go to project management and accounting → setup → project management and accounting parameters → budgeting tab. verify the budget control settings are not forcing an immediate actual update on pr approval.
third if you are using encumbrance accounting ensure prs are mapped as pre-encumbrances and pos as encumbrances. if both are mapped to the same ledger staging the system reports prs as consumption.
if you already have erroneous consumed balances showing — run the budget control statistics or budget transaction detail report to identify the orphaned budget transactions, then use a budget adjustment journal to credit the consumed amount back. do not edit these values directly in sql — always use the standard budget register entry or budget adjustment journal.
hope that helps — feel free to mark as verified if it resolves the issue.
