Payment Journal Workflow has greyed out the "Generate Payment" option

Payment Journal Workflow has greyed out the “Generate Payment” Button on Vendor Payment Journal. Can someone please advise why the workflow can grey out the button? and how it can be operational again?

are the methods of payment setup appropriately? can you send screenshots of the method of payment setup?

yes, this is the out of the box behaviour.

If a vendor payment journal has a workflow attached to it, only once the workflow is APPROVED, the [Generate Payment] button becomes enabled.

This follows the standard business flow:

  1. Accountant created a payment journal (intention to pay)
  2. The payment journal is approved by a manager
  3. Only than the accountant can make the payment (–> press the “General Payment” button which controls both printing checks and paying using ACH)

Hi,

I am facing the same issue. Even after the invoice is approved now, Generate payments option is disabled. Kindly help!

Many thanks

I’ve run into this before , usually when the workflow status or user permissions aren’t fully aligned. A couple of things to check:

  • Make sure the payment journal workflow is fully completed/approved (sometimes it needs a refresh).

  • Verify the user role has rights to generate payments after approval.

  • If batch jobs are stuck, re-running the workflow infra often fixes it.

For one of our customers, once the workflow finished properly and roles were set right, the button became active again. Might work for you too.

You can also reach me at hardik.gupta@allgrowtech.com if you want to discuss it in detail.

thanks! I checked. Workflow is fully completed and I have system admin role. :frowning:

Thanks for checking that! Since the workflow is completed and you already have the system admin role, the issue could be tied to something else:

  • Sometimes the workflow history/messages still hold stuck records; clearing/restarting them can help.

  • It may also be linked to method of payment or bank setup not being properly tied to the vendor or journal.

  • In one case we saw, re-running the workflow infrastructure config after clearing old batch errors made the button active again.

It worked for one of our customers, but of course, your setup might differ. Worth giving it a try.