Skip to content
SAFE Billing PlatformDocs

Changelog

Use this page to find new and updated guidance by audience. Entries are listed newest first.

September 2026

Added
Changed
  • Support admins: Support & Ticketing now explains when a case replaces a ticket: where a dealer has Inbound Mail Opens Cases switched on, unmatched customer email opens a CRM case and the Raise Ticket buttons disappear for that dealer’s customers, with the 20-open-case and 200-message limits that send mail back to the ticket flow.
  • Support admins: User Management and User Groups cover the Login (CRM) access type, CRM Sections, the CRM permission family, the four supplied CRM groups, and the customer form’s Credit Control section now being granted per user group.
  • Support admins: MyAccount Profiles documents the CRM surfaces a profile controls, including that My Cases appears only where the profile names at least one case category.
  • API integrators: The API and KPI pages name the /crm/api/v1 and /crm/kpi/ addresses, AI Assistants covers the Pre-Sales, Credit Control and Outreach access levels, and Bulk Actions lists the six CRM record types now supported.
  • Billing teams: Leads, deals and pre-sale products are now created in the CRM only. The billing backend no longer offers the Add Lead entry, the Pre-Sale submenu or the Pre-Sale add options on customer, number and service pages; it keeps the deal page for Bring Deal Live. Customer statuses carry an Is Lead flag and number, service and feature statuses a Pre-Sale flag.
  • Support admins: Display Settings offers the CRM design as a theme for the whole billing backend, alongside Modern and Retro.
  • Billing teams: The auto top-up Threshold Value reads as the headroom left before the Reference Limit for both threshold types and for prepay and post-pay alike, so review any Percent of Limit profile; a blank Reference Limit is no longer treated as a limit of zero.
  • Billing teams: The Marketing correspondence class is now Sales & Marketing, and the Sales: Email type carries it, so ad-hoc sales email follows the same consent rules as a campaign.
  • Support admins / Billing teams: Customer figures drawn from other records now follow those records’ permissions. A user holding Customers but not Invoices, Payments or Features no longer sees the balance, spend and monthly-equivalent figures on the customer screens, in reports, on the API or through an assistant, and the credit limit chips beside the customer’s name follow the Customers Billing Details field permissions. A number’s inbound rate figures follow the tariff rate cost permission the same way.
  • Billing teams: The Service Charges Monthly Equivalent counts recurring charges on features held against a service, as well as those against the customer or one of its numbers, so it reads higher for any customer whose charges sit there.
  • Support admins: The Prepaid Balance, Discount Plan Usage and Customer and Number Credit Limit reports answer to the Credit Checks reports permission rather than Invoices, matching the menu sections they sit in.
  • Billing teams: Part-free calls priced through a feature, customer default or platform default tariff had their chargeable part written off instead of re-rated, and are now charged correctly. Where a part-call genuinely cannot be re-rated, the rating evidence records Part-call could not be re-rated rather than passing without trace.
  • Support admins: A remembered browser records which kind of verification it completed, and only an authenticator satisfies authenticator-protected functions. Every remembered browser completes two-factor authentication once more when a platform takes this release.
  • Billing teams: Setting an override tariff on a feature - or changing its calls transaction code, calls VAT rate or call charge commission profile - reported “No Changes Found” and discarded the selection. Those fields save again, from the feature form and from the inline add-feature slots on customers, numbers and services.
  • Billing teams: A bulk file can tell apart two numbers holding the same number under one customer with an Alternate CDR Number column, which is also the only disambiguator that works in a feature file.

August 2026

