Requisitions vs. Purchase Orders in Microix (Modern Version)

Creation date: 1/6/2026 4:55 PM    Updated: 1/6/2026 6:31 PM   purchase order requisition

📌 Overview

Questions may arise regarding the distinction between Requisitions and Purchase Orders in the Microix Modern version particularly when the initial entry screen is labeled Purchase Order. This article clarifies how the process works within Microix.

🔄 How Microix Handles Requisitions and Purchase Orders

Microix does not use two separate documents or entry screens for Requisitions and Purchase Orders in the traditional sense.

Instead, Microix utilizes a single, unified entry form that supports the full lifecycle of a purchase:

  • 📝 Requisition (Request for Purchase):
    The initial entry represents a request for purchase. This request flows through the configured approval workflow.

  • ✅ Purchase Order:
    Once the request receives final approval, it automatically becomes an approved Purchase Order. (No re-entry or conversion to a separate document is required.)

🖥️ Screen Labeling

Although the entry screen may be labeled Purchase Order, the document should be understood as:

  • A Requisition while it is pending approval

  • A Purchase Order once it has been fully approved

This labeling reflects the unified design rather than a change or removal of requisition functionality.

🔢 Numbering Configuration

Microix can be configured to support sequential numbering throughout the process (Optional):

  • The document can initially be assigned a REQ number (See screenshot below)

  • Upon final approval, the system can automatically assign a PO number (See screenshot below)

This allows organizations to maintain clear audit trails and reporting distinctions while still benefiting from a streamlined process.

⚠️ Req/PO Numbering – Implementation Guidance

The REQ-to-PO numbering process should only be implemented if organizational policies require the use of a Requisition number during the approval phase and a Purchase Order number after final approval.

If policies do not require separate numbers, Microix recommends using a single document number from start to finish.

If the REQ/PO numbering option is implemented, the system behaves as follows:

Prior to approval:

  • The Document Number displays the REQ number

After final approval:

  • The REQ number is moved to the Reference Number

  • The PO number becomes the Document Number

📎 Key Takeaways

  • The Requisition-to-PO process still exists in the Modern version of Microix

  • Requisitions and Purchase Orders are managed through one form, not two separate documents

  • Approval status determines whether the document is considered a Requisition or a Purchase Order

  • Optional configuration supports REQ-to-PO numbering transitions