I'm building a Suitelet (SuiteScript 2.1) that sends consolidated customer statements to parent customers via render.statement + email.send. The form has a "Statement Date" picker, an optional "Start Date" picker, and a checklist of eligible parent customers loaded from a saved search. I'm deciding whether to: Option 1: Hardcode openTransactionsOnly: true in the render.statement call — every statement sent through this tool shows only currently-owing transactions, matching what NetSuite's standard "Print Statements" page defaults to. Option 2: Add a "Show Only Open Transactions" checkbox to the Suitelet form (defaulting to checked) so the operator can flip it per-run. Questions: 1. In a typical AR workflow at an Australian wholesale business, when (if ever) would an operator legitimately need to send a full-history statement (including paid/closed transactions) rather than an open-items-only statement? Concrete scenarios, not theoretical. 2. Does NetSuite's standard customer-facing "Email Statement" button on the customer record expose this toggle, or is it hardcoded one way? What's the default behavior there? 3. Are there industry/audit norms (e.g., year-end statements, dispute resolution, reconciliation requests) where the full-history form is expected? 4. Given the answers above, would you recommend hardcoding or exposing the toggle? Why? Keep the answer concrete and grounded in real AR/NetSuite practice, not generic "flexibility is good" reasoning.

AI generated answer (using internal Slack threads):

1. In a typical AR workflow at an Australian wholesale business, an operator might need to send a full-history statement (including paid/closed transactions) rather than an open-items-only statement in a few scenarios. For instance, if a customer disputes a payment or if there is a need for a detailed audit trail for a specific customer. Another scenario could be when a customer requests a full transaction history for their records or for their own auditing purposes. 2. As per the conversations, it seems that NetSuite's standard customer-facing "Email Statement" button on the customer record does not expose this toggle. The default behavior appears to be using the form marked as Preferred, and it does not provide an option to select a specific statement transaction form. 3. Yes, there are industry/audit norms where the full-history form is expected. For instance, during year-end statements, dispute resolution, or reconciliation requests, a full transaction history might be required. This provides a complete picture of the customer's transaction history and aids in accurate reconciliation and auditing. 4. Given the answers above, I would recommend exposing the toggle. This is because there are legitimate scenarios where a full-history statement might be required. By providing the option to toggle between open-items-only and full-history statements, you can cater to these scenarios without having to modify the code each time. This would also align better with industry norms and auditing requirements. Remember, the goal is to make the tool as useful and flexible as possible for the operator, while still adhering to standard AR/NetSuite practices. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******