Added
  • Billing teams / Credit control: New How Automatic Collection Works page covering the two triggers for a collection, the create and submit lead times in working days, everything an invoice and mandate must satisfy to be collected, and why an older unpaid invoice joins a later collection at the newest invoice’s due date rather than its own. Includes the five ways to stop a collection, among them cancelling a created payment before it is submitted, and the cases where automatic collection does not run at all.
  • API integrators / Support admins: Documented the optional maximum rows per list request, the X-API-Partial-Completion header announcing a capped response, and the optional API access ceiling capping every key to the permissions on the API user account. Both are off unless a platform turns them on.
  • Support admins: New Changing Your Email Address section covering the password check, the two ten-minute codes and the lockout after five wrong passwords, plus the focused pages used for required password changes, email verification and authenticator setup.
  • Support admins / Credit control: New MyAccount access links section covering the 30-day life of password reset and setup links, and the warning shown against an email address whose outstanding link has expired.
  • Billing teams: New Direct Debit Collections section for Stripe, covering the requested collection date, the three to fifteen day window Stripe accepts, and what happens either side of it - collected as soon as possible below it, rejected rather than taken early above it.
  • Credit control / API integrators: Documented the reallocate action on payments and cancelCollection on card collection attempts, along with the previously undocumented Xero linking actions.
  • API integrators: Documented the resolved feature charge fields - serviceChargeExplicit, serviceChargeCalculated and serviceChargeActual with their connection charge twins - and the warning that an empty serviceCharge is not zero.
  • Telecom teams: Documented the CDR ruleset additions - settings.processAfter for a file that waits on another, the backfill: block that fills fields on freshly loaded rows from earlier files or the same file, filename allow and deny lists, and useAlternate: case lists with literal values.
  • Telecom teams: New Externally Maintained Lists section covering the per-carrier CDR rule value lists and CDR rule translations settings, so numbers and charge band spellings can be maintained without editing a ruleset.
  • Telecom teams: Documented the permitted senders checks on CDR email, including the Common permitted envelope senders setting shared across carriers, whole-domain entries, and the addresses named on the processing report.
  • Support admins: New Platform Status page covering the main-menu health tab: the billing task queue and what a long-waiting task means, user access and security counts including the users heading for a two-factor lockout, separate API and assistant activity totals, and server and cache health.
  • Support admins: New Display Settings page covering the per-user interface options on the Advanced menu, including the Easy Read stylesheet - larger, bolder text in the Atkinson Hyperlegible typeface, with enlarged grids and a thicker focus outline - and how it combines with Reduce motion, Compact layout and High contrast / inverse.
  • Billing teams: New Rating evidence section covering what the platform records for each rated call - the tariff and rate row with their revisions, how the tariff was reached, the price date, the carrier tariff, and a log of every discount allowance applied or passed over with the reason - plus the Rating Evidence tab, the Evidence column on Call Details, and the settings controlling recording and retention.
  • Billing teams: New Earlier Versions of a Bill section covering the Invoice Files subtab on the invoice History tab, which holds each generated revision and bill length with the invoice amount as it stood at the time, and the data-protection access needed to download a superseded bill.
  • Billing teams / API integrators: AI assistants can filter KPI questions on the same fields the KPI endpoint permits, so a reporting question turning on a threshold or a range - invoices over an amount, collections retried three times or more - stays an aggregate query rather than a record listing.
  • Billing teams: Documented AI assistant summaries and rollups - a customer’s balance, overdue amount, exposure, recent invoices, payments and open TODOs in one request; invoice totals grouped by charge source and largest charges; and grouped counts and billed totals over numbers and transactions, split per currency. Unlike the KPI endpoint, an assistant can scope these figures to one customer.
  • Credit control / Billing teams: Documented the payment and pricing records an assistant can read - card collection attempts with provider decline detail, payment allocations, expected payments, tariffs, fixed fee tariffs, discount plans with their allowances, feature discount schemes, call types and carrier tariffs.
  • Support admins / Billing teams: Documented the AI assistant Pricing grant for changing tariffs, price books, discount plans and call types including bulk price increases, unticked by default, and the pricing records an assistant can read under General Records access.
  • Billing teams: New Manual Billing Fees section covering the charge for customers who do not pay by Direct Debit: setting the amount on each payment type, selecting the Manual Billing Fee account flag, when and how the fee reaches the invoice, and why it stops on its own when a customer moves to Direct Debit. Includes the UK rules on setting the amount, covering the consumer card surcharge ban and the cost-reflective test.
  • Billing teams: Documented the customer Account Flags options - Manual Billing Fee, Late Payment Fee, Do Not Chase, Payment Plan Agreed, Email Bills and Post Bills - and which are set on a new account.
  • Billing teams: New Charging an Account-Level Fee worked example for flat account charges such as a paper billing charge, covering the feature type that allows customer-level attachment, and the fact that a customer’s bill delivery settings never start or stop the charge for you.
  • Credit control: New Charging a Failed Payment Fee section covering the supplied transaction type, adding the charge to the Unsent invoice as each payment bounces, and Ofcom’s treatment of default charges.
  • Billing teams: New Backing Out an Invoice section covering when to back one out rather than credit it, the unapprove to clear to delete sequence, why moving transactions beats deleting them, and every reason the Delete option may not appear.
  • Support admins: Documented sending Disaster Recovery Files to your own storage through a stored file provider, so invoice bundles and backups reach Amazon S3, Google Cloud Storage or Google Drive without anyone downloading them.
  • Support admins: The main menu tabs are now named and described, including what sits under the Advanced tab.
