D365 Finance & Operations and Dynamics AX Forum

Expand all | Collapse all

AP invoices in workflow pending approval fail after month is closed

  • 1.  AP invoices in workflow pending approval fail after month is closed

    Posted 21 days ago
    I have seen much older posts posing this question, but so far am unable to find a documented solution. And I rather prefer not reinventing the wheel. We are running AX2012 R3 CU13.

    When AP invoices linger pending approval over a month-end, once the approval is given the system fails with the error Stopped (error): Posting of order  canceled.  Fiscal period mm/dd/yyyy is not open.

    Is there configuration or a process already available that would signal the system to reset the posting date to the current date and process without error? In effect, when we recall and resubmit the invoice this is what we are doing. This also creates confusion for the approver as they wonder why they are approving this multiple times.

    I have seen documentation pertaining to KB2852252 indicating 'The accounting date of any document such as the Travel & Expense report can be updated automatically to the next fiscal period open date.' We applied this KB long before our upgrade to R3 but this did not resolve our pending AP invoices issue.

    Thanks for your help,
    Paula

    ------------------------------
    Paula Richardson
    Performance Contracting Group, Inc.
    Lenexa KS
    ------------------------------
    Conference-AXUG_200x200


  • 2.  RE: AP invoices in workflow pending approval fail after month is closed

    GOLD CONTRIBUTOR
    Posted 21 days ago
    Have you considered this KB?

    https://fix.lcs.dynamics.com/Issue/Details/1207916?kb=3200349&bugId=3788630&dbType=0&qc=d6f0ea1a7ea7af80e1af60abfc26236f72ffb02d29f1d65bfb2943550c9f5845

    ------------------------------
    Ian Gorman, PMP, MCSE
    Senior Consultant
    ------------------------------

    Conference-AXUG_200x200


  • 3.  RE: AP invoices in workflow pending approval fail after month is closed

    SILVER CONTRIBUTOR
    Posted 21 days ago
    we had similar issue in R3 and this KB fixed it indeed

    ------------------------------
    S. Ayachi
    Ottawa ON
    ------------------------------

    Conference-AXUG_200x200


If you've found this thread useful, dive deeper into User Group community content by role