Beta » Wallets track balances in tokens, credits, or dollars, automatically as they are used.Learn more
New » Metering turns raw usage events into billable quantities on a subscription.Learn more
/

Help Center › Getting Started › Product Releases

October 2026 Product Release

Applies to: All Maxio modules

··View as Markdown·

Last updated on Nov 7, 2026

Maxio released the following updates and new features during October 2026. Maxio adds new entries to this list throughout the month as features become available. For the full list of changes, see the Product Change Log.

Selling

Map more Salesforce fields and edit a transaction's Salesforce ID

Salesforce field mappings offer new options: the parent Account's name and the contact fields Salutation, Phone, Alt Phone, Fax, Contact, Alt Contact and Account Number as Account Metadata sources, a Customer's QuickBooks ID in Send Financial Records, and the renewal's Duration and Start Date for Renewal Opportunity Line Items. A Transaction's Salesforce ID can also be edited on its Update Transaction screen. (Released: 1 to 13 October 2026)

Learn more
Why it matters:
You can map more of your Salesforce data to Maxio, and Maxio data back to Salesforce, without creating a Sales Order or filling fields in by hand, and any Editor can correct a Transaction's Salesforce ID after an Account merge.
Where to find it:
In the Salesforce integration settings, on the Account Metadata Field Mappings, Send Financial Records and Send Renewal Opportunities tabs, and on a Transaction's Update Transaction screen. For setup, see Configure Get Account Metadata for Salesforce, Configure Send Financial Records for Salesforce and Configure Send Renewal Opportunities for Salesforce.

Auto-process Sales Orders created through the API and accept Sales Order and Advanced Billing fields

A Sales Order created through the API can now be processed into a Customer, Contract and Transactions as soon as it is created, and the response reports whether it was processed, skipped or failed. The Sales Order API also accepts the customer contact, cadence template, list price and Advanced Billing subscription fields that processing reads, which were previously dropped, so an API-created order could never create an Advanced Billing subscription. (Released: 2 to 12 October 2026)

Learn more
Why it matters:
If you create Sales Orders through the API, you no longer have to process each one from the queue by hand, and you can set the same details the screens and CRM syncs already could. An order with a product line and automatic payment collection can now build its Advanced Billing subscription, using a payment token that is never echoed back or logged. Some values, such as CC and escalation emails, cadence template and local unit list price, apply only when the matching account settings are on.
Where to find it:
Turn on Admin > Account Settings > API > Auto-Process API Sales Orders, which is off by default, then send autoprocess: true on POST /api/v1.0/sales_orders/. The new fields are optional and are documented in the in-app API documentation under Admin > Settings > API Documentation. For the processing steps, see Processing Sales Orders.

Billing

Get more control over wallet overage and balances, and see which grant each charge came from

Wallets give you more control and clearer detail. You can correct overdraft usage with Adjust on an Overdraft row, create and edit Wallet Billing Products on a dedicated page and add a price point to an existing one, and choose Bill usage beyond the balance as overage. Balance Breakdown on a wallet's page now shows each grant as the amount used out of its original amount, with what is left underneath and a bar that fills with the share used, and balance corrections made with Adjust Balance and expirations are listed apart from usage. In a wallet's Ledger, a Usage row now names the grant it drew from on a line under its description, for example Drawn from Monthly allowance, and an Expired row names its grant as From Monthly allowance. The overage line for a wallet created from a feature now adds the included allowance to the wallet product's name, for example Additional calls (beyond 100 included), on the invoice and on previews of the upcoming invoice. For API users, Wallet API responses show the posted balance next to the spendable balance, and a grant, debit, adjustment or wallet creation can be retried with a request header so it is not applied twice. (Released: 2 to 27 October 2026)

Learn more
Why it matters:
You have more control over how a wallet is funded, corrected and billed, and you can tell the balance a customer can spend from the balance posted to the ledger. You can also see at a glance how much of each grant has been used, and a grant you corrected down no longer looks as if it was used. On an overage line, the included amount shows your customer that the quantity is beyond their allowance, so a line reading Additional calls with a quantity of 75 isn't read as 75 calls in total. In the Ledger, you can match each usage and expiration row to the grant it came from, so a usage row isn't mistaken for the grant row it drew from.
Where to find it:
On a Subscription's Wallets tab, under Catalog > Wallet Products, and in the Wallets API, on sites with wallets turned on. Open a wallet to see Balance Breakdown, where the column reads Used, or Recorded Usage for a wallet paired with a meter. The new overage line title appears on a subscription's invoices. In a wallet's Ledger, each Usage and Expired row names its grant. A wallet added manually on the subscription, or an overage line that bills several wallets, keeps the plain wallet product name. For details, see Understand Wallets, Manage Subscription Wallets, Create and Manage Wallet Products, Correct a Wallet Balance, Check a Wallet Balance and Funding, Manage Wallets with the API and Review Wallet Grants and Ledger Entries. Look for it here if it's available to you.

A Customer can hold a company registration number for France, such as a SIREN or SIRET, beside their VAT number, through the API and an optional SIREN/SIRET field on the Create and Edit Customer forms. A Customer and your Tax Origin Address can also store the addressing line registered in the French e-invoicing directory, and invoices and credit notes submitted to Avalara under France's B2B e-invoicing mandate send it as each party's endpoint ID instead of the SIRET. A document whose customer or seller has no addressing line isn't submitted, and the error names the party that needs one. Those documents also start their note with the three legal mentions French e-invoicing requires, late payment penalties, early payment discount and the fixed recovery fee, followed by the document's memo. (Released: 2 to 22 October 2026)

Learn more
Why it matters:
You can keep both identifiers France requires. The French directory routes documents by addressing line and rejects one it doesn't recognize, even when the SIRET is correct, so sending it, and catching a missing one before submission, keeps your French documents from coming back as rejections. Refund and void credit notes pass French validation without you adding the legal mentions to every memo, and you can set the wording once for your Site.
Where to find it:
The SIREN/SIRET field is on the customer forms when eInvoicing is on and the Customer is in France. On the customer form, fill in Addressing line (optional), which shows when eInvoicing is enabled and the Customer's Shipping Country or Tax ID country is France, or your site has an enabled French eInvoicing mandate. For your own business, add an Addressing Line identifier to your Tax Origin Address on the Taxes settings page when its Country is France. Enter the 9-digit SIREN, optionally followed by a registered suffix. For the legal mentions, go to Config > Invoicing > eInvoicing and use the French legal mentions section, which appears when your connected company has the French B2B or B2G e-invoicing mandate. Edit the three texts and click Save legal mentions. A blank field uses the French default text. For the Avalara e-invoicing setup, see Setting Up the Avalara ELR Integration and Using the Avalara ELR Integration. Look for it here if it's available to you.

