Complete Guide to Procurement Workflow Implementation: PR, RFQ, PO, GRN (2024)
This article examines the implementation of the PR, RFQ, PO, and GRN procurement workflows from both a technical and practical standpoint, making it suitable for operations and IT managers. Learn step by step how to build an efficient and transparent system, supported by code examples and best pract
Inefficient procurement management of goods and services is one of the largest 'black holes' in business operations, especially in the healthcare sector such as hospitals and clinics. Imagine a common scenario: the pharmacy department needs essential medicines, but the requisition process (PR) is still manual, authorization takes days due to physical documents, requests for quotations (RFQ) to vendors are done via separate emails, purchase orders (PO) are prone to input errors, and the recording of goods receipt (GRN) is often out of sync with stock. As a result, there are delays in vital deliveries, over-purchasing or shortages of critical stock, operational cost inefficiencies of up to 10-15% of total expenditure, and increased fraud risk. This problem is not merely administrative; it has the potential to disrupt patient care, reduce service quality, and inflate budgets. This article will guide you in depth on how to implement a structured and automated procurement workflow, covering Purchase Requisition (PR), Request for Quotation (RFQ), Purchase Order (PO), and Goods Receipt Note (GRN), with a focus on practical and implementable technology solutions.
Basic Concepts and Benefits of a Structured Procurement Workflow
A structured procurement workflow with four main pillars—Purchase Requisition (PR), Request for Quotation (RFQ), Purchase Order (PO), and Goods Receipt Note (GRN)—is the foundation for operational efficiency and transparency. Each stage has a crucial role and is interrelated, ensuring that every company expenditure has a strong and accountable basis. Without a clear flow, organizations risk budget leaks, wrong purchases, delivery delays, and even unethical practices. A concrete example: a hospital that does not have an integrated PR system may find that two different departments separately purchase the same items in large quantities, losing potential volume discounts and causing stock buildup.
Purchase Requisition (PR) is an internal document created by the department that needs goods or services. This is the first step that officially initiates the procurement process. A PR must include details such as the type of goods, quantity, specifications, purpose of use, and required date. For example, the Radiology Department needs 50 units of X-ray film with certain specifications on July 15. This PR will be submitted to the department manager for initial approval, then forwarded to the procurement department. A digital PR system ensures that every request is documented, traceable, and goes through an authorization process that follows the organizational hierarchy, reducing the risk of unnecessary or over-budget purchases.
Request for Quotation (RFQ) is the process in which the procurement department invites several vendors to submit price and terms quotations for the goods or services requested in the PR. An effective RFQ must be very detailed, covering all technical specifications, quantities, delivery schedules, and warranty requirements. Imagine you send an RFQ for the supply of 1000 liters of disinfectant liquid to three leading medical suppliers: PT Medika Jaya, CV Sehat Selalu, and PT Mitra Farmasi. This transparent and competitive RFQ process is essential to obtain the best price, ensure quality, and avoid collusion. Recording all quotations digitally makes comparison and future audits easier.
Purchase Order (PO) is an official document created by the buyer to the seller, containing product details, quantity, agreed price, payment terms, and delivery date. A PO is a legally binding contract once received and approved by the vendor. After the RFQ is evaluated and the best vendor is selected (for example, PT Medika Jaya because it offers a price 5% lower and a 2-year warranty), the PO will be issued. This PO becomes the official instruction to the vendor to send the goods or provide the services. Without a structured PO, organizations risk receiving wrong or non-standard goods, as well as facing complicated payment disputes.
Goods Receipt Note (GRN), sometimes called Goods Received Note, is a document created when goods or services are received. The GRN confirms that the ordered goods have arrived, match the PO, and are in good condition. For example, when 980 liters of disinfectant liquid from PT Medika Jaya arrives, warehouse staff will record it in the GRN, match it with the PO, and note the 20-liter difference if any. The GRN becomes important physical evidence of receipt for the vendor payment process and stock updates in the inventory system. Integration of the GRN with the accounting system ensures that payment is made only for goods actually received, reducing the risk of duplicate payments or payments for fictitious goods. With the implementation of these four pillars, organizations can achieve high accountability, significant operational efficiency, and a reduction in procurement costs of up to 8-12%.
Technical Implementation Details of the Procurement System
Implementing an effective procurement system requires a solid technical architecture and the right technology choices. In the context of Nugroho Setiawan, who has experience with ERP and SIMRS, a modular approach based on web services is highly recommended. We will build this system using a modern framework that is proven to be scalable and easy to maintain. For the backend, we can utilize Laravel 11.x (PHP 8.2+), which provides a rich ecosystem for RESTful API development and database management. As the database, PostgreSQL 16 is the superior choice due to its reliability, strong transactional data handling capabilities, and JSONB features for schema flexibility. For the frontend, we can use Vue.js 3 or React 18, integrated through the API.
The system architecture will consist of several main modules: (1) Procurement Module (core PR, RFQ, PO, GRN), (2) Master Data Module (Vendor, Item/Product, Unit of Measurement), (3) User & Role Management Module, (4) Reporting & Analytics Module, and (5) Integration Module. The Procurement Module will manage the lifecycle of each document, from PR creation to goods receipt. Each document will have a clear status (for example: Draft, Submitted, Approved, Rejected, In Progress, Completed) and status transitions will be managed by an internal workflow engine. For authorization, we will implement strict Role-Based Access Control (RBAC), where only users with certain roles (for example, 'Department Manager' or 'Head of Procurement') can approve documents at certain stages. For example, a PR can only be approved by the relevant 'Department Manager', while a PO can only be approved by the 'Finance Director' if its value is above a certain threshold (for example, IDR 50,000,000).
Integration is the key to the success of this system. The procurement system must be able to communicate with other systems such as the Hospital Management Information System (SIMRS) or an existing ERP. For example, after a GRN is approved, the procurement system must trigger a stock update in the SIMRS inventory module and create an accounts payable entry in the ERP accounting module. This can be achieved through RESTful APIs. For SIMRS systems, Nugroho Setiawan has experience with BPJS/SatuSehat/FHIR integration. Although FHIR (Fast Healthcare Interoperability Resources, version R4 or STU3) focuses more on clinical data, its interoperability principles can be adopted. We can define a standard JSON payload for data exchange between the procurement system and other systems. For example, when a GRN is completed, an event will trigger an API call to the SIMRS inventory endpoint with a JSON payload containing the received items, quantities, and warehouse location. For notifications, it can be integrated with email services (for example, Postmark or Mailgun) or an SMS gateway for document approval or rejection notifications.
Data security is also a top priority. All communication between systems must use HTTPS. API authentication can use JWT (JSON Web Tokens) or OAuth 2.0. Sensitive data such as vendor details or item prices must be encrypted in transit and hashed if stored. A complete audit trail must record every user action, including who created, edited, or approved a document, along with timestamps. This is very important for regulatory compliance and investigation if anomalies occur. For example, every change in PR status from 'Submitted' to 'Approved' must record the ID of the approving user and the approval time. With this approach, the procurement system is not only efficient but also secure and fully integrated within the organization's IT ecosystem.
Example of a Simple Workflow Implementation Code
To provide a concrete illustration, let's look at a simple implementation example using Laravel 11.x and PostgreSQL 16. We will focus on the model for Purchase Requisition (PR) and how we can manage status and approvals.
PurchaseRequisition Model in Laravel
First, we define the `PurchaseRequisition` model that will represent purchase requests in the database. This includes important attributes such as the requested item, quantity, status, and who requested and approved it.
<?phpnamespace App\Models;use Illuminate\Database\Eloquent\Factories\HasFactory;use Illuminate\Database\Eloquent\Model;class PurchaseRequisition extends Model{ use HasFactory; protected $fillable = [ 'item_id', 'quantity', 'unit_price', 'total_amount', 'status', // e.g., 'draft', 'submitted', 'approved_manager', 'approved_procurement', 'rejected' 'requested_by_user_id', 'approved_by_manager_id', 'approved_by_procurement_id', 'request_date', 'needed_by_date', 'remarks' ]; protected $casts = [ 'request_date' => 'date', 'needed_by_date' => 'date', ]; public function item() { return $this->belongsTo(Item::class); } public function requester() { return $this->belongsTo(User::class, 'requested_by_user_id'); } public function managerApprover() { return $this->belongsTo(User::class, 'approved_by_manager_id'); } public function procurementApprover() { return $this->belongsTo(User::class, 'approved_by_procurement_id'); }}Code Explanation: This `PurchaseRequisition` model defines the important columns for a purchase requisition. The `status` column is key to managing the workflow, with values such as 'draft', 'submitted', 'approved_manager', 'approved_procurement', or 'rejected'. The `belongsTo` relationships connect the PR to the requested `Item` and the `User` who submits and approves it. The `item_id` column will refer to the `items` master table, `requested_by_user_id` to the `users` table (requester), and so on. The use of `$fillable` allows mass assignment, while `$casts` ensures that date columns are interpreted as PHP date objects.
PR Approval Logic in the Controller
Next, let's look at how a PR can be approved by a manager. This will be a method in `PurchaseRequisitionController`.
<?phpnamespace App\Http\Controllers;use App\Models\PurchaseRequisition;use Illuminate\Http\Request;use Illuminate\Support\Facades\Auth;use Illuminate\Validation\ValidationException;class PurchaseRequisitionController extends Controller{ // ... other methods ... public function approveByManager(Request $request, PurchaseRequisition $pr) { // 1. Authorization: Only managers can approve PRs if (!Auth::user()->hasRole('manager')) { throw ValidationException::withMessages([ 'message' => 'Anda tidak memiliki otorisasi untuk menyetujui PR ini.' ]); } // 2. Validate PR status: Only 'submitted' PRs can be approved if ($pr->status !== 'submitted') { throw ValidationException::withMessages([ 'message' => 'PR ini tidak dalam status yang dapat disetujui oleh manajer.' ]); } // 3. Update PR status and approver $pr->update([ 'status' => 'approved_manager', 'approved_by_manager_id' => Auth::id() ]); // 4. Optionally, dispatch an event for further actions (e.g., notify procurement) // event(new PrManagerApproved($pr)); return response()->json([ 'message' => 'Purchase Requisition berhasil disetujui oleh manajer.', 'pr' => $pr ]); } // ... other methods ...}Code Explanation: The `approveByManager` method is responsible for processing PR approval by a manager. First, authorization is performed using `Auth::user()->hasRole('manager')` to ensure that only users with the 'manager' role can perform this action. If not, a `ValidationException` is thrown. Second, the PR status is validated; only PRs with the status 'submitted' can be approved by a manager. This prevents double approval or PRs that have already been rejected. Third, if validation succeeds, the PR status is updated to 'approved_manager' and `approved_by_manager_id` is filled with the ID of the currently logged-in manager. Finally, a JSON response is sent back to the client. You can add event dispatching (`event(new PrManagerApproved($pr));`) to trigger follow-up actions such as sending notifications to the procurement department or recording activity in an audit trail.
Example Integration Payload and Error Handling
In an integrated system, data exchange between modules or between systems is essential. Let's take an example JSON payload for creating a Purchase Order (PO) via API, as well as how we handle errors that may occur.
Example JSON Payload for Creating a Purchase Order
Suppose that after a PR is approved and a vendor is selected, the procurement department wants to create a PO. This can be done via the API endpoint `/api/purchase-orders` with the POST method. The JSON payload will look like this:
{
"vendor_id": 45,
"pr_id": 102,
"items": [
{
"product_id": 12,
"quantity": 100,
"unit_price": 25000
},
{
"product_id": 8,
"quantity": 50,
"unit_price": 15000
}
],
"expected_delivery_date": "2024-08-15",
"payment_terms": "NET30",
"notes": "Mohon dikirim ke gudang pusat"
}After the payload is sent, the server will validate required fields such as vendor_id, pr_id, and items. If valid, the system will create a PO with the status 'draft' or 'issued' depending on the configuration. A successful response usually returns the complete PO object with an automatically generated po_number, for example {"status": "success", "data": {"po_number": "PO-2024-08-001", "total_amount": 3250000}}.
Common Error Handling
In integration, errors can come from input validation, authorization, or server issues. Here are examples of recommended error handling:
- 422 Unprocessable Entity: Occurs if the payload is invalid, for example
vendor_iddoes not exist. The response must include details of the incorrect field, such as{"errors": {"vendor_id": ["Vendor tidak ditemukan."]}}. - 401 Unauthorized: If the API token is invalid or expired. The client must refresh the token or log in again.
- 500 Internal Server Error: An unexpected error on the server. It is best to log the error and provide a generic message to the client, while ensuring that no sensitive data is leaked.
Always use try-catch on the client side to handle error responses and provide clear feedback to the user. On the server side, ensure that every error is recorded in the log for auditing and debugging.
Practical Tips for Implementing a Procurement Workflow
Implementing a seamless procurement workflow requires careful planning. First, ensure that each stage (PR, RFQ, PO, GRN) has a clear status definition and controlled transitions. Use a state machine or enum to avoid ambiguous statuses. For example, a PR can only change from 'submitted' to 'approved_manager' or 'rejected', it cannot go directly to 'approved_finance'. This prevents unauthorized process jumps.
Second, integrate automatic notifications at every status change. Utilize Laravel events and listeners to send emails or Slack messages to relevant parties. For example, when a PR is approved by the manager, send a notification to the procurement team; when a PO is created, send it to the vendor. This speeds up response and reduces manual communication. Additionally, log every action in an audit trail for compliance and troubleshooting purposes.
Third, conduct thorough testing, including error scenarios and edge cases. Test whether the system rejects a PR with an incorrect status, or whether a PO can be created without an approved PR. Use tools like Postman to test the API, and write unit tests for business logic. Don't forget to monitor performance and logs periodically after deployment, and prepare a rollback mechanism in case of issues.
FAQ
Does a PR always need to be approved by a manager before creating an RFQ?
Yes, generally a PR must be approved by a manager first to ensure the need is valid and the budget is available. However, some organizations allow RFQs to be created in parallel with PR approval to speed up the process, as long as there are strict controls. Adjust according to your internal policies.
What if the vendor does not respond to the RFQ?
The system should have a timeout mechanism or automatic reminders. After a certain period (e.g., 7 days), the RFQ can be closed and another vendor selected. Ensure there is an option to extend the deadline if necessary, with a note of the reason for extension.
Does a GRN need to be created for every PO?
Ideally yes, a GRN (Goods Receipt Note) is created when goods are received to verify quantity and quality. However, for service purchases or subscriptions, the GRN may be replaced with a service acceptance confirmation. Ensure there is documented proof of receipt.
How to handle a PO that is cancelled after GRN?
If a PO is cancelled after GRN, there needs to be a process for returning goods and adjusting inventory. Create a return document and update the PO status to 'cancelled' or 'returned'. Ensure communication with the vendor and finance team for payment or credit settlement.
Conclusion
Implementing an integrated procurement workflow from PR, RFQ, PO, to GRN requires attention to status details, authorization, and error handling. By following the guidelines and tips above, you can build a system that is efficient, transparent, and easy to audit. Don't hesitate to continuously evaluate and improve the process as your business grows.
Need further assistance in designing or implementing a procurement workflow in your company? Consult your needs with our expert team to get a solution tailored to your business scale and complexity. Contact us now for a free consultation session!
This article is part of the knowledge base of Nugroho Setiawan, an IT consultant in Jogja (Yogyakarta). Related solutions: SIMRS (Hospital Information System) BPJS & SatuSehat Integration. Need a free consultation?
Komentar
Belum ada komentar. Jadilah yang pertama!
Saya membantu konsultasi IT, pengembangan aplikasi, dan visualisasi data untuk rumah sakit, klinik, dan bisnis di Yogyakarta (DIY), Magelang, dan sekitarnya.