Skip to navigation

October 28, 2026

Summary

Happy Halloween. This release has no tricks, only treats. Its theme is this: you see the result before you commit, so no surprise waits for you afterwards.

Preview the invoice of a plan change before you make the change. The preview is available from your integration and from the customer portal. Your upgrade screen can show the amount, and the customer decides with the number in front of them.

Solvimon refuses a wallet grant that it cannot book at the moment you create it, not later in accounting. Desk hides the actions that a role does not permit. A user no longer finds a permission limit on an error page.

Quotes receive three features that sales teams asked for:

  • Mandatory signing. You can require a signature before a customer accepts a quote.
  • Ramps. You can sell a ramp of consecutive schedules on one subscription, each step on its own plan version.
  • Templates on upgrades. You can start an upgrade quote from a quote template, so it uses the same defaults as a new quote.

You can upload a usage file of up to 2 GB directly to storage, and Solvimon processes it from there. Workflows can tag the emails that they send, and they can export to each ERP that you have connected.

Quotes

Signing can be made mandatory A platform can require a signature before a quote is accepted. Set quote_settings.signing_required on the platform for the default. Set signing_required on a quote template to override it for the quotes built from that template. A quote version resolves the value and reports it read-only, so a single quote cannot switch signing off. The template’s value wins when the quote has a template that sets one. The platform default applies otherwise. Both default to false, so a platform that does not configure signing is not affected. See Quote templates.

A quote can carry a ramp of consecutive schedules POST /v1/quotes/init takes a pricing_plan_schedules list on a subscription, where it took a single pricing_plan_schedule. Each entry is one step of the same subscription, priced on its own plan version. This is how you sell a multi-year ramp: year one discounted, years two and three at full price. A schedule can now also end before the subscription’s initial term ends, so the first step does not have to run the full term. The singular pricing_plan_schedule still works. Validation errors name the schedule by its index only when the request used the list. See Quotes.

The upgrade flow takes a quote template POST /v1/quotes/upgrade accepts quote_template_id, so an upgrade quote starts from the same commercial defaults as a new one. Desk offers the template picker in the upgrade flow. An id that does not resolve to a quote template on the platform answers 404. See Upgrade quotes.

Fixes

bug-fix
  • A subscription that is canceled, or has a cancellation scheduled, no longer offers the upgrade quote flow. The quote it produced could not be acted on.
  • Quote PDFs break between pages where the content allows it. The billing period is left out of a schedule when it matches the pricing period.

Subscriptions

Preview the invoice a plan change produces POST /v1/invoices/change-plan/preview returns the invoice a plan change creates at the start of the new schedule, and changes nothing. The body is the one that change-plan takes, with the subscription named in it. It holds pricing_plan_subscription_id, the target pricing_plan_id, an optional start_at and an optional billing_period. The group’s timing policy resolves the start exactly as the change itself does. A NEXT_BILLING_PERIOD policy previews the invoice of the next period. An immediate policy previews the invoice of the change. Running discounts and coupons on the current schedule are carried into the preview. An upgrade screen can show the amount before the customer commits. Until now, you had to make the change and read the invoice afterwards. The call needs the INVOICE.PREVIEW permission.

The customer portal has the same route at POST /v1/portal/invoices/change-plan/preview, limited to the subscription the session is scoped to.

A schedule’s overridden pricing follows the plan version’s entitlements An entitlement added to a pricing on an active plan version now reaches the schedules that override that pricing with SPECIFIC. Those schedules kept only the entitlements the override held when it was created, so a feature added to the plan never arrived for customers on custom pricing. You can also reset a schedule’s entitlement overrides with PATCH /v1/pricing-plan-schedules/{id}, which puts it back on the version’s own entitlements. See Custom pricing.

Fixes

bug-fix
  • Copying a subscription or a schedule copies its override pricings and the discounts that target them. The copy dropped overrides priced per currency or per billing period, and the request still answered 200.

Customer portal

Checkout asks for a phone number The checkout form has a phone number field. The customer enters it as a single input with the country dialing code in it. Labels are hidden where the field explains itself, so the form stays short on a payment terminal or a phone.

Fixes

bug-fix
  • Charging on-demand pricing items with finalize_immediately works on a platform that holds invoices for approval. The one-off invoice is finalized without going through the approval policy. Before, the call answered 422 saying the invoice was not FINAL and left a DRAFT invoice behind on every attempt. An invoice that cannot be finalized now answers a validation error naming finalize_immediately and the status it reached.

Invoices

Invoices follow a change of payment acceptors on the subscription Changing the payment acceptors on a subscription refreshes the payment methods on its OPEN, DRAFT and FINAL invoices. Invoices in any other status are left alone. Before, an invoice offered a method that you had withdrawn, or missed a method that you had added, until you updated each invoice by hand. See Payment options.

Fixes

bug-fix
  • A one-off invoice created without a payment method no longer picks up the billing entity’s payment acceptor on its own. The invoice offered a method the caller did not ask for.

Payments

Your own beneficiary name on the invoice’s bank details A payment acceptor takes an optional beneficiary_name. When set, it is used as the legal_name in the invoice’s payment_actions[].bank_account. It replaces the billing entity’s legal name, or the customer’s organization legal name on a self-billing invoice. A platform that collects through an account held in a different name can print that name on the invoice without changing its billing entities. Leave it out and nothing changes. See Payment options.

Wallets and credits

A wallet grant that cannot be booked is refused when you create it POST /v1/wallet-grants validates paid_amount against the grant. Its currency must equal grant_amount.currency. Its quantity cannot be negative and cannot exceed grant_amount.quantity, because the promotion is the difference between the two and a negative promotion cannot be booked. A credits grant takes no paid_amount at all, because a credit has no exchange rate to book the difference with. An unpaid grant defaults to the grant’s own currency. These configurations previously failed later, inside accounting, far from the call that caused them. See Credit types and wallets.

Pricing

Price caps keep the precision you configure A pricing band’s minimum_amount and maximum_amount are stored at the precision you send, instead of being rounded to the currency’s decimals. A cap of 0.005 EUR on a percentage price stays 0.005 EUR, where it was stored as 0.01 EUR without warning. A platform that prices in fractions of a cent, such as payment and interchange fees, can set a floor or a ceiling the currency has no unit for. See Flexible pricing.

Meters

A required meter value or property can be made optional PATCH /v1/meters/{id} accepts required going from true to false on a meter value or meter property of an ACTIVE meter. Events already ingested keep their values. Events that arrive without the field are accepted from that point on. This also makes it possible to remove a field that nothing references. Make the field optional, then remove it in a second update. Deleting a field that is still in use stays blocked. Desk allows the same change on the meter form.

Event ingestion

Upload a usage file of up to 2 GB straight to storage POST /v1/files with source: "BUCKET" answers with a signed upload link instead of taking the file’s content in the request body. Upload a gzipped CSV to that link, then call process. Solvimon ingests up to 2 GB compressed and 5,000,000 lines per file. The content never passes through the API, so a retry re-sends only the upload. line_counts reports how many lines were done, not matched, duplicate or in error. A result file gives the outcome per line. See Large event file uploads.

Workflows

Tag the emails a workflow sends The “send email to customer” action takes up to three free-text tags in send_email_to_customer.tags. Each tag is ASCII and at most 128 characters. Desk exposes them on the action form. The tags travel with the message, so you can identify the emails of one workflow in your email provider’s reporting. See Workflow actions.

Export to ERP offers every connected ERP The “export to ERP” action lists the accounts of every connected ERP integration, where it listed only Exact Online. Any ERP you have connected now appears in the integration picker: Exact Online, NetSuite, Xero, Dynamics Finance, Dynamics Business Central, QuickBooks, Rillet and Campfire.

Reporting

A conditions column in the invoice report The invoice report carries a conditions column. It is resolved the same way as the comparator column the usage report already has. A line priced through a condition says which condition applied, without a second report to cross-reference.

AI and MCP

Download a quote’s PDF from its card The quote card an AI client renders has a download action, as the invoice card does. It also shows the quote’s deal metrics and its signers.

Desk

Desk shows only the actions your role allows Actions and pages a user’s role does not permit are no longer offered. A Quote Viewer no longer sees Accept on a final quote or Cancel approval request on someone else’s quote. A Customer Draft Contributor no longer sees Save and activate when adding a customer. Publishing a draft pricing plan version, through Activate subscription or through the schedule editor, is offered only to users who may publish one. Before, clicking through to a permission error was the only way to find out. See Roles and permissions.

Insights dashboards carry a chat A Dynamic Insights dashboard has the AI chat next to it, so you ask a question about a graph where the graph is.

Variables moved under Meters The Variables screen is a tab on the Meters page rather than a separate entry. This puts meter property variables next to the meters they belong to.


October 21, 2026

Summary

This release makes group contracts and self-service plan changes first class. A parent can sign one quote that covers several forward-billed subsidiaries. A customer can move between the plans of a pricing plan group without a support ticket, from your integration or from the customer portal. A checkout for physical goods collects the delivery address in the same flow and attaches it to the subscription. Desk gains a ⌘K search over every page, record and action.

Quotes

A quote version can hold several subscriptions A quote version is no longer limited to one subscription. POST /v1/quotes/init takes a pricing_plan_subscriptions list. Each entry has its own pricing plan schedule. The quote version reports all of them in pricing_plan_subscription_ids and pricing_plan_subscription_infos. One customer signs, and the others are forward billed against it. This is how a group contract is usually sold: the parent signs for the subsidiaries, and each subsidiary is invoiced separately. The deal metrics already report per subscription, so the totals on a multi-subscription quote need no extra call. The single-valued pricing_plan_subscription_id and pricing_plan_subscription_info still work and are deprecated. See Quotes.

Subscriptions

Move a subscription to another plan in its group POST /v1/pricing-plan-subscriptions/{id}/change-plan moves a running subscription to a sibling plan in the same pricing plan group and returns the schedule it created. The body takes the target pricing_plan_id and an optional start_at. Add billing_period when the new plan is billed on a different cycle. If you leave billing_period out, the current period is kept.

The group decides when the change takes effect, so the same call is correct for an upgrade and for a downgrade. upgrade_type, downgrade_type and cancellation_type each take IMMEDIATE, IMMEDIATE_PRO_RATA, NEXT_BILLING_PERIOD or NOT_ALLOWED. start_at is accepted only for the two immediate policies. The change needs PRICING_PLAN_SUBSCRIPTION.UPDATE and PRICING_PLAN_SCHEDULE.CREATE. See Plan changes.

A subscription carries the address its goods go to default_shipping_address_id on a subscription names an ACTIVE shipping address of the same customer. Set it to null to clear it. A customer that takes the same product at more than one location can keep a subscription per address, and each renewal ships to the right place. You cannot delete an address while a subscription points at it.

Customers

