# School Procurement Software: Suppliers, Purchase Requests and Receiving

Source: https://wakp.net/en/school-procurement-software/
Last reviewed: 2026-11-15

> School procurement software connects what the school needs with what it buys and what it pays the supplier. In wakp a staff member raises a purchase request that is approved or rejected with a reason, then a purchase order is issued to a supplier, and receiving is recorded per line with accepted and rejected quantities, which creates a stock receipt, a supplier invoice and a ledger entry in one step. Supplier payments then go out of treasuries, and each supplier has a statement that is reconciled with the general ledger.

School procurement software makes buying a clear cycle instead of phone calls and papers: what was requested, who approved it, what actually arrived, and how much the school owes each supplier. It is part of the wakp [school management system](/en/) and connects directly to the school's warehouse and general ledger. This page walks through the cycle as the system works today, and what it does not cover.

## The problem: why school purchasing falters

When purchasing runs without a system, the same problems repeat:

- Verbal or paper requests where nobody knows who approved them.
- An order is issued and nobody knows what arrived and what is late.
- Goods arrive short or damaged with no record of what was rejected and why.
- A supplier invoice is recorded weeks later, so payables are late.
- Nobody knows how much the school owes each supplier right now.
- The warehouse and the accountant work from different numbers for the same goods.

## How the purchasing cycle works in wakp, step by step

### 1. Suppliers

Each supplier has a code, name, contact person, phone, email, tax number, address and notes, and an active or archived status. A **statement** is shown for each, built from posted invoices and payments only, so cancelled documents never enter it.

### 2. The purchase request

A staff member requests items from the warehouse catalogue for a given warehouse, with a quantity and estimated cost per line, a **needed-by date** and a **priority** (low, normal, high, urgent). The request moves through these states:

- **Draft**, still editable.
- **Submitted**, awaiting a decision.
- **Approved** or **rejected** with a written reason.
- **Ordered** once a purchase order is raised from it.
- **Cancelled** with a reason.

A request has no accounting effect: nothing is booked before receiving. The decision is recorded with the name of who made it in the audit log.

### 3. The purchase order

A purchase order is created from an **approved request** (one order per request) and a supplier is chosen. For each line you set the **unit cost**, the **tax rate** and the expense account if the line is a service. The order then moves through **draft**, **issued**, then **partial** or **received**, or **closed** with a reason when the rest will not arrive, or **cancelled** before anything was received, in which case the request returns to approved.

### 4. Receiving: accepted and rejected

When goods arrive, receiving is recorded **per line**: how much was accepted and how much rejected. The system does not allow more than the remaining quantity, and requires a **written reason** for any rejected quantity. Receiving can be partial, and the order stays "partial" until complete. In one transaction the system:

1. Writes a numbered **goods receipt** with the supplier's delivery reference and date.
2. Posts the **accepted quantities of stock-tracked items** into the warehouse through the stock ledger.
3. Builds a **supplier invoice** for the accepted quantities at the order's cost and posts it to the accounts.
4. Updates the order's counters and status.

Nothing is created for rejected quantities. If a receipt is cancelled with a written reason, the warehouse document, the invoice and the entry are all reversed, not deleted.

