Understanding the procurement workflow | Spendive Help

Understanding the procurement workflow

  Audience: Requesters, procurement teams, approvers, and finance teams 
 Spendive's procurement module follows a chain from intention to payment. Each stage has its own page, and each produces a record the next stage draws on. 
 The chain 
 
 Approval in Principle (AIP) — pre-approve a spending budget so buying can move quickly later. Optional, but it is what makes budget-controlled purchase requests possible. 
 Purchase Request (PR) — someone asks to buy something. Sourced either From Approved AIP or as a Direct Purchase. 
 Request for Quotation (RFQ) — invite vendors to quote, then compare offers. 
 Purchase Order (PO) — the formal order placed with the chosen vendor. 
 Goods Received Note (GRN) — record what actually arrived and match it against the PO. 
 Bill — the vendor's invoice, recorded against the order. 
 Bill Payment — money leaves the business, handled under Accounting. 
 Debit Note — issued when you need to claim value back from a vendor, for example for short or damaged delivery. 
 
 Why the stages are separate 
 Each stage exists so a different control can be applied. AIP controls budget before commitment. RFQ controls price through competition. GRN controls that you only pay for what arrived. Skipping a stage does not just lose paperwork, it removes the control that stage provided. 
 Reference numbers 
 Every record carries a reference containing your organisation code: AIP, RFQ-, PO-, GRN and debit note references, plus JRN- for the accounting journal each transaction eventually produces. Quote the reference when raising a support ticket. 
 Need help? If the page, field, or approval action is missing, confirm the active organisation and ask an administrator to check your role and permissions. Quote the record reference when contacting support. 
    • Related Articles

    • Request approval workflow: illustrated guide

      A typical request moves from creation and supporting evidence to manager review, finance review, and final processing. Your organization’s approval path may vary by amount, department, location, project, or request type. Approvers should review the ...
    • Emergency procurement policy

      Emergency procurement may be used only when delay creates a material operational, safety, legal, or financial risk. The requester must document the emergency, why normal competition was impractical, vendor selection, price reasonableness, and ...
    • Managing procurement contracts

      Audience: Procurement and contract-management teams Contracts hold your vendor agreements in one place, with their value and expiry visible. Creating a contract Go to Procurement → Contracts. Select Create Contract. Record the vendor, the agreement ...
    • Understanding request statuses

      Audience: All Spendive users Every request you raise moves through the same tracking pattern, whatever its type. Overview and Action Required Each request page has two tabs. Overview lists your records with summary cards counting the total, pending, ...
    • Understanding wallet balances and transactions

      Using your Spendive wallet The Spendive wallet is where authorised users view available funds, send transfers, and track money moving into and out of the organisation. Who sees the wallet - Employees may see My Wallet, depending on their role and ...