> 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-learning-hub-tutorials-and-best-practices/utilities/import-masters-transactions-from-external-files/import-sale-bills-from-external-file/import-sale-bills-from-external-file-configuration/bill-series.md).
# Bill Series
**YouTube:** [How to Set the Default Bill Series in Import Sale Configuration?](https://youtu.be/OH1-fxt_S-8)
## How to Set the Default Bill Series in Import Sale Configuration?
In this tutorial, we will learn how to configure the **default Bill Series** while importing Sale Bills from an external file in Logic ERP.
This feature allows you to define a specific Bill Series that will be automatically selected during the Sale Bill import process.
***
### Access to the Import Sale Bills Module
* Navigate to the **Import Sale Bills from External File** module.
* Here, you will find the **Bill Series** dropdown.
#### Default Behavior
* As you can see, the **Bill Series** dropdown displays all the available Bill Series.
* By default, **GST** is selected.
Now, let's configure a different Bill Series as the default.
***
### Configure the Default Bill Series
* Open the **Configuration** option.
* Locate the option labeled as:
> **"Bill Series"**
* This option allows you to define the Bill Series that should be selected automatically during the import process.
* Select "**R"** as the required Bill Series.
* Save the configuration changes.
**System Behavior**
As you can see, **"R"** is now automatically selected as the default Bill Series in the import window.
***
### Import the Sale Bill
Now, let's proceed with the import process.
* Select the required Sale Bill file.
* Verify that **"R"** is selected in the Bill Series field.
* Proceed with importing the Sale Bill document.
#### Import Result
* The Sale Bill document has been imported successfully.
* Now, let's verify whether the configured Bill Series has been applied to the imported bills.
***
### Verify the Imported Sale Bills
* Open the **Sale Bill** module.
* Locate the imported Sale Bills.
* Check the Bill Series assigned to the imported documents.
#### System Behavior
As you can see, the Sale Bills have been successfully imported under the configured default Bill Series **"R"**.
***
### Key Benefits
* Automatically selects the required Bill Series during import.
* Reduces manual selection during every import.
* Helps maintain consistent Bill Series usage.
* Simplifies the Sale Bill import process.
### Final Outcome
By configuring the **"Bill Series"** option, you can define a default Bill Series for Sale Bill imports. In this example, after setting **WSL** as the default, all imported Sale Bills are successfully created under the **WSL Bill Series**.
---
# 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-learning-hub-tutorials-and-best-practices/utilities/import-masters-transactions-from-external-files/import-sale-bills-from-external-file/import-sale-bills-from-external-file-configuration/bill-series.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.