A shipping address can be created ready to use POST /v1/shipping-addresses now takes status: DRAFT, as before, or ACTIVE to skip the activate call. A system that already knows its addresses are good no longer makes two calls per address. DEPRECATED is refused on creation. status stays read-only on PATCH: use activate and deprecate. See Shipping addresses.

Collect a shipping address during checkout A hosted checkout page can ask the buyer for a delivery address. Turn it on per checkout page in Desk, next to the success URL and the terms. The portal’s authorize call then accepts shipping_address_details in the init_pricing_plan_subscription context: a reference, a recipient and an address. Solvimon upserts the address on the customer the checkout resolves to and attaches it to the subscription it creates. A merchant selling physical goods gets the address and the subscription in one flow. A checkout that sells software is unaffected. The portal also has its own read and deprecate endpoints for the addresses of the customer the link belongs to.

Customer portal

A customer can change their own plan The portal exposes the same plan change as the API, limited to the subscription the link belongs to. A buyer can move between the plans of a pricing plan group under the group’s own timing policy. A transition the group marks NOT_ALLOWED is refused, not hidden. See Self-serve plan changes.

Invoices

Fixes

bug-fix
  • Adding a one-off line without a pricing_band answers 400 and names the field. A FIXED or FLAT line without one returned 500.
  • “Request usage report” is hidden on VOID and ARCHIVED invoices. No usage is billed on a voided invoice, so the report held only its header row.

Payments

Your own text on the customer’s bank statement A payment acceptor configured for Adyen takes two optional settings. shopper_statement is the text the customer sees on their bank statement. metadata is a list of key and value pairs sent with the payment. Both are templates, so {{invoice.invoice_number}} puts the invoice number on the statement and into the Adyen settlement report, which carries no merchant reference of its own. Reconciling a settlement file against invoices no longer needs a separate lookup. Neither setting has a default, so platforms that do not configure them are unaffected. Both are editable in Desk on the payment acceptor.

An abandoned payment closes itself Solvimon now acts on Adyen’s offer-closed notification. When a buyer leaves an iDEAL or other redirect payment and Adyen reports the offer expired, the payment moves from PENDING to CANCELLED and keeps the gateway’s reference. Only a PENDING payment whose reference matches is touched, so a late authorization is left alone. The payment list settles on its own, and a retry starts from a clean state.

Fixes

bug-fix
  • An Adyen request that is rejected for a validation error now records which fields were rejected. A failed integration or payout setup says what to correct instead of only “invalid information provided”.

Event ingestion

Fixes

bug-fix
  • GET /v1/events answers 400 and names the parameter when processed_details_type is a value the platform does not know, or when the customer id is not a valid resource id. Both returned 500.

Roles and permissions

Fixes

bug-fix
  • A user whose only customer role is Customer Draft Contributor can no longer activate a customer. The role covers customers in DRAFT. Activating one is an administrator’s action.

Workflows

Send an email later The “send email to customer” workflow action takes a delivery delay. Set it in minutes on the action in Desk, up to three days. The API carries it as delivery_delay_seconds on the action. A dunning reminder can be scheduled for the next working morning instead of going out the moment the invoice falls due. See Workflow actions.

ERP actions show which integration they run against A workflow action that posts to an ERP now shows that system’s name and logo in the action list. A workflow with several integrations is readable at a glance.

AI and MCP

The cards link to each other The customer, quote, subscription and invoice cards an AI client renders are now linked. A breadcrumb moves between them, a customer card has tabs, and a card opens full screen. A quote’s first invoice preview has a card of its own, so building a quote in chat no longer falls back to a markdown table. The cards are built from Solvimon’s own component library, so they look like Desk.

Cards keep rendering in a long conversation A card no longer stops appearing after several turns in the same chat. A list card is built from the list it was given instead of re-fetching each item. A card that cannot render is logged, not silently replaced with text. A read-only card no longer carries contact details or payment methods.

Desk

Find any page, record or action with ⌘K ⌘K, or Ctrl+K, opens a search over the whole of Desk from anywhere. It finds pages by title, path or synonym, so “discounts” reaches Coupons and “group” reaches Plan groups. It opens a record from a pasted id. Before you type, it offers the common actions: create a customer, a one-off invoice, a subscription or a quote, and ingest an event. The sidebar’s search field opens the same panel.

Meter property variables have a screen The meter property variable API gained a Variables section in the sidebar. Create a variable, give an ENUM, NUMBER or STRING meter property its list of values, import the values from a CSV, and reprocess the events the change affects. Pricing conditions that refer to a variable can now be maintained without calling the API. See Meter property variables.

Filter invoices on amount The invoice list filters on the invoice amount, using the amount search the API gained last release. A platform that bills usage produces final invoices worth nothing at all. This filter separates them from the invoices worth collecting.

Fixes

bug-fix
  • Rows on the subscription and invoice lists open in a new tab with a right click anywhere in the row, not only on the first column.
  • Creating a rate card works after opening and closing the customer picker without choosing anyone. The empty picker sent an invalid id, and the error named nothing.
  • Editing a pricing from flat to tiered sends the type you chose. On a plan with several currencies or periods the PATCH still said FLAT.
  • Saving a usage-based pricing with nested conditions no longer fails on an unknown use_billing_cycles field.

For developers

Realistic examples in the API reference Solvimon rewrote every example in the API reference with values from a plausible billing setup instead of placeholders. This covers request bodies, responses, error responses, parameters and headers, for example on POST /v1/customers. Copying an example and changing the ids now gives a request that makes sense. This matters most to an AI agent that reads the specification as its only documentation.

SDK elements render before the translations arrive An SDK element in en-US renders immediately instead of waiting for two translation catalogs the bundle already contains. The element paints and starts its requests one network round trip sooner.

Deprecated API fields

The following fields are now deprecated. They continue to work for backwards compatibility. Migrate to the replacements.

  • pricing_plan_subscription_id (quote version info): use pricing_plan_subscription_ids. The single-valued field is only set when the quote version has exactly one subscription.
  • pricing_plan_subscription_info (quote version): use pricing_plan_subscription_infos, which carries one entry per subscription on the quote version.
  • pricing_plan_subscription_id (quote version create-subscription action): use pricing_plan_subscription_ids, which lists every subscription the action created.

October 14, 2026

Summary

This release gives sales, finance and AI clients the same numbers. Deal metrics on a quote version come from the invoice engine, so the figure in Desk, the CRM and the first invoice agree. Shipping addresses become a resource of their own. An invoice and its replacement are linked after a credit and copy. A payment you recorded by hand can be refunded or reversed. Desk approves schedule changes, and the Solvimon cards in an AI client are interactive apps instead of generated HTML.

Quotes

Deal metrics for a quote version GET /v1/quote-versions/{id}/summary returns the commercial numbers of a quote. The same invoice engine that will bill the quote calculates them. Each value is an amount in the quote’s currency, and pricing_plan_subscriptions repeats the breakdown per subscription.

GroupFields
Contract valuetcv, list_tcv, acv, contracted_arr, contracted_arr_fully_ramped
Totalsone_off_total, commitment_total, discount_total, unallocated_discount_total, markup_total
Usage estimatesestimated_usage_total, estimated_tcv
Discountblended_discount against list

Desk, the CRM integrations and the MCP quote tool now all show the same numbers. The total a sales rep reads off the quote, the figure written onto the opportunity in the CRM and the amount on the first invoice are the same, with overrides, discounts, commitments, ramps and proration already applied. The endpoint answers 404 when no summary can be calculated and 409 while a configuration change is still being processed. It answers 422 when the engine cannot calculate the summary, for example for a term that spans too many invoices. It needs QUOTE.VIEW. See Quote deal metrics.

Edit a signer or viewer on a quote version PATCH /v1/quote-versions/{id} changes a recipient’s role, name or email in place, so you can switch a signer to a viewer without removing them. Previously the only way to correct a typo in an email address was to delete the signer and add them again, which lost their position in the signing order. See Quote templates.

A tighter quote PDF The quote PDF is tighter. The schedule’s start and end dates are left aligned next to the schedule they belong to. Disabled feature entitlements are left out, and an item that is not billed is hidden. When nothing in a schedule is billed, the whole billed-items section is hidden with it. Pricing item names in the portal and the PDF now render at the same size as in Desk.

Invoices

An invoice and its replacement point at each other After a credit and copy, linked_invoices carries a REPLACED row on the original and a REPLACES row on the new invoice, alongside the existing credit links. A reconciler can walk from an invoice to the document that superseded it and refund the charges that were on the original but are missing from the replacement, instead of matching on amounts and dates. Solvimon writes the links only for replacements made through credit and copy, the one flow where both invoices are known at the time.

Search invoices on what they are worth POST /v1/invoices/search takes invoice_amount_including_tax.quantity as a numeric range and invoice_amount_including_tax.currency as a filter. Use the pair to find every invoice over a threshold in one currency, which is how approval thresholds and collections queues are usually defined.

Refund or reverse a payment you recorded by hand A payment created with POST /v1/payments, with no gateway behind it, can now be refunded with POST /v1/payments/{id}/refund or canceled with POST /v1/payments/{id}/reverse. Both write back to the invoice, so its paid_amount and open_amount follow. A manual payment counts as captured, so reversing one cancels it outright.

The same work corrects partial refunds on gateway payments. The right amount reached the gateway, but Solvimon updated the invoice with the full original amount. After a partial refund the invoice’s paid and open amounts, and its payment status, were wrong. See Invoice payment status.

Fixes

bug-fix
  • A linked invoice that has no invoice number yet can be opened from the invoice detail page. Only a FINAL invoice has a number, and the number was the link. Right after a credit and copy, neither the credit note nor the copy could be reached while both were still DRAFT.
  • A discount line is rendered after the line it applies to, not before it.

Subscriptions

Approve a schedule change from Desk A pricing plan schedule that is created as DRAFT goes through the approval flow before it takes effect. Desk now shows that flow: the schedule’s approval_status, who has to approve, and the approve and decline actions. An approval policy can be created with Schedule as its resource, so a plan change on a running subscription can be held for review in the same way as a quote. Approval type groups no longer offer to add levels, which only ranked groups support.

Fixes

bug-fix
  • Canceling a subscription is retryable when the customer or one of its invoices is locked at that moment. The status moved to CANCELLED before the future invoices were deleted. If that deletion then failed on the lock, the retry was refused because the subscription was no longer ACTIVE. This left a canceled subscription with invoices still on it.
  • A discount whose end date has passed can be edited and deleted in Desk, as the API already allowed. Desk applied stricter rules than the backend and hid the buttons.

Customers

Shipping addresses as a resource A customer can hold any number of shipping addresses. POST /v1/shipping-addresses creates one with a reference, a description and the same address shape used elsewhere. The recipient block is separate from the customer. It has a type of ORGANIZATION or INDIVIDUAL with the matching sub-object, a phone number and an email. This covers delivery to an employee’s home address or to a site that is not the billing address.

