> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/improvements/material-purchase-payment-to-cbo.md).

# Material purchase payment to CBO

## Scope

Purchase Bill

System should allow to make purchase bill in name of CBO as purchase reimbursement.

## Actors <a href="#actors" id="actors"></a>

Employee: Bill Creator (JE/ AE/ IE)

## Details <a href="#details" id="details"></a>

1. As of now a purchase bill can only be prepared in the name of vendor organization.
2. System should allow to prepare a purchase bill in the name of CBO for the reimbursement of material purchase payments.
3. With this system will allow to create prepare a purchase bill either in the name of Vendor of CBO.
4. To achieve this some change in the existing purchase bill are suggested.
   1. Organization type a new field is added, which is by default selected “CBO”.
   2. Option to search organization will remain as it is.
   3. There is minor change in invoice detail section, please refer wire-frame for the same.
   4. There is minor change in bill details section, please refer wire-frame for the same.
   5. Rest all remain same.

### Actions <a href="#actions" id="actions"></a>

Actions and workflow remain same.

### User Interface <a href="#userinterface" id="userinterface"></a>

<figure><img src="https://content.gitbook.com/content/Oahp3xBKoPsr1r1NAaNj/blobs/osLaQwBl2Z5UqjSXDsno/Create%20Purchase%20Bill.png" alt=""><figcaption></figcaption></figure>

## Acceptance Criteria <a href="#acceptancecriteria" id="acceptancecriteria"></a>

1. System allows to prepare a bill either in the name of vendor or CBO.
2. There are minor UI changes to accommodate this.
3. Workflow is not changed.


---

# 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://docs.digit.org/works/reference-implementations/muktasoft-v2.2/specifications/functional-requirements/user-stories/improvements/material-purchase-payment-to-cbo.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.