Purchase Order Approval Workflow

  • Purchase Order Approval Workflow

    Posted by DSC Communities on April 11, 2019 at 5:21 pm
    • David Spangler

      Member

      April 11, 2019 at 5:21 PM

      Hello:Ā 

      I would like to create a Purchase Order Approval Workflow for a client where the PO will not go back to being required to be reapproved, after having been initially approved based solely on the criterion of the PO amount. Ā 

      The scenario is this — for PO’s over $500:Ā 
      1.Ā  PO’s over $500 go to one individual for approval. Ā Ā 
      2.Ā  Approver approves the PO
      3.Ā  Receipt is performed.
      4. Accounting gets invoice, which includes, e.g., an additional misc fee or shipping.Ā 
      5. Accounting reopens the purchase order and adds the charge.
      6. Accounting posts the invoice.Ā 

      The issue is that when Accounting reopens the document to enter the miscellaneous charge, then the PO goes back through the approval cycle:
      Ā  — it is queued back to the approver. Ā  Because the PO has already gone once through the cycle, essentially it is good to go and the organization does not want to have it have to be reapproved.Ā 

      Any ideas welcome as to how to accomplish without a customization but through just steps in BC, changes to the workflow or otherwise.
      See attached workflow as currently set.

      Thanks,

      ——————————
      David Spangler
      Velosio
      Dublin OH
      ——————————

    • Amanda Mayer

      Member

      April 12, 2019 at 7:44 AM

      ,

      If you change your Invoicing process to utilizing the Purchase Invoice with the Get Receipt Lines functionality, you will not need the additional PO approval. Additionally, it will provide Segregation of Duties. Your AP Clerks should not have access to the PO since there is no field level security. It allows (appropriate) price changes? and additional charges to be added without having to mess with the PO. Below is a link to the Microsoft Docs that explains this process.

      https://docs.microsoft.com/en-us/dynamics-nav-app/purchasing-how-to-combine-receipts

      ——————————
      Amanda Mayer
      New View Strategies
      Milwaukee WI
      ——————————
      ——————————————-

    • David Spangler

      Member

      April 12, 2019 at 9:20 AM

      Thanks so much, I’ll run this solution by the client, and I believe this is it!

      Thank you again.

      Dave Spangler

      ——————————
      David Spangler
      Velosio
      Dublin OH
      ——————————
      ——————————————-

    • David Spangler

      Member

      April 12, 2019 at 9:48 AM

      Amanda:Ā 

      In finishing this process off, I do notice that the PO remains in the PO’s list.Ā  It does not get removed from the purchase orders list. Ā Ā  Is there a way that the PO can close and be removed from the PO’s list? Ā  Ā  I see the behavior in both NAV 2017 and in BC Cloud, but this seems to be a bug.Ā  I’ll look into it further but appreciate insight into it.

      Thanks,Ā 

      Dave

      ——————————
      David Spangler
      Velosio
      Dublin OH
      ——————————
      ——————————————-

    • Amanda Mayer

      Member

      April 12, 2019 at 9:52 AM

      ,

      That is correct. At the bottom of that link it explains the Delete Invoiced Purchase Order function needs to be run. Most companies will put that in a nightly or weekly job queue to update the PO list.

      Regards,?

      ——————————
      Amanda Mayer
      New View Strategies
      Milwaukee WI
      ——————————
      ——————————————-

    DSC Communities replied 7 years, 1 month ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘Purchase Order Approval Workflow’ is closed to new replies.

Start of Discussion
0 of 0 replies June 2018
Now

Welcome to our new site!

Here you will find a wealth of information created for peopleĀ  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!