An address is created DRAFT, goes live through activate and is retired through deprecate. You can delete it while it is DRAFT or DEPRECATED, but not while it is in use. POST /v1/shipping-addresses/{id}/set-as-default marks the address to use when a request names none, reported as is_default. See Shipping addresses.

Wallets and credits

List auto top-up configurations on their own endpoint GET /v1/auto-top-up-configs lists the top-up configurations of one or more wallets. Pass wallet_id for a single wallet or wallet_ids[] for several, and narrow further with pricing_plan_schedule_id and statuses[]. This replaces the wallet’s expand[]=auto_top_up_configs as the way to read them. An auto top-up configuration is a top-level resource with its own lifecycle, with paging and filtering of its own.

Integrations

Key pair authentication for Snowflake A Snowflake data export can authenticate with a key pair instead of a username and password. Put the private key, -----BEGIN PRIVATE KEY----- and all, in the credential field of the export configuration. Solvimon recognizes it by that header and uses key pair authentication. Snowflake is withdrawing password authentication for non-human users, and key pairs are the only alternative the export connector supports.

AI and MCP

Solvimon cards are interactive apps The invoice, subscription, quote and customer cards an AI client renders are now MCP Apps served from Solvimon, not HTML the model writes from a template. A card is a real application bundle behind a show_card tool. It looks the same every time, the model cannot fabricate it, and its actions carry the platform they belong to.

A sales representative can open what the cards show The Sales Representative role now includes the Document Viewer, Quote Template Viewer and Quote Viewer roles. A sales rep reading a quote through an AI client was shown a card for a document they then could not open.

Desk

Mark a credit note as paid A credit note can be marked as paid, and the change undone, from the invoice page. The API already accepted it. Desk offered the action on regular invoices only, and now also on credit notes.


October 7, 2026

Summary

This release removes steps between Solvimon and the people and tools that use it. An AI client connects with your Solvimon login, so you no longer paste an API key into a configuration file. A sales rep can ask whether a quote version needs approval before they finalize it. A quote version and an invoice both give out a short-lived link to their PDF, so your portal or CRM does not proxy the file. A checkout page can show your terms and conditions, and a customer can buy an on-demand item from the portal and pay for it in one visit.

For integrations, the file lines endpoint filters on several statuses in one call, and a subscription created from a template accepts your own fields. Invoice paging is now stable, only a draft customer can be deleted, and Desk creates enum and boolean custom fields.

Event ingestion

Filter file lines on several statuses at once GET /v1/files/{id}/lines takes a repeatable statuses[] parameter. One call returns every line you still have to act on, for example statuses[]=ERROR&statuses[]=SKIPPED. Before this, reviewing a processed file upload took one request for each status. A line reports IMPORTED, DONE, SKIPPED or ERROR. The same statuses[] parameter is now on GET /v1/files, so you can list the files that are still running or that ended in error. The single-valued status parameter on the lines endpoint still works and is deprecated.

Fixes

bug-fix
  • A cost prediction for a configuration that the engine does not price yet now reports NOT_MATCHED. The separate NOT_SUPPORTED status is removed. It described the same outcome, and two values for one result meant that every caller had to handle both.

Quotes

Ask whether a quote version needs approval before you finalize it POST /v1/approval-policies/evaluate with a quote_version_id reports what finalizing that quote version would do about approval. It creates and changes nothing:

Response
{
"object_type": "APPROVAL_POLICY_EVALUATION",
"status": "APPROVAL_REQUIRED",
"triggered_approval_policy_ids": ["appo_5RmXe2QbtKfYuA9DcNH3P"],
"approval_strategy": "EVERYONE_HAS_TO_APPROVE",
"approvers": [ ... ]
}

status is NO_APPROVAL_REQUIRED, APPROVAL_REQUIRED, or CANNOT_BE_DETERMINED. The last value means that a rule could not be answered, and finalize would refuse in that case. The response also names the policies that would be breached, the reason, and the approvers who would receive the request. A sales rep learns what a discount costs them in approval time while they still edit the quote. An integration no longer has to re-implement the rule engine against GET /v1/approval-policies, where it would drift from the evaluation on the server. The endpoint needs QUOTE.VIEW and APPROVAL_POLICY.VIEW. See Approval policies.

Signature anchors on the quote PDF The quote PDF now renders a signing section with a labeled anchor for each signer. The e-signature integration places each signature box on a literal string in the PDF. A quote with several signers now routes each box to the correct person. See Quote templates.

Invoices

A short-lived link to the PDF GET /v1/invoices/{id}/download-url and GET /v1/quote-versions/{id}/download-url return a signed link to the rendered PDF. A portal, a CRM or an email template can give the document to the reader directly. Your own service does not have to proxy the bytes. See Downloading the invoice PDF.

Fixes

bug-fix
  • Paging GET /v1/invoices now returns each invoice exactly one time. Without order_by, the list sorted on invoice date alone, and a billing run gives many invoices the same date. Rows with the same date could come back in a different order for each query. A page boundary then moved between calls, so the same invoice appeared two times while another was skipped.
  • A self-billing invoice that was overpaid now shows “Total amount payable” instead of a negative “Amount due”.

Subscriptions

Set your own fields when you create a subscription from a template POST /v1/pricing-plan-subscriptions/init now accepts a set of fields on top of the copy from the template, instead of only reference and status. You can set customer_id, variant, forward_customer_id, billing_entity_id, billing_currency, combine, custom_fields, purchase_order_number, name, description and the invoice-line display flags. A subscription created from a template can now be forward billed. This was not possible while templates had to be DEFAULT. The template stays the source of truth for pricing. Solvimon refuses a field outside the set by name, so it never ignores a new field silently.

Fixes

bug-fix
  • Deleting a draft subscription now releases the coupon redemptions that it held. Before this, the redemption stayed behind and pointed at a subscription that no longer existed. The detail screen of the coupon then failed to load.
  • A SELF_BILLING subscription now shows the customer and the billing entity in the correct positions, as its invoices already did. Editing its details no longer resets the variant to DEFAULT.

Customers

Only a draft customer can be deleted DELETE /v1/customers/{id} is now refused unless the customer has status DRAFT. A customer that has been active can have invoices, subscriptions and events that point at it. Deleting it left those references dangling. To take an active customer out of use, archive it with POST /v1/customers/{id}/archive. The archive keeps its history.

Customer portal

Terms and conditions on a checkout page A checkout page portal URL now carries a note: up to 2,000 characters of Markdown that the customer sees on the page. Use it for your terms, a link to them, or anything the customer has to read before they subscribe. The field sits next to success_url on POST /v1/portal-urls and PATCH /v1/portal-urls/{id}. In Desk, you can edit it from the checkout page after you publish, not only in the publish dialog.

Buy an on-demand item from the portal A customer can now buy an on-demand item from the customer portal. They select the item, set a quantity on a one-off item priced FLAT, see a preview of the cost, and pay. The preview is the same invoice preview that the API returns. The amount that the customer confirms is the amount that Solvimon charges.

The SEPA direct debit mandate text Selecting SEPA direct debit in the hosted checkout or the customer portal now shows the mandate wording. The text names the billing entity that collects the payments. The customer sees what they authorize at the moment they authorize it.

AI and MCP

Connect an AI client with your Solvimon login An MCP client now signs in with OAuth 2.0 instead of a pasted API key. The Solvimon identity host publishes /.well-known/oauth-authorization-server and /.well-known/jwks.json. It registers a client through POST /v1/oauth2/register, and it runs the authorization code flow with PKCE over GET /v1/oauth2/authorize and POST /v1/oauth2/token. The browser step lands on a consent screen in Desk. The screen names the application, shows the access that it asks for, and lists the platforms that you are a member of. You select the platforms that the client may reach, then you approve or deny. A client asks for solvimon:read, solvimon:write or both. A request that names neither is narrowed to solvimon:read instead of refused.

To add Solvimon to an AI client, you enter the URL and log in. There is no key in a configuration file and no setup on our side. A token is bound to the platforms you selected and the scope that was granted, so a client you connected for one platform cannot read another. See Connect with OAuth and the Claude integration.

Desk

Enum and boolean custom fields Creating a custom field in Desk now offers the types that POST /v1/custom-fields already accepted: string, enum and boolean. An enum takes its allowed values in the same form. Before this, Desk created a string field whatever the field was meant to hold.

Discounts on a one-off invoice line Adding a one-off line to an invoice now offers to include it in the invoice-level discounts of the subscriptions on that invoice. POST /v1/invoices/{id}/add-line gained this last release as applicable_for_clauses. The option appears only when the invoice has subscription clauses to apply.

Fixes

bug-fix
  • The status filter on products and pricing plans no longer starts on “Deprecated”. The default hid the active resources that you were looking for.
  • Publishing a checkout page no longer creates the portal URL when activation failed. The two calls ran without the second waiting on the first.

Deprecated API fields

The following parameter is now deprecated. It continues to work for backwards compatibility. Migrate to the replacement.

  • status (GET /v1/files/{id}/lines): use statuses[] instead. It takes one or more line statuses in a single request, where status takes exactly one.

September 30, 2026

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.

A condition that matches a variable
{
"id": "mprp_5RmXe2QbtKfYuA9DcNH3P",
"comparator": "IN",
"meter_property_variable_id": "mpva_2PnBx7VdtRgLmE4WcQJ8K"
}

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:

Add two values and remove one
{
"add": ["FR", "BE"],
"remove": ["LU"]
}

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

bug-fix
  • 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_id for 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

bug-fix
  • 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_configuration and self_billing_credit_invoice_number_configuration when 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:

File typecontent_typeMaximum size
JSONapplication/json10 MB
HTMLtext/html10 MB
Markdowntext/markdown10 MB
PPTXapplication/vnd.openxmlformats-officedocument.presentationml.presentation25 MB
POTXapplication/vnd.openxmlformats-officedocument.presentationml.template25 MB

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}:

Guidance on a pricing plan
{
"agent_context": {
"guidance": "Mid-market plan, 50 to 500 seats. Pick this over Starter once a prospect asks for SSO or a custom contract."
}
}

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

bug-fix

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

bug-fix
  • 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.

September 23, 2026

Summary

A wallet denominated in a currency now pays for the invoice. Solvimon deducts the money from the taxable base of the lines the wallet covers, so no amount is taxed twice. You can now require approval before a pricing plan schedule becomes active. A coupon can now continue on the next schedule of a subscription. You can now backdate a discount to billing periods whose invoices are still draft. Solvimon now bills AvaTax partial exemptions as partial. You can now manage pricing plan groups in Desk. The customer portal is now available in German and Italian. Solvimon now disables a webhook after 20 consecutive failed deliveries. Desk now shows workflow executions on the customer and the invoice they ran for.

Pricing