Changed
  • Billing teams / Support admins: An AI assistant’s KPI totals cover business customers only unless the connection holds Personal Customers access, matching what its record lookups already report for the same connection. The assistant is told which basis it is quoting. The KPI endpoint always reports platform-wide, so the two legitimately differ.
  • API integrators: Notes, TODOs and tickets carrying no customer follow their allocation on the REST API, the KPI endpoint and AI assistants, as they always have on the platform’s own screens. A key with access to all customers is unaffected; a key restricted to its own accounts reaches only the unlinked records it is allocated.
  • API integrators: KPI cohort filters on features count features owned through a number or a service, not only those held directly against the customer, so feature figures filtered by owning customer are higher and now correct. The REST API’s feature cohort filters are corrected in the same way.
  • API integrators: An attachment upload refused on permission or an unrecognised value returns the status naming that reason, rather than a general failure.
  • API integrators: idAfter does not filter a KPI query, on the endpoint or through an assistant, because differencing two totals either side of one id recovers a single customer’s own figures. Cohort scoping keeps createdSince, updatedSince and droppedSince. Record paging on the REST API is unaffected.
  • API integrators: Documented that the KPI endpoint answers GET only, returning 405 with an Allow header to anything else, and that a field sent in both bare and operated form has one silently replace the other.
  • Telecom teams: Grouping an assistant’s call summary by site or number needs individual record access alongside call access, since both identify the customer in practice. Grouping by period, direction, call type, rating period, number type or dealer is unchanged.
  • Support admins / Billing teams: Rewrote connecting an AI assistant for URL-only connectors. Claude, ChatGPT, Claude Code, Codex CLI and other MCP-capable assistants register themselves, so there is no OAuth Client ID to enter, and the page adds the Claude Code and Codex CLI command lines. Connections approved before 4 August were revoked by the upgrade and need approving again.
  • API integrators: Reworked KPI filtering around what each category accepts - its own named filters, resolvable by ID or name, generic f[field] filtering on the fields permitted for that category, and customer cohort scoping for aggregate questions about a group of customers. Adds the per-category filters to every KPI page, and the numbers sold by period series grouped on Date Sold.
  • Billing teams: Documented changing the payment method on an invoice - the unapprove, edit, recreate, approve sequence, and the rule that an invoice with no method of its own follows the customer’s while an explicit method overrides it permanently. Also corrected the approval wording: the lock covers the whole invoice record, not only its transactions.
  • API integrators: API list filters on lookup fields accept a display name as well as the ID, matched without regard to letter case, and an unusable date value is reported rather than quietly changing the records returned. Writes match lookup names the same way, so VOIP selects an existing VoIP number type.
  • Billing teams: Corrected the Bulk Add Numbers template guidance. Extension and Alternate CDR Number are headed (Do Not Change) because they hold what the calls are matched on, and the prefilled Alternate CDR Number applies whatever it holds. The Bulk Add Numbers: conditional Alternate CDR Number setting applies it only where it differs from the Number.
  • Billing teams: Documented the bulk CSV header markers (Information Only), (Ignore) and (Do Not Change), and the alternative column headings each field answers to - “Drop Date”, “Account Number”, “Telephone Number” and “CLI” among them - on every upload route.
  • Support admins: Updated Send Recovery Code Email for a user who has lost both password and authenticator, who now needs one code rather than two, and noted that recovery access does not count as authenticator verification, so Elevated functions stay unavailable until a new authenticator is verified.
  • Support admins: Corrected the menu path for Disaster Recovery Files, which are on the Advanced tab of the main menu and need elevated access as well as data-protection access. The page now also explains that invoice bundles are how you download every bill at once, and how they differ from a print bundle.
  • Billing teams: Non-Usage Charges now lists payment method fees as a source of charges alongside one-off, recurring, carrier-generated and manual charges.

