Summary
This release makes pricing conditions easier to maintain and makes invoice-level discounts more accurate. The largest change is the meter property variable: a named list of values that you define one time. A pricing condition matches the list with IN or NOT_IN, so a list of hundreds of countries or SKUs no longer has a copy in each condition.
On invoices, an invoice-level discount can now include one-off lines, and Solvimon applies a fixed-amount discount one time for each invoice, not one time for each billing period. Domestic UK self-billing invoices now contain the tax note that HMRC requires. A wallet grant that Solvimon reverts now shows the reason, so you can tell a removed charge from spent balance.
For sales teams, a quote template now accepts JSON, HTML, Markdown, PPTX and POTX attachments, and a quote can have a name. Products, product items, pricing plans and quote templates now have a guidance field for AI agents, which Solvimon’s MCP server gives to an agent together with the catalog. Desk also gets a quantity input for one-off items, lifecycle actions for approval policies, and correct currency balances for wallets funded with an amount.
Pricing
A reusable list of values for a pricing condition
A meter property condition can now refer to a meter property variable. A variable is a named list of values that belongs to one meter property. The condition uses meter_property_variable_id and a comparator of IN or NOT_IN. It does not repeat the values inline. You therefore define a list of countries, SKUs or merchant ids one time. Each pricing item config that refers to the variable uses the same list.
To create a variable, use POST /v1/meter-property-variables. Send meter_property_id or meter_property_reference, and the initial values. A variable can contain a maximum of 10,000 values. To change the list, use PATCH /v1/meter-property-variables/{id}/values. The request contains an add set and a remove set. Solvimon applies the two sets as one change:
The response gives the result for each value in added, removed and skipped. Solvimon skips a value in add that is already in the list, and a value in remove that is not in the list. You can therefore send the same request two times and get the same list. GET /v1/meter-property-variables/{id}/values returns the list in pages. Each value has an added_at timestamp. The variable shows value_count and does not include the values. GET /v1/meter-property-variables therefore stays short when a list is long. You can expand meter_property_variable_id on a condition into meter_property_variable.
A change to the list changes which future events match. Solvimon does not reprocess events that it priced before the change. See Event reprocessing. Solvimon rejects DELETE /v1/meter-property-variables/{id} while a condition refers to the variable.
A quantity for a one-off item in the hosted checkout
A one-off item priced FLAT bills a unit price multiplied by a quantity. The schedule customization of the hosted pages now accepts units. This is the same quantity for each pricing item config that a pricing plan schedule already accepted. Send it in POST /v1/pricing-plan-subscriptions/init. A customer who buys through the hosted checkout can therefore order three units. POST /v1/invoices/preview shows the price of the three units before the customer confirms. Each entry contains a pricing_item_config_id and a number. If you omit a config, Solvimon uses its default_units. If default_units is not set, Solvimon uses 1.
Fixes
- When you override one pricing on a schedule, you no longer have to send the discounts, commitments and markups that you did not change. PATCH /v1/pricing-plan-schedules/{id} validated the clauses against the request body, not against the schedule. An override alone therefore failed with
discount applies to <pricing> but override for <pricing> is updated or removed. Solvimon now validates against the schedule. - GET /v1/pricing-plan-subscriptions/{id} now expands
pricing_plan_version_idfor a subscription on a rate card pricing plan. Before, the expansion returned no data for this plan type.
Invoices
An invoice-level discount applies to one-off lines, one time for each invoice
A one-off line that you add with POST /v1/invoices/{id}/lines can now use the invoice-level discounts of the subscriptions on that invoice. Set applicable_for_clauses to ["discount.totals"]. The line then counts towards the discount, and Solvimon applies the discount to the line. If you omit the field, the discounts do not include the line, as before. Use the field only for a one-off line on a regular invoice. A one-off invoice has no subscription clauses.
Solvimon now also applies a fixed-amount invoice-level discount one time for each invoice. Before, an invoice with a period billed in advance and a period billed in arrears got the full amount for each period. A 50 EUR discount therefore decreased the invoice by 100 EUR.
Domestic UK self-billing invoices contain the HMRC tax note
HMRC self-billing rules require a domestic UK self-billed VAT invoice to state whose output tax the VAT is. Solvimon now adds the tax note SELF_BILLING_UK_DOMESTIC to a self-billing invoice when the two parties are in the United Kingdom. The text of the note is “The VAT shown is your output tax due to HMRC”. Other self-billing invoices and other countries do not change.
A future invoice can take its date from finalisation
A subscription can start in the future and have its first invoice finalised in advance. Before, the invoice date was the start date of the subscription, also when the invoice date setting was WHEN_INVOICE_GOES_TO_FINAL. The invoice date is now the date on which Solvimon finalised the invoice. Your invoice numbers and your reporting periods therefore agree with the issue date. To change the setting through the API, use PATCH /v1/platforms/{id}.
Fixes
- Solvimon now validates an invoice number prefix that refers to a custom field when you save the configuration. The prefix supports
{{customer.custom_fields[reference]}}and{{billing_entity.custom_fields[reference]}}. Before, Solvimon resolved these references for the first time at finalisation. Solvimon now also prevents the rename or removal of a custom field that a prefix uses. - The self-billing invoice number settings now have a default. GET /v1/platforms/{id} returns the default for
self_billing_invoice_number_configurationandself_billing_credit_invoice_number_configurationwhen you did not set them. - The invoice PDF from GET /v1/invoices/{id}/pdf now shows the invoice number in its title, not the resource id. The tax details are now below the price details. The body text and the headings are larger. Bold text no longer breaks in the middle of a word.
Wallets and credits
A reverted grant shows the reason for the revert
A charge can issue a wallet grant. Solvimon reverts the grant when the charge no longer exists, for example when you shorten a schedule and Solvimon no longer bills its period. The grant now contains reverted_at and revert_reason, and the customer can no longer spend it. Read the two fields with GET /v1/wallet-grants/{id}.
revert_reason has one of these values: INVOICE_VOIDED, SCHEDULE_DATES_CHANGED, SCHEDULE_DELETED, SUBSCRIPTION_CANCELLED, SUBSCRIPTION_UPGRADED, SUBSCRIPTION_VOIDED, SUBSCRIPTION_CANCEL_UNDONE or WALLET_GRANT_REVERTED. A balance can decrease because the customer spent it, or because Solvimon removed the charge. The two fields identify the second cause. Before this release, a grant without a charge stayed funded and the customer could spend it. Grants that Solvimon reverted before this release have neither field.
Quotes
More file types on a quote template
A quote template attachment now accepts JSON, HTML, Markdown, PPTX and POTX files in addition to PDF. A quote that inherits the attachment accepts the same types. Your sales team can therefore send a presentation or a structured appendix through the quote portal. POST /v1/documents accepts these content_type values:
Solvimon accepts text/plain only when the document name ends in .md or .markdown, because editors frequently send that type for Markdown. Solvimon validates the content against the declared type, and rejects a macro-enabled PowerPoint file.
A name on a quote
POST /v1/quotes now accepts a name, as a subscription already does. A sales team with more than one quote for one customer can give each quote a name. The team does not have to identify the quotes by resource id.
AI and MCP
Guidance for AI agents on a catalog resource
Products, product items, pricing plans and quote templates now have an agent_context object with a guidance field of a maximum of 2,500 characters. The field contains free text for an AI agent, not for a customer: when to select this plan, what the item includes, and which deals it fits. Solvimon’s MCP server gives this text to agents together with the catalog metadata. An agent that selects a template or a plan therefore reads your intent and does not guess from names. Set the field with a PATCH on the resource, for example PATCH /v1/pricing-plans/{id}:
The same object applies to PATCH /v1/products/{id}, PATCH /v1/product-items/{id} and PATCH /v1/quote-templates/{id}. Desk has an input for the guidance on each of these resources. See Agent context.
Event ingestion
Fixes
- POST /v1/ingest/meter-data/{id}/delete now returns
deleted: true. Before, Solvimon deleted the event but returned the event as it was before the update. The response therefore showedfalse, while the next GET /v1/ingest/meter-data/{id} showedtrue. See Event ingestion API.
Desk
Desk shows a wallet funded with an amount as a currency balance
Desk now shows a CREDIT wallet type that is funded with an amount as a currency balance. This applies to the balance, the top-up and the deduction on the invoice line. More than one wallet can pay an invoice line, so each line lists the contribution of each wallet. Before, Desk showed each wallet as a quantity of credits.
Manage the lifecycle of an approval policy You can now create an approval policy as a draft and activate it when it is ready. You can deprecate or archive a policy that you no longer need. The actions are in the same context menu as for the other catalog resources. They use POST /v1/approval-policies/{id}/activate, POST /v1/approval-policies/{id}/deprecate and POST /v1/approval-policies/{id}/archive. You therefore do not have to edit a policy in place while it approves live traffic.
Refresh the custom fields on a final invoice
The refresh menu on a FINAL invoice now has the option “Refresh custom fields”, next to customer information, PO number and payment acceptors. Use it when a custom field with copy_value_to_invoice changed after you issued the invoice. Desk then copies the new value to the invoice. The API equivalent is POST /v1/invoices/{id}/refresh with CUSTOM_FIELD in types. See Refreshing invoice data.
A quantity for a one-off flat item
The subscription and quote screens now have a quantity input for a one-off item priced FLAT. Set the quantity when you add the item.
Fixes
- The audit log now shows the name of the user who made a change, not the user id. The same records are available from GET /v1/audit-records.
- The event filter now selects a meter by its reference, not by its name. Event ingestion also uses the reference.
- The events screen now separates the table from the detail panel. The filter no longer shows two clear buttons.