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

# Purchase Comments and Notes

Add and manage comments and internal notes on purchase documents.

There are a number of ways you can add additional information to a purchase document, be that for internal or external use. You might want to store a document against a purchase blanket order to be able to refer to it later or include vendor-specific packaging instructions.

{% hint style="warning" %}
**Prerequisites**

Ability to create purchase documents.
{% endhint %}

### Purchase Document Attachment Factbox

All purchase documents have an **Attachment** Factbox Section. Here you can add both **Attachments** and **Notes.**

* **Attachments**: upload a pdf, image, word document or any file to the document. The attachment is stored within the database, meaning anyone else can open and read it. Note that the use of attachments will increase the size of your database especially if you are attaching large files.
* **Notes**: type or copy/paste free text to the document. These notes are for internal use only and not suitable for printing or reporting on.

Both Attachments and Notes can be copied to a posted transaction.

See also [How to add links to a record](https://docs.microsoft.com/en-gb/dynamics365/business-central/ui-how-add-link-to-record)

### Purchase Comments

All purchase documents have a **Purchase Comments** area, this is accessed from each document's page. Here you can add free text. Comments have a **Comment Type** that impacts how each line is used within Bevica.

| Comment Type            | Note                                                    |
| ----------------------- | ------------------------------------------------------- |
| Internal                | These are internal comments and not published anywhere. |
| Delivery Instr. (Sales) | These are not used on purchase documents.               |
| Picking Instr. (Sales)  | These are not used on purchase documents.               |
| Sales Documents         | These are not used on purchase documents.               |
| Purchase Documents      | These are displayed on the purchase order output.       |
| Gift Note               | These are not used on purchase documents.               |

### Default Vendor & Order Address Comments

Both the Vendor and Order Address pages have a comments area, accessed from each pages' ribbon option. When a purchase document is created, all Vendor and Order Address comments are copied to the document along with their **Comment Type**.

### Purchase Line Comments & Standard Text Codes

It is possible on any document to add comments at line level. To do this to make sure the **Type** field is set to 'Comment' and enter your text in the **Description** field. Alternatively, you can create **Standard Text Codes** which appear in the 'No.' field lookup.

Comment lines appear on all outputs as they appear on screen and are copied to posted documents alongside all other lines. Line comments are typically used to highlight something about a particular line, but can be used as general notes you want your customer to see.

### Item Extended Texts

It is possible to add multiple default comment lines against an item, these are then copied to a document whenever that item is used. From the Item card ribbon, select **Extended Texts**. Here you can add multiple text lines specifying, if you want, language code, valid start and end date, and which purchase documents they are to be copied to.

As **Purchase Line Comments** above, these can be used to highlight a product on offer or something unique about that item.

See also [How to define Extended Texts](https://docs.microsoft.com/en-gb/dynamics365/business-central/ui-how-define-ext-text)

### Report Layouts

All vendor facing purchase document outputs are managed by **Report Layouts** which are themselves **Word documents**. As such you can open the Word document and add a generic comment or message. That message will then appear on all subsequently printed/emailed outputs. I.e. this can be used to display Easter / Christmas office opening times or company news.

See also [Manage report layouts](https://docs.microsoft.com/en-us/dynamics365/business-central/ui-manage-report-layouts)


---

# 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/purchase_comments_and_notes.md?ask=<question>&goal=<endgoal>
```

`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.