July 2026

Added
  • Support admins / Billing teams: Documented the AI assistant call data grants - read-only aggregate call summaries and full per-call detail - including the groupings available and the extra access needed for customer-backed summaries.
  • Billing teams: Documented the connection and recurring charge columns available to custom Service Charges Report formats, showing the explicit, calculated and actual charge side by side.
  • Billing teams: New Price lock dates section covering how customers, numbers, services and features can be held on the rates that applied on a chosen date, per tariff class or across the board, including forward-dating a lock to move customers onto new pricing during a notice period.
  • Billing teams: New Early termination charges section covering the Apply Early Termination Charge and Early Termination Charge To controls on the Drop and Final Bill forms, when a charge arises from a minimum or committed term, and reversing one on reinstatement.
  • Billing teams: Documented invoice approval value limits, including separate limits for invoices, credit notes and debit notes, and how automated billing holds larger invoices for manual approval.
  • Support admins: New Customer Segment field, with the matching filter on the Customers Report.
  • Billing teams: Documented customer lifecycle actions in bulk - drop, reinstate, final bill and debt or credit write-off - and editing inherited and calculated values through Bulk Update, including indexed tariff, discount plan and price lock fields.
  • Support admins: New Who can prepare and who can apply section covering the split between preparing a bulk file and applying it, the Intern and Standard expert levels, and the Apply (Platform) and Apply (Rules) permissions.
  • Billing teams: Documented launching annual increases from the tariff lists and the Tariff Class column for carrier files with duplicate tariff names.
  • Support admins / Billing teams: New AI Assistants (MCP) integration section covering connecting Claude, ChatGPT or another MCP-capable assistant to the platform: initial setup with per-user login and 2FA approval, what each permission category grants, and using and revoking connections. Early access, enabled per platform on request.
  • API integrators: Documented the new generic list filtering (f[field][operator]=value with min/max/in/null/contains and parent-customer scoping) and sorting (orderBy=field.desc) parameters on the REST API.
  • Billing teams / API integrators: New KPI categories for payments received, Direct Debit and card collections and debt ageing, growth and churn series on the customer, number and feature KPIs, and the new groupBy, interval and measures parameters for flexible grouping on every KPI category.
  • Support admins / Billing teams: New Bulk Actions section covering the Expert Mode bulk facility: running named actions (drop, reinstate, suspend, make billable, recalculate and re-bill) across numbers, services and features, bulk approving invoices and reversing payments, the test-then-apply lifecycle, live progress, and the per-row audit trail.
  • Support admins: New Bulk Edit and Bulk Add page covering the CSV workflow for editing and creating records in bulk, including the pre-filled edit export, blank add templates, revision checking, rename columns, multi-choice fields, and per-row Update Reason and Update Details columns.
  • Billing teams: New Bulk Update and Bulk Action Lists page covering third-party and multi-customer files: automatic header recognition, name matching through the customer hierarchy, the generation log and skip report, saved rulesets, and running named actions over uploaded lists.
  • Billing teams: New Update Rules Reference documenting the full YAML rules language for awkward files, written so an AI assistant can author rules from it, with a plain-Markdown version to fetch or download for your assistant.
  • Billing teams: Annual price increases on tariffs, fixed fee tariffs and standard features can now run in bulk over an uploaded list via the New Bulk Action flow.
  • Telecom teams: New CDR Processing Rules page covering how each carrier’s file format is described: file recognition and safety holds, column mapping, call-leg fan-out, direction logic, and the YAML rules language shared with Bulk Update.
  • Billing teams: New Bulk Rate Updates page covering bulk edit and add of call tariff and fixed fee tariff rates from the tariff page: effective and direct-only rate sheets, based-upon overrides stored as minimal deltas, crystallising rates via Bulk Add, dated rate versions from pre-filled add templates, and processing carrier rate files through Bulk Update with call-type alias matching and optional tariff creation.
  • Billing teams / Telecom teams: The update rules language gains date comparisons (before, after, onOrBefore, onOrAfter, anchored to the file’s upload date), inclusive numeric bounds (atLeast, atMost), suffix matching, noneOf: condition groups, warn rules that flag rows for review without skipping them, and the pad and dateAdjust transforms.
