- Invoices — unused numbers

- Invoices — unused numbers

Discover your Recurly invoice data effortlessly with the Invoices - Unused numbers feature.

Overview

Required plan

This feature or setting is available to all customers on any Recurly subscription plan.

Definition

The unused invoice number export showcases the fundamental details of all the invoice numbers that have not been utilized in successfully generated invoices. Situations such as failed sign-ups could result in an unused invoice number.

This log aids significantly in audit procedures, supplementing the numbers provided in the Invoices - Summary export to furnish a detailed account for every number in your sequence.

Filters

Date Range Filters

List all unused invoice numbers that could have been created within the selected timeframe.

Exports table

Download Button Download our complete export schema

To help you identify and organize information effectively, the export provides a structured table that contains the following columns:

Column NameExampleDescriptionData type (max size)
invoice_number1291External invoice identifier.string
invoice_typepurchase, refund, renewal, immediate_change, termination, credit, gift_card, write_off, external_refund, carryforward_credit, carryforward_gift_credit, usage_correction, importThis refers to the origin of the invoice. The primary invoice possesses a 'purchase' type. Negative invoices generated due to refunds or voids to offset the initial one have a 'refund' type. Other invoice types become accessible when the Credit Invoices feature is activated. Detailed descriptions can be found in the invoice origins section.string
invoice_doc_typelegacy, charge, creditThis column indicates the document type of the invoice. Before activating the Credit Invoices feature, all invoices bear the 'legacy' type. Post activation, the invoices are categorized as either 'charge' or 'credit'.string
invoice_date2019-07-19 12:01:33 PSTThe date and time the invoice creation was attempted. The inception date for this export is July 1, 2019.timestamp

Version changelog

No version changelog available at the moment.