Skip to main content

What are Different Types of Purchase Orders?

Different Types of Purchase Orders

A purchase order (PO) is an official document generated by a buyer of goods/services as an offer for the seller. It becomes a “legal document of contract” once the seller accepts the purchase order. There are mainly 4 different types of purchase orders;
  1. Standard PO
  2. Contract PO
  3. Blanket PO
  4. Planned PO

Standard Purchase Order

It is the most basic and widely used among different types of purchase orders, it is created when a buyer is sure about the order details such as the item, price, delivery schedule, payment terms etc.
Example – Unreal corp. decides to buy 50,000 x 9W led bulbs from GE for a unit price of 10 each to be delivered within 60 days of order date. In such case, Unreal corp. will raise a standard PO and send it to GE for acceptance.  

Contract Purchase Order

It is created for a set period of time (often for a year) the item, pricing, quantity etc. can’t be anticipated precisely. In this case, a contract purchase order can be raised by the buyer, which upon acceptance becomes a legal contract.
During contract period the buyer can raise a standard PO with specifications of requirements and request for goods.
Example – Unreal Corp. analyzes and concludes that it often requires led bulbs of different wattage around different times of the year, however, the requirement is irregular and can’t be anticipated. In this case Unreal corp. can raise a contract purchase order.

Blanket Purchase Order

It is used in cases where the item is known, but quantity and required delivery schedules are unknown. There can be numerous delivery dates against a blanket PO, they are often used in case of large quantities with exceptional discounts.
Example – Unreal corp. decides to buy 5,00,000 x 9W led bulbs each year but they are not sure about the delivery schedule & quantity of each release. In such a situation Unreal corp. will raise a blanket purchase order.

Planned Purchase Order

It is used for a planned purchase anticipated for long-term where the delivery schedule is not known in advance. The dates of delivery can only be anticipated therefore only tentative dates are provided to the seller. Item, pricing and quantity are however known in advance.
Example – Unreal Corp. has evaluated that it will have a long-term need for the next 5 years to buy 25,000 x 11W led bulbs each year. Instead of raising a standard PO each time Unreal Corp. can create a planned purchase order.
The reference table is shown below with different types of purchase orders and their respective scenarios




Labels:

Comments

Post a Comment

Popular posts from this blog

O2C Cycle with Accounting Entries

  ORDER    TO  CASH  PARTICULARS  DR  CR SPL NOTES ACCOUNT IS PULLED FROM Sales order entry No Accounting Sales Order Pick From Sub Inventory A/c 100 At Standard Cost Sub-inventory Material A/c Setup To Sub Inventory A/c 100 At Standard Cost(Staging) Sub-inventory Material A/c Setup Sales Order Issue COGS 100 It can be fetched from five places Master Item/Org/Order Type/Line Type/Shipping Params To Sub Inventory A/c 100 At Standard Cost Sub-inventory Material A/c Setup Transaction level Receivable A/c 120 Auto Accounting Tax A/c 10 Auto Accounting Freight A/c 10 Auto Accounting Revenue A/c 100 Auto Accounting Receipts Receipts with no remittance method Cash 100 Before application of the receipt Receipt class Unapplied A/c 100 Receipt class Unapplied A/c 100 After application of the receipt to the transaction Receipt class Receivables A/c 100 Receipt class Cash A/c 100 Receipt class Unidentified A/c 100 In case of receipt without customer...
Post a Comment
Read more

Oracle Subledger Accounting (SLA) Tables, Views

Oracle Subledger Accounting (SLA) Tables, Views Oracle Subledger Accounting Tables: TABLE NAME DESCRIPTION XLA_AAD_GROUPS The XLA_AAD_GROUPS table stores the merge dependencies analyzed during the merge analysis.  All application accounting definitions with the same GROUP_NUM must be merged together. XLA_AAD_HDR_ACCT_ATTRS The XLA_AAD_HDR_ACCT_ATTRS stores standard, system and custom sources assigned to an accounting attribute at the AAD level. XLA_AAD_HEADER_AC_ASSGNS Store the analytical criteria for the application accounting definitions. XLA_AAD_LINE_DEFN_ASSGNS This table stores the journal lines definitions for the application accounting definitions. XLA_AAD_LOADER_DEFNS_T The XLA_AAD_LOADER_DEFNS_T table is the interface table that facilitates the data transfer from data files and the database. XLA_AAD_LOADER_LOGS The XLA_AAD_LOADER_LOGS table stores the errors and logs generated by the application accounting definitions loader. XLA_AAD_SOURCES XLA_AAD_SOURCES table stores a...
1 comment
Read more

Number to Word conversion in RTF

<?xdofx: expression ?> for extended SQL functions <?xdoxslt: expression ?> for extended XSL functions. You cannot mix xdofx statements with XSL expressions in the same context This function enables the conversion of numbers to words for RTF template output. This is a common requirement for check printing. The new function is “to_check_number”. The syntax of this function is <?xdofx:to_check_number(amount, precisionOrCurrency, caseType, decimalStyle)?> The following table describes the function attributes:   Attribute Description Valid Value amount The number to be transformed. Any number precisionOrCurrency For this attribute you can specify either the precision, which is the number of digits after the decimal point; or the currency code, which will govern the number of digits after the decimal point. The currency code does not generate a currency symbol in the output. An integer, such as 2; or a currency code, such as ‘USD’. caseType The case type of th...
Post a Comment
Read more