The following setup uses Flows, Bill Through Date Override, Override Next Billing Date, and Evergreen Subscriptions to create a subscription that is invoiced weekly.
Limitations:
Setup:
Add a field to the Order Product to indicate a weekly invoiced subscription. If needed, add the same field to the Quote Line and Product so it twins to the Order Product. See Mapping Custom Fields Between Objects. For this set up, use a Checkbox field called Weekly Invoicing where True indicates a weekly invoiced product.
Set up the Product as follows:
Flows:
Pricing:
If the desired outcome is a consistent price week to week, then set the Billing Configuration Settings for Proration Type to either 30 Days or Monthly (CPQ Formula). The setting Calendar Days cause small variations week to week depending on the number of days in the month. Note that this is a global setting and affects all proration in your org.
To price a product based on a weekly price, set up an effective daily price. Use the Proration Type setting = 30 Days and set the Product up this way:
-Subscription Term= 1
-Subscription Pricing = Fixed Price
-Subscription Type = Evergreen
-Standard Price = [Daily Price x 30]. Note that because we are working around the existing billing frequency we are actually setting the 30-day price for a 30-day period. In other words, setting the standard price to 300.00 returns a weekly price of 70.00.
If you want to show the weekly price to your users in the Quote Line editor, create and expose a custom formula field with the formula:
[Net Total * (7/30)]
Validation Rule:
Consider setting up a validation rule on the Product that enforces the correct setup for a weekly product.
Testing:
Build this out in a full sandbox and test thoroughly before pushing to production to make sure your implementation works as expected with this setup.
Suggested tests include Bill Now, Invoice Schedulers, and Cancel and Rebill.
000389735

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.