**[Book a demo meeting](https://my.wakp.net/book?utm_content=article)**

### 5. Supplier invoices

A receipt's invoice is built and posted automatically. **Manual invoices** (for services such as maintenance or cleaning that have no stock) are recorded as a draft and then posted by an authorised user, with each line carrying its description, quantity, cost, tax rate and expense account. Every invoice is posted with an entry that debits inventory or the expense, records the tax, and credits supplier payables.

### 6. Supplier payments and the statement

A payment is recorded from a **treasury** by cash, bank, cheque or transfer, with a reference and notes. The system refuses a payment that exceeds what is owed to the supplier or that the treasury cannot cover. It is posted with an entry that lowers supplier payables and the treasury balance, and can be cancelled with a reason, which reverses the entry. The **supplier statement** shows invoices and payments with a running balance.

### 7. Reports and reconciliation

The procurement overview shows requests awaiting approval, approved requests waiting for an order, orders being received, draft invoices, the total owed to suppliers and the number of active suppliers. There are four procurement reports: **supplier balances**, **open purchase orders** with the remaining value, **purchases by supplier** over a period, and **supplier payables reconciliation** against the general ledger.

## Capabilities at a glance

| Function | What wakp offers |
| --- | --- |
| Suppliers | Supplier details and a statement built from posted documents |
| Purchase request | Items, quantities, estimated cost, priority and needed-by date, approval or rejection with a reason |
| Purchase order | From an approved request, with cost and tax per line, and states from draft to received |
| Receiving | Per line accepted and rejected with a reason, partial or full |
| Inventory | Accepted quantities of stock-tracked items enter a warehouse receipt document |
| Supplier invoice | Automatic from receiving, manual for services |
| Payments | From a treasury by four methods, never above what is owed |
| Cancellation | With a written reason, reversing the entry rather than deleting it |
| Reconciliation | Supplier payables in the ledger against the documents |
| Audit | A record of sensitive decisions with user and time |

## Integration with other modules

- **Inventory:** purchased items come from the catalogue of [inventory and books software](/en/school-inventory-management-system/), and the accepted ones enter a numbered receipt in the warehouse.
- **General ledger:** the supplier invoice and payment are posted to the [general ledger software](/en/school-general-ledger-software/) by posting rules, and supplier payables are reconciled against it.
- **School finance:** payments go out of the treasuries of [school finance and treasuries](/en/school-finance-management-system/).
- **Dashboard:** submitted purchase requests waiting for approval appear, for users allowed to approve them, in the follow-up lists of the [school management dashboard](/en/school-management-dashboard/).

For more: [school management system features](/en/school-management-system-features/).

## Document states: what do they mean?

| Document | States |
| --- | --- |
| Purchase request | Draft, submitted, approved, rejected, ordered, cancelled |
| Purchase order | Draft, issued, partial, received, closed, cancelled |
| Supplier invoice | Draft, posted, cancelled |
| Supplier payment | Posted, cancelled |

The states prevent skipping steps: an order that was not issued cannot be received, an order cannot be cancelled once goods were received against it, and an invoice that is not posted cannot be paid.

## What the software does not do today

- It does not compare quotations from several suppliers or run tenders: an order starts from an approved request and a supplier the school chooses.
- It does not send the purchase order to the supplier: the staff member informs the supplier through the channel the school uses.
- It does not rate or rank suppliers.
- It does not apply pricing or tax rules for the school: the tax rate and unit cost are entered on each line.

## Paper purchasing versus purchasing in wakp

| Aspect | By hand | With wakp |
| --- | --- | --- |
| Stating the need | A message or a sheet | A request with items, quantities and priority |
| Approval | Verbal consent | A recorded decision with the decider's name |
| Following the goods | Calling the supplier | An order with a status and a remainder per line |
| Rejection and shortage | No written trace | A rejected quantity with a written reason |
| Warehouse | Double entry | The receipt document is created automatically |
| Payables | A separate sheet | Invoices, payments and a statement |
| Reconciliation | At year end | A reconciliation report against the ledger |

## An example: buying stationery from request to payment

1. The store keeper raises a purchase request for items from the main warehouse with normal priority and a needed-by date.
2. The administration approves it, and it shows under "approved requests waiting for an order".
3. A purchase order is created for a supplier, each line's cost is set, and the order is issued.
4. The goods arrive short and one item is defective, so receiving records an accepted quantity and a rejected one with a written reason. The order stays "partial".
5. The warehouse receipt document, the supplier invoice for the accepted quantities and its entry are created automatically.
6. The rest arrives later, a second receiving is recorded, and the order becomes "received".
7. Accounting pays the supplier from a treasury and the supplier's balance drops in the statement.

## Who uses the module

The **store keeper, librarian or administration** raise purchase requests, the **administration** approves them and issues orders, the **warehouse keeper** records receiving, and the **accountant** handles service invoices, payments and reports. Permissions are granted separately: view, create, update, archive, approve, reopen, post, export and print, so you can separate who requests from who approves, receives and pays.

## Implementation checklist

1. Prepare the warehouse catalogue with the items you buy.
2. Add current suppliers with their details.
3. Decide who raises requests and who approves them.
4. Decide who receives goods and who posts service invoices.
5. Set the expense account for each type of service you buy.
6. Review the supplier reconciliation report regularly with the accountant.

## How wakp helps

wakp puts every stage of purchasing in a clear state with a clear owner, and turns receiving into a warehouse movement, an invoice and an entry in one step, so the warehouse and the accountant do not work from different numbers. Every cancellation carries a written reason and reverses the entry, so accounts stay consistent and the trail stays written.

## Who it is for

Private, national and international schools in Egypt and Saudi Arabia that buy stock items and operating services, and want to control the cycle from request to payment and tie it to their accounts. Each school applies its own internal rules and its country's official procedures for purchasing and contracting.

## Common mistakes in school purchasing

- **Buying before approval:** approval loses its meaning.
- **Recording receiving as complete without inspection:** record what was rejected and why so the school's right stays documented.
- **Leaving purchase orders open:** close what will not arrive, with a written reason.
- **Entering service invoices late:** posting them on time keeps payables correct.
- **Not reviewing the supplier reconciliation:** it exposes differences before they grow.

## A suggested purchasing routine

1. The approver reviews submitted requests and approves or rejects with a reason.
2. Approved requests become purchase orders and are issued.
3. The warehouse keeper follows orders being received and records what arrives.
4. The accountant posts service invoices and records payments.
5. At month end, supplier balances and the payables reconciliation are reviewed.

**[Book a demo meeting](https://my.wakp.net/book?utm_content=article)**

### What is school procurement software?

A system that runs the school's buying cycle: suppliers, purchase requests, purchase orders, receiving goods, supplier invoices and payments, and ties that to stock and accounts instead of loose papers and spreadsheets.

### What is the purchasing cycle in wakp?

A purchase request (draft, submitted, then approved or rejected), then a purchase order from the approved request (draft, issued, then partial, received or closed), then receiving of the lines, then a supplier invoice, then a payment from a treasury. Every stage has a clear status.

### What happens when a purchase order is received?

For each line you record an accepted and a rejected quantity, with a written reason for the rejected ones. A receipt document is created, accepted quantities of stock-tracked items go into the warehouse, and a supplier invoice for the accepted quantities is created and posted to the accounts. Cancelling a receipt with a reason reverses all of it.

### Can goods be received in batches?

Yes. You can receive part of a quantity now and the rest later, and the order stays partial until it is complete or the administration closes it with a reason because the rest will not arrive.

### Is it linked to inventory and accounts?

Yes. Items come from the warehouse catalogue and enter a receipt document there, the supplier invoice is posted to the general ledger and recorded in supplier payables, and a payment goes out of a treasury and is posted too.
