30 — Procurement

Overview

Procurement is the controlled purchasing module used to manage company spending before it becomes a financial commitment. It is the workspace where departments raise Purchase Requests, buyers collect Quotations, teams compare vendor responses, Procurement issues Purchase Orders, receiving teams confirm Goods Receipt, and finance reviews Purchase Invoices, Payment records, Vendor Statements, Order Returns, and Debit Notes inside one connected process. In the current product structure, the Procurement workspace includes exact records such as Vendors, Products/Services, Purchase Request, Quotations, Contracts, Goods Receipt, Purchase Order, Purchase Invoice, Payment record, Compare Quotes, Vendor Statement, and Debit Notes.

The main purpose of Procurement is governance, not only record keeping. It helps the company answer important operational questions before money is committed: what is being requested, by whom, for which department or project, from which Vendor, under what price and terms, with which approvals, with what delivery date, and with what receiving evidence. By keeping all of that in one workflow, Procurement reduces uncontrolled purchasing through calls, chat messages, and email chains and gives the business a clean audit trail across request, approval, order, delivery, invoice, and payment review.

A well-run Procurement process also improves coordination between operations and finance. Requesters can see whether their Purchase Request is still waiting for approval. Buyers can see which Quotations are missing and which Purchase Orders are still open. Receiving teams can confirm whether a delivery was full or partial. Finance can review whether a Purchase Invoice matches the Purchase Order and Goods Receipt before payment moves forward. Management can review spend by Vendor, category, department, and delivery performance without relying on offline summaries.

Procurement should be treated as the system of record for the purchase lifecycle. It is not only a document generator. It is the place where the business controls supplier selection, purchasing discipline, commercial terms, delivery follow-up, payable visibility, and purchase history. It is especially important in organizations that buy frequently, work with multiple Vendors, depend on approval rules, or need visibility into open commitments before payment is made.

Roles and permissions

Procurement works best when responsibilities are clearly separated.

A Requester should create the Purchase Request, define the business need, specify Products/Services, add quantities, attach supporting documents, and track the request status. The Requester should not be allowed to approve their own high-value request or change approved pricing and supplier-selection decisions without an authorized process.

An Approver should review the business need, policy compliance, completeness of supporting evidence, and the reasonableness of the requested spend. The Approver should be able to approve, reject, or send back the request, quotation decision, or Purchase Order according to policy. The Approver should not be responsible for maintaining Vendor records or receiving confirmations.

A Buyer / Procurement Officer should own sourcing execution. This role identifies candidate Vendors, issues quotation requests, records supplier responses, uses Compare Quotes, documents the selection rationale, creates the Purchase Order, and follows up on delivery commitments. This role should not control final payment status because payment authority belongs to finance policy.

A Procurement Manager should monitor exceptions, open commitments, delayed deliveries, category spend, and strategic Vendor choices. This role usually approves higher-risk or higher-value decisions, reviews SLA performance, and resolves sourcing exceptions such as urgent purchases or single-source procurement.

A Receiver / Warehouse role should confirm Goods Receipt, record whether the delivery was full or partial, attach delivery evidence, and help keep open quantities visible. This role should not change negotiated prices or Vendor commercial terms.

A Finance / A/P Reviewer should review Purchase Invoices, validate them against Purchase Orders and Goods Receipt where applicable, track payment request status, maintain Payment records, and monitor unpaid, partially paid, and paid obligations. This role should not rewrite sourcing decisions or approve a request on behalf of Procurement.

A Procurement Admin should maintain Vendor master quality, product and service setup, document numbering, permission boundaries, duplicate cleanup, document templates, and settings. This role should not override approvals casually and should preserve a clean audit trail around administrative changes.

A strong separation of duties usually means request creation, approval, ordering, receiving, and payment are not all owned by one user. This is one of the most important controls in the module because it protects the company from weak approvals, uncontrolled spend, and poor payable discipline.

What records Procurement manages

Procurement is broader than Purchase Orders alone. Teams should understand the full set of records.