Show GST on each line, save zero-rated custom tax rules, report Taxwire tax on consolidated invoices and recalculate tax on reissued invoices

Invoices, credit notes and debit notes in Australian or New Zealand dollars can show a per-line GST Rate, GST Amount and Gross Amount when Display Tax Line Item is on. A Custom Tax Rule can be saved with a 0% rate and shows a $0.00 tax line on invoices. Taxwire now reports tax for consolidated invoices. Reissuing a GL-synced invoice to the Billing Portal now asks your connected Advanced Billing tax provider to recalculate sales tax. (Released: 7 to 15 October 2026)

Learn more
Why it matters:
You can show customers in Australia, New Zealand and zero-rated regions the tax breakdown they expect, and get a real recalculated tax amount when you correct a taxable address on a synced invoice.
Where to find it:
Go to Config > Settings > Invoices > Tax for Display Tax Line Item, Config > Taxes for Custom Tax Rules, and Reissue to Billing Portal in an Invoice's action drop-down menu. Reissuing does not sync the new tax amount back to your general ledger, so check the matching record there. Taxwire reporting is automatic for sites using Subscription Groups. Look for it here if it's available to you.

Set rates for one usage segment on a subscription and keep rating interval pricing steady

You can now give one Subscription its own rate for a single type of metered usage, called a Segment, without changing the price point other Subscriptions use, and add a Segment value the price point doesn't define, such as a new region, for that Subscription only. Set it in the new Segment Rates section of Custom Pricing on the Subscription's Update Price Point screen. A rating interval is the stretch of time over which Maxio adds up a Customer's usage to decide which pricing tier applies. Metered usage on a Price Point with a rating interval is now priced from the total the Customer has already reached, instead of from zero. To keep that total from resetting or re-pricing usage that was already billed, a Price Point with a rating interval can be set only on a Product that has never been active on the Subscription, and a Product that already has one can switch only to another Price Point with the same rating interval and billing interval. A change that contradicts a locked-in Renewal's Price Point is rejected, and so is a term renewal, Plan change or scheduled Subscription change that doesn't fit a metered Product's rating interval, with a message naming the Product. On a Termed Subscription this applies when the rating interval doesn't fit evenly into the remaining term, or into the new term of a Renewal waiting to take effect. A Subscription can no longer bill an event-based metered Product over a period longer than the site's limit, which is 3 months by default or 18 months when Maxio Support extends it. For API users, segment custom pricing in a request that can't save it now returns an error instead of being ignored, and the Metering Events list no longer accepts a page number and uses cursors. The Events tab moves one page at a time with Previous and Next. (Released: 5 to 30 October 2026)

Learn more
Why it matters:
You can give one Customer a special rate for a type of usage, even one your catalog doesn't define, without touching the catalog price, and tiered usage is priced from the right place when a Price Point changes. If you poll metering events, bill metered Products over long intervals or renew terms and change Plans on Subscriptions with a rating interval, check your requests and Price Points: a page number is refused, and anything outside the new limits returns an error that names the Product and the rule it breaks. When a lock-in or change is rejected, fix the term or the Price Point.
Where to find it:
Go to Metering > Streams and open a Stream, for the Events tab and Meter charts, and the Subscription create and update API for segment rates, on Sites with Maxio Metering. A Scheduled Renewal rejects Save and Lock In, and an Auto-Renewal with an immediate Lock-in Date fails the same way. A Plan change, and a scheduled Subscription change that adds a metered Product, are rejected on the same rule. Scheduled Subscription changes are available on sites with Planless Subscriptions. For segment rates on a Subscription, open the Subscription, select Products, click the Product's More icon (...), select Update Price Point and then Custom Pricing. The Segment Rates section doesn't appear on sites that track list and sales prices. Errors also appear when you create or change a Subscription, activate a metered Product on its Components tab, or add an interval to a price point. For details, see Understand Streams, Meters, and Segments, Design Your Catalog: Use Metering with Products, Set Custom Pricing on a Subscription and Report Product Usage and Allocations. Look for it here if it's available to you.

Change a branding theme's template, show payment terms and set a default theme

Branding Themes have three new options: a Change Template button in the Template Editor to apply one of five base templates, Payment Terms and Payment Terms Label tags that show Maxio Core payment terms on invoices, and an account-wide Default Branding Theme applied to new Customers. (Released: 8 October 2026)

Learn more
Why it matters:
You can start an invoice design from a different base template, show customers the same payment term wording Maxio Core tracks, and no longer pick a theme by hand for each new Customer.
Where to find it:
Go to Config > Branding > Actions > Template Editor for the template and the tags, and Advanced Billing > Settings > Invoice Defaults > Default Branding Theme. Branding Themes must be available on your account. For details, see Manage Branding Themes, Edit Invoice Template Layout and Display Payment Terms on Invoices. Look for it here if it's available to you.

Keep entitlements through scheduled renewals and custom pricing, and see feature limits and units in the catalog

Subscribers now keep the features and limits you agreed after a scheduled renewal or a change to a component's custom price. A scheduled renewal for a subscription on a custom product or component price point now copies that price point's entitlements onto the renewal, where before the renewal removed them, and changing only a component's custom price no longer adds back default entitlements you had deliberately left off. When you override the default entitlements for a Plan or component in a scheduled renewal, the renewal page shows your overridden values after you save and reload it, instead of the price point's defaults. Limit entitlements now show their feature's unit, and every team member with access to your site can see the feature catalog, while changes need the permission to manage the product catalog, settings and integrations. For API users, creating a feature catalog item with a price point that does not match its Product or Component now returns an error, and feature changes sent without propagating to subscriptions now apply to a copy of the price point when it has subscribers. (Released: 8 to 26 October 2026)

Learn more
Why it matters:
If you manage entitlements through the API, check that requests send matching price points and that you ask for propagation when you want existing subscribers to change. Team members no longer need Admin or Owner access just to view features. You can also confirm that a locked-in renewal carries the entitlement values you agreed, and edit its price without setting the override again. If you agree entitlements through custom pricing, your subscribers keep the features and limits you agreed after a scheduled renewal and after a later component price change.
Where to find it:
Go to Catalog > Features, a Subscription's Entitlements tab, and the feature endpoints of the API, on sites with entitlements turned on. For a scheduled renewal, select Manage Renewal on a termed subscription, then Preview Details to see the overridden values. Manage Renewal appears for multi-frequency subscriptions on sites that allow Planless Subscriptions; other sites see a Change button there instead. For details, see Configure Entitlements, Understand Entitlements, Read Subscription Entitlements with the API and Set Custom Pricing on a Subscription. Look for it here if it's available to you.

New payment not attempted webhook event

