what does the procurement payment run approval process look like ?

AI generated answer (using internal Slack threads):

The procurement payment run approval process in NetSuite can be customized to fit the needs of your organization. Here's a general overview based on the conversations: 1. Approval Routing for Vendor Payments: NetSuite provides an option under Accounting Preference - Approval Routing for Vendor Payments. This allows you to set up an approval process for bill payments, making the transaction non-posting until it is approved. However, this is only applicable for checks and not for EFTs. 2. Role-Based Approvals on Vendor Bills: You can use standard, role-based approvals on vendor bills. This allows for a multi-layer approval process. However, if you need to see line-level detail and not just header (i.e. line-level dept and GL accounts) during the approval process, you might need to create a new, scripted page, possibly a Suitelet. 3. Workflow for Customer Payment Approval: You can set up a workflow for customer payment approval. However, this will not stop the transaction from getting posted as customer payment is a posting transaction. Alternatively, you can create a saved search to email key people when a customer payment is created. They can then open the transaction and either delete or query about it. 4. Custom Record for Unapproved Customer Payments: You can create a custom record for unapproved customer payments and have a script that generates the posting payment once the custom record has been approved. This can be a bit complicated if you haven't implemented a custom record before. 5. Custom GL Impact: You might be able to use a native payment record and a Custom GL Plugin to reverse the GL impact until a custom approved field is checked. However, this could have negative impacts if not used correctly. 6. Custom Transaction: You can create a custom transaction that can manage posting to GL's very easily with posting statuses. However, this would require an additional step to apply it against an invoice and could lead to cash application issues. Remember, the best approach depends on your specific needs and the complexity you're willing to manage. Always test any changes thoroughly before implementing them in a live environment. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******