Purchase Requisition to Payment: What an Integrated ERP Should Track

Purchase Requisition to Payment: What an Integrated ERP Should Track

A purchase does not begin when the supplier sends an invoice.

It begins when someone inside the business identifies a need.

Production may need raw materials. A warehouse may need replenishment. An office may require equipment. A project team may need a service.

From that point, several things have to happen correctly.

The requirement must be approved. Procurement may compare suppliers. A purchase order is issued. Goods or services are received. The supplier submits an invoice. Accounts verifies the liability. Only then should payment move forward.

When these steps sit in different spreadsheets, emails or departmental systems, the business loses the connection between the original requirement and the final payment.

That is why the purchase requisition to payment process should be evaluated as one connected ERP workflow.

For manufacturing, trading and distribution businesses in Bangladesh, an integrated ERP should make one question easy to answer:

Why are we paying this supplier this amount for this purchase?

The answer should be traceable from the original request to the final payment.

This guide covers eight controls that matter.

What Does Purchase Requisition to Payment Mean?

Purchase requisition to payment is the operational flow that connects an internal purchasing need with the final supplier payment.

A practical process may look like this:

Requirement → Purchase Requisition → Approval → RFQ / Supplier Comparison → Purchase Order → Goods Receipt → Supplier Invoice → Matching → Payment → Accounting

Different businesses will configure this differently.

A low-value routine purchase may not need the same sourcing process as a high-value capital purchase.

Imported materials may require additional documentation.

Service purchases may use different receiving evidence.

The important point is not that every company follows exactly the same sequence.

The important point is that every stage remains connected, controlled and traceable.

Why the Process Breaks When Systems Are Disconnected

Consider a simple example.

Production requests 2,000 units of raw material.

The requisition is approved.

Procurement creates a purchase order for 2,000 units.

The supplier delivers 1,850.

The warehouse records the actual receipt.

But the supplier invoice still shows 2,000 units.

If procurement, warehouse and accounts are working from different files, someone now has to reconstruct the transaction manually.

Which quantity was requested?

Which quantity was ordered?

Which quantity actually arrived?

Was the remaining quantity still pending?

Was anything rejected?

Should the supplier be paid for 1,850 units or 2,000?

An integrated ERP should make these questions easier to answer because the documents remain connected to the same transaction chain.

A controlled purchase requisition to payment workflow makes every purchasing decision easier to trace.

1. Start With a Controlled Purchase Requisition

A purchase requisition should record the business need before procurement makes a supplier commitment.

A useful requisition normally identifies:

  • requested item or service
  • requested quantity
  • requesting department
  • required date
  • warehouse, project or cost centre where relevant
  • business justification
  • requester
  • approval status

The requisition is not the purchase order.

It is the internal request to purchase something.

That distinction matters.

Without a controlled requisition, purchasing can begin through phone calls, emails or chat messages.

By the time finance sees the supplier invoice, the reason behind the purchase may already be difficult to verify.

A reliable purchase requisition to payment process therefore starts with a clear source document.

2. Keep Approval Before Supplier Commitment

Approval should happen before the business commits to the supplier whenever company policy requires it.

The ERP should make it clear:

  • who requested the purchase
  • who approved it
  • when approval happened
  • whether it was rejected or returned
  • whether anything changed after approval

Approval paths may differ by:

  • department
  • amount
  • item category
  • business unit
  • project
  • warehouse
  • purchasing type

For example, a routine purchase may require one approval while a major capital purchase requires several.

The objective is not to create more approval steps.

It is to create clear authority.

For a broader ERP evaluation framework, see our ERP Buying Guide for Bangladesh Manufacturers: 2027.

3. Connect Supplier Evaluation to the Original Requirement

Some purchases require competitive sourcing before a supplier is selected.

The process may move through:

RFQ → Supplier Quotation → Comparative Statement → Supplier Selection

The important question is whether those records remain connected to the original requirement.

Suppose three suppliers submit quotations.

Supplier A offers the lowest price.

Supplier B offers faster delivery.

Supplier C meets a technical specification that the others do not.

