Verdana Procurement · purchase orders

Purchase order software that checks the supplier before the order is issued

Verdana's purchase orders module issues and manages every order linked to the supplier's record, checking its clearance before issue and tracking the cycle that follows through to closing. Your company stops committing to suppliers whose insurance has lapsed and stops planning around delivery dates nobody confirmed.

No order goes out unless the supplier is cleared.

What supplier-linked purchase orders save your company

Commitments only with cleared suppliers, clear approvals, and confirmed dates.

  • Supplier status counts at commitment

    Supplier clearance is checked before issue: a contractor with lapsed coverage does not get the order.

  • Each team approves its own share

    Approvals follow amount, team and cost center; when an order spans teams, each one approves its part.

  • Confirmed dates, not assumptions

    The supplier confirms the order and its committed delivery date in the portal, and every date change comes with a reason.

What a purchase order looks like

An abstraction of the order with its checks and of what the supplier sees.

Purchase order: supplier checked, approvals by team, and follow-up through closing.Supplier portal: the supplier sees its orders, confirms them and updates the date.

How a purchase order works in Verdana

From the supplier check to closing, with no email chains.

  1. Supplier check

    Before issue, the supplier's clearance is checked on its record: with lapsed coverage, the order does not go out.

    What is a third-party record →
  2. Approval by amount, team and cost center

    The order is approved under your rules; when it spans teams, each one approves its own share.

    Budgets and cost centers →
  3. Sent to the portal

    The supplier receives the order in its portal and accepts it right there, with no attached spreadsheets.

    Supplier portal →
  4. Committed delivery date

    The supplier confirms the delivery date and updates it with a reason when it changes.

    Expediting →
  5. Receipts and closing

    Deliveries are recorded in full or in part, the open balance stays under follow-up, and the order closes.

    Goods receipt →

Purchase orders in depth

The process in detail, and why it is designed this way.

A purchase order formalizes the commitment with a third party, and that is the moment when the third party's status should matter. In most organizations it does not: the order is issued from the ERP against a supplier in the master file, without anyone knowing that its insurance policy has expired or that it has an open compliance finding.

Verdana issues and manages purchase orders linked to the supplier's file, with prior validation of its clearance, and with tracking of the cycle that follows: supplier confirmation, committed delivery date, updates to that date with a reason, partial receipts and closing. The supplier sees its orders in the portal and confirms or updates them right there, without email chains with attached spreadsheets.

Actively tracking committed delivery dates is what makes downstream planning reliable. An unconfirmed original date is not information: it is an assumption, and maintenance and construction work get scheduled on assumptions until someone replaces them with confirmations.

Clearance before the orderInput: Linked to the supplier's file. Rule: Prior validation, The third party's clearance status at the moment of issuing. Cleared supplier: It is issued; the supplier confirms from their portal. Date changes: It is updated with a reason and the rescheduling history is kept. Expired policy or finding: It is not issued until resolved, even if the ERP would allow it. An unconfirmed original date is not information: it is an assumption, and downstream planning is built on it.CLEARANCE BEFORE THE ORDERPurchase orderLinked to thesupplier's filePrior validationThird party's clearance statusat the moment of issuingCleared supplierIt is issued; the supplier confirmsfrom their portal.Date changesUpdated with a reason, keepingthe rescheduling history.Expired policy or findingNot issued until resolved,even if the ERP would allow it.An unconfirmed original date is not informationit is an assumption, and downstream planning is built on it.
In most organizations the order is issued from the ERP without anyone knowing the supplier's insurance policy has expired.

Frequently asked questions

What teams usually ask when they evaluate purchase order software.

How do you stop purchase orders going to non-compliant suppliers?

By checking supplier clearance at issue, not afterward. In Verdana the order is linked to the supplier's record, and a contractor with lapsed coverage does not get the order.

How does a supplier confirm a purchase order?

From its portal: it sees its orders, accepts them, and confirms or updates the committed delivery date with a reason, with no email chains or attached spreadsheets.

How do you approve a purchase order that spans several departments?

With approvals by amount, team and cost center: when the order spans teams, each one approves the part that belongs to it.

Why track the committed delivery date on a purchase order?

Because downstream planning depends on it. An unconfirmed original date is an assumption, and maintenance and construction work get scheduled on it until someone replaces it with a confirmation.

Related concepts