We sensed a need to redesign statements for our merchants. Our goal is to present billing periods and charges in an easy-to-read manner. Statements made it difficult to reflect on the reason and outcome of different billing events.
The old way of presenting subscription-based charges was through transactions grouped into statements. The ordering of transactions could be somewhat arbitrary, often making it difficult to see why a particular amount was being billed.
Statements represent a billing period; however, transactions on a statement may actually be billed at different times. One-time charges and prorated component upgrades had the potential to be captured for payment at mid-period, while other transactions on the same statement might be captured at the end of the period.
Invoices needed the same make-over as statements, which led us to include this in our release of the new architecture.
Invoice billing was the term for non-automatic payment collection before invoice architecture. Previously, an invoice was issued as a request-for-payment from the subscriber. The corresponding payment was typically remitted later. This style of legacy-invoices were similar to legacy-statements. However, there was one major difference; a subscriber could have multiple invoices per statement period, since an invoice was issued for each billing event.
This resulted in a situation where invoices didn’t exactly match up with statements, causing confusion for merchants and subscribers.
Existing invoices and statements will remain unaffected. In your subscriptions, you and your subscribers will be able to still view and act upon any previously-generated invoices or statements.
Your site data will be unaffected by this change.
As more features are developed, we will be releasing new webhooks to complement invoice architecture for invoice creation, invoice payments, invoice paid in full, etc. Old webhooks remain unaffected.
Currently, these are the new webhooks available for Relationship Invoicing:
- Invoice Issued (when an invoice is generated)
Once enabled, invoice architecture is active for an entire Site. At this time, we can only enable invoice architecture for new sites. A migration path for old sites is under development.