Adds a new opt-in webhook and API event, payment not attempted, with reason no_payment_method. It fires when Advanced Billing tries to collect from a Subscription and finds no payment method on it at all, covering a periodic renewal, a dunning retry, a Component allocation, a reactivation, a one-time charge, and a payment applied to an Invoice. (Released: 12 October 2026)

Learn more
Why it matters:
Previously, a collection attempt against a Subscription with no payment method on file produced only a renewal failure and a dunning step reached event, the same pair a declined card produces, with nothing distinguishing "there was nothing to charge" from "the gateway declined the charge." An integration that reacts to payment failure the way it reacts to a decline, for example by asking the Customer to update their card, would act on Customers who did nothing wrong. This new event carries its own reason, so you can tell the two cases apart and react to each correctly.
Where to find it:
Subscribe an endpoint to it under Config > Settings > Webhooks, where it's listed as "Payment Not Attempted." It's also selectable in the admin Test Webhook tool, and appears in the API v1 event feed and the Subscription's activity log like any other event. Subscribing is opt-in per endpoint; no existing endpoint receives it without choosing to.

Filter invoices by date and due date at the same time

Date, Due Date, and Paid Date are now separate filters on the Invoices list, so you can set any combination of them together instead of choosing only one. The redesigned filter bar also adds quick Document ID and Customer search, and a collapsible row of pill filters for the rest. (Released: 13 October 2026)

Learn more
Why it matters:
Previously you could filter Invoices by only one of Date, Due Date, or Paid Date at a time. Now you can combine them, for example Invoices issued last month with a due date this week, without exporting results and cross-referencing them yourself.
Where to find it:
Go to Billing > Invoices and click Filter to show the row of filters, where you can set a Date, Due Date, and/or Paid Date range. Document ID and Customer search stay available directly on the filter bar.

Mandrill as a second email delivery provider

Advanced Billing can now send through Mandrill as well as Mailgun. You can connect your own Mandrill account directly, or Maxio Support can assign your Site a Maxio-managed subaccount; either way, an optional sending domain gets checked against Mandrill's SPF, DKIM, DKIM2, and DMARC records. (Released: 15 October 2026)

Learn more
Why it matters:
If you're migrating from e-Bill and already have a Mandrill account, you can connect it directly instead of standing up a brand-new Mailgun sending domain and publishing fresh DNS records.
Where to find it:
Go to Tools > Email Insights > Setup Info, new Mandrill section. Contact Maxio Support to have it turned on for your Site. A Site can only have one active custom email provider (Mailgun or Mandrill) at a time. Delivery status for emails sent through Mandrill is not recorded yet. Look for it here if it's available to you.

Import dunning configuration from a sandbox into a live site

You can copy the Dunning Schedules you tested on a sandbox into a live Site from the Retries & Dunning page, along with their dunning email templates, email layouts, and the dunning settings you select. A preview shows the result for every Schedule before anything on the live Site changes. (Released: 19 October 2026)

Learn more
Why it matters:
You no longer rebuild every Schedule, step, email and Product assignment on your live Site after testing it on a sandbox, so the two Sites match. A Schedule you configured on the live Site is overwritten only when you choose to replace it and confirm a second time, and never while subscriptions are in active dunning on it. Customers, subscriptions, invoices, payments, gateways and prepaid dunning are never copied.
Where to find it:
On a live Site, Config > Retries & Dunning > Import from sandbox. Credit Card, ACH, Remittance and Direct Debit Schedules are imported, for All Products and for Products or Product Families matched by handle. You need the manages product catalog, settings, and integrations permission on both Sites (account administrators always have it), and only sandboxes in the same account are offered. Look for it here if it's available to you.

Subscription custom fields in invoice email messages

You can now use Subscription custom fields as placeholders in Email Message Library messages, alongside Customer and Invoice custom fields. A {subscription_<reference name>} placeholder is replaced with the value from the Subscription the invoice bills. (Released: 19 October 2026)

Learn more
Why it matters:
Subscription-level details, such as a link to a usage report, can go out in the invoice email itself, so you don't need to send the Customer a separate follow-up message.
Where to find it:
Mark the Subscription custom field Available on e-Bills on the custom fields page, then pick it from the Subscription Custom Fields group in the placeholder drop-down when you create or edit a message in the Email Message Library on the Admin screen. Available only for accounts with the Billing Portal enabled. The placeholder is blank when the invoice bills no Subscription or its line items span more than one Subscription.

Edit tax, accounting, signup, Billing Portal and proration settings on many plans and products at once

A new Bulk Edit Catalog Items page lets you select up to 500 Plans and Products from any Product Family and change Taxable, the tax code, Item category and Accounting code on all of them in one action, instead of editing each item. A validation check shows which items would fail before you apply, and the results list each item's outcome so you can reselect and retry the ones that failed. On AvaTax, TaxJar, Numeral and Taxwire sites, the Taxes page also warns when taxable items have no tax code and links to those items. The Edit Fields panel also changes Require Payment Method, Require Shipping Address and Require Billing Address on Plans, and Allow Customer Updates in Billing Portal, Allow Fractional Quantities, Hide Service Date Range on Invoice Lines and the two Custom Proration settings on Products. Custom Proration can be set to Prorated, Full amount or None, or returned to the site default with Use Site Default. The panel shows only the fields that apply to every selected item. (Released: 20 to 27 October 2026)

Learn more
Why it matters:
After you switch tax providers, or reorganize your accounting codes, you can correct every affected item in one pass instead of opening each Plan and Product in turn, and the Taxes page tells you which taxable items still need a tax code. You can also change signup requirements, Billing Portal access and proration on a whole set in one pass, and a setting is never applied to an item that doesn't support it.
Where to find it:
In Catalog > Products (Catalog > Product Families on sites that allow Planless Subscriptions), under More Actions > Bulk Edit Catalog Items, and from the warning on Config > Taxes. Available to users with the Setup access level, on sites where the feature is turned on; it is off by default. The tax code field appears only on sites using AvaTax, TaxJar, Numeral or Taxwire. Plan fields appear when only Plans are selected, and Product fields when only Products are selected. Allow Customer Updates in Billing Portal and Custom Proration don't apply to Metered, Prepaid or Event-based Products, Allow Fractional Quantities doesn't apply to On/off Products, and Hide Service Date Range on Invoice Lines appears only on invoice-centric billing sites. For details, see Edit Catalog Items in Bulk. Look for it here if it's available to you.

Allocations on unpaid subscriptions are billed without collecting payment

On Relationship Invoicing sites, changing a Component's allocated quantity on an Unpaid Subscription now creates the charge or credit for the proration scheme you choose, but no payment is attempted. An accrued upgrade goes on a pending Invoice, an upgrade charged immediately issues an Open Invoice that isn't collected, and a credited downgrade creates a Credit Note. This replaces the earlier behavior, where the scheme was replaced with no proration and only the quantity changed. Sites that don't use Relationship Invoicing, and other end-of-life states such as Canceled, are unchanged. (Released: 20 October 2026)

