Supply Chain · Project Procurement

Every purchase line on a project, every PO against a budget

Built for EPC and project companies: solar and renewable EPC, construction, oil and gas, infrastructure. A requisition line names its project and budget line once; the RFQ and the PO inherit it. The Budget page shows what is requested, quoted, ordered and received against each line, and an over-budget PO is warned or blocked before it is sent.

From budget line to site

Six steps. The cost object is set once and never retyped.

1
Budget
A project has budget lines. Each line has an amount and a running view of what is requested, ordered and received against it.
2
Requisition
Each line carries a cost object (project, budget line or department), a destination warehouse and a need-by date. The header is derived from the lines.
3
RFQ
Lines inherit the cost object and destination. Vendors quote per line with a ship-to per line where sites differ.
4
PO
Availability is checked against the budget line. Within budget, the PO commits the amount. Over budget, it warns or blocks by policy.
5
Receive
GRN at the site store against the PO line. Received value shows on the budget line.
6
Issue
A material issue moves stock from the store to the project. Consumption lands on the cost object.

How a budget line is controlled

Commitment accounting: a PO reserves budget the moment it is raised.

Inside the product

Cost object on every line

Requisition, RFQ and PO lines each carry a cost object and a destination warehouse. The cost object is inherited from PR to RFQ to PO, and the document header is derived from its lines. Multi-site and multi-project requisitions need no splitting.

Project, project budget line or department per line
Destination warehouse and need-by date per line
Inherited PR to RFQ to PO; header derived from lines

The Budget page

Cost control for supply-chain projects. Each budget line shows frozen columns: requested (PR), RFQ, PO, ordered, received and gap. Pending requisitions are counted in the gap so the number is forward-looking.

Requested · RFQ · PO · ordered · received · gap
Pending PRs included in the gap
Coverage and queue widgets per project on the dashboard

Availability control and commitments

When a PO is raised, the amount is checked against the budget line. The policy decides whether an over-budget PO warns the buyer or is blocked. A PO within budget encumbers it as a commitment, so later POs see what is actually left.

Warn or block, by policy
POs encumber the budget line (commitment accounting)
Over-budget POs blocked before they reach the vendor

Site stores and material issues

Goods are received into the site warehouse against the PO line. A material issue moves stock from the store to the project, with its own number series. The project sees what was bought and what was consumed.

GRN pegged to the PO line
Material issue slip from store to project
Issued stock recorded against the cost object

Data scope by site

A person in a role can be limited to certain warehouses and projects. A site supervisor sees their sites; a project buyer sees their projects. The limit follows the role the person is working as.

Scope on the role assignment: warehouses and projects
Lists, pickers and writes respect the scope

Project procurement is the purchasing half of the project story. For bill of quantities, work packages and site execution, see Construction.

Speaks your market's language

The documents keep their meaning across industries; the labels follow yours.

Cost object

WBS element · project code · cost centre · account assignment

Commitment

Encumbrance · committed cost · open PO value

Material issue

Store issue · issue slip · consumption voucher

Questions buyers ask

Where is the project set on a purchase order?: On each line. Every requisition, RFQ and PO line carries a cost object, which can be a project, a project budget line or a department, plus a destination warehouse. The header is derived from the lines, so one PO can serve several projects or sites.
What does the Budget page show?: Per budget line: requested (PR), RFQ, PO, ordered, received and the gap. Pending requisitions are included in the gap so you see what is about to be committed, not only what has been.
Can a buyer raise a PO beyond the budget?: Availability is checked when the PO is raised. By policy it either warns or blocks. POs encumber the budget as commitments, so the next PO sees the remaining amount, not the original one.
How does material reach the project?: Goods are received into the site store against the PO line. A material issue then moves stock from the store to the project, so consumption is recorded against the cost object.
Can a site supervisor only see their own sites?: Yes. A person in a role can be limited to certain warehouses and projects. Lists, pickers and writes respect that scope.

Related supply chain pages:Approvals Purchase Orders Control Tower Supply Chain overview

Put your next project on a budget

Load the budget lines, raise the first requisition, and watch the gap column move.

Get started free Explore the product

Loading…

Every purchase line on a project, every PO against a budget

From budget line to site

Six steps. The cost object is set once and never retyped.

Budget

A project has budget lines. Each line has an amount and a running view of what is requested, ordered and received against it.

Requisition

Each line carries a cost object (project, budget line or department), a destination warehouse and a need-by date. The header is derived from the lines.

RFQ

Lines inherit the cost object and destination. Vendors quote per line with a ship-to per line where sites differ.

Availability is checked against the budget line. Within budget, the PO commits the amount. Over budget, it warns or blocks by policy.

Receive

GRN at the site store against the PO line. Received value shows on the budget line.

Issue

A material issue moves stock from the store to the project. Consumption lands on the cost object.

Inside the product

Cost object on every line

Project, project budget line or department per line
Destination warehouse and need-by date per line
Inherited PR to RFQ to PO; header derived from lines

The Budget page

Requested · RFQ · PO · ordered · received · gap
Pending PRs included in the gap
Coverage and queue widgets per project on the dashboard

Availability control and commitments

Warn or block, by policy
POs encumber the budget line (commitment accounting)
Over-budget POs blocked before they reach the vendor

Site stores and material issues

GRN pegged to the PO line
Material issue slip from store to project
Issued stock recorded against the cost object

Data scope by site

A person in a role can be limited to certain warehouses and projects. A site supervisor sees their sites; a project buyer sees their projects. The limit follows the role the person is working as.

Scope on the role assignment: warehouses and projects
Lists, pickers and writes respect the scope

Questions buyers ask

Where is the project set on a purchase order?

On each line. Every requisition, RFQ and PO line carries a cost object, which can be a project, a project budget line or a department, plus a destination warehouse. The header is derived from the lines, so one PO can serve several projects or sites.

What does the Budget page show?

Per budget line: requested (PR), RFQ, PO, ordered, received and the gap. Pending requisitions are included in the gap so you see what is about to be committed, not only what has been.

Can a buyer raise a PO beyond the budget?

Availability is checked when the PO is raised. By policy it either warns or blocks. POs encumber the budget as commitments, so the next PO sees the remaining amount, not the original one.

How does material reach the project?

Goods are received into the site store against the PO line. A material issue then moves stock from the store to the project, so consumption is recorded against the cost object.

Can a site supervisor only see their own sites?

Yes. A person in a role can be limited to certain warehouses and projects. Lists, pickers and writes respect that scope.