Skip to navigation

Summary

An included volume can now reset on its own period while you keep invoicing monthly, a quote shows every invoice of its term, checkout sessions complete end to end, and subscriptions can remind customers before they end.

Pricing

An included volume can reset on its own period An allowance no longer has to follow the billing period. default_included_volume and a schedule’s included_volumes[] take reset_type: PERIOD with a period, so an order form that includes 3,000,000 units per quarter can still be invoiced monthly, with the overage billed in arrears each month and the allowance starting again every third one. partial_period decides what happens when such a period is cut short: FULL keeps the whole allowance, the default, and PRO_RATA scales it down by whole months, or by days when the period is shorter. The period has to be a whole multiple of the billing period, or of the pricing period when the config declares no billing period, and that is checked wherever a schedule is created, including subscription and quote init, carry-over and group transitions. Top-up pricing accepts neither PRO_RATA nor PERIOD. In Desk the reset is chosen on every pricing editor and on a schedule’s included-volume override, where an override that sets no reset_type inherits the pricing’s. The quote PDF prints the reset period and the proration, and now shows the included volume on tiered and stair-step pricing as well.

Markups are no longer capped at 100% A markup percentage above 100 is accepted, so a bundle resold at four times its cost can be configured as a 400% markup instead of being split into several clauses. Discounts keep the cap, where a percentage over 100 has no meaning.

The order of your pricing is stored when you save it display_order is resolved on save rather than only when Desk’s “Change pricing order” screen is used, so a plan and its invoices stop falling back to the order in which events happened to be processed, which differed per invoice. An order you submit on a pricing, a pricing group or a pricing item is stored as sent and takes precedence over the underlying product order. A pricing added without one is placed after its siblings when they are numbered, and a list where nothing is numbered sorts on the product, product item and product category order instead, both when the plan is read and on the invoice. 0 and below is refused, and two entries in the same list cannot share a number. An override follows the pricing it overrides and carries no order of its own.

Fixes

  • Indexation scoped to a product, a revenue item or a price rule applies to override pricing. It resolved the override’s own id instead of the original’s and refused the call with “is not part of pricing plan schedule”, so only indexing all pricing at once worked.
  • A pricing plan schedule read straight after it was created returns its discounts, coupons, markups, commitments and entitlements. The create event was built from the in-memory model, where those are not yet filled in, so the first read, the PRICING_PLAN_SCHEDULE.CREATED webhook and the audit record all showed the schedule without them. Invoicing was never affected.
  • Resetting a customized price in a multi-period setup leaves the period’s pricing in place and shows the default again, instead of removing the pricing from that period.

Quotes

See every invoice in a quote’s term GET /v1/quote-versions/{id}/summary returns the whole billing schedule of a quote, not just the first invoices. Each schedule carries an invoices[] list with the invoice_date, the amount_excluding_tax and last_invoice on the final row, and each invoice carries periods[] with start_at and end_at, a billing_timing of IN_ADVANCE or IN_ARREARS, and per_product amounts. Commitments and lines that span several products land in other_amount_excluding_tax, and a one-off fee gets its own zero-length period. Only invoices that actually bill something produce a row, the same rule the existing invoice_count uses. This is what a two-year ramp needs to be reviewable: a sales rep, or an agent building a quote card, can see what the customer pays and when without pulling thirteen full invoice objects. Each period is rounded on its own and an invoice is the sum of its periods, so the rows add up to the quoted total up to rounding.

Subscriptions

Find the subscriptions that hold a product, or do not POST /v1/pricing-plan-subscriptions/search takes product_id and exclude_product_id as filter_fields, each accepting a single value or a list of values. They match against the products on the schedule that is active now, so “which active customers do not have Support yet” is a single call rather than a scan of every subscription. Every filter value on this search is validated now: a status or type outside the accepted list, or an id of the wrong resource type, answers 400 naming the entry, where it used to return an empty result that looked like a working query with no matches. Product ids are checked for their format only, so a well-formed id that does not exist simply matches nothing. status accepts a single value as well as a values list, which it silently ignored before. See Searching resources for the full filter table and an example.

Fixes

  • An invoice finalised ahead of its invoice date no longer causes a second invoice for the same period. The lookup that finds the invoice to merge into considered only future, open and draft invoices, so a finalised one was invisible and the billing chain created a duplicate.
  • A schedule that starts and ends inside a single local day produces its invoice. On calendar billing the period was clamped to the schedule end, so start and end landed on the same date and the schedule change failed with “no next invoice”.