Learn more
Why it matters:
The part of the period between an allocation change and the next renewal is billed on Unpaid Subscriptions, the same way their renewals are invoiced but not collected, so you no longer lose that revenue or find the scheme you picked silently replaced. Expect new Invoices and Credit Notes for these Subscriptions; the allocation doesn't start dunning or change the Subscription's state.
Where to find it:
Applies automatically whenever a Component allocation changes on an Unpaid Subscription, from the Subscription in the app or through the allocation and allocation preview API endpoints, on sites that use Relationship Invoicing.

See current names for 23 countries, a new country choice and updated state lists in address forms and invoices

Address dropdowns, the Taxable Regions page, and invoices that print full address names now show the current English names for 23 countries, such as Türkiye, Czechia, and Eswatini, and state lists include current ISO 3166-2 subdivisions. Kosovo is also available as a country choice in Advanced Billing country selectors, such as customer and payment method addresses, and in the Maxio Invoicing Suite country list in Core, and Kosovo addresses don't require a state. (Released: 22 October 2026)

Learn more
Why it matters:
A country now carries one name everywhere in the app, so a Customer in Türkiye or Czechia no longer appears under an older spelling on one screen and a new one on another. Customers already saved under an old name, such as Turkey or Czech Republic, keep their state choices in Maxio Core.
Where to find it:
Automatic, no setup needed. Look for the new names in any address dropdown, such as the country list on a signup page, on the Taxable Regions page, and on invoices that print full address names.

Reorder and reset the columns on the invoices page

The Columns chooser on the Invoices page lets you drag the columns you show into the order you want, using a mouse or the keyboard, and the table follows that order. Hidden columns are listed alphabetically below the ones you show, and Reset to default restores the default columns and order. Previously the column order was fixed. (Released: 26 October 2026)

Learn more
Why it matters:
You can put the invoice details you check most, such as Status or Amount Due, next to each other without scrolling across the table, and get back to the standard layout in one click after hiding columns.
Where to find it:
On the Invoices page, click the Columns icon on the filter bar. Consolidation Level and ID always show first and can't be moved. Your column order is saved in your browser, and the All and eInvoicing views each keep their own order. Available on sites that use Invoice Centric Billing.

One-time products with a custom price on planless subscriptions

On sites with Planless Subscriptions, one-time quantity-based Products don't need a billing interval. You can add one with a custom price when you create a Planless Subscription, allocate it later, or include it in a subscription change, where it was previously rejected with "Planless subscriptions cannot contain products without a billing interval." Recurring Products still need an interval. (Released: 26 October 2026)

Learn more
Why it matters:
You can charge a one-time fee, such as an onboarding package, at a price you set for that customer on a Planless Subscription, instead of having the Subscription rejected.
Where to find it:
Go to Billing > Subscriptions, click Create Subscription, leave the Plan blank and add a one-time quantity-based Product with a custom price. The same applies when you allocate the Product to an existing Planless Subscription. Locking in a scheduled renewal still requires an interval on every Product. For details, see Understand Planless Subscriptions. Look for it here if it's available to you.

Warn Customers before their subscription term ends

You can now send Customers an optional email before their Subscription Term ends, so they have time to renew. It goes out when no auto-renewal or scheduled renewal is in place and no cancellation is scheduled on or before the Term End. You choose how many days ahead, from 1 to 365, and the default is 30. (Released: 28 October 2026)

Learn more
Why it matters:
No more Term Subscriptions that end without warning. Customers hear that their service is ending while there is still time to renew, and you don't have to contact each one yourself.
Where to find it:
Go to Config > Settings > Emails, and in Upcoming Term Expiration Emails select Email my customers before their subscription term expires and set the number of days. The section appears only on sites that use Term Subscriptions, and the email is off by default. For details, see Configure Email Settings.

Submit invoices and credit notes under France's B2G e-invoicing mandate

Invoices and credit notes submitted to Avalara under France's B2G e-invoicing mandate (FR-B2G-EINVOICE) use their own default mapping, built for Chorus Pro, instead of the generic Peppol BIS mapping. It sends each party's SIRET as its identifier, your registration address, a credit transfer payment means with an optional payee account for your IBAN, and the three French legal mentions in the note. The French legal mentions settings now apply to FR-B2G-EINVOICE as well. (Released: 29 October 2026)

Learn more
Why it matters:
You can submit French public-sector invoices and credit notes from Maxio without building them outside Maxio, since the generic mapping sent identifiers Chorus Pro rejects. You and each French customer need a 14-digit SIRET on file: a party with only a SIREN is sent without an identifier.
Where to find it:
Under Config > Invoicing > eInvoicing, on sites with eInvoicing enabled and the FR-B2G-EINVOICE mandate, in that mandate's mappings and in the French legal mentions section. Store your SIRET as a Company-Reg No. identifier on your Tax Origin Address, and each customer's in the SIREN/SIRET field on the customer form. For details, see Setting Up the Avalara ELR Integration.

Payments

Refund under review notice for refunds held by Maxio Payments risk review

When Maxio Payments holds a refund for risk review instead of accepting or declining it immediately, Advanced Billing now shows a persistent Refund Under Review notice and tracks the hold, its release to the gateway, and its outcome in the invoice history. (Released: 14 October 2026)

Learn more
Why it matters:
Previously, a refund held for risk review looked like a plain failure, with no record of it in the invoice history and no way to tell a held refund from a rejected one. You now get a clear notice that stays visible until you dismiss it, and the invoice history shows the hold, its release, and whether it was ultimately approved or rejected.
Where to find it:
Refunding an invoice from its More Options > Refund Invoice... menu, or refunding a prepayment from the subscription's Prepayments tab, when Maxio Payments holds that refund for risk review.

Google Pay surcharging now matches credit card and Apple Pay

A credit-funded Google Pay card now gets the same surcharge treatment as a credit card or Apple Pay: a surcharge preview and checkout disclosure, and inclusion in the Surcharge-Impacted Customers export. Debit and prepaid Google Pay cards are never surcharged. (Released: 15 October 2026)

Learn more
Why it matters:
Previously, a Customer paying with a credit-funded Google Pay card saw no surcharge preview or disclosure, so merchants couldn't fully disclose the fee to them, and those profiles were left out of the report used to identify which buyers surcharging will affect. Both now cover Google Pay the same way they already cover credit cards and Apple Pay.
Where to find it:
The public signup page and the public invoice payment page (preview and disclosure), and the self-service page (disclosure), when a Customer chooses Google Pay backed by a credit card. Applies to Sites that use Maxio Payments. Also the Surcharge-Impacted Customers export from the Customer List's Export menu. Look for it here if it's available to you.

