> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-version-release-notes/december-2018/billing/new-update-in-setup-bill-series-section.md).

# New Update in Setup Bill Series Section

YouTube: [New Update in Setup Bill Series Section](https://youtu.be/G3BtfoX29cg)

### Setup Bill Series New Updates

LogicERP made new changes in Setup Bill Series Section. Now, you can select a new Option in “Add Fin Year/Branch” column, which is “**Series Description Only**.” There’s also new column attribute added i.e., “**Bill No. Length**.” To access these operations, you need to follow the given steps:

**Step-1** Go to “Setup Bill Series” option.

**Step-2** A window will open displaying rows and columns of Setup Bill Series.

**Step-3** In the “Add Fin Year/Branch” when you select the options, you will see a new option i.e., Series Description Only.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2FNKVgnJZ5NACnzO2OizIc%2Fimage.png?alt=media&amp;token=6a5ae15c-0c4a-4385-8a08-48239720ef88" alt=""><figcaption></figcaption></figure>

**Note:** When you select ‘Sale Description Only’ option, then in order to save the detail, you have to enter the description in ‘Sale Description’ Column.

**The limit for entering Bill No. Length should always be less than 10, or you can even keep it empty.**

### How Bill Number Will Display?

When you will go to “Sale Bill” Section to check the billing details of a particular account, the Sale Bill Number will display in the following format:

**Series Number (Series Description at start+Bill Number at End)**

The length of the Sale Bill Number will be equal to the value that you inserted in the Bill No. Length Column. The remaining characters space will get filled by the “Zero’s.

<figure><img src="https://4031188996-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXMVkjt8zqHBQX1c9QvFS%2Fuploads%2Fej90MXNAdDHL3O3TlOEa%2Fimage.png?alt=media&amp;token=e390735b-35c0-436b-912c-1e6778e58db2" alt=""><figcaption></figcaption></figure>


---

# 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://kb.logicerp.com/logic-erp-version-release-notes/december-2018/billing/new-update-in-setup-bill-series-section.md?ask=<question>&goal=<user_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.