Deprecated
  • Support admins: Bulk Import Files is superseded by Bulk Actions for new work. Bulk Import remains available and existing workflows keep working.
Changed
  • Support admins: Documented the AI assistant Personal Customers grant, which keeps individual records for personal and unclassified customers out of an assistant’s reach unless it is deliberately ticked, with the lawful-basis caution shown on the approval screen and a plain list of which assistant plans count as commercial - an individual Claude Pro or ChatGPT Plus subscription is a consumer account even when the company pays for it, and OpenAI’s Data Processing Agreement has to be executed rather than arriving with the plan.
  • Support admins / Credit control: Documented the split between direct and bulk sending permissions for correspondence and for bills and CDRs, including the separate Add (Bulk) permission for creating correspondence in bulk.
  • Billing teams: Documented the two reasons a bill cannot be emailed - nobody set to receive bills by email, versus no usable address - now that the invoice page distinguishes them.
  • Support admins: Rewrote the AI assistant approval screen around the granular permission categories - General Records, Pre-Sales, Credit Control, Customer Interaction, Pre-Sales Outreach, Service Lifecycle and Financial - with the read-access dependencies, and how a user’s flags, the connection’s grants and the platform MCP settings user combine.
  • Support admins: Documented batch lookups through an AI assistant (up to 100 values in one request), and the usedMCP flag on the user activity log.
  • Billing teams: Reworked the call tariff Scope Options for the cumulative Apply To tiers (costs, surcharges, connections, minimum cost, price rounding), the Direct rates only default versus all effective rates, and the Any of / None of call type filters for applying different increases to two halves of a tariff.
  • Credit control: Documented the bulk correspondence prerequisite checks and the seven-day duplicate warning that leaves recently contacted customers unticked.
  • Billing teams: Updated Payment Runs for the Manual Direct Debit Collection Required step, which now counts customer accounts that automatic collection cannot attempt, and collects once per customer and payment method. Billing run pages now refresh their own progress while a run is in flight.
  • Support admins: Documented the rendered email body tab on correspondence types, and added the Correspondence Archived status.
  • Support admins: Noted that future cancellation notice dates require Expert Mode.
  • Billing teams: Documented bulk adding missing numbers from the Unregistered CLIs, Unrecognised Numbers and Loose Matches reports: download the Bulk Add Numbers template with the number, carriers and calls start date prefilled, complete the customer and provisioning columns in a spreadsheet, then upload it to be tested and applied.
  • Billing teams / Support admins: Documented that the Loose Matches breakout can now be switched off on its own in the Billing Error Reports setting, with those numbers reported under Unrecognised Numbers instead.
  • Billing teams: Reworked Billing Errors for the new single Apply Changes workflow (per-row, colour-coded bill/delete/ignore/add controls applied in one pass), CSV export of every summary table, the Billable calls only filter, a searchable customer selector for adding numbers, cost columns on the charge band reports, and improved charge band allocation and Add New Call Type. Documented the on-demand Apply Discount Plans and Update Call Transactions actions on the billing run.

June 2026

Added
Deprecated

May 2026

