Hey! We're using EBP and I'm looking into having A...
# general
e
Hey! We're using EBP and I'm looking into having Approvals on vendors' Bank Details record. If one edit a vendor's primary bank detail record we want it to require an approval before its bills show up under Bill Payment Processing in EBP. So far, the only solutions I've come up with is unticking EFT Bill Payment on the vendor. That does not feel very clean. Is there someway to add a filter on a custom field to the search? Seems like that is the case for Generate Bill Payment File but not for Bill Payment Processing.
p
NetSuite does not have native approval routing on vendor bank detail changes. The usual approach is to add a custom approval workflow on the Vendor record and drive a custom flag field that prevents it from showing in Bill Payment Processing until approved.
e
Yeah something like that is what I had in mind. But, I don't know how I would perform the filtering in the last step based on that flag. Would I use this method: https://docs.oracle.com/en/cloud/saas/netsuite/ns-online-help/section_3908470574.html?
g
Hi from another Geoffrey! Not sure if I can help directly, we were running into record qty limits with EBP so we ended up with a custom solution along side EBP. UI to search for bills and background tasks to create the PFA records, rest is EBP. Our payment team wanted to be able to temporarily exclude vendors so I was able to just add a field and update the query in our custom payment app. That addFilter looks promising but for some reason I get the sense that it would just be a selectable ui filter so users could choose whatever value they wanted there essentially bypassing i that control.
e
Thanks for the insights Pandorahiccup and Geo! I will try out that interface and see where it leads me.
🙌 1
r
I would just create a saved search for changes (edits) to Vendor bank details and have that sent to users or that they can run. Still meets the requirement for what Finance need. There is nothing native as stated and custom WF is the only option if you really need it.
m
We built our approval via workflow directly on the bank detail custom record. It marks them as secondary and inactive until approved.
e
Okay thanks @michoel! What happens when you approve it? Do you always set it to be a Primary Account?
In that case, using Global Payments could be problematic because vendors may require having multiple bank accounts.
m
We do because we don't use global payments. You could have workflow just set as inactive until approved.