Send Multiple Invoices to Customer in One Email

Providing a convenient, fast, and safe method on collecting payment from your customers is key to building and maintaining that recurring revenue relationship. Chargify's core functionality on sending invoices provides an easy way to both send automatic and ad-hoc invoices via email. 

We are excited to announce that we have extended our functionality to include sending multiple invoices to a customer in one email. When managing a subscription’s invoices, you can apply filters to refine the invoice selections before selecting 'Email Customer' option. You can attach up to 24 invoices in one single email.


For more information on sending emailed invoices to customers, see our documentation here>

Backdate a Received Date for External Payments

We understand that some of our customers are entering external payments into Chargify, and oftentimes the day it gets entered is not the same day it was received. In order to support downstream reporting and align the date you received these external payments (such as paper checks via mail), you can now specify a received_on date for external payments. 

In the UI, users can provide an effective date via Invoices > Invoice Show > Record Payment > Record External Payment. The received_on date will be set to the current day by default, but the user can backdate by changing the received_on field.

For historic reporting, this field has been backfilled with the created_date date in order to facilitate reporting from this field; however, the received_on date can only be different from the created_date going forward. 

In the UI, received_on will be exposed in the /payments and /transactions pages and exports. Please note that this is the /transactions page, not the new Transactions Report page. There are plans to add this field to the new Transactions Report page in the future.

The received_on date is also available via the following API endpoints: transactions, invoice, and invoice-events. 

For more information on backdating a received date for external payments, see our documentation here>

Include Avalara Sales Tax When Creating Price Points

The tax landscape for recurring revenue businesses can oftentimes be difficult to manage, leading to confusion on how to effectively apply taxes to your products and services. Adding to that complexity is determining a final price for your product that includes tax so that your customers are only advertised and charged one single price.

Within Chargify, your Avalara Managed Sales Tax account helps eliminate the ongoing headaches in managing sales tax for your recurring revenue business. Adding to Chargify's native Avalara functionality, our Product Team was recently working on a beta feature with some of our customers. We are happy to announce that this new feature is now in general availability!  

You can now utilize a 'tax included' option when setting your final prices in your Product Catalog within the UI. For example, if you want the final price (with taxes included) to be $20 for one of your subscription offerings, you can choose the "Tax included in price?" when building out your price point. Your customer will be billed $20, and in turn you will be collecting your subscription base price + tax. 

For more information on Avalara Managed Sales Tax, see our documentation for products here and for components here>

Immediately Charge Existing Payment Method on Ad-Hoc Invoices

In a customer-centric world, selling add-ons, services, or products outside of your recurring subscriptions can become a common practice. Because of this, we love knowing that our customers can take advantage of ad-hoc (one-off) invoices, either within the UI or API. Our Billing Team has released several enhancements to one-off invoicing over the past several months, from backdating functionality, new filtering options (via API), and a date selector modal. 

Today, we are excited to announce that you now have the option to immediately collect payment on these ad-hoc invoices. Two options are available when creating an ad-hoc invoice in the UI: 

  1. The invoice will be marked for remittance payment; or 
  2. The invoice amount will be collected automatically from the payment method on file 


In addition, users can select the desired behavior if payment fails. The ad-hoc invoice can either: 

  1. Roll back (not be created); or
  2. The status can be set to 'Open' and Chargify will attempt collection at the next scheduled renewal 

The default behavior can be set in your Site Settings. However, behavior for individual and ad-hoc invoices can be overridden. Payment instructions can be sent via API with the payment_instrucions parameter. If payment instructions are not specified, the settings for the invoice will default to the site settings.

For more information, see our ad-hoc invoice documentation or API documentation here>

Ad-hoc Invoice Date Selector Modal

At times you may be selling additional services and add-ons to your customers that are outside of their recurring subscriptions. With Chargify's ad-hoc invoice feature, you can easily create those additional charges with the option of backdating the creation date. 