• Vendors are the supplier master records and can include company information, contacts, vendor category, bank details, payment terms, tax details, and purchasing history.
• Products/Services and Items are used in Purchase Requests, Quotations, and Purchase Orders and can include unit price, quantity, units, groups, codes, images, vendor-items, and imports.
• Purchase Request is the internal demand record that starts the lifecycle and should include business justification, requested items/services, expected date, quantity, attachments, requester, and approval visibility.
• Quotations are used to collect supplier responses and apply disciplined vendor selection before issuing a Purchase Order.
• Compare Quotes is the structured review layer where buyers compare offers, document notes, and record selection rationale.
• Purchase Order is the formal supplier-facing commitment document and can include Vendor, references, department, project, type (CAPEX/OPEX), currency, tags, order date, buyer, delivery date, shipping details, line pricing, taxes, discounts, shipping fee, Vendor note, and terms.
• Goods Receipt confirms full or partial receipt, receipt date, receiving evidence, and pending quantities.
• Purchase Invoice is the supplier invoice record reviewed by finance and should include invoice number/date, amount, tax, due date, notes, reminders, payment request status, and linked purchasing references.
• Payment record tracks payable settlement status (unpaid, partially paid, paid) and payment evidence.
• Contracts handle recurring/formal vendor relationships, including contract number, signed status, payment cycle, payment terms, delivery terms, and references.
• Vendor Statement provides cumulative supplier statement and reconciliation visibility.
• Order Returns and Debit Notes manage formal post-delivery/post-invoice corrections and adjustments.

Setup checklist

Before rolling out Procurement, the company should complete a disciplined setup:

1. Prepare Vendor master readiness, remove duplicates, define onboarding ownership, and confirm legal/financial required fields.
2. Prepare item/service catalog standards and decide when controlled free text is allowed.
3. Define approval thresholds and routing, including urgent, single-source, and contract-based exceptions.
4. Define quotation rules including multi-quote requirements and Compare Quotes usage.
5. Configure Purchase Order numbering and output templates (including terms, notes, and shipping details).
6. Define receiving rules and required receiving evidence, including partial delivery handling.
7. Define invoice-matching policy (PO-only vs PO+receipt vs extended matching) and tolerance limits.
8. Define payment evidence and payment-status update authority.
9. Standardize category, department, project, CAPEX/OPEX type, tags, and date/status discipline.
10. Run go-live acceptance testing across the full request-to-payment flow and exception cases.

Key workflows

#### 1. Purchase Request intake

The Requester creates Purchase Request, adds Products/Services, quantities, expected dates, and business justification, attaches supporting files, and completes category/department tags before submission.

#### 2. Approval process

The Approver reviews business need, policy compliance, and completeness, then approves, rejects, or sends back for revision. Approved requests enter the buyer queue.

#### 3. Quotation request and Compare Quotes

The Buyer identifies candidate Vendors, issues quotation requests, records responses, and uses Compare Quotes to document and justify supplier selection.

#### 4. Purchase Order creation

The Buyer creates Purchase Order from approved Purchase Request or selected Quotation (or directly where policy allows), validates commercial details, and issues the PO.

#### 5. Receiving and delivery follow-up

The receiving team posts Goods Receipt with full/partial status and delivery evidence. Partial receipts must keep remaining quantities visible for follow-up.

#### 6. Purchase Invoice and Payment record review

Finance records Purchase Invoice, verifies matching against related documents per policy, manages payment request flow, and updates Payment record status.

#### 7. Contracts, Vendor Statement, returns, and Debit Notes

For recurring vendor relationships, teams should maintain contract details. Vendor Statement supports reconciliation. Order Returns and Debit Notes support formal purchasing corrections.

#### 8. Monthly procurement performance review

Leadership should review open requests, approval backlog, overdue POs, delayed deliveries, vendor performance, spend trends, invoice backlog, payment visibility, and recurring exceptions.

Reports and review rhythm

Procurement reporting should be part of routine governance:

• Approvals queue
• Open requests by requester/age/department
• Purchase Orders by status
• Overdue deliveries
• Spend by vendor/category/department
• Invoice/payment visibility
• Vendor history / Vendor Statement
• Management reports such as cost of purchase orders and number of purchase orders

A practical cadence is daily review for approvals and overdue deliveries, weekly review for open POs and exceptions, and monthly review for spend trends and vendor performance.

Best practices

• Use one clean Vendor master and enforce duplicate control.
• Require business justification on every non-standard Purchase Request.
• Keep quotation comparison in Compare Quotes, not inboxes.
• Do not issue Purchase Order before approvals are complete.
• Use department, project, type, and category fields consistently.
• Record partial deliveries as partial.
• Require invoice matching before marking payment-ready.
• Use Vendor Statement and Debit Notes for formal reconciliation.
• Review open commitments before they become finance surprises.

Troubleshooting and FAQ

#### Users cannot see Procurement menus

Confirm module activation and role permissions first.

#### Purchase Request cannot move to Purchase Order

Confirm request approval status, required fields, and whether quotation completion is required by deployment policy.