Activating a pricing plan schedule can require approval An approval policy now accepts PRICING_PLAN_SCHEDULE as its source resource type. When such a policy applies, POST /v1/pricing-plan-schedules/{id}/activate does not activate the schedule. It creates an approval request, sets the schedule’s approval_status to PENDING_REVIEW, and returns the schedule in DRAFT. The schedule becomes active when an approver approves the request. A user who prepares a change can therefore ask for its release without the permission to release it.

Approval uses the same endpoints as quotes and invoices: POST /v1/approval-requests/{id}/approve, POST /v1/approval-requests/{id}/decline, and POST /v1/approval-requests/{id}/cancel. The same approver models apply: by group or ranked. A renegotiation usually changes more than one schedule. The three actions are therefore also available in bulk: POST /v1/approval-requests/approve, POST /v1/approval-requests/decline, and POST /v1/approval-requests/cancel.

Approve every schedule of a change in one request
curl -X POST https://test.api.solvimon.com/v1/approval-requests/approve \
-H "X-API-KEY: <apiKey>" \
-H "Content-Type: application/json" \
-d '{
"resource_ids": ["appr_jwDeeN0tYSY3F7BkeN1v", "appr_QwDeeN0vcYJaBLAc0C29"]
}'

Solvimon acts on each request separately. The response contains one result for each resource id. Each result has a status of SUCCEEDED or FAILED. A failed result also contains the error that stopped it. One failed request does not roll back the others.

To find the schedules that wait for review, read the subscription with GET /v1/pricing-plan-subscriptions/{id}. pending_review_pricing_plan_schedule_ids lists the schedules of the subscription that are pending review, in start_at order. pricing_plan_schedule_infos is unchanged: it lists only the active schedules. GET /v1/approval-requests now accepts source_ids[] for several sources in one request, in addition to source_id. Solvimon rejects a request that sends both.

A platform can have one active approval policy for each source type. These policies contain a single always-approve rule, and a second policy would repeat it. Solvimon also approves schedules in timeline order. You cannot activate a schedule while the schedule before it is still draft or pending review. See Requiring approval to activate.

A coupon can carry over to the next schedule You redeem a coupon against a pricing plan schedule, so its discounts belong to that schedule. POST /v1/pricing-plan-schedules/{id}/migrate and POST /v1/pricing-plan-schedules/{id}/copy now accept coupon_discount_behaviour. This field sets what happens to the coupons that are still active when you replace the schedule:

Continue the active coupons on the new schedule
{
"pricing_plan_version_id": "ppve_QwDeeN0vcYJaBLAc0C29",
"start_at": "2026-10-01T00:00:00+02:00",
"coupon_discount_behaviour": "CARRY_OVER"
}

NONE is the default. The discounts end with their schedule, as before. CARRY_OVER continues them on the new schedule for the remaining time of the coupon. Solvimon calculates the end date from the original start of the coupon. A three-month coupon that has run for two months therefore continues for one month on the new schedule. Solvimon does not redeem the coupon a second time. See Coupons across schedule changes.

A discount can be backdated while its invoices are still draft A discount can now start in any billing period whose invoice is not issued. The lock on billed periods now follows the last FINAL invoice. An invoice that is still DRAFT, for example on hold and not sent, therefore leaves its period open. You can add an ad hoc discount that you agreed on before the invoice goes out. A period with a FINAL invoice stays closed. The same rule applies when you remove a discount clause that has already started. See Invoice lifecycle.

An on-demand charge started from a payment carries its quantity When you charge an on-demand item through POST /v1/payments/authorize, you now state the quantity and the amount in the payment context. Each item accepts the same two optional fields as the direct request: units and flexible_amount. The flow can therefore charge a one-off item priced FLAT for the units ordered, and a flexible item for the agreed amount. FIXED items work as before.

Pricing items on the payment context
{
"pricing_items": [
{ "pricing_item_id": "prii_5RmXe2QbtKfYuA9DcNH3P", "units": { "number": "2" } },
{ "pricing_item_id": "prii_2PnBx7VdtRgLmE4WcQJ8K", "flexible_amount": { "quantity": "50.00", "currency": "EUR" } }
]
}

Solvimon validates both fields when you create the payment context. An incorrect quantity therefore returns an error to the caller before the customer pays. Solvimon still reads payment contexts stored in the earlier shape.

Wallets and credits

A wallet denominated in a currency pays for the invoice A CREDIT wallet type funded with an amount holds money, not credits. Such a wallet now pays for the invoice lines it is allowed to cover. Solvimon invoices the customer for the remainder.

The wallet holds a net amount, because Solvimon already charged tax on the top-up that funded it. Solvimon therefore deducts the money from the net amount of the line, and the covered part has no tax. Solvimon charges and taxes the remainder of the line as usual. For example, a 30.00 EUR line at 21% VAT against a 10.00 EUR balance invoices 20.00 EUR plus 4.20 EUR VAT:

NetVATTotal
Line as priced30.006.3036.30
Covered from the wallet-10.000.00-10.00
Charged20.004.2024.20

Solvimon always splits the coverage and never skips it. If the balance is less than the line, the wallet covers part of the line and Solvimon charges the remainder. Only lines whose product tax category matches the tax category of the wallet type are in scope. Other lines do not change. Solvimon applies the deduction last: after included volume, credits, discounts, and minimum commitment, and before tax. The deduction applies to the net amount that remains. A customer with both types of wallet spends credits first, because credits reduce volume and the money wallet reduces the amount.

Each charge reports what each wallet paid in a new wallet_balances list. Each entry names the wallet and gives its figures:

What one wallet paid for a charge
"wallet_balances": [
{
"wallet_id": "wall_5RmXe2QbtKfYuA9DcNH3P",
"used_balance": { "amount": { "quantity": "10.00", "currency": "EUR" } },
"left_balance": { "amount": { "quantity": "0.00", "currency": "EUR" } },
"available_balance": { "amount": { "quantity": "10.00", "currency": "EUR" } }
}
]

The list has one entry for each wallet that paid. A charge that a credits wallet and a money wallet both paid therefore reports the figures of each wallet separately. wallet_balances replaces wallet_balance_details, which holds one wallet at a time and only credits. See “Deprecated API fields” below, and An amount-denominated wallet pays for the invoice.

A grant into such a wallet must be in the currency of the wallet. Solvimon rejects a fixed grant in a different currency with wallet type <reference> is denominated in EUR, but the grant is in USD. Solvimon also rejects a grant that takes a percentage of pricing in a different currency, because there is no conversion. The error tells you to use a fixed grant or a different wallet type. A wallet type created before the default currency became mandatory has no default currency. You cannot grant into it until you set one.

Customers

A live seat assignment protects the resources it references Seat assignments record which child customer occupies which seat. Solvimon attributes per-seat credits against them. Solvimon now protects three resources while a live assignment references them: the child customer in the seat, the parent customer that holds the seat, and the per-seat product item that defines the seat type. For example, Solvimon rejects POST /v1/customers/{id}/archive for a child customer who still holds a live seat. A seat therefore cannot stay occupied by a customer that is no longer operational. The error names the assignment that blocks the change, and its status. First end the assignment: set end_at with PATCH /v1/seat-assignments/{id}. Then change the status. See Seat-based credits.

Fixes

bug-fix
  • You can now remove a billing email. PATCH /v1/customers/{id} with {"email": null} used to return INVALID_FIELD, although an empty string cleared the email. null, "", and whitespace now all mean no email.

Invoices

AvaTax partial exemptions are billed as partial Some jurisdictions tax part of a line and exempt the remainder. Software in Texas is a common example: 8.25% applies to 80% of the base, and the other 20% is exempt. Solvimon now stores the taxable fraction that AvaTax returns on the rate, and applies it. Solvimon calculates the rates on the taxable part of the base. The exempt remainder becomes a single 0% summary. The invoice and the tax filing therefore both show the split. The Texas example produces four tax lines: three on the 80% base, and one exempt line for the 20%. The invoice shows the exempt part once, not once per jurisdiction. A fully taxable or fully exempt line does not change. An invoice that is already issued keeps its tax. To apply the split to it, refresh it with POST /v1/invoices/{id}/refresh. See Tax calculation and integrations.

Fixes

bug-fix
  • Custom fields now persist after an invoice refresh. A CUSTOM_FIELD refresh with POST /v1/invoices/{id}/refresh used to update the “show on invoice” fields in the response and in the regenerated PDF. It did not write them to the invoice. The next GET returned the values from before the refresh.

Workflows

Filter and expand the resources a workflow ran against POST /v1/workflow-action-executions/search now filters on pricing_plan_subscription_id and wallet_id. The existing invoice, customer, payment, action, workflow, trigger, and status filters still apply. Workflow triggers now expand the resources they reference: workflow_id on a workflow trigger, pricing_plan_subscription_id and pricing_plan_schedule_id on a subscription trigger, wallet_id on a wallet trigger, and payment_id on a payment trigger. An execution row expands its workflow_action_id. You can therefore read the execution log in one call, with the resources of each row inline.

A condition on the billing entity of the invoice On invoice workflows, a workflow condition can now test invoice.billing_entity.id. A platform that bills from several billing entities can give each entity its own automation. Before this, you had to run one workflow and filter afterwards.

Workflow executions are shown where the work happened Desk now shows the execution table on the customer screen, on the invoice screen, and on the workflow. Each table lists the executions for that resource. To see what the automation did for an invoice, open the invoice. Select a row to open a panel with the details of that execution. The full log stays on its own page, “All workflow executions”. See Monitoring and audit.

Fixes

bug-fix
  • An EXPORT_TO_ERP action now requires an integration. You could leave the field empty, and Desk saved an action that had no integration to export through.

Integrations

Solvimon disables a webhook that never succeeds Solvimon now disables a webhook automatically after 20 consecutive failed deliveries. disabled_reason on the webhook gives the reason, so you can tell a webhook that Solvimon disabled from one that you disabled. An endpoint that is permanently unavailable therefore leaves the delivery queue. Before this, Solvimon retried it without end, on a backoff of up to several hours. While a webhook is disabled this way, you cannot send it a test event or resend its penalty box payload. Reactivate the webhook with PATCH /v1/webhooks/{id} first. Reactivation also clears the reason. See Webhooks.

Customer portal

German and Italian The customer portal and hosted checkout are now available in German and Italian, in addition to English and Dutch. The language switcher is now a standard part of both. You do not have to enable it. The starting language is the selection the visitor made. Without a selection, it is the locale on the customer record. Geolocation is the last fallback, because the location of the browser does not identify the customer. A regional variant falls back to its language: de-AT shows German and nl-BE shows Dutch.

The pay-invoice page uses the checkout components Paying an invoice from the customer portal and paying through the hosted checkout now use the same components. A payment therefore behaves the same from both starting points. Solvimon now passes the invoice amount to the payment method options. The page therefore offers only the methods that can settle the currency of the invoice.

Payments

