> For the complete documentation index, see [llms.txt](https://wiki.dieagenturverwaltung.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/onboarding/nummernsysteme/kostenvoranschlagsnummern.md). # Estimate numbers ### **Best practice for estimates** The numbers consist of \-\-\ > KV-2018-015 \ > KV-2019-001 The three-digit sequential number of the estimate starts again at 001 at the turn of the year. If in one year there are actually more than one thousand estimates for a customer, the number will automatically become four digits. #### The estimate number does not include a customer code When we create a proposal for a new business customer, we may not want to create a customer, customer account and a job in the agency software right away. We don't yet know whether the lead will turn into anything.\ \ If the customer later approves the estimate and we create the customer and the job in the system, we simply move the existing estimate into the newly created job. Since estimates generally do not carry customer codes, this also does not create a numbering conflict when creating further estimates for that customer. #### Advantages of this pattern * The number is suitable as a filename - even on a web server * The prefix distinguishes between estimate and invoice * In a file system, files named by estimate number automatically sort by year and sequential number #### Estimate number is not the same as job number * An estimate should also be able to be created without a job * A job can contain multiple estimates * A job can contain multiple (not realized) versions of an estimate that have already been with the customer. These versions should be clearly distinguishable from each other by different numbers. #### Number ranges for estimate numbers are possible Estimates can optionally be maintained in so-called number ranges. That means you can open a separate estimate number range for each customer. \ As a result, it will not be apparent from a customer's estimate number whether and how many estimates you issue to other customers. --- # 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://wiki.dieagenturverwaltung.de/die-agenturverwaltung-en/onboarding/nummernsysteme/kostenvoranschlagsnummern.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.