> 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.md).

# Purchasing

Purchasing workflows in Bevica, including orders, returns, tracking, and notes.

The purchasing function in Bevica comprises a number of transactions that, in combination, provide the ability to manage your vendors effectively.

<figure><img src="https://2932934759-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfUgpGDVvyqBWVvwVIy9a%2Fuploads%2FfygEeNArWjrcu5AVasJ8%2Fkb-purchasing-infographic.svg?alt=media&amp;token=6ab2db69-fdf0-47f1-a596-281fcdeb8b76" alt="Purchase document workflow diagram"><figcaption></figcaption></figure>

### Document Types

#### Purchase Order

Purchase orders are used to request stock and account for services from vendors. They contain all the information needed to manage the shipping of the goods from the correct address at the right time and post the invoice from the vendor appropriately. See [Working with Purchase Orders](https://kb.bevica.com/documentation/guides/purchasing/working_with_purchase_orders-1.md).

#### Purchase Return Order

When you need to return stock for credit, you create a return order. Items to be returned can be applied to the original purchases to properly allocate costs.

#### Purchase Quote

A purchase quote can be created against a vendor or prospect to display pricing and confirm details.

#### Purchase Credit Memo

When you want to record a financial credit from your vendor.

#### Purchase Invoice

When you want to register a vendor's invoice, be that for stock or services. Purchase Invoices help keep track of inventory costs by invoicing inventory receipts using the '**Get Receipt Lines**' process or by applying costs such as freight, handling, delivery to inventory movements.

#### Purchase Blanket Order

Blanket orders are used when a vendor has committed quantities of stock to you. Purchase orders are created from blanket orders allowing you to see how much was originally promised, is now on order, and has been receipted. See [Managing Blanket Orders](https://kb.bevica.com/documentation/guides/purchasing/managing_blanket_orders.md) for more information.

For more information about blanket orders, see [Work with Blanket Sales Orders](https://docs.microsoft.com/en-gb/dynamics365/business-central/sales-how-to-create-blanket-sales-orders) (Blanket purchase orders work in a similar way as blanket sales orders).

#### Purchase Archives

Purchase Archives exist that can be used to take a snapshot of any purchase document. They can be created manually or automatically if the option is set in Purchases & Payables Setup. For more information about archiving documents, see [Archive Documents](https://docs.microsoft.com/en-gb/dynamics365/business-central/across-how-to-archive-documents).

For more information about the purchasing function, see [Purchasing](https://docs.microsoft.com/en-gb/dynamics365/business-central/purchasing-manage-purchasing) and [Managing Payables](https://docs.microsoft.com/en-gb/dynamics365/business-central/payables-manage-payables)


---

# 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.bevica.com/documentation/guides/purchasing.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.