See the card surcharge before confirming a mid-period allocation

When you change a Product allocation that is charged immediately to a surcharged credit card, the allocation form now shows a summary of what the card will be charged: the allocation charge, any credits applied, the surcharge with its percentage, and the total. Unpaid automatic proration Invoices collected in the same payment are listed separately. If the charge accrues to the next billing period, a notice says the surcharge is added at the next renewal. (Released: 22 October 2026)

Learn more
Why it matters:
You can tell the buyer exactly what their card will be charged, surcharge included, before you confirm the allocation, instead of finding the surcharge on the Invoice afterwards. The surcharge is calculated on the amount left after service credits and prepayments, so the figure you share matches the charge.
Where to find it:
In the Product allocation form on a Subscription, when your site has surcharging enabled, the Subscription is collected automatically from a credit card that qualifies for a surcharge, and the allocation is set to Charge immediately. On sites that tax surcharges, the total is labeled Total before surcharge tax. Look for it here if it's available to you.

eWAY validates cards on $0 signups and card updates

Advanced Billing now validates a card with eWAY before storing it when nothing is charged at that moment. An authorization for 1.00 in your site's currency is placed and then reversed, and a declined card fails the signup instead of being stored. This applies to the eWAY, eWAY Rapid 3.1 and eWAY Rapid 3.1 (Legacy) gateways. (Released: 27 October 2026)

Learn more
Why it matters:
Previously, a free trial or a signup reduced to $0 by a coupon could store an invalid card on eWAY, and the problem only surfaced when the first renewal failed. Invalid cards are now caught at signup, so you aren't left chasing failed payments later. Your customers may see a temporary authorization for 1.00 in your site's currency until it's reversed.
Where to find it:
Any signup or card update on a site using an eWAY gateway where no charge is collected at that moment, such as a free trial, a $0 signup, or a card updated mid-period. Paid signups validate the card through the signup charge. Pre-authorizations can't be turned off for eWAY.

Accounting

Import product families, products, payment profiles, payment terms and custom field definitions in bulk

Imports under Admin > Import can now create and update Payment Terms in bulk, create custom field definitions, Advanced Billing product families and products, and Advanced Billing payment profiles, leave a required custom field unmapped in an Update import, use dd/mm/yyyy or dd/mm/yy as the Date Format, and preview an import's field mappings without uploading a file. Importing an Advanced Billing subscription that sets only Starts At to backdate it now fails validation on sites that are not invoice-centric billing, instead of importing without the backdate. (Released: 1 to 21 October 2026)

Learn more
Why it matters:
You can load and correct records in bulk instead of entering them one at a time, bring stored payment methods across when you migrate to Advanced Billing, and see what an import needs before you build the file.
Where to find it:
Go to Admin > Import and choose Create, Update or Create & Update. Product family, product, payment profile and subscription imports for Advanced Billing appear only once Advanced Billing is connected and Maxio staff have turned the Advanced Billing importers on for your account. For the steps, see Run an Import, Format a CSV File for Import, Import Advanced Billing Payment Profiles and Import a Product Catalog from a CSV. Look for it here if it's available to you.

Download, replace and import project templates from a file and re-apply milestone revenue actions to later work

A Project Template's detail page offers a CSV or Google Sheets download of its Milestones and Triggered Actions, a Replace from File action, and an Import Project Template page that creates a new Template from a file. Performance Obligation Triggered Actions also have an Also apply to work added later checkbox that runs the action again on Transactions added after the Milestone is complete. (Released: 13 to 19 October 2026)

Learn more
Why it matters:
You can move or edit a Template's configuration in a spreadsheet, and revenue held back or released by Milestones is applied to lines added later without clearing or recognizing it by hand.
Where to find it:
Go to Projects > Templates: Import Project Template on the list, Download Project Template and Replace from File on a Template's detail page, and the checkbox in a Milestone's Triggered Actions. Projects must be enabled, and import and replace need the Editor role.

Complete project milestones in bulk from a CSV file

A Complete Project Milestones import marks Project Milestones complete from a CSV file, one Milestone per row. For each row, you choose what happens to the Milestone's Triggered Actions: Run them, Run and Clone them into a new Milestone, Defer them to a new Milestone without running them, or Skip them without running them. It replaces opening each Project to mark its Milestones complete one at a time. (Released: 23 October 2026)

Learn more
Why it matters:
If you complete dozens of Milestones each month, for example at month end, you can complete them all in one upload. Rows with a problem, such as a Milestone that's already completed or a Triggered Action missing its value, are reported with the reason, and the valid rows still complete.
Where to find it:
In the Admin menu, go to Import > Additional Imports > Complete Project Milestones. Requires Projects and file import to be enabled on your account and the Admin role.

See issues and sync results in chips, and open the Customer behind a Xero sync issue

Customer, Invoice, Invoice Line Item, Item, Payment, Expense, Expense Item, Vendor and Bill detail pages now show their issues in a titled chip next to the page title, in place of banners and separate alert tables. The chip is red for blockers, amber for warnings and blue for information, and lists the most serious issue first. On Invoice and Invoice Line Item pages, status notices such as being synced with your general ledger, being in a closed period or, on a line item, belonging to a committed Invoice or being synced with Advanced Billing are no longer counted as issues. When they are the only notices, the chip is gray and names the first one next to the system's logo or a lock, for example Synced with QuickBooks · +1. When there are also issues, the chip shows the issue count followed by the logo, and the status notices are listed under About this Invoice. Customer detail also adds warning icons on flagged Financial Summary amounts and an action footer for Build Transactions and Verify Transactions. Integration pages for Salesforce, HubSpot, Pipedrive, QuickBooks Online, Intacct, Xero, Rillet, NetSuite, Advanced Billing, AvaTax, Stripe, Expenses and QuotaPath show the result of the last sync in a sync status chip, and each integration's Sync Issues list has a filter bar for Date, Step, and Message and can be sorted by those columns. When Xero rejects a Customer on the Send Customers or Send Customer Updates step, the other Customers in the same batch are still sent, and each rejected Customer gets its own sync issue that names the Customer, includes Xero's reason and, when Maxio can match the Xero contact to a Customer, ends with a link to that Customer. (Released: 5 to 26 October 2026)

