> For the complete documentation index, see [llms.txt](https://docs.platform.softwareone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.platform.softwareone.com/developer-resources/rest-api/billing-api/invoice/invoice-line.md). # Invoice Line The Invoice Line object represents a record of invoice generated in the ERP system.

Field Name	Data Type	Core	Description
`id`	string	true	The unique identifier for the invoice line. No nesting exists for this identifier. Example: INL-685-123-555
`invoice`	object	-	A reference to `invoice` object.
`documentNo`	string	-	The document number. Example: `{ "id": "INV-123-567-321" }`
`erpCountryCode`	string	-	The country code as defined in the ERP system. Example: GB
`lineNo`	integer	-	The line number. Example: 50000
`amount`	decimal	-	The total amount of the invoice. Example: 193.2
`lineAmount`	decimal	-	Total amount for the line item. Example: 193.2
`discountAmount`	decimal	-	The discount amount applied. Example: 0
`amountIncludingVat`	decimal	-	The total amount including VAT. Example: 231.84
`vatBaseAmount`	decimal	-	The base amount for VAT calculation. Example: 193.2
`unitOfMeasure`	string	-	The unit of measure. Example: Pieces
`itemNo`	string	-	The item number. Example: X120.00128.ML
`description`	string	-	A description of the item. Example: Power BI Pro
`description2`	string	-	Additional description for the item. Example: Monthly Subs incl SoftwareOne Cloud Support Advanced
`quantity`	integer	-	The total number of units. Example: 23
`unitPrice`	decimal	-	The price per unit. Example: 8.4
`countryOfUsage`	string	-	The country of usage. Example: GB
`contractNo`	string	-	The contract number. Example:GB-CCO-155406
`primaryCodeIdentifier`	string	-	Primary code identifier
`primaryCodeVersion`	string	-	The version of the primary code.
`primaryCodeValue`	string	-	The value of the primary code.
`secondaryCodeIdentifier`	string	-	The identifier of the secondary code.
`secondaryCodeVersion`	string	-	The version of the secondary code.
`secondaryCodeValue`	string	-	The value of the secondary code.
`MSRP`	decimal	-	The manufacturer's suggested retail price. Example: 20
`timestamp`	integer	-	The date and time details. Example: 28495870095
`rowVersion`	string	-	The row version. Example: 0x000000011A867F68
`parentItemNo`	string	-	The identifier for the parent item. Example: X120.00128.ML
`type`	string	-	Type. Example: 2
`responsibilityCenterCode`	string	-	The code for the responsibility center. Example: LON
`vatCalculationType`	string	-	Type of VAT calculation. Example: 0
`vatPercent`	decimal	-	The percentage of VAT. Example: 20
`varPartnerNo`	string	-	The partner number.
`swoPurchaseOrderNo`	string	-	The SoftwareOne purchase order number.
`varAgreementNo`	string	-	The number of the agreement.
`externalPositionNo`	string	-	The external position number.
`dataOrigin`	string	-	The origin of the data.
`primaryKey`	string	-	The primary key. Example: GB\|GB-PSI-332155
`sellToContactNo`	string	-	The sell-to contact number. Example: GB-CON-113713
`externalDocumentNo`	string	-	The external document number. Example: CSP
`externalDocumentNo2`	string	-	The additional external document number. Example: CSA6/5/23-5/6/23
`yourReference`	string	-	The reference for the invoice. Example: vixtechnology.com

--- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.platform.softwareone.com/developer-resources/rest-api/billing-api/invoice/invoice-line.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.