#### Quotation comparison is incomplete

Confirm all supplier responses are recorded and compared against consistent specifications, units, and quantities.

#### Delivery status looks wrong

Confirm Goods Receipt was posted against the correct Purchase Order and partial receipt was used where applicable.

#### Purchase Invoice does not match Purchase Order

Validate quantity, rate, tax, delivery status, and references. Route through exception policy instead of forcing payment-ready status.

#### Duplicate Vendors are causing confusion

Merge/retire duplicates under Vendor-master ownership and tighten onboarding checks.

#### Payment status is unclear

Standardize who updates Payment records and require payment evidence before setting fully paid.

#### Reporting is weak

Make owner, department, category, delivery status, and payment-status fields mandatory in daily usage.

نظرة عامة

تُعد وحدة Procurement مساحة العمل الرئيسية لإدارة الشراء المنضبط داخل المؤسسة، وهي المسؤولة عن ضبط الإنفاق قبل أن يتحول إلى التزام مالي فعلي. من خلالها يتم إنشاء Purchase Requests من الإدارات، وجمع Quotations من Vendors، ومراجعة Compare Quotes، وإصدار Purchase Orders، وتأكيد Goods Receipt، ثم مراجعة Purchase Invoices وPayment records وVendor Statements وOrder Returns وDebit Notes داخل مسار واحد مترابط.

الهدف من Procurement ليس حفظ المستندات فقط، بل فرض الحوكمة على عملية الشراء نفسها. فهي تساعد المؤسسة على الإجابة عن أسئلة تشغيلية مهمة قبل الالتزام بالإنفاق: من طلب الشراء؟ لأي إدارة أو مشروع؟ لأي أصناف أو خدمات؟ من أي Vendor؟ وبأي سعر وشروط؟ وما هي الموافقات المطلوبة؟ وما هو تاريخ التسليم؟ وهل تم الاستلام بالكامل أم جزئيًا؟ وهل تمت مراجعة الفاتورة وربطها بالمستندات الصحيحة قبل السداد؟

وتمنح Procurement تنسيقًا أفضل بين التشغيل والمالية. يستطيع Requester متابعة حالة الطلب، ويستطيع Buyer متابعة العروض وأوامر الشراء المفتوحة، ويستطيع فريق الاستلام تسجيل الاستلام الكامل أو الجزئي مع الإثباتات، وتستطيع المالية مراجعة Purchase Invoice على ضوء Purchase Order وGoods Receipt قبل التحويل إلى Payment record.

يجب التعامل مع Procurement على أنها السجل الرسمي لدورة الشراء، لا مجرد وحدة لإخراج PDF. فهي المكان الذي تُضبط فيه قرارات الشراء، ويُوثق فيه اختيار المورد، وتُتابع فيه شروط التوريد والتسليم، وتُربط فيه الفواتير والمدفوعات بتاريخ الشراء الحقيقي.

الأدوار والصلاحيات

تنجح وحدة Procurement عندما تكون المسؤوليات موزعة بشكل واضح:

• Requester ينشئ Purchase Request ويحدد الحاجة والأصناف والكميات والتاريخ المتوقع ويرفق المستندات.
• Approver يراجع المبررات والالتزام بالسياسة ويعتمد أو يرفض أو يعيد الطلب للمراجعة.
• Buyer / Procurement Officer يدير التوريد، يجمع العروض، يستخدم Compare Quotes، ويوثق سبب اختيار Vendor وينشئ Purchase Order.
• Procurement Manager يراجع الاستثناءات والقرارات عالية القيمة والمخاطر ويتابع الالتزامات المفتوحة والتسليمات المتأخرة.
• Receiver / Warehouse يثبت Goods Receipt ويؤكد الاستلام الكامل أو الجزئي مع الأدلة.
• Finance / A/P Reviewer يراجع Purchase Invoices ويطابقها مع Purchase Order وGoods Receipt ويتابع Payment record.
• Procurement Admin يحافظ على جودة بيانات Vendors وإعدادات Products/Services والترقيم والصلاحيات والقوالب.

أفضل ممارسة هي الفصل بين إنشاء الطلب واعتماده وإصدار Purchase Order وإثبات الاستلام وتسجيل الدفع.

ما الذي تديره وحدة Procurement

Procurement تدير مجموعة واسعة من السجلات:

• Vendors
• Products/Services وItems
• Purchase Request
• Quotations
• Compare Quotes
• Purchase Order
• Goods Receipt
• Purchase Invoice
• Payment record
• Contracts
• Vendor Statement
• Order Returns وDebit Notes