Learn more
Why it matters:
Each issue and each sync result stays on the page it belongs to, with a short title, so you can see what is wrong and what to do at a glance. You can also narrow sync issues to when an error started, which step it affects or which errors repeat. For Xero, you can open a rejected Customer straight from its sync issue, and one invalid Customer no longer holds back updates to the rest of your Customers. A synced or closed-period Invoice with nothing wrong no longer shows a 1 issue chip, so you can see at a glance which Invoices need fixing.
Where to find it:
Next to the page title on each of those pages. Click a chip to see every issue, or to see who ran the last sync and a link to its issues. On an Invoice or Invoice Line Item, the chip also lists the status notices under About this Invoice or About this Invoice Line Item, each with an explanation. On the Xero home page, in the Attention Needed panel, click Sync Issues. Issues from the Send Customers and Send Customer Updates steps link to the Customer when Maxio can match the Xero contact to one, and the link opens the Customer in a new tab. For help, see Understand and Resolve Invoice Alerts, How to Identify and Correct Out-of-Balance Conditions and Review, Filter, and Sort Sync Issues.

Download payment terms and mismatch lists as CSV or Google Sheets and avoid duplicate exports

The Payment Terms page and the Transaction/Invoice Line Item Not in Same Contract alert page have a Download menu with CSV and Google Sheets exports of every row. Export buttons on pages such as Transactions and Payments no longer start a second identical export while one is running, and offer a Force new export option. (Released: 13 to 19 October 2026)

Learn more
Why it matters:
You can export a full list to a spreadsheet instead of paging through it, and duplicate exports no longer slow every export on your Site.
Where to find it:
Go to Admin, select Payment Terms under Lists, and open Download. For the mismatch list, open Invoicing Home, select Transaction/Invoice Line Item Not in Same Contract in the Attention Needed list, and open Download. The export buttons, such as Export Current View, are on pages like Transactions and Payments. For more, see Export and Download Data.

Reorder items and transaction rows, and keep that order on generated invoices

On the Create Transactions screen, the Add Items dialog's Selected list now has move-to-top, up, and down controls, and each Transactions grid row that affects Invoice Line Items has a drag handle (or an Alt+Up/Down keyboard shortcut) for reordering after Items have been added. That arranged order now persists as the Line Item order on the Invoices Maxio generates, including after Invoices are regenerated. A line added later to an existing Invoice is placed after the lines already on it, and an Invoice's detail page lists its lines in that saved order. In the Selected list, clicking an entry now highlights it instead of removing it. (Released: 13 October 2026)

Learn more
Why it matters:
The order of line items on a generated Invoice was previously not saved: regenerating Invoices could reset your arranged order, and adding a line to an existing Invoice could insert it in the middle instead of at the end. You can now set the order Items appear as Invoice line items, and trust that the order holds.
Where to find it:
From a Contract, choose Add Transactions > Create Transactions. The move-to-top, up, and down buttons are beside the Selected list in the Add Items dialog, and the drag handle is in the first column of each Transactions grid row. To reorder with the keyboard, focus a row's handle and press Alt+Up or Alt+Down. To remove an entry from the Selected list, highlight it and use the Remove from Selected button. A row shows a locked handle when its position cannot change anything, for example when the row is set not to generate Invoices.

Post Advanced Revenue Summary journal entries to Campfire

Campfire is now a full Advanced Revenue Summary GL Sync destination, alongside QuickBooks Online, NetSuite, Xero, Sage Intacct and Rillet. Each period you sync becomes one balanced journal entry in Campfire, built from the report's Consolidated Journal Entries section and posted to the Entity you select, with each line posted to the Campfire account mapped to its Maxio Account, and optional Department and Custom Dimension defaults applied to every line. Campfire gets the same workflow as the other destinations: preview the journal entry before posting it, sync on demand or on a daily, weekly or monthly schedule, and re-sync an open period to update its existing journal entry instead of creating a duplicate. Maxio can also match a journal entry that is already in Campfire rather than posting it twice, and it stops when Campfire reports that the period is closed. (Released: 6 October 2026)

Learn more
Why it matters:
Revenue recognized in Maxio reaches your Campfire general ledger as period-end journal entries without a manual export and import, so recognized revenue, deferred revenue and unbilled AR stay aligned between Maxio and Campfire through every close.
Where to find it:
Open the Advanced Revenue Summary report and use its GL Sync panel, with Campfire as the destination. Campfire must be connected and enabled for your account, and an Entity must be selected before a sync can be previewed or run. Currency is optional: Maxio uses the report's currency, and the Currency you select is used only if the report has none. Campfire doesn't receive workpaper attachments. For setup, see Set Up Advanced Revenue Summary GL Sync. Look for it here if it's available to you.

Sync invoices, credit memos and deposits with Campfire, generate Maxio profiles for new items automatically and review sync issues

The Campfire integration has new sync steps for invoices (Get Invoices and Send Invoices), credit memos (Send Credit Memos and Send Credit Applications) and deposits (Send Deposits, posted to Campfire as journal entries). The Chart of Accounts page also shows a Campfire ID column that links to Campfire. A new Automatically Generate Maxio Profiles for Items setting lets Get Products create every new Item from a Campfire product without a Maxio Profile, whatever its revenue account: the Item is created with Sync Invoices on and the account field that matches its linked Maxio Account filled in. A product on a Liability account becomes a recurring Item with the defaults for new recurring Items, other products get the defaults for new non-recurring Items, and existing Items aren't changed. Campfire also has its own Campfire Sync Issues list, like the other general ledger integrations, showing the records a sync couldn't sync and the reason for each. (Released: 14 to 28 October 2026)

Learn more
Why it matters:
You don't need to re-enter invoices, credit memos or deposits in Campfire or Maxio to keep the two in step, and you can see which Campfire account each Maxio Account is linked to. You also don't have to complete a Maxio Profile for every new Campfire product before syncing with Campfire can continue. When a sync skips a record, you can see which one and why, and fix it without contacting Maxio Support.
Where to find it:
Go to Left Menu > Campfire, then the gear icon (Integration Settings) and the Synchronization table. The new steps are off by default, and the Send steps appear only after Maxio Support turns them on for your account. To use the profile setting, click Edit Settings and select it in the Configuration section. It's off by default. The Campfire ID column is on Admin > Chart of Accounts. Sync issues are on the Issues tab below the Synchronization table once Campfire is connected, and opening the list needs the Bookkeeping User or Admin User role. For setup and sync details, see Sync Data Between Maxio and Campfire. Look for it here if it's available to you.

Keep partial months in SSP and carve out formulas with a fractional transaction length

SSP formulas and carve out formulas can use a new Transaction length (fractional) variable, FractionalTermMonths, which counts a transaction line's length in months including any partial month. Transaction length in months, TermMonths, is unchanged and still counts whole months only. (Released: 20 October 2026)

Learn more
Why it matters:
TermMonths drops any partial month, so a formula based on it understates the allocation for a term that doesn't end on a month boundary, and treats a term shorter than one month as 0. With FractionalTermMonths, a May 1, 2026 through June 15, 2027 line counts as 13.5 rather than 13. Partial months are measured in days, so wrap the variable in Round(...), for example Round(FractionalTermMonths, 2). Existing formulas that use TermMonths calculate exactly as before.
Where to find it:
On the SSP Lists tab of your revenue recognition settings, open or edit an SSP List. Transaction length (fractional) is in the Variables group of the variable picker for an SSP Formula and for a carve out set to Formula. Editing SSP Lists needs the Admin User role.