Added
  • Billing teams / API integrators: Dated rates on call tariffs and fixed fee tariffs, with Start Date and End Date on individual rates so price changes can be staged ahead of time. A new optional Effective Date on the Apply Increase and Create Increased Version actions schedules a percentage increase for a future day. A new Expert Mode action, Recalculate Calls From Start Date, re-rates already-rated calls when a back-dated rate is added to a retail tariff. For fixed fee tariffs, dated rates are also the route to apply a mid-cycle change so the platform pro-rates old and new prices across the billing period.
  • Support admins: New Companies House integration page covering Companies House account signup, REST API key generation in the Live environment, and entering the key under Advanced > Companies House. Out of the box, the platform uses a shared default key to run the initial Companies House lookup the first time a customer is put into a class with the Check Companies House flag set. Configuring your own key takes over from the shared key for all Companies House traffic and enables periodic background refresh of UK Limited and UK PLC customer profiles, so the data stays current as Companies House records change.

April 2026

Added
  • Support admins: New Customer Classes page in System Administration covering the shipped classes, the personal vs company distinction, Companies House profile auto-population, PECR confidentiality for itemised bills and traffic data (with links to ICO guidance), and the per-contact attachment-preference route. Consent is now recorded on the customer record through the new GDPR & PECR Consent Given flag rather than through duplicate class variants. See GDPR and PECR Consent on Customers for the paper-trail workflow using the Update Reason and Update Details fields.
  • Support admins: New Suspend and Unsuspend actions for customers, numbers, services, and features. Suspended statuses suppress recurring charge generation while usage charges continue to apply. Unsuspending back-fills missed recurring charges.
  • Support admins: New Make Non-Billable and Make Billable actions for customers, numbers, services, and features. Switch between billable and non-billable statuses without changing active or suspended state.
  • API integrators: New suspend, unsuspend, makeNonBillable, and makeBillable actions on Customers, Numbers, Services, and Features API endpoints.
  • Support admins: New Transaction Types and Feature Types pages in System Administration covering the configuration objects that drive invoice grouping, accounting codes, feature defaults and contract terms. Cross-linked from Fixed Fee Tariffs and Transactions.
  • API integrators: New Transaction Types and Feature Types API endpoint reference pages with full field tables, including the one-off and recurring transaction type defaults on feature types.
  • Billing teams: New Applying Credits and Refunds user guide covering all three approaches, refunding a billed charge, adding a goodwill credit or manual adjustment, and recording money back to a customer, with a decision table to help choose the right method.
  • Billing teams: Expanded Working with Payments with a dedicated Recording a Payment Refund section, worked example for negative-amount payments, and improved page structure throughout.

March 2026