If the business selects Supplier C, the purchasing record should preserve the evidence behind that decision where company policy requires it.

Otherwise, management later sees only a purchase order.

It cannot easily see why that supplier was selected.

This becomes particularly important for higher-value purchases or businesses with formal procurement controls.

4. Make the Purchase Order the Commercial Commitment

Once the purchase is approved and the supplier is selected, the purchase order becomes the formal commercial reference.

A useful PO should identify:

  • supplier
  • item or service
  • ordered quantity
  • agreed price
  • delivery location
  • expected delivery date
  • payment terms
  • applicable tax or charges
  • relevant requisition or sourcing reference

The PO should not become another isolated document.

Management should be able to move backward from the PO to the approved requirement and forward from the PO to receiving, invoice verification and payment.

This is where an integrated ERP procurement process starts becoming materially useful.

Instead of asking several departments for separate files, the transaction itself preserves the history.

5. Record What Was Actually Received

A purchase order shows what the business expected to receive.

The receiving transaction shows what physically arrived.

Those figures are not always the same.

For example:

StageQuantity
Purchase Requisition2,000
Purchase Order2,000
Goods Received1,850
Pending / Difference150

The ERP should preserve that difference.

It should not automatically treat the ordered quantity as the received quantity.

The receiving stage may also need to capture:

  • actual received quantity
  • warehouse
  • receiving date
  • batch or lot where relevant
  • damaged quantity
  • rejected quantity
  • partial receipt
  • responsible user

SAP’s procure-to-pay guidance also treats purchase order, goods receipt, invoice verification and payment as connected but distinct stages of the purchasing process. See the SAP Procure-to-Pay process documentation.

That distinction matters.

Ordered quantity and received quantity represent two different business events.

6. Match the Supplier Invoice Before Payment

This is one of the most important controls within the purchase requisition to payment process.

Before paying a supplier, the business should know whether the invoice agrees with the approved purchase and receiving records.

A common control is three-way matching:

Purchase Order ↔ Goods Receipt ↔ Supplier Invoice

Consider this example:

DocumentQuantityUnit Price
Purchase Order2,000Tk 100
Goods Receipt1,850Tk 100
Supplier Invoice2,000Tk 100

Something needs attention.

The business should not silently pay the full invoice just because the supplier submitted it.

Three-way matching is one of the most important controls within the purchase requisition to payment process because it helps expose quantity and pricing differences before payment.

Oracle’s procurement documentation similarly supports invoice matching against purchasing and receiving records, including three-way matching controls. See Oracle Match Approval Levels.

The exact tolerance and approval configuration will vary by ERP and business policy.

The principle is more important:

Payment should be supported by both the commercial commitment and evidence of receipt.

7. Keep Exceptions Visible Instead of Fixing Them Outside the ERP

Real procurement processes are rarely perfect.

Common exceptions include:

  • partial delivery
  • excess delivery
  • damaged goods
  • rejected materials
  • invoice quantity differences
  • price differences
  • purchase returns
  • cancelled purchase orders
  • revised delivery dates
  • changed supplier terms

The weak approach is to fix these exceptions in spreadsheets outside the ERP.

That breaks the evidence trail.

Suppose 100 damaged units are returned to the supplier.

Accounts should not discover that return only when someone prepares payment.

The return should remain connected to the purchase and receiving records.

A strong ERP workflow makes exceptions visible to the teams responsible for resolving them.

This is also where approval history and audit trails become important.

The objective is not only to record the final number.

The system should preserve why the number changed.

8. Connect Supplier Payment With Accounts

Payment is not only a procurement event.

It is also a financial event.

Once the approved supplier liability is ready for payment, the ERP should connect that payment with:

  • supplier
  • purchase reference
  • invoice
  • payable amount
  • payment amount
  • payment date
  • bank or payment account
  • remaining balance
  • related accounting entries

The same purchase should not need to be rebuilt manually inside the finance team.

If procurement shows one payable amount while finance maintains another spreadsheet, reconciliation continues even after ERP implementation.

For growing businesses, a connected purchase requisition to payment workflow reduces the need to reconstruct transactions across separate files.