Cancel multiple transactions from the transaction list

The Transactions List has a Cancel action that cancels every eligible selected Transaction in one step. A confirmation page shows how many Transactions will be canceled and how many will be skipped and why: those with a non-recurring Item, those already canceled or renewed, and those managed by Advanced Billing. Canceled Transactions stay in effect until their End Date. (Released: 22 October 2026)

Learn more
Why it matters:
You can mark a page of Transactions as not renewing in one confirmed action, instead of opening each one, and the skipped counts tell you which Transactions need a different action.
Where to find it:
On a Transactions list, select the Transactions, choose Cancel from the list's actions, review the counts, and click Cancel Transactions. Requires the Bookkeeping User or Admin User role, and isn't offered when you use the All N Records option.

Copy transaction notes onto renewals automatically

A new Copy Transaction Notes to Renewals account setting starts each renewal Transaction with the Notes of the Transaction it renews. It applies to renewals you create one at a time or in bulk, and to auto-renewals, and you can still edit or clear the Notes on the renewal form. Revenue Notes aren't copied. The setting is off by default. (Released: 26 October 2026)

Learn more
Why it matters:
If you keep licensing or contract details in Transaction Notes, they carry forward to each new term, so you don't have to retype them on every renewal or risk losing them.
Where to find it:
On the Admin page, open Account Settings, click Update Settings, and select Copy Transaction Notes to Renewals under Transaction Settings. Changing Account Settings needs the Admin User role.

Show GST and PST from NetSuite as separate tax lines on e-Bills

If your NetSuite account uses legacy tax with two taxes, such as GST and PST, Maxio can bring in each tax as its own named line on Invoices and Credit Memos, with sales tax set to their total. (Released: 30 October 2026)

Learn more
Why it matters:
Your Customers see each tax listed by name on their e-Bills, matching the invoices you raise in NetSuite, so you don't need a NetSuite workaround that adds the two taxes together.
Where to find it:
Contact Maxio Support to turn on Get Tax 1 / Tax 2 as Invoice Tax Lines for your NetSuite integration. It isn't available with NetSuite SuiteTax. Then name the two lines with Tax 1 Line Label and Tax 2 Line Label in the Get Invoices sync step's settings, and turn on Show Tax Detail in your e-Bill theme.

Insights

Add Salesforce Opportunity IDs to the Basic Report and get a warning before a report over 500,000 cells runs

The Basic Report's Additional Details offers a Salesforce Opportunity ID column for accounts with a Salesforce integration. A Basic Report or Projection Report that would contain more than 500,000 cells now stops before it generates results and shows a This report is too large to run warning with the rows, columns, cells and the limit. (Released: 6 to 21 October 2026)

Learn more
Why it matters:
You can tie billing activity to its Salesforce Opportunity in the report, and you find out right away when a report is too large and what to change.
Where to find it:
On a Basic Report, open Additional Details and select Transaction: Salesforce Opportunity ID. The warning appears on the report's page with an Edit report button and a Back to report history button, and report emails include an Edit the report link.

Re-run a contract or customer momentum report in place

Subscription Momentum and Advanced Subscription Momentum reports that you run from a Contract or Customer page show a Re-run Report link on the results page. It runs the report again for the same Contract or Customer with the same settings and date range, using your current Transaction data. (Released: 16 October 2026)

Learn more
Why it matters:
When you're reconciling an account, you can edit a Transaction and refresh the report in the same tab instead of going back to the Contract or Customer and launching the report again. The date range doesn't change, so activity your edit moves outside it appears only when you launch the report again from the record.
Where to find it:
Open a Contract or Customer and select Reports > Advanced Subscription Momentum™ (or Subscription Momentum™, depending on which report your account has enabled), then click Re-run Report on the results page. Requires permission to run reports. The link appears only on unsaved Momentum reports; a saved report shows Run instead.

Group and filter expense reports by expense and vendor contract custom fields

The Expense Details report's Calculate By list includes your active Vendor Contract and Expense custom fields, labeled Vendor Contract: [field name] and Expense: [field name], alongside the Vendor custom fields it already offered. The expense filters on Expense Details, Advanced Expense Summary, and Margin Analysis also include your active Expense custom fields. (Released: 19 October 2026)

Learn more
Why it matters:
If you track attributes such as department or cost center on Expenses or Vendor Contracts, you can break expense reporting down by those values, or narrow a report to them, in Maxio instead of exporting and sorting the data yourself.
Where to find it:
When you create or edit an Expense Details report, open Calculate By and select a Vendor Contract: or Expense: custom field. On Expense Details and Advanced Expense Summary, add the filter under Additional Filters; on Margin Analysis, add it under Expense Filters. Only custom fields that are in use appear, and a filter value must match the custom field's type.

Platform

Create Maxio Core transactions from your AI client and see who really made each Maxio MCP change

Maxio MCP has a new Create Maxio Core Transactions tool that opens a review in your AI client, pre-filled with the Transactions you described for one Maxio Core contract, and writes nothing until you confirm. Report downloads from the Download Existing Report Run tool now come from the same domain as your Maxio MCP Server URL instead of a temporary Amazon S3 link. Changes and report runs made through Maxio MCP now record the real caller, the AI agent and the person it acted for, and each viewer sees that person's identity according to who they are: your own team by name, Maxio staff as Maxio Support, and anyone else as Unidentified user. (Released: 6 to 20 October 2026)

Learn more
Why it matters:
You can set up a multi-period schedule on a contract in one conversation, you only need to allow your Maxio MCP Server URL's domain, not Amazon S3, if your organization restricts which domains your AI client can reach, and you can tell which AI agent acted and for whom when you review activity for governance or compliance.
Where to find it:
Ask your AI client to create Transactions or download a report run through a Maxio MCP connector, on sites with Maxio Core. In Claude, the domain allowlist is under Organization Settings > Capabilities. The audit detail is on the Audit Information tab of a Customer or Transaction record, on the Invoice detail page and in the Run By column in Report History. For tools and setup, see Review Maxio MCP Supported Tools, Configure the Maxio MCP Connector and Maxio MCP Security, Access, and Governance FAQ. Look for it here if it's available to you.

Developer Experience

Filter customers, projects, sales orders, invoices and payments through the API and read customer numbers on includes

The Maxio Core API list endpoints accept new filters. Customers and Projects can be filtered by name, Sales Orders by customer identifiers, and Invoices, Payments and Customers by Advanced Billing IDs, invoice dates and Maxio IDs. The invoice, payment and contract lists honor a page size, invoice responses include three read-only fields, and the customer nested in invoice and transaction responses includes the customer's number. (Released: 12 to 15 October 2026)

