Rate cards
A rate card is a pricing plan designed to be shared across many subscriptions. You link subscriptions to the rate card itself rather than to a specific version, so when you publish a new version, every subscription automatically uses the updated prices.
Rate cards vs. pricing plans
A rate card behaves like a standard pricing plan. You configure pricing items, charge types, and pricing groups the same way, with a few key differences:
Versioning
Like pricing plans, rate cards are versioned to maintain an audit trail and history of pricing changes over time. Rate card versions differ in how they are scheduled:
- Each version has a start date that determines when it becomes applicable.
- A version can be edited as long as it has not started yet. Once its start date has passed, the version is finalised.
- There is no separate end date. A version remains in effect until a later version’s start date is reached, at which point the later version takes over.
Discounts and overrides
Rate cards currently support total-level discounts, commitments, and markups only. The following are not available on rate cards:
- Discounts, commitments, or markups applied at the invoice, product, revenue item, or condition level
- Coupons
- Pricing overrides
For developers
Create a rate card
To create a rate card, call the Create pricing plan endpoint with the RATE_CARD variant:
The variant field distinguishes a rate card (RATE_CARD) from a standard pricing plan (DEFAULT).
Create a rate card version
A rate card version includes a start date that determines when it becomes applicable. Create it with the Create pricing plan version endpoint, referencing the rate card in pricing_plan_id:
Add pricing_categories to the request to configure pricing items, exactly as you would for a standard pricing plan version.
The start_at date must be after the previous version’s start date and cannot be in the past.
Link a rate card to a subscription schedule
To attach a rate card to a subscription, call the Create pricing plan schedule endpoint, referencing the subscription in pricing_plan_subscription_id and the rate card in pricing_plan_id. Omit pricing_plan_version_id; Solvimon resolves the applicable version at processing time:
For standard pricing plans, reference a specific pricing_plan_version_id instead.
Need more help?
Reach out in your Solvimon support Slack channel. Our team is available for questions at any stage of the integration.