A connected ERP should maintain the relationship between procurement activity and accounts payable while still allowing finance to review and approve what needs judgment.

A Practical Purchase Requisition to Payment Example

Consider a manufacturing business purchasing packaging material.

Step 1: Purchase Requisition

Production requests 10,000 packaging units.

Step 2: Approval

The responsible manager reviews and approves the requirement.

Step 3: Supplier Evaluation

Procurement collects quotations and selects the supplier according to company policy.

Step 4: Purchase Order

A PO is issued for 10,000 units at the agreed price.

Step 5: Goods Receipt

The warehouse receives 9,800 units.

Another 200 units remain pending.

Step 6: Supplier Invoice

The supplier submits an invoice for all 10,000 units.

Step 7: Matching

The ERP shows that invoiced quantity is greater than received quantity.

The difference is reviewed before payment.

Step 8: Payment

The approved amount is processed according to company policy and supplier terms.

Step 9: Accounts

The supplier payable and related financial records remain connected to the purchasing transaction.

Now management can trace the transaction from the original requirement to the final financial impact.

That is what an integrated purchase requisition to payment process should achieve.

What Should Management Be Able to Track?

An integrated ERP should allow management to review procurement from several angles.

Useful views include:

  • pending purchase requisitions
  • requisitions awaiting approval
  • RFQs
  • supplier quotations
  • comparative statements
  • open purchase orders
  • partially received POs
  • overdue supplier deliveries
  • purchase receipts
  • purchase returns
  • invoice differences
  • pending supplier payments
  • supplier payable balances
  • purchases by department
  • purchases by warehouse
  • purchases by supplier

The value is not the number of reports.

The value is whether management can move from a number back to the transaction that created it.

Why Warehouse Integration Matters

Procurement cannot be evaluated separately from inventory.

Once purchased goods arrive, the ERP should update the correct warehouse according to the actual receiving transaction.

If the company operates several warehouses, the destination matters.

Material received into Warehouse A should not automatically appear inside Warehouse B.

This becomes particularly important for manufacturers and distributors where purchasing decisions depend on stock already available across multiple locations.

Before raising another PO, management should be able to ask:

Do we genuinely need to purchase this quantity, or is usable stock already available somewhere else?

If your business manages inventory across several locations, review our ERP Stock Transfer Controls for Multi-Warehouse Distribution guide to understand transfer approvals, dispatch, in-transit stock, receiving and warehouse reconciliation.

Why Finance Integration Matters

A purchasing process can look efficient operationally and still create financial reconciliation problems.

Procurement has approved the purchase.

Warehouse has received the material.

The supplier has submitted the invoice.

But finance cannot clearly connect those records.

Now accounts has to rebuild the transaction manually before payment.

That creates unnecessary reconciliation.

For growing businesses, a connected purchase requisition to payment workflow reduces the need to reconstruct transactions across separate files.

A connected ERP should maintain the relationship between procurement activity and accounts payable.

That does not eliminate finance review.

It gives finance better evidence to review.

Automation Is Not the Same as Control

Automating the purchase requisition to payment process does not mean every purchase should automatically move from requisition to supplier payment without human review.

Good automation removes unnecessary handoffs and repeated data entry while keeping important controls.

Examples include:

  • automated approval routing
  • purchase order creation from approved requirements where appropriate
  • receiving against purchase orders
  • invoice matching
  • exception alerts
  • accounts payable creation
  • approval history
  • supplier payment tracking

Human judgment may still be needed when:

  • supplier selection is unusual
  • quantity differs
  • price changes
  • goods are rejected
  • budget is exceeded
  • payment requires senior approval

Automation should make these exceptions easier to identify.

It should not hide them.

How Managerium ERP Fits the Workflow

Managerium ERP connects procurement, inventory, approvals, accounts and finance within the same ERP environment.

Its documented purchasing workflow includes:

  • Purchase Requisition
  • Request for Quotation
  • Supplier Quotation
  • Comparative Statement
  • Purchase Order
  • Purchase Receive
  • Purchase Return
  • Purchase Payment
  • Purchase reporting

