--- title: "Flags Always Included" slug: "flags-always-included" updated: 2026-07-24T09:02:57Z published: 2026-08-10T20:21:16Z canonical: "help.idibilling.com/flags-always-included" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.idibilling.com/llms.txt > Use this file to discover all available pages before exploring further. # Flags Always Included The following table lists tags that are always included in the XML file: | XML Tag | Description | Example | | --- | --- | --- | | `version` | Standard release version associated with the release level and build number. | | | `corp_ charge` | Rolled-up child taxes, recurring and non-recurring charges. | | | `parent_ charge` | Total tax for the parent. | | | `payment_ type` | Identifies customers who pay automatically by credit card or debit card. Value = “direct_debit” or “e_pay”. | or | **Invoice New Customer** The following tag requires that the new customer entry be set in Admin Console. | XML Tag | Description | Example | | --- | --- | --- | | `status` | Identifies new customer bills. | or | **Customer Invoice Messages** The following tag identifies report group notes and customer notes. - `ReportGroupNote` messages are received by all customers in that Report Group. - `CustomerNote` messages are received only by the specific customer as designated in Customer Management. | XML Tag | Description | Example | | --- | --- | --- | | `messages` | Identifies invoice messages. | Subscribe to our Pager Plus Service and receive 25 FREE local calls each month!!! THIS INVOICE IS OVER DUE AND PAYABLE IMMEDIATELY< /message> | **Entitlements** The following tag displays the amount of the entitlements that the customer receives. This is part of the financials section of the output. | XML Tag | Description | Example | | --- | --- | --- | | `entitlements` | Identifies value of customer’s entitlements. | | **Sales Person** To include sales person information, the **sales tag** must be included with the indicators. | XML Tag | Description | Example | | --- | --- | --- | | `sales_person` | Enters the sales person’s name. | | **Additional Company Address** An additional company address can be added for inclusion on the invoice. This centralized information is not specific to any Billing Group. See the settings in Admin Console. | XML Tag | Description | Example | | --- | --- | --- | | `company_info` | Identifies an alternative “return” address on the invoice. | Info Directions
833 Phillips Rd.
Suite C
Victor NY 14564
585-924-4110
| **OCN Tiered Rating Method** Information can be included in the usage summary reports for OCN tiered rating if your company uses the OCN Tiered rating method. See settings in Admin Console. OCN tiered rating method only applies to Equal Access, Toll Free, Equal Access Dedicated, and Toll Free Dedicated based services. | XML Tag | Description | Example | | --- | --- | --- | | `from_tier` | Displays the name of the OCN tier used for the originating OCN. | see below | | `to_tier` | Displays the name of the OCN tier used for the terminating OCN. | see below | | `OrigOCN` | Displays the originating OCN (Operating Company Number). | see below | | `OrigOCNTier` | Displays the origination OCN tier name. | see below | | `TermOCN` | Displays the terminating OCN. | see below | | `TermOCNTier` | Displays the terminating OCN tier name. | see below | ```plaintext ``` **Packages Tree Structure** Packages can be a part of a package creating a tree structure of up to 4 levels. The attribute “package” can have the following values PP (package parent, PC (package child), PSP (package under a parent package or a subpackage under a child package), PSC (child under a child package or child under a subchild package), and NP (single product). | XML Tag | Description | Example | | --- | --- | --- | | `package` | Describes the level of the product in the package tree structure. | see below for an example | ```plaintext ```