Restrict the payment methods an Adyen acceptor offers allowed_payment_methods on a payment acceptor of type PAYMENT_GATEWAY on Adyen limits the methods it offers to a set you select. For example, one billing entity can accept cards, and a second can accept cards and direct debit. Desk lists the methods enabled on the selected Adyen integration, for integrations that Solvimon owns. If you leave the field empty, the acceptor offers every method that the integration has enabled. See Payment options.

Desk

Manage pricing plan groups in Desk A pricing plan group lets a subscription move between related plans. Plan groups are now a tab next to pricing plans. You can create and maintain a group in Desk, without the pricing plan groups API. You create a group with its name, its plans, and its portal settings. Drag the plans to order them, lowest tier first. That order is the upgrade path. Upgrades, downgrades, and cancellations each have their own timing: immediately, immediately with pro-rated fees, from the next billing period, or not allowed. A toggle sets whether customers can move between these plans themselves in the self-serve portal. You deprecate and reactivate groups from the same context menu as the other catalog resources.

Fixes

bug-fix
  • Desk now creates a user with a role. The form used to allow a user without a role, and that user could not do anything. The form now preselects Read only.
  • Clearing the end date of a schedule now clears it. An absent end_at means “keep the end date of the source schedule”, and only an explicit null means “no end date”. Desk used to drop the key when you emptied the field. The schedule therefore kept the old end date, which was usually in the past.
  • Extending an active schedule past a draft schedule that follows it no longer fails with No adjacent schedule found but flag to adjust the NEXT schedule was passed. The save used to ask to shift the next schedule without a check that this schedule was a draft.
  • The customer screen now hides archived payment methods. The list shows only the methods you can charge.
  • Revenue items on a pricing plan version now have even spacing. A gap used to appear between two of them.

Deprecated API fields

The following fields are now deprecated. They continue to work for backwards compatibility. Migrate to the replacements.

  • wallet_balance_details (pricing item summary price details): use wallet_balances instead. The block holds one wallet at a time. A charge paid by two wallets therefore reports only the figures of the wallet that paid last. The block can also express only credits.
  • used_wallet_credits, left_wallet_credits, available_wallet_credits (pricing item summary wallet balance details): use the used_balance, left_balance, and available_balance of the matching entry in wallet_balances instead. These fields carry credits or an amount.

September 16, 2026

Summary

A one-off item priced FLAT can now bill a unit price and a quantity, not only a single lump sum. A subscription can move between the plans of a pricing plan group in one API call. Credits can now belong to one seat instead of a shared pool. An invoice that spent an amount-denominated wallet now books that spend out of the wallet when it goes final. E-invoicing has a new downloadable report. An invoice’s payment status can now be set directly. Workflows can export invoices to an ERP and tag the emails they send. An integration can now be addressed by its reference.

Pricing

A one-off item can bill a unit price and a quantity A one-off charge used to carry only a single lump sum. To sell four products at 100 EUR, you had to calculate 400 EUR and enter that amount yourself. A one-off pricing item config priced FLAT now carries a unit count, the same way a per-seat item carries seats. The band’s amount becomes the unit price. Its fixed_amount stays a flat fee, charged once. The line bills fixed_amount + amount × units. FIXED is unchanged: it still bills a single lump sum.

You can set the count in three places. default_units on the pricing item config sets the plan-level default. When absent, it defaults to 1. units on a pricing plan schedule overrides the default per subscription. It is keyed on the pricing item config, the same way seats_values is:

Units on a schedule
"units": [
{ "pricing_item_config_id": "pico_5RmXe2QbtKfYuA9DcNH3P", "number": "4" }
]

On an on-demand charge, you state the quantity yourself. units is required for a FLAT item, and it must be positive. It does not fall back to default_units. default_units is a prefill for an ordering flow. It is not a quantity you confirmed.

Order three more units
curl -X POST https://test.api.solvimon.com/v1/invoices/charge-on-demand-pricing-items \
-H "X-API-KEY: <apiKey>" \
-H "Content-Type: application/json" \
-d '{
"pricing_plan_schedule_id": "ppsc_jwDeeN0tYSY3F7BkeN1v",
"pricing_items": [
{ "pricing_item_id": "proi_hwDeeN0vcYJaBLAc0C1W", "units": { "number": "3" } }
]
}'

A unit count is always a number. default_units.amount and default_units.count are rejected. Use number instead. Both fields are accepted only on a one-off item priced FLAT.

A count of zero is valid on a schedule. It bills no line. Ordering zero units on demand is rejected: it is not an order. A fixed wallet grant on such an item scales by the unit count. A top-up product that grants 500 credits per unit grants 1500 credits for three units. A grant that converts from the paid amount, or takes a percentage of it, cannot scale this way. It is rejected at configuration time with credits_grant.conversion and amount_grant.percentage are not supported on a ONE_OFF pricing item priced FLAT. Copying or migrating a schedule carries its units across.

Move a subscription between the plans of a pricing plan group Pricing plan groups have held the rules for moving between related plans since they were introduced. Until now, there was no way to execute the move. POST /v1/pricing-plan-subscriptions/{id}/change-plan performs it:

Upgrade a subscription to another plan in its group
curl -X POST https://test.api.solvimon.com/v1/pricing-plan-subscriptions/ppsu_jwDeeN0tYSY3F7BkeN1v/change-plan \
-H "X-API-KEY: <apiKey>" \
-H "Content-Type: application/json" \
-d '{
"pricing_plan_id": "ppla_QwDeeN0vcYJaBLAc0C29"
}'

The target plan must belong to the same group as the subscription’s current plan. That group must be ACTIVE. Solvimon infers the direction from the members’ order. A move from a lower order to a higher order is an upgrade. It follows the group’s upgrade_type. A move from a higher order to a lower order is a downgrade. It follows the group’s downgrade_type. That policy sets the timing:

PolicyTiming
IMMEDIATEStarts now, or at a start_at you supply
IMMEDIATE_PRO_RATAStarts now, or at a start_at you supply
NEXT_BILLING_PERIODStarts at the next invoice date; rejects a caller-supplied start_at
NOT_ALLOWEDRejects the transition

You can also move a plan sold in several billing periods between those periods. Pass billing_period with the same pricing_plan_id. The direction then follows the length of the period instead of the order. The response is the new schedule. See Plan changes in a pricing plan group.

The move builds a new schedule on the target plan. It does not carry over the optional pricings, commitments, discounts, or seats configured on the schedule it replaces. It works whether the current schedule follows a pricing plan version or a rate card. Solvimon validates the currency against the target version’s settings. For the customer portal, GET /v1/portal/pricing-plan-subscriptions/{id}/pricing-plan-group returns the group a subscription’s plan belongs to. A self-service plan picker needs this to know which plans it may offer.

A credits-priced config takes its periods from the credits item A pricing item config that prices usage in credits used to declare its own billing_period and pricing_period. These could disagree with the CREDITS item that settles the credit type it consumes. Where they disagreed, each pricing period’s overage landed on its own invoice instead of the one invoice for the billing period. For example, August’s usage was invoiced on 1 September instead of 1 October. Both periods are now inherited from the credits item. This keeps the overage and the credits it draws on the same invoice.

Three configurations that used to be accepted are now rejected: a credits-priced config with its own periods, credits items that disagree on a cadence, and a pricing period wider than its billing period.

See Credits in pricing plans.

A draft schedule can be corrected, and a draft subscription can be removed Two validations used to treat a draft as though it were already billing. A draft schedule’s start date could not move into the past, even though a contract being prepared often starts earlier than the day you configure it. A draft subscription could not be deleted while it still carried draft schedules, which is every draft subscription. Solvimon now allows both. See Draft schedules.

Fixes

bug-fix
  • You can now add a discount to a product item that a coupon already discounts. The request used to fail with start_at before previous, needs to start after, regardless of the dates you sent. The index named in the error pointed at a clause the caller never sent: the coupon’s own discount, appended to the list during the merge and out of date order. Both clauses were always valid. Only their order was not.
  • Migrating a pricing plan schedule that carries override pricings now succeeds. POST /v1/pricing-plan-schedules/{id}/migrate used to fail with Pricing ... not in the pricing plan version ... whenever the schedule had any override, even though the request never touches overrides. Solvimon was resolving the override against the version being migrated away from.
  • Activating a draft schedule beside an existing one no longer fails on its seats. Ending the adjacent schedule used to pass the draft’s own override pricings on as if they belonged to the active schedule. That schedule then rejected them as pricings its version does not contain.

Wallets and credits

Seat-owned credits SEAT_POOL grants credits per seat into one shared customer pool. Any seat can spend any credit in that pool. PER_SEAT is now the third wallet grant source. It keeps each seat’s credits to that seat: one grant per active seat assignment, restricted to the customer who occupies it. A seat can spend its own grant plus any unrestricted grant in the same wallet. A personal allowance and a shared pool can sit side by side.

Solvimon prorates the quantity by how much of the period the assignment covers. A seat handed over mid-month grants the incoming occupant only the remainder, not a full allowance. Assignments are not capped against the seats you paid for: credits follow the assignments. A period with a handover, or with more seats assigned than paid for, therefore grants more than the paid seats account for. Solvimon reports this excess rather than withholding it, because capping would make one seat’s credits depend on another’s. It is recorded at issuance and read back as over_granted: on the grant, on the wallet balance status, and per customer in customer_details.

A grant issued to a seat
{
"source": "PER_SEAT",
"seat": {
"customer_id": "cust_5RmXe2QbtKfYuA9DcNH3P",
"product_item_id": "proi_2PnBx7VdtRgLmE4WcQJ8K"
},
"grant_credits": { "quantity": "250", "credit_type_id": "ctyp_7KdRa4NvpWzYbT6FgXH2M" },
"over_granted": { "credits": { "quantity": "50", "credit_type_id": "ctyp_7KdRa4NvpWzYbT6FgXH2M" } }
}

A seat-owned grant must be attributable to one seat. PER_SEAT therefore requires a fixed credits_grant.credits on a pricing item priced PER_SEAT. Solvimon rejects an amount grant with PER_SEAT requires a fixed credits_grant.credits; a seat-owned amount grant is not supported. A wallet type granted from PER_SEAT cannot carry a second grant rule on the same wallet type: two rules would produce the same grant key, and Solvimon would drop the second one without a trace.

An invoice that spent an amount-denominated wallet books that money out at final A CREDIT wallet type funded with an amount keeps its ledger in a currency. Usage covered by such a wallet used to be held only as a reservation. The available balance already reflected it, so a second invoice could not spend the same money, but no money had actually left the wallet. When the invoice goes FINAL, the covered amount now leaves the wallet, oldest-expiring grant first. Solvimon recognises it as revenue with no tax, because it already charged tax on the top-up that funded the balance. Voiding or recalculating the invoice before it is final releases the reservation, and the balance becomes spendable again. Re-running a final invoice does not book the spend twice. See Credit types & wallets.

