Docs
A Purchase Order (PO) is a document generated by the buyer in order to authorize a purchase transaction. A PO Number uniquely identifies a purchase order and is generally defined by the buyer. The buyer will match the PO number in the invoice to the Purchase Order.
When the buyer purchases a subscription and provides the PO number, it is associated with that subscription and is displayed in all the invoices associated with that subscription.
In Chargebee, you can add or update the PO Number while
a) Creating a subscription, or
b) Changing a subscription.
Additionally, your customers can add or update the PO Number via
a) Web Interface (Invoice Details Page)
b) The Hosted Checkout page during sign up, or
c) The Customer Portal during change of subscription.
PO number is not supported by Hosted Pages v1.
If you modify the PO number at the Subscription level, it will not be updated in the existing invoices. You can use the Update PO Number option to update it at the invoice level.
Enabling PO Number in your Hosted Checkout depends on the Hosted Checkout version you have enabled in your Chargebee site.
Single Page Checkout: PO Number can be enabled in the Additional Information section, under Settings > Configure Chargebee > Checkout & Portal > Field Configurations.
In-app Checkout: PO Number can be enabled in the Settings > Configure Chargebee > Checkout & Portal > Configuration > Advanced Settings.
If you would like to change the text for the same, this can be done under Settings › Hosted Page Settings › Text Configurations.
The PO number can be viewed in:
The PO Number details are included in the Invoice and Subscription export files.
The PO Number can also be added as part of the email notification sent to the customer using Mail Merge Fields.
The PO number can be added/updated using the following APIs:
One-off invoice is the invoice generated consisting of no-recurring items alone.
Currently, you can add PO number to one-off invoices only via API. PO number can be added to one-off invoices using the following APIs:
Articles & FAQ