> For the complete documentation index, see [llms.txt](https://docs.cloudscaff.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudscaff.com/general-tools-and-features/reference-code.md).
# Reference Code
## What is the Reference Code?
The **Reference Code** is an optional input field used to store any third-party identifier associated with a request, delivery, return, transfer, or movement.
It allows users to attach external documentation or tracking numbers directly to a Cloudscaff transaction so it can be easily searched and matched later.
***
## Where You Will See It
The Reference Code field appears throughout the system, including on:
* Requests
* Deliveries
* Returns
* Transfers
* Inventory Movements
Wherever this field appears, it is **optional**. You may leave it blank or fill it in when required.
***
## What Can Be Entered?
Any external reference such as:
* Purchase Order (PO) Number
* Work Order Number
* Job Card Number
* Customer reference
* Supplier delivery note number
* External tracking ID or freight number
If your business relies on external paperwork or systems, the Reference Code links that information directly to Cloudscaff records.
***
## Why Use It?
The Reference Code allows users to:
* Match Cloudscaff transactions to accounting or procurement systems
* Trace deliveries or returns against external documentation
* Quickly locate specific entries using a PO or work order
* Improve record accuracy during audits or reconciliations
***
## Searchable in System Tables
Once saved, the Reference Code becomes searchable across all relevant tables.
This means you can search by:
* Code
* Customer name
* Site name
* **Or Reference Code**
Example:\
If a delivery arrives with PO #PO123, entering PO-123 into Reference Code allows anyone to find it later by searching directly for that number.
---
# 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://docs.cloudscaff.com/general-tools-and-features/reference-code.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.