Invoices

Fixes

  • Voiding an invoice that is already cancelled at the tax provider no longer fails the void.

Payments

Filter the payments list by result GET /v1/payments takes a repeatable results[] query parameter, so ?results[]=REFUSED&results[]=ERROR lists only the payments that did not go through. A payment matches when its result is any of the given ones, and leaving the parameter out changes nothing. An unknown value answers 400 naming the field. Until now the list filtered only on customer, invoice and external reference, so finding refused payments or failed refunds meant paging through everything.

Customer portal

A checkout session finishes the job A paid checkout session now produces everything it was meant to: the customers, with parents created first and the payer stored under the id the payment charged, the payment method on the payer, a subscription per template sharing one start date, a single invoice, and the payment attached to it. The session then reports COMPLETED, its link closes, and a PORTAL_URL.CHECKOUT_SESSION_COMPLETED webhook fires. Completion starts inline right after the payment is authorised and is finished by a retrying queue item, with each step recording what it created, so nothing is made twice and a session can be resumed rather than restarted. A session that cannot finish reports FAILED with the step and message that stopped it, raises PORTAL_URL.CHECKOUT_SESSION_FAILED, and can be resumed with POST /v1/portal-urls/{id}/complete. The first invoice is held until the last subscription is on it and the payment is linked, so it is no longer finalised seconds too early. A session subscription can override its payment_acceptor_ids, otherwise it takes the template’s list, so renewal invoices are charged with the card the customer just used.

Payment methods that match the session The payment-method options call accepts a portal_url_id and answers for that checkout session: its own acceptors, the country of the invoice customer and the total the payment will take. The checkout page had to pass a preview amount and could not ask for the session’s acceptors, so it could offer a method the payment then refused, and the right answer changes as soon as the customer enters a country. A session token opens only its own session, and a platform caller needs PORTAL_URL.VIEW.

Fixes

  • A discount at checkout is listed under the product it applies to, with the same chip an invoice line carries in Desk, and reads as written rather than shouted: ”↘ 100% discount” instead of “100% DISCOUNT”. Markup, adjustment and commitment chips are unchanged.

Workflows

Remind customers before a subscription ends A workflow can notify a customer a configured time before their subscription’s final schedule ends, with an END_DATE_REMINDER variant under PRICING_PLAN_SUBSCRIPTION. reminder_periods takes one or more periods in the usual workflow units, so a reminder can go out both sixty and seven days ahead, and include_auto_renewing decides whether subscriptions that renew by themselves are reminded too, which they are by default. Reminders are scheduled from the subscription’s own lifecycle and revalidated before they are sent, so a subscription whose end date moved, or that was paused and resumed, is not reminded about a date that no longer applies.

Desk

Branding and portal settings are separate pages Settings splits branding in two. Branding keeps the primary and secondary colour with the logo and the icon side by side. Portal is new, needs BRANDING.UPDATE, and holds the display name, the icon, and an optional second icon for dark backgrounds, next to a live preview of the portal that updates as you change them. When the dark-background icon is set, the preview shows it on the primary colour, which is where it will appear. Image uploads accept drag and drop, and check what is dropped against the formats the field takes.

Approval requests say why you cannot approve your own A user who sent a quote, an invoice or a schedule for approval and is also an approver on the policy sees that it is waiting for another approver, and what to do when they are the only one, instead of a missing button with no explanation. On schedules, their own requests are left out of the reviewable ones, so Approve and Reject no longer appear for them and a bulk approve sends only the requests they may actually review.

Fixes

  • Modals and side panels open and close the same way everywhere, with side panels sliding in and modals no longer doing so.
  • Opening or closing a side panel on the product and reporting pages no longer reloads the page behind it, which refetched its data, showed its loader again, jumped to the top and lost the filters you had set.
  • GET /v1/products pages correctly, so a catalogue larger than one page is no longer cut off at fifty.

For developers

Discounts, commitments and markups have their own ids Each clause on a pricing plan schedule carries a stable public id, disc_ for a discount, comm_ for a commitment and mark_ for a markup, along with created_at and updated_at. The clauses report lists them, so a clause can be followed across exports and matched to the one in the API rather than being identified by the schedule and its values.