Its wider ERP environment also connects warehouse inventory, multi-warehouse operations, approvals, accounts payable and financial reporting.

The important point is not simply that these features exist.

The value comes from the relationship between the transactions.

A requisition should not disappear when a PO is created.

A PO should not become disconnected when the material is received.

A receipt should not become invisible when accounts records the supplier liability.

And the supplier payment should remain traceable back to the transaction that created it.

That is the standard an integrated ERP should be tested against.

What Should You Ask During an ERP Demo?

Do not ask only:

“Does the ERP support purchase requisition and purchase order?”

Most ERP systems will say yes.

Instead, ask the vendor to demonstrate one imperfect transaction:

Purchase Requisition → Approval → RFQ → Supplier Comparison → Purchase Order → Partial Receipt → Supplier Invoice → Quantity Mismatch → Purchase Return → Payment → Accounts

Then ask:

  1. Can the PO be traced back to the original requisition?
  2. Can we see who approved each stage?
  3. Can received quantity differ from ordered quantity?
  4. What happens if the invoice exceeds the received quantity?
  5. Can rejected or returned goods remain traceable?
  6. Does inventory update from actual receipt?
  7. Does accounts use the same transaction reference?
  8. Can management see what remains pending?

The exception scenario usually reveals more than a perfect demo.

Purchase Requisition to Payment Control Checklist

Before approving an ERP for procurement, verify that it can show:

ControlWhat You Should See
Purchase needRequisition and requester
AuthorizationApproval history
Supplier selectionRFQ, quotation and comparison where applicable
Commercial commitmentPurchase order
Physical receiptActual received quantity
VarianceQuantity, price or receipt difference
Purchase returnRelationship to original purchase
Supplier liabilityVerified invoice / payable
PaymentSupplier payment reference
AccountingConnected financial impact
Audit trailUser, action and timestamp

If a vendor cannot demonstrate these relationships through one transaction, the process may still depend heavily on manual reconciliation.

Final Check

A strong purchase requisition to payment process should make the purchasing story easy to explain.

Who requested the purchase?

Who approved it?

Why was that supplier selected?

What was ordered?

What actually arrived?

What did the supplier invoice?

What difference had to be resolved?

What was finally paid?

Where did the financial impact go?

If those answers require several spreadsheets, emails and phone calls, the procurement process is still fragmented.

An integrated ERP should preserve one connected evidence trail from business requirement to supplier payment.

That is the standard worth testing.

Frequently Asked Questions

What is purchase requisition to payment?

Purchase requisition to payment is the end-to-end procurement process from an internal purchase request through approval, supplier selection, purchase order, receiving, invoice verification and supplier payment.

Is a purchase requisition the same as a purchase order?

No. A purchase requisition is generally an internal request to purchase something. A purchase order is the formal purchasing document issued to the selected supplier.

What is three-way matching in procurement?

Three-way matching compares the purchase order, goods receipt and supplier invoice before payment according to the company’s configured tolerances and controls.

Why should goods receipt be separate from the purchase order?

The purchase order records what was ordered. The goods receipt records what actually arrived. Keeping them separate helps identify partial deliveries, shortages, excess quantities, rejected goods or damaged items.

What should an integrated ERP track before supplier payment?

It should preserve the relationship between the original requirement, approvals, supplier selection, purchase order, actual receipt, supplier invoice, exceptions, payable amount and final payment.

Can Managerium ERP support the purchase requisition to payment process?

Managerium ERP’s documented purchasing scope includes purchase requisition, RFQ, comparative statement, purchase order, purchase receive, purchase return and purchase payment, connected with inventory, approvals and accounts.

Take One Imperfect Purchase to the Demo

Do not evaluate ERP using only a perfect purchasing scenario.

Use something closer to real operations.

Order 1,000 units.

Receive 930.

Reject 20.

Let the supplier invoice 1,000.

Then ask the vendor to show what happens next.

If the ERP can preserve the requisition, approval, PO, receipt difference, return, supplier liability and final payment without losing the transaction trail, you are looking at a much stronger procurement process.