Added
  • Billing teams: New Correcting Charges on an Already-Invoiced Period guide covering all four approaches (delta adjustment, replace with credit, add with external credit note, unapprove and correct) with step-by-step instructions and a decision table.
  • Billing teams: New Add New Charges mode on the Change Recurring Charge action, allowing new charges to be added without removing or refunding existing ones. Designed for use when a credit note is being raised outside the platform to cover the old charges.
  • API integrators: New chargeChangeMode: add value on the changeRecurringCharge action, alongside the existing replace and delta options.
  • Billing teams: New Collect Payment action on invoices for on-demand payment collection via direct debit or card (Expert Mode).
  • Billing teams: New Collecting a Specific Invoice quick-reference for choosing between on-delivery, Collect Payment, and Instant Bank Pay.
  • Billing teams: New Common Tasks section on GoCardless ongoing page covering single-invoice collection, payment status checks, and failed collection handling.
  • Billing teams: New Billing Preview tab documentation covering live pre-run customer preview with projected charge breakdowns, previous invoice comparison, and projected outcome indicators.
  • All users: New Bulk Import Files guide covering upload, type/mode selection, the two-step test-then-import process, file activity tracking, supported formats, and column references for all 10 import types.
  • Billing teams: New Managing Annual Price Increases guide covering the end-to-end workflow for applying periodic price increases using the Service Charge Report’s Annual Increase format and bulk import.
  • All users: New Using Reports guide covering how to run, filter, and export reports, with guidance on filter views, output types, CSV downloads, and custom report formats.
  • Support teams: New Contacts guide covering direct and shared contacts, communication settings, and when to use contacts vs comma-separated emails.
  • Support teams: Expanded customer email addresses with comma-separated format example and contacts cross-reference.
  • Support teams: Updated Managing Multiple Addresses with guidance on comma-separated emails vs contacts.
  • Billing teams: New Direct Debit Accounts guide covering account management, payment links, manual and automated collection via GoCardless, and Instant Bank Pay.
  • Billing teams: New Payment Cards guide covering card management, payment links, manual and automated collection via Stripe, and card status management.
  • API integrators: New Direct Debit Accounts Endpoint and Payment Cards Endpoint API documentation with full field references.
  • Billing teams: New Charge Change Mode (delta mode) on the Change Recurring Charge action, allowing price changes to preserve approved invoice history by adding adjustment rows instead of replacing existing charges.
  • API integrators: New changeRecurringCharge action on the Features Endpoint with chargeChangeMode parameter supporting replace and delta modes.
  • Billing teams: New Transaction Cut-off Date option for invoices and billing runs, allowing non-call charges to be included by transaction date instead of bill date. Useful for complex billing setups and manual/ad-hoc transactions. Documented across Invoices, Billing Run, Request Bills, and Transactions.
  • API integrators: New transactionCutoffDate field on Invoices and Billing Runs API endpoints, including webhook payloads.
  • Billing teams: New Transaction Amount Mode documentation covering the per-item entry toggle for transactions with a feature count, available in enhanced mode.
  • Billing teams: New comprehensive Managing Features user guide covering the full feature lifecycle with worked examples, including a mid-month feature count increase scenario.
  • Billing teams: Expanded Change Recurring Charge action documentation with a worked example, feature count visibility note, pro-rata cross-references, and corrected From Date field description.
  • Billing teams: New bundle tariff worked example showing end-to-end setup of inclusive minutes with overage, covering tariff, discount plan, feature, and the Discount Plan Multiplier vs Feature Count distinction.
  • Billing teams: New backdating and mid-period features section covering pro-rated first charges, past start dates, and moving charges onto already-issued invoices.
  • Billing teams: New Reapply Discount Plans action documentation for recalculating allowances after invoice changes.
  • Billing teams: New adding a bundle to an existing number step-by-step guide.
  • Telecom teams: New Call Management guide covering where call records appear in the UI, combined calls vs call details views, A-leg/B-leg call concepts, admin vs customer views, unbilled calls, deleted calls, and a worked example.
  • API integrators: New Calls and Deleted Calls API endpoint documentation with full field references, query parameters, and example requests.
  • Billing teams: New per-class markup documentation covering percentage markups per call class (Inbound, National, Mobile, etc.) on customers and numbers, applied during rating when a tariff has no matching rate.
  • Billing teams: New rating priority guide showing the four-level pricing chain: tariff rate, default tariff, per-class markup, and fallback markup.
  • Billing teams: New tariff resolution chain documenting the six-step lookup order the platform uses to find a tariff for each call, from feature tariff through to default tariff.
  • Billing teams: New default tariffs section covering automatic fallback tariffs matched by carrier and number type, including requirements, matching rules, specificity ordering, and deletion restrictions.
  • Billing teams: Expanded fallback markup documentation to cover fallback settings on customers and numbers, with priority chain (tariff > number > customer).
  • Billing teams: New default fixed fee tariffs documentation covering automatic fallback tariffs, rate specificity matching, priority between multiple defaults, deletion restrictions, and a practical example. Updated the tariff lookup chain and tariff availability sections with default tariff references.
  • Telecom teams: New Events section on the Call Management page covering event-count billing, per-event rating, where events appear on invoices and call detail pages, and discount plan allowance support.

February 2026

Added
Changed

January 2026

Added
Changed

December 2025

Changed

November 2025

Added

October 2025

Changed

July 2025

Changed

June 2025

Added
Changed

August 2023

Added

July 2023

Added