Procure to pay: from requisition to supplier payment

Request, source, order, receive, match the supplier invoice and pay — who does each step, on which screen, and what BSuit records.

On this page

Process at a glance

  1. Raise requisitionRequesterPR approved; stock reserved and budget committed.
  2. Request quotationsBuyerRFQ awarded; a draft PO is created.
  3. Issue purchase orderBuyerPO issued to the supplier.
  4. Supplier acknowledgesSupplier (Vendor Portal)PO acknowledged.
  5. Receive goodsStorekeeperStock increased; PO partially received or received.
  6. Supplier invoicesSupplier (Vendor Portal)Invoice submitted for review.
  7. Review and approve invoiceAccounts payableInvoice approved and posted to payables.
  8. PayFinancePayment approved and posted from the bank.

#Purpose and scope

This chapter covers buying goods and services with BSuit’s procurement documents: requisition, request for quotation (RFQ), purchase order (PO), goods receipt note (GRN), supplier invoice, payment and returns. Suppliers take part through the Vendor Portal.

#Two ways to buy — choose one

BSuit offers two purchasing models. They do not share documents, so pick one per organisation or per category of spend and use it consistently.

Purchasing models
ModelDocumentsBest for
Procurement documents (this chapter)Requisition → RFQ → PO → GRN → supplier invoice → payment orderControlled purchasing with supplier collaboration in the Vendor Portal
Purchase vouchersEstimate → Quotation → Order → Purchase invoice (Purchase transactions)Simple purchasing recorded directly as accounting vouchers; the purchase invoice moves stock when posted

#Before you start

  1. Suppliers (with a party ledger), products, units, warehouses, currencies and tax codes.
  2. Inventory posting ledgers (stock, goods-received control, COGS, variance) in inventory posting configuration.
  3. Purchase-invoice posting configuration (Invoice posting config): AP control ledger and default expense ledger.
  4. Approval workflows for PREQ (requisitions), GRN-RCV (receipts) and BANK-PAY (payments).
  5. Budgets per cost centre if you want spend control at requisition.

#1. Raise a purchase requisition

  1. Open Requisitions and create a requisition with the items, quantities, priority (low, normal, high, urgent) and cost centre.
  2. Choose Save & Submit (or Submit for approval on a saved draft).
  3. BSuit checks the budget for the cost centre. A blocking rule stops submission; a warning rule lets it through with a warning.
  4. The requisition goes to the PREQ approval workflow. Approvers act from their approvals inbox.
Requisition statuses
StatusMeaning
DraftBeing prepared
SubmittedWaiting for approval
ApprovedStock reserved and budget committed
RejectedReturned by the approver
ConvertedTurned into a purchase order

#2. Request and compare quotations (RFQ)

  1. In RFQs create an RFQ with lines and scoring criteria.
  2. Invite at least one supplier. The RFQ becomes Sent and invited suppliers respond in the Vendor Portal.
  3. Score each response, then Award the winner. BSuit creates a draft purchase order from the winning response and marks the other responses rejected.

#3. Create and issue the purchase order

  1. Open Purchase orders › New, or open the draft created by the award. A PO created from a requisition needs that requisition to be approved.
  2. Choose the supplier, currency and lines. Choose Save draft or Save & issue.
  3. Issue the PO. The linked requisition becomes Converted, blanket-agreement consumption is applied, and the supplier is notified.
Purchase order lifecycle
StatusSet byButtons available
DraftBuyerIssue, Cancel
IssuedIssueAcknowledge, Cancel
AcknowledgedSupplier or buyerClose, Cancel
Partially received / ReceivedAccepted goods receiptsClose, Cancel
ClosedClose—
CancelledCancel (reason required)—

#4. Receive the goods (GRN)

  1. Open Goods receipt notes and create a receipt for the PO, with received quantities, warehouse, and batch or serial numbers where the product needs them.
  2. Submit for approval if your GRN-RCV record type requires it.
  3. Accept the receipt. Accepting is currently limited to superuser accounts.
What accepting a receipt does
EffectDetail
StockWarehouse quantity increases; weighted-average cost and cost layers update; a stock movement (IN) is recorded.
AccountsDebit stock asset, credit goods-received control — only if inventory posting ledgers are configured.
Purchase orderReceived quantity updates; the PO becomes Partially received or Received.
TolerancesA warning when received quantity or price is outside tolerance (10% by default).

#5. Supplier invoice and review

  1. The supplier submits the invoice in the Vendor Portal (Invoices) against an issued or received PO.
  2. Accounts payable opens Vendor invoices. Opening the review panel claims the invoice.
  3. Approve, Reject (notes required) or Request more information (notes required).
  4. Approval (finance manager or superuser) posts the purchase invoice automatically: debit expense and input tax, credit the supplier (or the AP control ledger).
  5. Check Matching for the three-way match result between PO, receipt and invoice.
Supplier invoice statuses
StatusMeaning
DraftBeing prepared by the supplier
SubmittedSent to the buyer
Under reviewClaimed by an AP reviewer
More info requestedReturned to the supplier with a question
ApprovedAccepted and posted to payables
RejectedRefused, with a reason

#6. Pay the supplier

  1. Create payment orders in Payment orders, or use Payment run to propose payments from open posted bills and create them in one go.
  2. Submit the payment order. It goes to the BANK-PAY approval workflow.
  3. On approval BSuit posts debit supplier (beneficiary) ledger, credit bank ledger.
  4. Initiate, then download the bank batch file and mark it transmitted (or failed).

#7. Returns to the supplier

  1. Create a return in Return to vendors.
  2. Submit it for approval (RTV workflow), then Approve and Complete (superuser).
  3. Completing issues the stock out and posts debit COGS, credit stock.

#Reports

Procurement reports
ReportUse
AP agingSupplier balances in age buckets (current, 1–30, 31–60, 61–90, over 90). Aged by transaction date, not due date.
Procurement registerAll purchasing documents.
Spend analyticsSpend by supplier and category.

#Troubleshooting

Common problems
Message or symptomCauseWhat to do
“Budget exceeded for cost centre…”Blocking budget ruleReduce the amount, move budget, or ask finance.
“No active workflow is configured for record type 'PREQ'.”No approval workflow linkedAn administrator links a workflow to PREQ.
“PR … is …, must be 'approved'.”Creating a PO from an unapproved requisitionGet the requisition approved first.
“Cannot issue a PO with no lines.”Empty POAdd lines.
“Approval required before receiving.”GRN-RCV requires approvalSubmit the receipt for approval.
“…is batch-controlled — BatchId is required…”Batch-tracked productEnter the batch on the receipt line.
Accept button refusedAccept is superuser-only todayAsk a superuser to accept.

About this guide

Status
Partially reviewed
Application
BSuit ERP
Audience
Requesters, buyers, storekeepers, accounts payable and finance managers
Owner
BSuit documentation team
Reviewer
Editorial review pending
Last verified
2026-09-25
Checked against
cb3691bbf
Seen on a running system
Not yet
Help version
2026.0.0-preview
Guide ID
erp:article/guide/procure-to-pay

Known limits: Written from a line-by-line read of the implementation (every statement traced to source). Not yet walked through end to end by a trainer on a running system.

Need more help?If feedback above cannot be sent, email support and quote guide ID erp:article/guide/procure-to-pay.
Email support