Quotes

Pricing defined directly on a schedule appears on the quote A quote whose schedule carries its own pricing, instead of pricing from a pricing plan version, used to show that pricing nowhere: not on the quote overview, and not on the generated PDF. Both now show it. The quote overview also gained an “expand all” action. You can read a quote with several products in one pass, instead of opening each section separately.

Additional settings on a new quote are collapsed The quote creation form now groups its secondary fields into the same collapsible “Additional settings” section the subscription form uses. Billing currency overrides the pricing plan’s currency. Left open, the field invited a sales user to fill it in as though it were required. Collapsed, Solvimon sets it only when you are genuinely overriding the currency.

Invoices

Set an invoice’s payment status directly payment_status on an invoice used to be read-only. You could change it only by recording a payment. You can now patch it directly on a FINAL invoice, for settlement that happened outside Solvimon:

Mark a final invoice as paid
curl -X PATCH https://test.api.solvimon.com/v1/invoices/invo_jwDeeN0tYSY3F7BkeN1v \
-H "X-API-KEY: <apiKey>" \
-H "Content-Type: application/json" \
-d '{ "payment_status": "PAID" }'

You can only set PAID or UNPAID. PARTIALLY_PAID and OVERPAID follow from the paid and open amounts, so Solvimon rejects them. Solvimon also rejects a request that sets the deprecated paid flag to a value the status contradicts. You cannot set the field while creating an invoice.

See Invoice payment status.

Avalara e-invoicing moves to ELR 1.6 The Avalara integration now runs on E-Invoicing and Live Reporting 1.6. It reports a business status and an authority status alongside the document status. Two refresh behaviours come with this. Statuses stamped on the same millisecond now sort by their message instead of arbitrarily. Follow-up now stops once the most recently submitted e-invoice reaches a final state. Earlier failed attempts no longer keep follow-up alive. See E-invoicing.

The new invoice PDF renderer is enabled per platform The rendering service that already produces quote PDFs was introduced for invoices as an opt-in preview. An entitlement on your platform now selects it. It covers every invoice PDF, not only a download from Desk. The copy attached when an invoice is finalised or emailed goes through the same renderer, so one invoice cannot look two different ways. The download button is translated into the languages the customer portal supports. The renderer is still opt-in. Contact your account manager to have it switched on.

Search a full invoice history by date A date range on POST /v1/invoices/search now returns its page correctly on a platform with years of invoices behind it. A wide range used to risk running past the request timeout and returning a 500. You can now ask for a quarter or a year in one request, for a reporting or reconciliation run. Payment, payment request, bulk action, and subscription search filter on dates the same way, and answer faster.

This change also fixes a related bug: a bound given with sub-second precision now matches the second that contains it. It previously matched nothing at all.

Filter invoices by the workflow that acted on them You can now filter invoices on the status of the workflow actions that ran against them. Use workflow_action_execution_statuses[] when listing, and workflow_action_execution_status in a search body. You can now pull invoices whose workflow actions failed in one request. Before this, you had to read the execution log and look each invoice up yourself.

Fixes

bug-fix
  • You can now finalise a credit note against a one-off invoice without a manual refresh. The PATCH to FINAL used to return a 500, and the validator reported a total of 0. Solvimon was not reloading the sales tax rates of a one-off product for a credit note the way it does for the one-off invoice itself.
  • AvaTax rates are now loaded for the next schedule as well as the previous one. An invoice spanning two schedules, where the second schedule prices products the first does not, used to be taxed without rates for those products.

Reporting

An e-invoicing report E-invoicing status used to be visible only per invoice, never in aggregate. To answer “which invoices have not been accepted yet,” you had to open them one at a time. A new E_INVOICING report joins the report downloads, with one line per e-invoice. Each line carries the invoice it belongs to (number, date, billing period, status, type, currency, amount, billing entity, and customer) and the e-invoicing side of it (external reference, processor, applied mandate, integration, current status and message, submitted at, last status at, and how many statuses it has been through). An invoice submitted more than once gets a line per submission, so a failure and the resubmission that followed it both appear in the extract. See E-invoicing report.

Integrations

Address an integration by its reference The reference on an integration tells several integrations of the same type apart. You could already use it everywhere except on the integration itself, which only accepted its resource id. GET, PATCH, and DELETE on /v1/integrations/{idOrReference} now accept either, and so do the deprecate and activate actions under it. If your code already knows an integration by its reference, it no longer has to store the generated id alongside it. You can also now delete draft ERP integrations.

Workflows

Export an invoice to an ERP from a workflow EXPORT_TO_ERP joins SEND_EMAIL_TO_CUSTOMER as a workflow action type. The action names the integration responsible for the export through export_to_erp.executor. The one available executor is THIRD_PARTY. It performs the export through the connected ERP integration and records a workflow execution row for it. An export that used to happen outside the workflow engine is now visible in the execution log beside the rest of the automation, with the same retry and status reporting. You can configure the action in Desk. The panel lists the ERP integrations connected to your platform.

Tag the emails a workflow sends The send-email action now accepts tags: up to 3 ASCII tags of at most 128 characters each. Solvimon passes them to Mailgun as o:tag, so you can filter and report on messages in the Mailgun dashboard. The legacy Paragon integration exposed this, and migrated templates lost it. You set tags per workflow, so you can tell different workflows apart. They apply only to a Mailgun account you connected yourself. A Solvimon-managed email integration rejects them with not allowed for Solvimon-managed email integrations, and tags its own traffic instead.

Find the workflow activity for one customer POST /v1/workflow-action-executions/search now accepts a customer_id filter. The workflow trigger endpoints accept expand[]=customer_id, which inlines the customer on the trigger. Before this, answering “what did the automation do for this customer” meant searching every execution and then looking up each row.

An overdue reminder template of its own Selecting a trigger preselects the email template written for it, which keeps a workflow from going out under the wrong wording. The overdue invoice trigger had no template of its own and fell back to the standard final invoice template. That template reads as though the invoice had just been issued, not as though it were late. There is now a dedicated overdue reminder template. The “Invoice: status set to overdue” trigger preselects it, and a new sandbox is created with it already configured for the overdue notification.

Customer portal

Pricing defined directly on a schedule is shown A subscription schedule can carry pricing of its own, in addition to or instead of the pricing that comes from a pricing plan version. The portal used to render only the pricing plan version’s pricing. A customer looking at their own subscription saw a plan that was missing the products negotiated onto it directly. The portal now lists those products with the rest.

Desk

Fixes

bug-fix
  • Deleting a customer or a subscription now updates the list you deleted it from. A delete the API refuses now reports why, instead of appearing to do nothing. Deleting from a detail page no longer returns you to the previous page regardless of what happened.
  • Text in the rich-text editor of a quote is now rendered in the PDF in the font it was written in, and the right-hand edge is no longer cut off.
  • Invoice numbering settings no longer submit an invoice date determination type that you did not change. Editing a self-billing numbering format used to re-submit the platform’s date determination type, default it to WHEN_INVOICE_GOES_TO_FINAL, and apply it at the wrong level. That could change when invoices take their date, across the whole platform.
  • A custom field shared by two integrations is now edited per integration. With two fields carrying the same reference on different integrations, Desk used to match on the reference alone. Both inputs showed the same value, and editing one changed the other.

September 9, 2026

Summary

A wallet denominated in a currency now drives the same automation as one denominated in credits. Auto top-up fires on an amount threshold. Wallet balance workflows accept an amount threshold too. The trigger reports both the balance and the threshold in the wallet’s own unit. Wallet grants are now issued per pricing period, not per invoice. A repeated on-demand charge grants its credits per line. A forward-billed grant lands in the wallet of the customer the subscription is for. Seat assignments are manageable from Desk. Calendar billing anchors a multi-month period on the schedule start.

Pricing

A clearer error when pass-through pricing meets the wrong meter value Pass-through pricing bills the amount carried on the event, so it can only be configured against a meter value of type AMOUNT. Any other meter value was rejected with “not compatible with non AMOUNT usage”, which named neither the pricing type that refused nor what it needed. The message now reads PASS_THROUGH pricing requires an AMOUNT meter value.

Adding a pricing group no longer fails on the pricing category order Adding a pricing group to a pricing plan version could introduce a product category the version did not have yet. If a custom order had been set through “Change pricing order”, this failed with display_order is configured on 3 of the 4 pricing categories, it must be configured on all of them or on none of them. Desk now assigns a display order to the new category itself, so an explicit order stays complete. See Pricing groups.

Fixes

bug-fix
  • A seats value has to be a number. default_seats_value on a pricing item config was accepted as an amount, which is not a seat count anything could multiply by, and is now rejected with seats value must be a number. A seat count configured as zero bills no seat line at all, as a zero count already did.

Wallets and credits

Auto top-up and balance workflows for wallets denominated in a currency A CREDIT wallet type funded with an amount keeps its ledger in a currency rather than in a credit type. Invoice usage that takes the open balance below the configured threshold now schedules the auto top-up, and wallet.wallet_balance.threshold.amount is accepted on a workflow definition for such a wallet type.

There is no conversion between a credit type and a currency, so a threshold is only valid in the wallet’s own unit. An amount threshold on a wallet type denominated in credits is rejected with amount threshold not allowed for CREDITS wallets. A credits threshold on a wallet type denominated in an amount is rejected with credits threshold not allowed for AMOUNT credit wallets. An amount threshold’s currency has to match the wallet type’s credit.amount_grant.default_currency. LESS_THAN remains the only comparator. See Wallet top-ups and Credit types & wallets.

Threshold on a wallet type funded with an amount
{
"wallet_balance": {
"wallet_type_id": "wtyp_...",
"comparator": "LESS_THAN",
"threshold": { "amount": { "quantity": "500.00", "currency": "EUR" } }
}
}

In Desk, the threshold field now follows the unit of the selected wallet type. It resets when you switch to a wallet type in the other unit, so a figure entered in credits is never resubmitted as an amount. The workflow summary now states the amount with its currency instead of a credit unit name.

A wallet grant is issued per pricing period, not per invoice A wallet_grants rule on a pricing item config was issued once per invoice. Now each pricing period produces its own grant, with its own validity window. This matters when the config’s pricing_period is shorter than its billing_period: on a plan billed twice a year, a monthly expiry_policy now behaves as configured, instead of covering the whole six-month invoice. See Credits in pricing plans.

A repeated on-demand item grants its credits per line Charging on demand accepts the same pricing item more than once in one request. Both lines carry the invoice date and land in the same invoice group. So an item at 100 USD granting a fixed 500 credits, charged twice, takes 200 USD and deposited 1000 credits.

A forward-billed grant lands in the wallet of the customer the subscription is for Under forward billing the invoice is addressed to the parent, but the subscription belongs to the child. A wallet grant from such a subscription now resolves to the subscription’s own customer, not the parent. The same holds for forwarded usage: it draws from the subscription’s own customer balance. See Parent-child relationships.

