Issue Invoice In Advance

What is an Invoice in Advance?

An advance invoice is issued for renewal charges before the current subscription period ends. The billing period remains unchanged. The due date of the advance invoice reflects the subscription's period end plus its net terms. The invoice number follows the next number in your site's sequence. Any existing prepayments or credits on file will be automatically applied.

The line items on the advance invoice will exactly match those that would be generated at the normal renewal. If the renewal would not create an invoice, an advance invoice cannot be generated.

Like any open invoice, an advance invoice can be paid, emailed, or voided at any time. If the invoice is not paid by the due date, the site’s dunning strategy will be applied when applicable.

How Components Work

Metered usage will be reset when the advance invoice is generated, following standard usage rules. However, all component types remain available for allocation even when an advance invoice exists. Be aware that any additional allocations will result in a second invoice at the time of the subscription’s renewal.

To avoid a second invoice, void the existing advance invoice and regenerate it to include all line items, including the new allocations.

Restrictions

On generating an advance invoice:

• Only one advance invoice is allowed per subscription per billing period.
• The subscription must be in an active or trialing state.
• The subscription cannot be grouped.
• The subscription cannot be prepaid.
• The subscription cannot use prepaid components.
• The subscription cannot use calendar billing.
• The current time must not be within one hour of the subscription's renewal.
• If using a non-default currency, the subscription must use fixed exchange rates.

After the advance invoice is generated:

The subscription becomes locked to certain changes. To unlock, you must void the advance invoice.

• Product and product price points cannot be changed via immediate product change or migration.
• The next billing date cannot be changed.
• The subscription cannot be added to a group.
• The subscription cannot be canceled immediately (unless the advance invoice is fully unpaid, in which case it will be voided automatically).
• You cannot schedule cancellation for the same billing period if an advance invoice has already been generated.
• However, if a pending cancellation exists and charges will be due at cancellation, you may still generate an advance invoice.

Other:

• Feature available on Invoice Architecture sites only.

How to Use Invoice in Advance

In the Subscription Actions drop-down, select Issue Invoice Immediately. A proforma invoice will appear, previewing the line items, customer information, and pricing that will be included. If you notice incorrect details, click Cancel and make updates to the subscription, customer, invoice settings, or catalog item as needed.

If everything looks correct, click Confirm Invoice. A confirmation popup will summarize the effects of issuing the advance invoice. Click Issue Invoice to proceed, and you'll be redirected to the new advance invoice.

If automated emails are enabled, the invoice will be sent to the customer automatically.

Proforma preview of the invoice that will be generated

Confirmation prompt showing what will occur once issued

On the subscription’s Summary page, a banner will indicate when an advance invoice is present. If line item updates are needed before renewal, void the advance invoice. Updates to customer information, such as shipping addresses, can be made directly on the invoice.

Voiding

If the advance invoice is voided before the renewal, several rollbacks will occur:

• Prepayments and credits will be returned to their respective accounts. Any payments will be converted into prepayments.
• Any discounts from coupons will be restored.
• Metered usage will be restored to the relevant component, equal to the amount invoiced.

Once the subscription renews, the invoice is no longer considered "in advance." At that point, voiding follows standard behavior without rollbacks.