Learn more
Why it matters:
If your integration lists records, you can ask Maxio Core for exactly the records you need instead of paging through full lists and matching them yourself, and you can read a customer's number without a second call.
Where to find it:
In Maxio Core's in-app API documentation, under Admin > Settings > API Documentation, on the customers, projects, sales orders, invoices, payments and contracts list endpoints. A page_size above 100 is capped at 100, and a malformed Maxio ID returns an error. For an overview of the API, see Get Started with the Maxio Core API.

Report run results mark which columns link to the record behind a figure. Deferred Revenue by Transaction, A/R Aging and Top Customers runs record and return the date their figures are as of, and a Deferred Revenue by Transaction or A/R Aging run can be started as of a date you choose. (Released: 13 to 16 October 2026)

Learn more
Why it matters:
If your integration reads or cites report data, you can tell which cells to link, read the exact as-of date from the run, and request a past period end in the run itself instead of editing the saved report definition and changing it back.
Where to find it:
In Maxio Core's in-app API documentation, under Admin > Settings > API Documentation: GET /api/v1.0/reports/runs/{id}/results/ for the linkable columns, as_of_date on the report runs endpoints, and as_of_date in the body of POST /api/v1.0/reports/runs/. Deferred Revenue by Transaction needs the last day of a month, and any other report type returns an error. For an overview of the API, see Get Started with the Maxio Core API.

Get a customer's receivables position as of a date through the API

A new endpoint, GET /api/v1.0/customers/{id}/receivables_summary/, returns one customer's open balance, past-due balance and count, oldest past-due date, last payment date, average days to pay over the trailing 12 months, and first contract start date, all as of a given date (or today, by default) and in the home currency. (Released: 13 October 2026)

Learn more
Why it matters:
If your integration needs a quick read on where a customer stands with their invoices, you can now get it in one call instead of composing it from several separate reads, and the figures agree with the A/R Aging report run "As of date," aging from the due date.
Where to find it:
GET /api/v1.0/customers/{id}/receivables_summary/?as_of=YYYY-MM-DD, documented in Maxio Core's in-app API documentation (Admin > Settings > API Documentation). Requires the same core.role_report permission as GET /api/v1.0/customers/{id}/analytics/. Credits (unapplied overpayments) are not netted into open_balance, matching the report run with Include Credits off.

Read resolved FX rates through the API

A new endpoint, GET /api/v1.0/fx_rates/, returns the rate Maxio Core would use to convert a local currency into the account's home currency on a given day or across a date range of up to 366 days, resolved the same way Maxio Core resolves it internally. (Released: 14 October 2026)

Learn more
Why it matters:
If your integration needs the tenant's reference FX rate, for reconciliation, reporting, or a Customer 360-style view, you can now read it directly instead of transcribing it from the FX Rate Schedule in the application. The response also tells you whether the rate came from a tenant override or the loaded rate, and which date it was actually found on.
Where to find it:
GET /api/v1.0/fx_rates/?local_currency=<code>&date=<date> (or start_date/end_date for a range), documented in Maxio Core's in-app API documentation (Admin > Settings > API Documentation). Requires the same core.role_report permission as GET /api/v1.0/currency_codes/, and only works on accounts with multi-currency enabled. The response gives rate_home_per_local: multiply a local-currency amount by it to get the home-currency amount. A day with no rate on or before it returns null values, not an error.

Read the current close dates and the history of close date changes through the API

Two new Maxio Core API endpoints return your closing date and transaction lock date as they stand today, with each date pick, manual date and the date in effect, and the history of every change to them, with the user who made it and the dates before and after. The current close dates also return the latest closing date Maxio enforces against revenue entries and invoices. (Released: 15 October 2026)

Learn more
Why it matters:
A tool that checks your close can work from your real closing date and see when someone moves it, who did it and what it was before, without an Admin opening Account Settings or the history page.
Where to find it:
GET /api/v1.0/account_settings/close_dates/ and GET /api/v1.0/account_settings/close_date_changes/, in the in-app API documentation under Admin > Settings > API Documentation. Both are read-only and need at least the Report User role in Maxio Core. For the settings themselves, see Manage Closing and Transaction Lock Dates.

List expired and expiring autopay cards through the API

A new endpoint, GET /api/v1.0/customers/expired_autopay_cards/, lists active customers on credit card autopay whose card has expired, or expires within two months, as of a date you choose (or today, by default). (Released: 15 October 2026)

Learn more
Why it matters:
If you check autopay cards before a billing run or a period close, you can now get every customer whose card has expired or is about to expire in one call, as of the period end rather than only today, instead of opening each customer. Without as_of, the endpoint returns the same customers that Maxio Core counts under Customers With Expired Autopay Card and Customers With Expiring Autopay Card. Each row carries the customer's id, maxio_id, number, name, and chargify_id, the card's autopay_exp_month and autopay_exp_year, and a status of expired or expiring. Rows never include card numbers, card brands, or gateway details.
Where to find it:
GET /api/v1.0/customers/expired_autopay_cards/?as_of=YYYY-MM-DD&status=expired, documented in Maxio Core's in-app API documentation (Admin > Settings > API Documentation). Requires the same core.role_report permission as GET /api/v1.0/customers/. A card is expired when its expiry month is before the month of as_of, and expiring when it expires in that month or either of the next two. Customers on bank account autopay, inactive customers, and cards with no expiry on file are left out. Results are ordered by expiry, earliest first, in pages of 100. An invalid as_of or status returns a 400 error.

Prevent API writes from overwriting newer changes to customers and contracts

GET /api/v1.0/customers/{id}/ and GET /api/v1.0/contracts/{id}/ now return an ETag response header, and PUT and PATCH on those records accept it back in an If-Match request header. Previously an API write always replaced whatever values were current. (Released: 16 October 2026)

Learn more
Why it matters:
If your integration reads a customer or contract, decides on a change, and then writes it, a change made in between, in Maxio Core or by another API client, is no longer overwritten silently. The write is refused with a 412 status and a code of precondition_failed, nothing is saved, and the response's ETag header carries the current tag so you can read the record again and retry.
Where to find it:
PUT and PATCH on /api/v1.0/customers/{id}/ and /api/v1.0/contracts/{id}/, documented in Maxio Core's in-app API documentation (Admin > Settings > API Documentation). Writes need the same role as before, at least Bookkeeping User. The tag covers the whole record as the GET returns it, including its nested billing_profile, so a change to any field refuses the write. If-Match: * only requires the record to exist, and a write without If-Match behaves as it always has. A successful write returns only the record's id, so read the record again to get its new tag.

Still need help?
Reach out and our support team will take it from here.

Contact support