قائمة الإعداد قبل التشغيل

قبل الإطلاق، نفّذ إعدادًا منضبطًا يشمل:

1. تنظيف بيانات Vendors ومنع التكرارات.
2. تجهيز دليل الأصناف والخدمات وتوحيد الأسماء والوحدات والرموز.
3. تحديد قواعد الاعتماد ومسارات الاستثناء.
4. تحديد قواعد Quotations واستخدام Compare Quotes.
5. ضبط ترقيم Purchase Orders وقوالب الإخراج.
6. تحديد قواعد الاستلام وإثبات Goods Receipt.
7. تحديد سياسة مطابقة Purchase Invoice وحدود التفاوت.
8. تحديد سياسة Payment record وأدلة السداد.
9. توحيد استخدام الحقول التحليلية (الإدارة/المشروع/التصنيف/النوع/الوسوم).
10. تنفيذ اختبار قبول شامل قبل التشغيل.

سير العمل الأساسي

#### 1) إنشاء Purchase Request

يبدأ المسار بإنشاء الطلب مع المبرر والكميات والتواريخ والمرفقات.

#### 2) الاعتماد

يراجع Approver الطلب ويعتمده أو يرفضه أو يعيده للتعديل.

#### 3) جمع Quotations والمقارنة

يتم إرسال طلبات الأسعار وتسجيل الردود واستخدام Compare Quotes لتوثيق الاختيار.

#### 4) إنشاء Purchase Order

يحوّل Buyer الطلب أو العرض المعتمد إلى Purchase Order ويُصدره بعد مراجعة الشروط التجارية.

#### 5) إثبات الاستلام

يسجّل فريق الاستلام Goods Receipt كاستلام كامل أو جزئي مع الأدلة.

#### 6) مراجعة Purchase Invoice وPayment record

تراجع المالية الفاتورة وتطابقها مع المستندات ثم تحدّث حالة السداد.

#### 7) العقود وكشوف الموردين والإرجاع وDebit Notes

تُستخدم Contracts وVendor Statement وOrder Returns وDebit Notes لإدارة العلاقات المستمرة والتسويات الرسمية.

#### 8) المراجعة الشهرية

تراجع الإدارة الطلبات المفتوحة، تراكم الاعتمادات، التأخر في التسليم، الإنفاق، الفواتير، وحالات السداد.

التقارير وإيقاع المراجعة

التقارير الأساسية تشمل:

• Approvals queue
• Open requests
• Purchase Orders by status
• Overdue deliveries
• Spend by vendor/category/department
• Invoice/payment visibility
• Vendor history / Vendor Statement

الإيقاع الموصى به: مراجعة يومية للاعتمادات والتسليمات المتأخرة، أسبوعية للأوامر المفتوحة والاستثناءات، وشهرية لاتجاهات الإنفاق وأداء الموردين.

أفضل الممارسات

• استخدم سجل Vendors موحدًا ونظيفًا.
• اطلب مبررًا واضحًا لكل Purchase Request غير قياسي.
• نفّذ المقارنة داخل Compare Quotes.
• لا تُصدر Purchase Order قبل اكتمال الاعتماد.
• سجّل الاستلام الجزئي بوصفه جزئيًا.
• لا تعتمد Purchase Invoice جاهزة للدفع قبل المطابقة.
• استخدم Vendor Statement وDebit Notes للتسويات الرسمية.

معالجة المشكلات / الأسئلة الشائعة

• إذا لم تظهر قوائم Procurement، تحقق من تفعيل الوحدة والصلاحيات.
• إذا لم ينتقل Purchase Request إلى Purchase Order، تحقق من حالة الاعتماد والحقول المطلوبة وسياسة Quotation.
• إذا كانت المقارنة غير واضحة، تأكد من تسجيل كل ردود الموردين وتوحيد المواصفات.
• إذا كانت حالة التسليم خاطئة، تحقق من تسجيل Goods Receipt الصحيح واستخدام الاستلام الجزئي عند الحاجة.
• إذا لم تتطابق Purchase Invoice مع Purchase Order، وجّه الحالة إلى سياسة الاستثناءات.
• إذا وُجد تكرار في Vendors، قم بالدمج أو الإلغاء تحت حوكمة واضحة.
• إذا كانت حالة الدفع غير واضحة، وحد مسؤول تحديث Payment records واطلب أدلة السداد.
• إذا كانت التقارير ضعيفة، اجعل الحقول التشغيلية الأساسية إلزامية.