Is there a way to build an approval workflow for advanced intercompany journal entries?

AI generated answer (using internal Slack threads):

Based on the conversations, it seems that it is indeed possible to build an approval workflow for advanced intercompany journal entries in NetSuite. Here are some scenarios that were discussed: 1. You can add an accounting approval custom field (list type = employee) in the employee record and use this value to route the approval to a designated person as long as this designated person is someone else. 2. Use the employee's supervisor as the approver in the workflow. 3. Use different SOD (Segregation of Duties) based role than the JE (Journal Entry) creator to route approval. If your company doesn't have a specific approver for each accountant, but instead has multiple Accounting Managers that approve various JEs depending on which area it falls under during the month-end close, you can use roles in your workflow with the exception of the user who created the JE. If you don't have much experience creating workflows, you might need to seek help from someone who does, or learn more about it. You could potentially create the custom accounting approval field but use list type = role. In more complex scenarios, you might consider using a “parent workflow” that is your initial workflow. Then use the initiate workflow action to initiate the correct sub-workflow based on your criteria. Then you can make updates to independent “sub workflows” which are easier to visualize and comprehend because they just represent one branch of the overall workflow. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******

Yes, you can build a SuiteFlow approval workflow specifically for Advanced Intercompany Journal Entries. First, enable Setup → Accounting → Accounting Preferences → Approval Routing → Journal Entries. Then, create a workflow with RecordType(Transaction), Transaction Type(Advanced Intercompany Journal Entry), trigger(All or After Record Submit), Condition(Custom Approval = T) State(Pending Approval, Approved, and Rejected) Approve/Reject buttons, Next Approver logic, record locking, and email notifications as needed. One important point is that a workflow created for regular or legacy intercompany journal entries will not run on advanced intercompany journal entries. you need a separate workflow for the advanced record type, and NetSuite recommends having only one active approval workflow per journal-entry type. At first, build and test in Sandbox.