From purchase request to approved payment
Approved requirement, accepted goods, matched bill, verified payment review.
Stop and check if…
- Different quote basis or unapproved terms
- Physical receipt does not equal inspection acceptance
- Cumulative billing exceeds accepted/ordered qty
- Missing bank routing or duplicate payment ref
Do not mark a stage done just because AI produced a draft. Use actual evidence and human approval. Keep private records in your approved tools. Prompt Bro never submits, posts, pays or approves anything.
0 of 5 stages verified
Stages unlock in order. Only completion ticks are saved in this browser; no documents, inputs or AI outputs are stored.
All 5 stages verified. Keep the approvals and evidence in your own records; this tick list is not proof.
- What you need
- Department requests, stock and reorder rules
- What to produce
- Approved requested SKU/unit/qty, stock and shortage
- Who checks it
- Stores checks actual stock; department approves
Open the tasks
- Consolidating purchase requests · Tested
- Reorder levels · Tested
If this happens
- Physical stock is unknown or the request duplicates another one: Count or check stock and merge duplicate requests before buying. Switch to: From physical stock count to reorder decision
Handoff template
Workflow: From purchase request to approved payment Stage: Confirm requirement (1 of 5) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Approved requested SKU/unit/qty, stock and shortage Approval status (approved / pending / rejected): [confirm] Approved by (Stores checks actual stock; department approves): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: Compare and order, needs: Same-basis quotes and approved limits
- What you need
- Same-basis quotes and approved limits
- What to produce
- Approved vendor/PO line, qty/rate/terms and pending items
- Who checks it
- Purchase and management approve PO
Open the tasks
- Finding vendors and sending RFQs · Tested
- Vendor quote comparison · Not yet tested
- Negotiation preparation · Tested
- Purchase orders · Tested
- Open purchase order and delivery ageing · Tested
If this happens
- Vendor quotes are on a different basis (unit, tax, freight, delivery): Ask vendors to requote on one basis; do not compare unlike quotes.
- Order value is above your approval limit or the vendor is new: Get management approval and verify the vendor's details before the PO goes out. Verify a customer or vendor bank-detail change (expert review pending)
Handoff template
Workflow: From purchase request to approved payment Stage: Compare and order (2 of 5) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Approved vendor/PO line, qty/rate/terms and pending items Approval status (approved / pending / rejected): [confirm] Approved by (Purchase and management approve PO): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: Receive and inspect, needs: Actual receipt and authorised inspection
Unlocks after stage 1 is verified.
- What you need
- Actual receipt and authorised inspection
- What to produce
- GRN/PO line, physical received, accepted, rejected, pending, evidence
- Who checks it
- Stores and quality owner confirm acceptance
Open the tasks
- Vendor follow-ups · Tested
- Goods receipt entry · Tested
- Rejections and returns · Tested
If this happens
- Quantity received differs from quantity accepted after inspection: Record received, accepted and rejected separately; return or debit only the rejected quantity. Use: Rejections and returns
- Goods arrive with no PO or against a closed PO: Hold the goods entry and ask purchase for the approved PO. Go to stage 2: Compare and order
Handoff template
Workflow: From purchase request to approved payment Stage: Receive and inspect (3 of 5) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: GRN/PO line, physical received, accepted, rejected, pending, evidence Approval status (approved / pending / rejected): [confirm] Approved by (Stores and quality owner confirm acceptance): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: Match invoice, needs: PO, accepted GRN, current and prior bills; approved adjustments
Unlocks after stage 2 is verified.
- What you need
- PO, accepted GRN, current and prior bills; approved adjustments
- What to produce
- Line-level pass/hold, taxable/gross, exceptions and supporting refs
- Who checks it
- Accounts verifies tax and any adjustment
Open the tasks
- Three-way match (PO, GRN, bill) · Tested
- Vendor bill entry · Tested
- Debit notes to vendors · Tested
- Detect duplicate bills and payments · Tested
If this happens
- Bill quantity or rate is more than PO or accepted GRN: Hold the bill; raise a debit note or ask for a corrected bill. Use: Debit notes to vendors
- Same bill number, amount or date seen before: Treat it as a possible duplicate and check before entry. Use: Detect duplicate bills and payments
Handoff template
Workflow: From purchase request to approved payment Stage: Match invoice (4 of 5) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Line-level pass/hold, taxable/gross, exceptions and supporting refs Approval status (approved / pending / rejected): [confirm] Approved by (Accounts verifies tax and any adjustment): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: Payment review, needs: Verified approved bills and payment refs, routing held locally
Unlocks after stage 3 is verified.
- What you need
- Verified approved bills and payment refs, routing held locally
- What to produce
- Unique ready-for-review list, held duplicates, payment advice and ledger query
- Who checks it
- Authorised bank/owner approves payment; no AI action
Open the tasks
- Approving payments · Tested
- Bulk payment file for the bank (expert review pending) · Not yet tested
- Payment advice to vendors · Tested
- Vendor ledger reconciliation · Tested
- Verify a customer or vendor bank-detail change (expert review pending) · Not yet tested
If this happens
- Vendor bank details changed or arrived by email/WhatsApp: Stop payment. Verify the change through a known contact before releasing anything. Verify a customer or vendor bank-detail change (expert review pending)
- Bill is on hold, disputed or its debit note is pending: Leave it out of the payment file; pay only approved, matched amounts. Go to stage 4: Match invoice
Handoff template
Workflow: From purchase request to approved payment Stage: Payment review (5 of 5) Source refs (document no. / date): [confirm] Item / unit / quantity: [confirm] Known (verified against source): [confirm] Unknown / held items and why: [confirm] This stage produced: Unique ready-for-review list, held duplicates, payment advice and ledger query Approval status (approved / pending / rejected): [confirm] Approved by (Authorised bank/owner approves payment; no AI action): [name / role] Evidence ref (where the proof is kept): [confirm] Next stage: none. Workflow ends after this approval.
Unlocks after stage 4 is verified.