Stripe: Invoice Line Item Details

Description

• Each record represents an invoice line item, enriched with details about the associated invoice, charge, customer, subscription, and pricing data.

Supported Data Sources

• Stripe

Columns

Type	Name	Description
STRING	invoice_line_item_id	The unique Identifier of the invoice line object. Note that the same line item can be shown across different invoices, so this value can appear multiple times.
STRING	invoice_id	The unique Identifier of the invoice object. Note invoices can have many line items, so this value can appear multiple times.
STRING	invoice_item_id	The ID of the invoice item this item is a part of
INTEGER	invoice_line_item_amount	Amount for this line item.
STRING	currency	Currency of this line item.
STRING	invoice_line_item_memo	Description for this line item.
BOOLEAN	is_discountable	Whether this line item is discountable.
STRING	plan_id	The ID that documents the plan record detailing the base price, currency, and billing information for each product. Valid if you are using the Plan API.
STRING	price_id	The ID that documents the price record detailing the base price, currency, and billing information for each product. Valid if you are using the new Prices API.
BOOLEAN	proration	Whether this is a proration.
INTEGER	quantity	The quantity of the subscription, if the line item is a subscription or a proration.
STRING	subscription_id	The ID of the subscription that the invoice item pertains to, if any.
STRING	subscription_item_id	The subscription item that generated this invoice item. Left empty if the line item is not an explicit result of a subscription.
STRING	type	A string identifying the type of the source of this line item, either an invoice item or a subscription.
STRING	unique_invoice_line_item_id	A unique id generated for old invoice line item ID's from a past version of the API
DATETIME	period_start	Start of the usage period during which invoice items were added to this invoice.
DATETIME	period_end	End of the usage period during which invoice items were added to this invoice.
DATETIME	invoice_created_at	Timestamp of when the invoice was created.
STRING	invoice_status	Current status of the invoice.
DATETIME	invoice_due_date	Date when payment for the invoice is due.
INTEGER	invoice_amount_due	Final amount due at this time for this invoice. If the invoice’s total is smaller than the minimum charge amount, for example, or if there is account credit that can be applied to the invoice, the amount_due may be 0. If there is a positive starting_balance for the invoice (the customer owes money), the amount_due will also take that into account. The charge that gets generated for the invoice will be for the amount specified in amount_due.
INTEGER	invoice_amount_paid	The amount, if any, that the customer has paid on the invoice
INTEGER	invoice_subtotal	The amount of the invoice before discounts and taxes.
INTEGER	invoice_tax	The amount of tax being charged in the invoice.
INTEGER	invoice_total	The total of the invoice after discounts and taxes.
STRING	connected_account_id	The ID of the account connected to the charge.
STRING	customer_id	The associated customer reference.
STRING	subscription_billing	How the subscription is billed
DATETIME	subscription_start_date	The start date of the subscription
DATETIME	subscription_ended_at	The end date of the subscription
BOOLEAN	price_plan_is_active	Boolean indicating if the plan or price is active (true) or in-active (false).
INTEGER	price_plan_amount	The unit amount in cents to be charged, represented as a whole integer if possible.
STRING	price_plan_interval	The frequency at which a subscription is billed. One of day, week, month or year.
INTEGER	price_plan_interval_count	The number of intervals between subscription billings. For example, interval_count=3 bills every 3 months.
STRING	price_plan_nickname	A brief description of the plan or price, hidden from customers.
STRING	price_plan_product_id	Reference to the product this price or plan is about.
STRING	source_relation	The source where this data was pulled from. If you are making use of the union_schemas variable, this will be the source schema. If you are making use of the union_databases variable, this will be the source database. If you are not unioning together multiple sources, this will be an empty string.