Customers

Manage seat assignments from Desk Seat assignments record which processing-only child customer occupies which seat, and they are what per-seat credits are attributed against. Until now they existed only on the API. From the context menu of a per-seat pricing item on a subscription, beside “Show seats history”, the new panel lists the seats assigned under that parent for that seat type with occupant, window and status, and assigns a child to a seat, ends an assignment, reopens it or deletes it. Only processing-only children of that parent are offered, and each action respects its SEAT_ASSIGNMENT permission. See Seat-based pricing and Seat-based credits.

Invoices

Fixes

bug-fix
  • Refunded payments are accounted for in the invoice amounts. An invoice that was paid and then partly refunded could report a negative open_invoice_amount and a paid_invoice_amount above its own total. A payment pending refund or reversal still counts as paid until the refund settles; a settled refund no longer does.
  • payment_status is persisted when an invoice is marked as paid by hand. The write that settled the invoice updated the paid flag and the open amount but left the payment status at its previous value, so the invoice read back as paid while still reporting NOT_PAID or PARTIALLY_PAID. See Invoice payment status.
  • Voiding a subscription no longer fails when an ingested event fed both a pricing summary and a feature summary. The reprocessing that follows the void removed every link for the event, then looked for the feature summary’s link again and raised an error on it. The feature summary is now removed with the rest, so reprocessing leaves nothing dangling to duplicate later.

Payments

A rate-limited request is retried instead of failing the payment A burst of invoice payments can take the payment provider over its rate limit. A 429 response was not in the retry set. It surfaced as an error, even though nothing had actually gone wrong: the payment action was marked ERROR and each item raised an alert. 429 is now retried. The fixed half-second wait between retries was also replaced with exponential backoff and jitter, as the provider documents. See Dunning and payment retries.

Workflows

Breaking: a wallet balance trigger reports the balance in the wallet’s own unit open_balance and threshold on the wallet_balance trigger were a bare credits object, which cannot express the balance of a wallet denominated in a currency. Both are now a container carrying credits and amount, of which exactly one is populated, decided by the wallet type:

Before and after
// was
"wallet_balance": { "open_balance": { "quantity": "40", "credit_type_id": "ctyp_..." } }
// is
"wallet_balance": { "open_balance": { "credits": { "quantity": "40", "credit_type_id": "ctyp_..." } } }
"wallet_balance": { "open_balance": { "amount": { "quantity": "40.50", "currency": "EUR" } } }

A consumer reading open_balance.quantity has to move to open_balance.credits.quantity. The send-email action is unaffected: wallet_balance and wallet_balance_threshold are rendered figures either way, and credit_unit_name carries the currency code when the wallet is denominated in an amount. See Workflow triggers.

Desk

Pick the billing currency when adding pricing to a subscription Adding a pricing directly on a subscription pre-selected the platform’s default currency and gave no way to change it, so a subscription billed in another currency had to be built elsewhere. The currency is still pre-selected, from the subscription, and is now editable. See Custom pricing.

Event reprocessing moved next to the usage it explains The reprocessing log is now a tab under Usage metering rather than a page of its own, so the events and the reprocessing they went through are read in one place.

Fixes

bug-fix
  • Events load on the Events page. Opening the page showed an empty table until a full refresh, and changing the meter in the dropdown did not fetch anything.
  • Only active meters are offered in the Events overview selector, so a deprecated or archived meter is no longer something you can select and get nothing back for.
  • The “Metric filters” option appears for a usage-based billing item that points at a meter directly, and not only for a saved meter value calculation, when dynamic meters are off.
  • Report generation requests that are DONE are hidden on an invoice, since the report they produced is listed already and showed as a duplicate beside it.
  • Inviting a user whose email address differs only in capitalisation from an existing one reports that the user already exists instead of failing on an error.
  • Collapsing the sidebar works again, and closing a modal by clicking the overlay no longer discards what you were verifying.
  • Status chips follow one set of meanings across Desk and the portal: neutral for metadata such as countries, currencies and versions, and a shared mapping from lifecycle state to neutral, informational, positive, warning or negative.

September 2, 2026

Summary

Credit grants on a pricing item can now scale with the number of seats purchased. Seat occupancy is tracked as its own resource through the new seat assignments API, and a wallet can show which customer’s usage reserved which part of its balance. Also: a credit-amount wallet’s tax category is now always set, workflow emails include the template variables the legacy integration used to inject, and draft workflows can be deleted.

Pricing

You can now leave product items unpriced One product can back several plans that each charge for a different subset of its items: leave the rest unpriced, and events matching those items produce no charge on that plan. The API always allowed a pricing to skip product items of its product; Desk was what enforced pricing every item. Now you can remove a product item from a pricing on a pricing plan version, a rate card version, or a schedule pricing, which makes filtered product items usable in practice. An unpriced item still renders as an “Unpriced” card with an “Add pricing” action, so leaving one out stays visible rather than silent.

Wallets and credits

Credit grants that scale with seats A wallet-grant rule on a pricing item config declares what its quantity is derived from through a new source field, so a plan sold per seat can hand out credits per seat without a separate rule per customer. FIXED is the default and grants the quantity exactly as configured, which is what every existing rule does. SEAT_POOL multiplies the configured quantity by the applicable purchased seat count and grants the result into the shared customer wallet as a single grant per rule per billing period, never one grant per seat. The seat count comes from seats_values on the pricing plan schedule for that pricing item, falling back to default_seats_value on the item config when the schedule sets none.

SEAT_POOL is only valid on a PER_SEAT pricing item, since seat counts are scoped to a pricing item rather than to the schedule as a whole; the API rejects it elsewhere with a validation error on wallet_grants. Issued grants carry the same source read-only, so a grant that was seat-scaled is identifiable after the fact. The enum also declares PER_SEAT, for credits owned by an individual seat rather than pooled; it is not implemented yet and is rejected with PER_SEAT is not supported yet. See Seat-based credits for the full configuration, including how the seat count is resolved and how seats added mid-period are topped up.

In Desk, the grant source is configured on the wallet grant in a pricing, and a seat-scaled grant shows the seat count it resolved against.

See whose usage reserved a wallet balance A shared credit pool spent by several child customers reported one reserved figure with no way to see where it came from. The wallet balance status can now return customer_details, a breakdown of the reserved balance per customer, requested with include_customer_details on the balance call. Each entry carries customer_id and that customer’s share of the reserved balance. The split is recorded when an invoice is built or refreshed, so it reflects the usage that has actually been drafted against the wallet.

POST
/v:version/wallets/:resourceIdOrReference/balance
curl -X POST https://test.api.solvimon.com/v1/wallets//balance \
-H "X-API-KEY: <apiKey>" \
-H "Content-Type: application/json" \
-d '{
"balance_at": "2026-10-09T12:00:00Z",
"include_customer_details": true
}'
Response
{
"balance": {
"credits": {
"quantity": "55000",
"credit_type_id": "ctyp_xwDeeN0vxxHxVWCZif14"
}
},
"reserved_balance": {
"credits": {
"quantity": "12480",
"credit_type_id": "ctyp_xwDeeN0vxxHxVWCZif14"
}
},
"open_balance": {
"credits": {
"quantity": "42520",
"credit_type_id": "ctyp_xwDeeN0vxxHxVWCZif14"
}
},
"balance_at": "2026-10-09T12:00:00Z",
"customer_details": [
{
"customer_id": "cust_lwDeeN0vxxHxMWCVef1S",
"reserved_balance": {
"credits": {
"quantity": "12480",
"credit_type_id": "ctyp_xwDeeN0vxxHxVWCZif14"
}
}
}
]
}

A credit-amount wallet type’s tax category is enforced A CREDIT wallet type funded with an amount carries a tax category and a default currency. The tax category was required at create time but only stored and returned: nothing read it, so it constrained nothing. It is now the declared spending scope of the wallet. Money funded under one tax category must not become spendable under another, so the tax category and the default currency can no longer be changed once wallets exist for that wallet type, and neither can be removed once set. Changing either on a wallet type that has no wallets yet is still allowed, and an attempt to change one under existing wallets is rejected with a validation error on credit.amount_grant.tax_category or credit.amount_grant.default_currency. See Credit types and wallets.

Customers

Seat assignments: record which customer occupies a seat seats_values on a pricing plan schedule records how many seats are paid for, but nothing recorded which child customer occupies one. A processing-only child was linked to its parent only through parent_resource_ids, so there was no way to exclude a child from being counted as a seat, to distinguish seat types, or to compare occupied seats against paid seats. Seat assignment is now an explicit resource at /v1/seat-assignments, with create, list, get, update and delete:

POST
/v:version/seat-assignments
curl -X POST https://test.api.solvimon.com/v1/seat-assignments \
-H "X-API-KEY: <apiKey>" \
-H "Content-Type: application/json" \
-d '{
"parent_customer_id": "cust_UwDeeN0vxxHxMTCJeF1K",
"customer_id": "cust_FwDeeN0vxxHxN0COeY1H",
"product_item_id": "proi_pwDeeN0vxxHxUUCxh81e",
"start_at": "2026-10-01T00:00:00-05:00"
}'
Response
{
"object_type": "string",
"id": "string",
"status": "SCHEDULED",
"parent_customer_id": "string",
"customer_id": "string",
"product_item_id": "string",
"start_at": "2024-01-15T09:30:00Z",
"end_at": "2024-01-15T09:30:00Z",
"created_at": "string",
"updated_at": "string"
}

Occupancy is keyed on the PER_SEAT product item, which is the seat type, rather than on the schedule, because capacity itself is scoped per pricing item. status is derived at read time from the dates: SCHEDULED before start_at, ACTIVE while the seat is occupied, ENDED after end_at. Ending an assignment is a PATCH that sets end_at, which must be strictly after start_at; clearing end_at re-opens the seat. On its own this changes no billing behaviour: it is the record that makes seat-owned credits and occupied-versus-paid reporting possible. Four permissions govern it, SEAT_ASSIGNMENT.VIEW, SEAT_ASSIGNMENT.CREATE, SEAT_ASSIGNMENT.UPDATE and SEAT_ASSIGNMENT.DELETE, with the viewer role rolled into Read Only. See Seat assignments.

Subscriptions

Preview an invoice for a subscription that has only draft schedules A subscription whose schedules are all still drafts could not be previewed: with no active schedule there was nothing to price, so the preview refused rather than showing what the drafts would produce. The preview now includes draft schedules, which is what makes a draft subscription reviewable before anyone activates it.

Draft schedules behave as one unit on a draft subscription While a subscription is itself a draft, every schedule on it is a draft too, so the per-schedule draft chip, the per-schedule activate action and the “Create as draft” toggles added noise around a decision that is not yours to make yet. On a draft subscription these are gone: schedules are created as drafts and all of them are activated together when you activate the subscription, from a single button. On an active subscription new schedules are still created as drafts, and the existing per-schedule controls are unchanged.

