We have a requirement for a configurable pricing engine at contract level. The client wants to support index-based formulas such as: Base Price × ARENH Index × Contractual Coefficient, with potential caps/floors and contract-year logic (Y1, Y2, Y3 based on contract start date). SuiteBilling will be implemented for subscriptions and recurring billing. My questions are: 1. Can SuiteBilling natively support dynamic index-based pricing formulas per contract, where the rate depends on an external index value stored in the system? 2. Is there any standard capability (e.g., Effective Date Pricing, Zone Billing, Price Plans, Ramp Pricing, etc.) that would allow formula-driven updates of rates without custom scripting? 3. If not, would the recommended architecture be: ◦ A custom record storing contract-level pricing parameters, ◦ A custom index table storing index values by period, ◦ A Scheduled Script / Map-Reduce calculating the new rate, ◦ And automatic creation of Change Orders to update the Price Plan? 4. We are trying to determine whether this can be handled purely through standard SuiteBilling configuration, or if a custom pricing calculation layer is required.

AI generated answer (using internal Slack threads):

Based on the conversations provided, here are the answers to your questions: 1. SuiteBilling does not natively support dynamic index-based pricing formulas per contract where the rate depends on an external index value stored in the system. This functionality would likely require custom scripting and a custom record. 2. NetSuite does have an Effective Date Pricing SuiteApp that might be able to handle future pricing changes. However, it's not clear if this SuiteApp can handle index-based formulas without custom scripting. Other standard capabilities like Zone Billing, Price Plans, Ramp Pricing, etc., are not mentioned in the conversations provided, so it's not clear if they would allow formula-driven updates of rates without custom scripting. 3. The recommended architecture you proposed seems plausible based on the conversations provided. It involves a custom record storing contract-level pricing parameters, a custom index table storing index values by period, a Scheduled Script / Map-Reduce calculating the new rate, and automatic creation of Change Orders to update the Price Plan. However, this would likely require custom scripting. 4. Based on the conversations provided, it seems that this requirement cannot be handled purely through standard SuiteBilling configuration and would likely require a custom pricing calculation layer. ****** Disclaimer: This response was generated by an artificial intelligence assistant based on previous conversations from multiple Slack channels, and may contain inaccuracies or mistakes. ******