> For the complete documentation index, see [llms.txt](https://docs.paigo.tech/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.paigo.tech/invoicing-and-payment/issue-invoice/automatic-line-item-formatting.md). # Automatic Line Item Formatting ### Overview Line items on invoices follow a predetermined format when generated by the Paigo. In this chapter, we take a deep dive into how line items are constructed in invoices. The line items automatic formatting also applies to the automatic invoices generated by Paigo. Off-cycle invoices with line items manually entered will be not formatted by Paigo. ### Line Item Format Format for line items are determined by properties of dimensions and offerings: * Offering Name * Dimension Name * Consumption Unit * Usage Increment A standard line item follows the following structure: ``` ${Dimension Name} - ${Converted Unit} - ${Offering Name} ``` The element `${Converted Unit}` is automatically determined by Paigo. It is based on the consumption unit and usage increment. For definitions of these two properties, see [Product Items](/saas-pricing/pricing-basics/product-items.md). As a quick example, when the consumption unit is `Byte` and usage increment is `1024`, the converted unit becomes `Kilobyte`. So the invoice will show `Kilobyte` for ease of understand and better user experience. ### More Examples We are providing a more detailed example regarding line item formatting. Assume a SaaS business that wants to bill customers on two dimensions `Queries` and `CPU Hours` for an offering called **Professional Plan**. The dimensions are defined as below. * **Seats** Usage Increment: 1000 and Consumption Unit: Count * **Process Time** Usage Increment: 1 and Consumption Unit: Hour An invoice is generated for the following usage amount: * **Seats** 400,000 Seats * **Process Time** 72 Hours The sample invoice is shown below.

The explanation of line items: * Line item `Seats` is shown in thousands because the usage increment is 1,000. Therefore, the quantity is showing 400, and the line item name is showing as `Seats - Thousand - Professional Plan`. * Line item `CPU Hours` is shown in its original terms `Hour` because the usage increment is 1. ### Unit Conversion Reference Below is a table reference for the different automated conversion units. #### Time Units

Unit	Usage Increment to Next Level
Second	60
Minute	60
Hour	24
Day

#### Data Units

Unit	Usage Increment to Next Level
Byte	1024
Kilobyte	1024
Megabyte	1024
Gigabyte

#### Count-based Units / Custom Units

Unit	Usage Increment to Next Level
The original consumption unit	1000
Thousand	1000
Million	1000
Billion

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.paigo.tech/invoicing-and-payment/issue-invoice/automatic-line-item-formatting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.