# Requisition Workflow In Manager

**URL:** <https://forum.manager.io/t/requisition-workflow-in-manager/40370>\
**Category:** ideas\
**Created:** [March 31, 2022, 2:50pm UTC](https://forum.manager.io/t/requisition-workflow-in-manager/40370 "2022-03-31T14:50:59Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Abeiku](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/abeiku/32/44970_2.png) [@Abeiku](https://forum.manager.io/u/Abeiku)\
**Post date:** [March 31, 2022, 2:50pm UTC](https://forum.manager.io/t/requisition-workflow-in-manager/40370/1 "2022-03-31T14:50:59Z")

</div>

I suggest the implementation of a new tab called `Requisitions` which will be where users request inventory items from stores (Internal) and from suppliers (External). Requisitions will have `Reference` numbers that will also appear on forms (Inventory Transfer, Purchase Quote, and others) linked with the requisition.

It can have the following statuses.

1. Pending (Amber)

2. Completed (Green)

3. Partially completed (Green)\*

4. Cancelled (greyed)

Users will use the `Copy to` button to copy from the Requisition form to:

1. Inventory Transfers (internal need)

2. Purchase Quote

3. Purchase Order

4. Purchase Invoice

5. Goods Received Note.

When a request is copied to any of the items above, mark the requisition form completed. If the number of requested items isn’t fulfilled, mark it as partially completed.

The requisition form can be made to use `Non-inventory` items too, for Service Orders/Request.

My Idea of the tab:

 ![image](https://us1.discourse-cdn.com/flex019/uploads/manager1/original/3X/8/0/80685e5aa3f3c75a6db9267640c98a78b5556e53.png)

---

<div class="post-metadata">

**Author:** ![EPR\_Capital1](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/epr_capital1/32/34515_2.png) [@EPR\_Capital1](https://forum.manager.io/u/EPR_Capital1)\
**Post date:** [February 20, 2023, 5:40am UTC](https://forum.manager.io/t/requisition-workflow-in-manager/40370/2 "2023-02-20T05:40:50Z")

</div>

I support this proposal. Enhances Managers ERP characteristics.

---

<div class="post-metadata">

**Author:** ![Omnipotent.inc](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/omnipotent.inc/32/35374_2.png) [@Omnipotent.inc](https://forum.manager.io/u/Omnipotent.inc)\
**Post date:** [February 21, 2023, 1:04am UTC](https://forum.manager.io/t/requisition-workflow-in-manager/40370/3 "2023-02-21T01:04:48Z")

</div>

@EPR_Capital1 , manager is not a ERP Software.

---

<div class="post-metadata">

**Author:** ![EPR\_Capital1](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.manager.io/epr_capital1/32/34515_2.png) [@EPR\_Capital1](https://forum.manager.io/u/EPR_Capital1)\
**Post date:** [February 24, 2023, 10:01am UTC](https://forum.manager.io/t/requisition-workflow-in-manager/40370/4 "2023-02-24T10:01:33Z")

</div>

It has to try to be because Many accountants work in an originator-approver-executer model of segregation of duties. Because accounting is mostly meant to assist management of an organization rather than being an end in itself.

---

<div class="post-metadata">

**Author:** ![eko](https://avatars.discourse-cdn.com/v4/letter/e/a8b319/32.png) [@eko](https://forum.manager.io/u/eko)\
**Post date:** [February 24, 2023, 10:24am UTC](https://forum.manager.io/t/requisition-workflow-in-manager/40370/5 "2023-02-24T10:24:11Z")

</div>

> [@EPR\_Capital1](#):
>
> It has to try to be because Many accountants work in an originator-approver-executer model of segregation of duties.

No it does not have to be an ERP. However, as is already listed in this idea the need for approval pathways is common in many businesses.
