Requisition Module
Requisitions are
useful to keep track of expenses made by the business. It leaves a record, and
it gives you statistics of all your purchases.
Â
It is also a
good way to require your employees to create a requisition when they have to
make purchases or pay for expenses.
After a
requisition, a PO (purchase order) always follows, and in most of cases it is a
different user that authorizes a PO.
Â
The requisition
expenses info offers several options:
Â
The area to help you identify the business area requesting the
expenses.
Â
NOTE: To modify or add a new area, go to Setup / Custom
Values / Areas. This field is
required.
Â
The
category identifies the general category of the requisition.
Â
The need is the date that the user requires the goods or services
to be delivered. This field is required, and this date will be applied to all
lines. You can edit the need by date on the PO requisition module when editing a
line.
Â
The assign to contract option, is a way to make a direct
reference of the requisition to a contract or order. This means that the
requisition expenses have a direct impact on providing the goods or services.
Â
The
req title is the title of the
requisitions
Â
The req description tells the user a little more about the use of the requisition.
Â
Sometimes your products or services don’t include tax; you can add the tax
percentage from here.
Â
The estimated price is a way to let the users share the new
cost or estimated cost. This “Estimate†will have no impact on the final
purchase, it is only informative.
Â
The “Save and got to PO†button
appears when all lines have been approved.
Â
When one or more
lines for a requisition have been rejected on the PO module, the requisition
will be automatically returned to the requisition module and displayed on the NONE completed list. From here it can
be modified by the user.
Â
A completed requisition
is a requisition in which all lines have already been marked as "Approved" and a purchase order PO has been requested or
created.