Quotes

Sales representatives can add schedules to a draft quote version Creating a pricing plan schedule required PRICING_PLAN_SCHEDULE.CREATE, which is the permission that governs changing live subscriptions. A sales representative building a quote therefore needed a permission far broader than the work in front of them. Schedule creation now checks which kind of subscription it targets: a quote subscription requires QUOTE_PRICING_PLAN_SCHEDULE.CREATE and is accepted only while the quote version is DRAFT, and anything else still requires PRICING_PLAN_SCHEDULE.CREATE. Adding a schedule to a quote version that has left draft is rejected with a validation error on quote_version_id, since a change to agreed terms belongs in the upgrade quote flow rather than in an edit.

Custom fields carry over to a new quote version Creating a new version of a quote sends the custom fields of the version it came from. The link a CRM establishes through a custom field, an opportunity id in particular, survived into the subscription when a quote ran straight through, but was lost as soon as the quote was rejected or returned to draft and continued from a new version. The subscription created from that version now carries the link. See the Salesforce quotes integration.

Invoices

A new invoice PDF renderer, in preview Invoice PDFs can be produced by the same rendering service that already produces quote PDFs, which brings invoices onto one templating and localisation stack: the layout is built from the same component library as the rest of the product, and the invoice template ships translations for the languages the customer portal supports. It is opt-in while it is being rolled out. Contact your account manager to have it enabled for your platform.

An auto rescue stops when the invoice is paid another way An invoice payment refused for insufficient funds schedules an automatic rescue with the payment provider. If the platform then settled the invoice through POST /v1/invoices/{id}/pay, the rescue still fired later and charged the customer a second time, leaving a refund to be issued. A successful invoice payment now cancels any pending auto rescue for that invoice, and a second auto rescue is not started for an invoice that already has one active. See dunning and payment retries.

Workflows

Delete a draft workflow A workflow in DRAFT can be deleted, in line with the other draft resources: subscriptions, customers and pricing plans. A workflow that was created by mistake, or that was superseded before it ever ran, no longer has to be left in place. Deletion is governed by the new WORKFLOW.DELETE permission, and only draft workflows are deletable; an active one still has to be deactivated rather than removed, so no execution history disappears.

Expand the trigger on an action execution GET /v1/workflow-action-executions/{id} and POST /v1/workflow-action-executions/search accept expand[]=workflow_trigger_id, which inlines the full workflow_trigger that produced the row. Building a list of executions with the resource each one acted on was a second call per row; it is now part of the search response. Successful email actions also record a more useful reason, naming the invoice and the message id the provider accepted, so a delivery can be traced from the execution log into the provider without correlating timestamps.

More template variables on the send-email action The native send-email action now passes invoice_type, open_amount, customer_name, customer_type, credit_note and original_invoice_number to the template alongside the variables it already sent. Templates written against the legacy Paragon-based Mailgun integration relied on these, and rendered them as empty values after the migration to native workflows. Migrated templates that use them render correctly without being rewritten.

Action execution details in Desk A workflow action execution opens into a details panel showing what the action did, the trigger it came from and the outcome it recorded, rather than only the row in the executions table.

Customer portal

Fixes

bug-fix
  • The Pay button is visible on the invoice list in the portal. It worked, but was not rendered, so paying from the list was only discoverable by accident; the overview page was unaffected.
  • Embedded components receive your platform’s primary colour as their brand colour, so an embedded balance or subscription view matches the surrounding page instead of falling back to a default palette.

Desk

Consistent metric selection on products The billing metric selector on a product item follows the same pattern as the rest of the side panel, and the meter filter, tiering metric and unit names moved into a context menu next to it. Choosing what a usage-based item measures looked different from every other field around it, and each of the related settings used its own control.

The integration reference explained where it is used The reference on an integration is what makes a multi-account setup possible: several integrations of the same type on one platform, told apart by their reference. The dialog now explains what the reference is for and what to put in it, rather than presenting an unexplained field.


August 26, 2026

Summary

📬 This release completes localized emails. use_template_subject sends no subject override, so the provider uses the subject of the same template as the body. Each email also has a threading header. Gmail therefore no longer puts the invoices and reminders of one customer in a single conversation. Solvimon now compares a top-up threshold in the unit of the wallet balance. Draft pricing plan schedules, which the API got last release, now have a full editor in Desk. Price indexation has its own page. Two silent errors also stop: Solvimon validates filter values against the meter property type, and Desk reads the invoice payment status from payment_status. Editable meters from ingestion and a pass on the Desk buttons and sidebar complete the release.

Pricing

Filter values are checked against the meter property type A usage-based product item can filter on a meter property. Before, Solvimon did not check the filter value against the type of the property. For example, Solvimon accepted EQUALS 1hello1 on a NUMBER property. The filter then matched no events, and the item stayed at zero usage. There was no indication of the cause. Solvimon now validates each value on a NUMBER meter property when you configure the item. An invalid value gives a values.{index} error that names the value and the property. STRING and ENUM properties do not change.

Fixes

bug-fix
  • Duplicate conditions on pricing item configs now fail validation. Before, a PATCH could add two configs with the same meter property conditions. Solvimon also compared a nested condition group only with its sibling groups, and not with its parent group. A child group could therefore repeat a condition of its parent group. Two configs can no longer claim the same usage. See Filtering on a meter property.

Wallets and credits

Fixes

bug-fix
  • Solvimon now compares the automatic top-up threshold in the unit of the wallet balance. Before, a credit wallet with a threshold in a currency compared two different units. The balance never crossed the threshold, and the wallet never topped up. The configuration gave no indication of the cause. Solvimon now converts the threshold before it makes the comparison.

Subscriptions

Draft schedules in Desk You can now build and release draft pricing plan schedules from the subscription screen. The API got them last release. You add a schedule as a draft, and you can edit it while it is a draft. You then activate it from the row actions or the context menu. The schedule list shows which schedules are drafts. You can therefore see a pending renegotiation, and you do not mistake it for the current terms. Activation obeys the permissions of the API. A user who cannot activate a draft sees a disabled action, and does not get an error on save.

Pricing plans on a schedule are collapsible The pricing plan and its connected pricings on a subscription or quote schedule are now a card. You can collapse the card. A subscription with several schedules stays easy to read. You do not scroll past pricing detail that you do not need.

Select or deselect a whole pricing group Multi-select pricing groups on subscription and quote schedules now have a control that selects and deselects all pricings. Before, you enabled each pricing in the group with a separate click. This is the usual case if you sell a plan in full.

Index a subset of revenue items If you apply price indexation to revenue items, a percentage is no longer necessary on each item. If you leave an item empty, Solvimon does not index that item. You can therefore raise one revenue item, and not enter a value for the other items. The API accepted a partial set before this change, but the form did not.

Invoices

Fixes

bug-fix
  • Desk now reads the invoice payment status from payment_status, and no longer from the deprecated paid flag. If payment_status is not present, Desk uses paid. Desk now shows each status between unpaid and paid, for example PARTIALLY_PAID. Before, Desk showed these statuses as “not paid”.
  • The status icon on an invoice usage report request no longer spins after the request is DONE. Before, the label showed “Done”, but the icon continued to spin.

Workflows

Use the subject defined in the email template Before, a send-email workflow action had an optional subject. If you did not set it, Solvimon used a hard-coded English subject. You could not complete a localized email. The body came from the localized template, but the subject did not. use_template_subject sends no subject override, so the provider uses the subject of the template that it renders. The default is true if the action has no subject. An action that has a subject continues to send it. You cannot use the two fields together. If you set both fields, Solvimon rejects the request with a validation error on use_template_subject. To use the subject of the template, remove the subject. See Subject lines.

Each email starts its own conversation Each workflow email now has an X-Entity-Ref-ID header. The value is unique to that email, and comes from the action and the trigger. Some mail clients group messages by this header. Gmail put the invoices and reminders of one customer in a single conversation. It then hid the most recent message behind the older messages. Each email now starts its own conversation. See Threading.

Fixes

bug-fix
  • The execution table for workflow actions now also shows the PENDING and NOT_EXECUTED statuses. NOT_EXECUTED shows that the conditions of the action did not apply. PENDING shows that the action has not run. See Execution statuses.

Meters and events

Edit a meter created during ingestion Before, you could use a meter from dynamic meter creation, but you could not examine it. It was only a name in a dropdown. The Show meter action on the meter dropdown now opens a side panel. In the panel you can see the meter, and make its values and properties required. You can also add new values and properties, and add more values to an existing ENUM property. You can therefore make a meter from your event stream into a deliberate definition. You do not create the meter again.

Reporting

Reporting metrics show their aggregation A reporting metric on a revenue item becomes read-only after you set it. Before, the read-only state showed only the name of the meter. Two revenue items with the same meter and different aggregations looked the same. You could not see a mistake. The state now shows the aggregation with the meter, for example SUM of Amount.

Integrations

A link that creates a new quote version The create new quote version action is now also available as a link. An external system can send a user directly into a new version of a quote. The Salesforce quotes integration uses this link. The user starts the new version from the opportunity, and does not first find the quote in Desk.

Desk

Consistent action buttons Action groups now use one pattern in all screens. One action is a single primary button. Two actions are a primary button and a secondary button. Three or more actions are a primary button and a context menu. The context menu always has the horizontal ellipsis icon. An action no longer moves between a row of buttons and a hidden menu on different screens.

A sidebar section with one page is a link A sidebar parent with only one visible child is now a link, and no longer an expander. The link has the name of that child page. Product catalog is now Products. Payments keeps its own name, and does not show the child name “Overview”. Usage metering also changed: Files is now a tab and not a submenu, and Reprocessing is under Insights.

Clearer labels on the wallet balance box The wallet balance box on a customer now shows correct labels. The first figure is “Available balance”. This is the open balance, which is the balance minus the reserved amount. The second line gives the name of the wallet type, and no longer repeats the word “Balance”. You can also create a credit and use it in one step. “Save and create wallet” on the credit panel saves the credit type. It then opens the wallet panel with that credit type selected.

Fixes

bug-fix
  • You can now edit a wallet workflow after you create it. Before, you could only create and delete it.
  • The parent customer list on the customer form no longer includes archived customers. You cannot connect a hierarchy to a customer that you retired.
  • Desk now shows products in the display order of the catalog.
  • Desk no longer shows a separator next to a quantity if the unit name is empty.
  • The date range selector no longer shows an arrow between the two fields. The fields now have the labels “Start date” and “End date”.
  • Smaller interface corrections: the payments side panel is now wide enough to read. A long shopper reference truncates, and does not break the layout. The buttons in each group have the same size. Desk hides the “Manage entitlements” action for a product that has no features.