We are happy to announce that we have added an intuitive date selector modal for how the Issue Date, Due Date, and Net Terms interact within the UI. You can now: 

  • Enter dates directly by keeping Net Terms equal to 'Calculate from Dates' 
  • Set Net Terms first (changing either date will dynamically change the other)  

For more information on Invoices at Chargify, see our documentation here>

Specify Invoice Recipients from the Admin UI

We understand that some of your customers need to have multiple recipients of an invoice for increased visibility amongst teams. We are excited to announce that you now have the ability to specify additional recipients when sending invoices from the Admin UI. 

Prior to this update, clicking the 'Send Invoice' button would automatically send the invoice to the primary contact on the account. Now, the UI will prompt the user with a modal which will be pre-populated with the primary contact, and additional contacts can be added on the To:, CC:, and BCC: fields. 

For more information on invoices in Chargify, see our documentation here>

Service Credits in Billing Portal

Chargify's billing portal provides a convenient interface for your customers to update their credit card and billing details, change plans and number of addons, as well as cancel their subscription. Best of all, modifying what actions are available for your customers can be done through the Chargify UI, all without having to write any code. 

To further enable your customers ability to manage their own accounts, we are excited to announce new Service Credit and Prepayment balances to the billing portal view. Your customers will know exactly what balance already exists before an invoice is issued. 

For more information about the billing portal, see our documentation here>

New Filter Options via API for Invoicing

Last month we released a new endpoint to send invoices via API to mimic the behavior of the "Send Invoice" button within the UI. This endpoint enables you to programmatically deliver ad-hoc invoices as well as the re-send of auto-generated invoices, thus giving you control of when to send out an invoice. 

As we continue adding new API endpoints, we are excited to announce new filter options on exposed event types on an invoice. You can now filter for multiple event types on an invoice (e.g. issue_invoice, apply_credit_note, refund_invoice) using a comma separated list. Previously, you were able to filter by only 1 invoice event. 

For more information, see our documentation here>



Backdating Issue Date on Ad-hoc Invoices

We understand that charges can occur outside of a normal billing cycle and therefore provide the functionality for you to send ad-hoc or one-time invoices. Many customers utilize ad-hoc invoices to sell services or items on a non-recurring basis to their customer base. We are excited to announce that our Product Team has made some exciting developments to these types of invoices! You can now backdate ad-hoc invoices using both the UI and API. 

If performing this in the UI, you go under Subscriptions > Invoices > Create an Invoice. There is a new input field for Issue Date in the top right of the ad-hoc invoice within the UI. The issue date will be set by default to the current date. In order to back date the issue date, you will use the date selector functionality by clicking into the Issue Date input field.

Alternatively, you can also backdate the issue date via the API with the "Create an Invoice Endpoint". If no issue date parameter is passed, then the issue date will default to the current date. If you desire to back date, you can simply pass an issue_date parameter of any date in the past.

The primary use case for backdating ad-hoc invoices is when you experience a delay in issuing an ad-hoc invoice but would still like for the invoice to be due at the same time it would have been had there been no delay. As an example, one-off usage is incurred but not charged until 7 days later and you want the due_date to reflect your standard net terms of 15 days. In this case, you could back date the ad-hoc invoice to the day the usage was incurred and set the due_date to Day 15.

For more information on backdating the issue date on ad-hoc invoices, see our documentation here>

Proforma Triggers

Proforma invoices allows for proactive communication to your customers by providing a preview of their upcoming expected billing amounts, taking away any surprises once their subscription renews. Thanks to feedback from our existing customers taking advantage of proforma invoices, we have added some exciting functionality by announcing new proforma invoice triggers!

These triggers will allow for a proforma invoice to automatically be generated on set intervals of a subscription billing cycle. These triggers will allow you to select if you want the proforma invoice automatically sent to your customer at generation. For your annual subscribers, this will provide insight into what their invoice will look like 2, 4, 6 months (or whatever time interval you choose) out from their renewal.

For more information on proforma triggers, see our documentation here>


Show Previous EntriesShow Previous Entries