> For the complete documentation index, see [llms.txt](https://kb.bevica.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.bevica.com/documentation/guides/purchasing/working_with_purchase_orders.md). # Creating Vendors Create Vendors in Bevica Select. Covers addresses, contacts, dimensions, payment terms, posting groups, and best-practice data entry. Vendor setup drives defaults across purchasing and reporting. Use this page as a checklist for the fields you should review. ### Key fields for vendor records These are the key fields to populate when creating new vendors: **General FastTab** * `No.`: This will be defaulted or you can type your own, depending on how your number series is set up * `Name` * `Blocked`: Payment - no new payments can be created for this vendor All - no transactions are allowed for this vendor. * `Duty Status`: For **stock vendors**, set this to be the duty status you normally purchase the goods in (you can change it per order). For **non stock vendors**, set this to **Duty Paid**. * `REX No.` If an Item has the Vendor No. populated, the REX No. from that Vendor will be displayed on sales lines and posted sales invoice lines. The sales invoice report word template can be amended to include this. **Address and Contact FastTab** * All applicable fields **AWRS FastTab** * All applicable fields **Invoicing FastTab** * `VAT Registration No.` * `EORI Number` (Economic Operator Registration and Identification) * `GLN` (Global Location Number) * `Gen Bus Posting Group` * `VAT Bus Posting Group` * `Vendor Posting Group` * `Currency Code` **Payments FastTab** * `Payment Terms Code` * `Payment Method Code` **Receiving FastTab** * `Location Code`: For **stock vendors**, populate with the location you would normally purchase stock from this vendor into. This will be defaulted onto Purchase Orders but can be amended on the order if needed. This also needs to be completed for **non stock vendors**, but it doesn't matter which location you select. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://kb.bevica.com/documentation/guides/purchasing/working_with_purchase_orders.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.