What are all the impacts of enabling the Consolidated Payments feature? What are some gotchas and side effects that could potentially affect our accounting, our users, the way we use transactions, our scripts and other processes, or our data? Our account is multi-subsidiary, and we're trying to query the following fields, which we are told aren't available without the Consolidated Payments feature, so we're considering turning it on for the main reason of just being able to query those fields: SELECT balance, currency, customer, depositbalance, overduebalance, overridecurrencyformat, unbilledorders FROM customercurrencybalance

AI generated answer (using internal Slack threads):

Based on the conversations, enabling the Consolidated Payments feature in NetSuite has several impacts: 1. Multi-Subsidiary Customers: If you want to use the Consolidated Customer Payments feature, you must enable Multi-Subsidiary Customers. This means that if a customer is associated with multiple subsidiaries, you need to maintain a single customer record and add the additional subsidiary when required. However, this might conflict with the requirements of some credit card processing companies, which may require you to duplicate the customer and assign the primary subsidiary accordingly. 2. Payment Application: The Consolidated Payments feature allows one deposit to be applied against multiple customer accounts that are part of the same customer group. This can simplify the payment application process if you have many customer payments that need to be applied across many child-level customer records. 3. Currency Conversion: Enabling the Consolidated Payments feature can affect how transaction amounts are consolidated in a multi-currency environment. NetSuite will convert any transaction amount to the highest-level subsidiary a user has access to. This is a consolidated conversion, not a transactional one, and it uses the Consolidated Exchange Rates that are in effect as of the current period. This might not align with your expectations if you expect the conversion to be done at the rate when the transaction happened. 4. Saved Searches: When running a saved search, NetSuite converts your results to the highest-level subsidiary you have access to. This is a consolidated conversion, not a transactional one. If you don't want any conversion to occur, you have the option of editing your saved search and setting a field to "None". Please note that these impacts are based on the specific use cases discussed in the conversations and may not cover all possible impacts of enabling the Consolidated Payments feature. Always thoroughly test any changes in a sandbox environment before implementing them in your live account. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******