Difference between revisions of "PO"
From wiki.pengtools.com
Line 3: | Line 3: | ||
===PO life cycle=== | ===PO life cycle=== | ||
#[[PO]] is created to make any expenditure. | #[[PO]] is created to make any expenditure. | ||
− | ##[[PO]] is | + | ##[[PO]] is issued against [[AFE]] for [[CAPEX]]. |
##[[PO]] is created for [[OPEX]] and [[G&A]]. | ##[[PO]] is created for [[OPEX]] and [[G&A]]. | ||
#[[PO]] is approved in accordance with [[Approval Process]]. | #[[PO]] is approved in accordance with [[Approval Process]]. |
Latest revision as of 09:36, 10 February 2017
Purchase Order
PO life cycle
- PO is created to make any expenditure.
- PO is approved in accordance with Approval Process.
- Invoices are attached to the PO.
- PO closes
PO Attributes
- Number
- Owner
- Company_Owner
- Company_Contractor
- Description
- Expenses type: CAPEX, OPEX, G&A.
- Expenses code
- Over budget: yes/no
- Total Cost free of VAT
- Total Cost incl. VAT
- Attached files
PO Status
- Status: Open/Closed
- Approval Status
- Budgeted: yes/no
PO Authorization
Sum | Budgeted | Unbudgeted | ||
---|---|---|---|---|
AFE in place | AFE not required | AFE not in place | ||
<$2k | Anyone Levels 1-3 | Anyone Levels 1-4 | 1x Level 2 | 2x Level 2 (incl Finance) |
<$10k | 1x Level 2 | 1x Level 2 | 1x Level 2 | 2x Level 1 |
<$100k | 1x Level 2 | 1x Level 2 (incl Finance) | 1x Level 1 | 2x Level 1 |
<$500k | 1x Level 1 | 1x Level 1 | 1x Level 1 | 2x Level 1 |
<$1m | 1x Level 1 | 1x Level 1 | Board of Directors | Board of Directors |
≥$1m | 2x Level 1 | 2x Level 1 | Board of Directors | Board of Directors |