Sign in Start free trial
Operations

Procurement

Buy under policy: requests, approvals, orders, receipts and suppliers on one record.

Procurement takes a request from anyone in the business, checks the budget and the contract, turns it into a purchase order that goes through approval, and records what was received. Suppliers register in a portal and are screened before they can be used, and spend is reported by supplier, category and cost centre.

60 features available 3 planned 8 capability areas
Highlights

What stands out

Guided buying

Requesters shop the catalogue or describe a need, with coding and budget shown before they submit.

Approvals that follow policy

Approval follows amount and category, and no one approves their own request or order.

Contracts and maverick spend

Orders are checked against contract prices and off-contract spend is flagged before it is bought.

Supplier onboarding and portal

Suppliers fill in their own details, are screened and approved by another person, and bank details go through four-eyes control.

Receipts that feed the match

What is received feeds Payables and stock once, so bills match what was ordered and received.

Capabilities

Every feature, in one list

Search or filter. Planned items are labelled; everything else is available now.

Requisitions and guided buying

Anyone can ask to buy something by shopping the catalogue or describing the need, with coding and budget shown before they submit.

8 features
  • Shop the catalogueAdd catalogue items to a request; each line takes its price, supplier and category from the item.
  • Free-text requestsDescribe what is needed and the price you expect to pay when the item is not in the catalogue; a buyer can correct the price on the order.
  • Draft a request from an email or a sentencePaste an email, a quote or a sentence and  AI prepares the lines for you to check and submit.
  • Coding filled in for youGL account, cost centre and project default from the item, its category and what the requester used last, and can be changed.
  • Budget check at submitThe company chooses whether a request that goes over budget only warns or is stopped, or whether the check is off.
  • Maverick and contract-price flagsA line that is off catalogue and off contract above the company's floor, or priced above a contract, is flagged to the approver.
  • Submit, take back and correctA submitted request does not change; the requester takes it back to correct it, or cancels it, and sees where it stands.
  • Approval that is never your ownThe requester can never approve their own request; the route follows amount band and category.

Catalogue and categories

The items people can buy, with prices, suppliers and the spend categories that decide default coding.

7 features
  • Catalogue itemsItems carry a sku, name, price, currency, supplier and category and can be added by hand.
  • Supplier catalogue importImport a supplier's catalogue from a CSV file; a re-import of the same sku updates the price and counts the changes.
  • Control totals on every importA file whose row count or price total does not match what the sender stated is refused before anything is written.
  • Hide, never deleteA retired item is hidden so earlier requests and orders keep what they bought.
  • Spend categories with default GL accountChange the default account of a category once and new lines follow.
  • Items from the CPQ product listPlannedProducts marked as purchasable in CPQ would arrive in the catalogue through the same feed; CPQ has no purchasable flag yet. This is planned and not yet available.
  • Punch-out to supplier shopsPlannedShopping in a supplier's own site and bringing the cart back is in the design and not built. This is planned and not yet available.

Purchase orders and change orders

Orders are raised for active suppliers, approved, issued and changed under control, with every version kept.

11 features
  • Orders from approved requestsTurn approved requisitions into draft orders, one per supplier, or open an order for a supplier and add lines.
  • Contract and maverick points on the orderThe buyer sees contract price and maverick points before sending the order for approval.
  • Approval on the authority matrixOrders are approved on the shared authority matrix by amount and category; the approver is never the buyer or the requester.
  • Issue and send to the supplierAn approved order is issued and the supplier is emailed; outside production the email is held, not sent.
  • Supplier acknowledgementThe supplier is asked to acknowledge an order or a change, and the order shows whether it did.
  • Versioned change ordersA change to an issued order is approved like the order and becomes the next version; an issued version never changes.
  • Quantity never below what was receivedA change order cannot reduce a line below what has already been received.
  • Withdraw, close or cancelAn order or change that is not yet issued can be withdrawn; an order can be closed or cancelled with the reason on record.
  • Order handed to Payables for matchingWhen an order is issued, Payables keeps the issued version as the snapshot the bill is matched against.
  • Drop-ship orders from WarehouseA drop-ship line in an order creates one draft purchase order here, raised by a buyer, with approval above a company value.
  • Supplier contract call-off guardAn order under an executed supplier frame agreement is checked against its cap, validity and prices at submit and at issue, with an override path.

Receiving and returns

Record what arrived or was done against an order, in parts, and what went back.

7 features
  • Goods receipts in partsEnter the quantity that arrived per line, with everything still open as the default; partial receipts add up.
  • Service receiptsConfirm a service was performed against an order line, so services follow the same match as goods.
  • Returns to the supplierA damaged or wrong delivery is returned with the lines and reason; Payables lowers what was received.
  • Limits that protect the booksYou cannot receive more than was ordered or return more than was received.
  • Documents that never changeEach receipt and return is a document; a mistake is corrected by another document.
  • Payables answer shown on the receiptThe receipt shows whether Payables booked it, and why not.
  • Stock books onceA receipt of a stocked item also books stock in Warehouse, and a repeat of the same receipt books nothing again.

Suppliers and the supplier portal

Suppliers register themselves, are screened and approved by another person, and then see only their own business with you.

10 features
  • Invite by emailA supplier gets a sign-in link to your portal and completes its own profile, tax ids and documents.
  • Document reviewEach document is accepted or rejected, and the company chooses which documents are required before approval.
  • Sanctions and PEP screeningScreening runs through a provider port; a hit waits for a person to review it and a confirmed hit blocks the supplier.
  • Approval by a second personOnly another person can approve; the supplier becomes active and orders can be raised for it.
  • Payables vendor created on approvalApproval creates the vendor in Payables so bills can be matched and paid.
  • Bank details through four eyesA supplier's bank details go straight to Payables' bank-change control (call-back, second person, hold window) and are not kept here.
  • Portal for orders, invoices and paymentsIn the portal a supplier sees only its own profile, orders, invoices and payment status and can acknowledge an order.
  • Which supplier for this?Ask which supplier to use for an item; the answer comes from past orders, the catalogue and contracts.
  • Block a supplierA supplier can be blocked so no new orders can be raised for it.
  • Live sanctions and PEP providerPlannedScreening runs against a stand-in adapter today; connecting a live provider needs a provider account the company must supply. This is planned and not yet available.

Contracts and price compliance

Agreed prices and caps are recorded and orders are checked against them.

7 features
  • Supplier contracts with pricesRecord validity, cap, payment terms and an agreed price per sku.
  • Contract picked up automaticallyA supplier's one active contract is applied to its orders, and a price above it is flagged.
  • Tolerance and block or warnThe tolerance above the contract price and whether a breach only warns or blocks are company settings.
  • Expired contract flagsLines under a contract past its end date are flagged.
  • Contracts from the contract hubWhen a contract is executed in the contract hub, its record with that reference becomes active for the executed dates.
  • Frame agreementsThe contract hub creates the frame in Procurement for a supplier agreement; restricted contracts show buyers only that a frame exists.
  • Contract coverageSpend reports count lines that are on a contract or a catalogue item.

Spend and budgets

See where the money goes and what is left, with maverick spend and contract coverage in view.

6 features
  • Spend by supplier, category, cost centre, project and monthOne set of figures feeds the reports, dashboards and  AI.
  • Maverick spendValue bought off catalogue and off contract above the tail-spend floor, by supplier and category.
  • Price against contractValue on lines priced above the contract, by supplier.
  • Budget against commitmentsRequests and orders are checked against what is left after approved requests and open orders; budgets are read from Planning or imported from a CSV file.
  • Requisition and order pipelines
  • Receiving and onboarding reportsValue received and returned and whether Payables booked it; suppliers by status and screening result.

Policy, decisions and  AI

Every procurement policy is a company setting with a safe default, and  AI prepares work that people decide.

7 features
  • Policy settings with safe defaultsBudget check, maverick rule, contract tolerance, change approval, acknowledgement, screening and required documents are settings.
  • Standard approval routes in one stepInstall the standard routes once, then edit them in Workflow.
  • Decisions in WorkflowRequisitions, orders, change orders and suppliers go to the approval route; with no policy a person who is neither requester nor buyer decides.
  •  AI actionsAbout 50 prepare-only actions across requests, catalogue, orders, receipts, suppliers, contracts and spend; approving and issuing stay with people.
  • Report pack and three dashboardsTwelve ready-made reports and dashboards for the buyer, the procurement head and finance.
  • Public API and eventsRequisitions, orders, receipts and suppliers are available through the /v1 API with change events.
  • Phone screensRequests, approvals and receiving have phone routes.
Assistant

What  AI prepares here

It prepares the work. A person confirms it.

  • Draft a requisition from an email, a quote or a sentence
  • Find catalogue items and suggest coding
  • Raise draft purchase orders from approved requisitions
  • Ask for a change order on an issued order
  • Record a receipt or a return
  • Screen a supplier and list what is missing
  • Suggest which supplier to use from past orders and contracts
  • Answer questions on spend, maverick spend and contract expiry
  • All of these are prepared for a person to confirm; approving, issuing and sending orders stay with people.
Inside every hub

Workflow, reporting, integration, migration

The same four building blocks, specific to Procurement.

Workflow

Requisitions, orders, change orders and new suppliers follow the approval routes the company sets on the shared authority matrix.

  • A requisition above the band goes to the budget owner and then to finance
  • A change order that raises the price is approved by someone other than the buyer
  • A new supplier is approved by a second person after screening and document review
  • An order above a company value needs a second approval step

Reporting and analytics

Spend and purchasing reports by supplier, category, cost centre, project and month, with three persona dashboards.

Datasets

SpendRequisitionsPurchase ordersReceivingSuppliers

Dashboards

Buyer workbenchProcurement headProcurement finance

Integration

Procurement publishes resources and events; Payables, Warehouse and the contract hub link to it by events and ports.

/v1 resources: requisitions, purchase orders, receipts, suppliers

Events

purchase order issuedreceipt recordedrequisition changedorder changedsupplier changed

Connectors

Supplier portalContract hub (frame agreements and call-off checks)Payables (order snapshot, receipts, vendor creation)Warehouse (receiving, drop-ship, reorder requisitions)

Migration

Supplier records can come in through the finance packs of a legacy ERP. Open purchase orders and procurement-suite packs are not built yet.

  • SAP family ERP finance packs (vendors as suppliers)available
  • Oracle family ERP finance packs (vendors as suppliers)available
  • NetSuite, Microsoft Dynamics and Sage finance packs (vendors as suppliers)planned
  • Open purchase orders from any ERPplanned
  • SAP Ariba, Coupa, Jaggaer, Ivalua, GEP, Zip, Tradeshift, Basware, Tipalti and Bill.com packsplanned
Mobile

On the phone

Requests, approvals and receiving have phone routes today. A native app is planned.

Who uses it

RequesterBuyerBudget ownerProcurement headControllerAccounts payable clerkWarehouse receiverSupplier (portal)Auditor

Industries

  • Distribution and manufacturing companies that buy stocked goods against orders
  • Services firms that buy by cost centre and project
Questions

Frequently asked

Can someone buy without approval?

Only as far as the company's policy allows. Requests follow an approval route by amount and category, and maverick lines are flagged to the approver.

How do suppliers join?

They are invited by email, complete their own profile and documents in the portal, are screened, and are approved by a second person before orders can be raised.

What if an order changes after it is issued?

A change order is approved the same way and becomes the next version. The supplier is asked to acknowledge it and a line cannot go below what was received.

Are contract prices enforced?

Orders under a contract are checked against its prices and cap. The company decides whether a breach warns or blocks.

Where do supplier bank details live?

They go to Payables' bank-change control with a call-back and a second person. Procurement does not keep them.

Can  AI place an order?

No. It drafts requests and orders and prepares changes. Approving, issuing and sending stay with people.

Is there punch-out or sourcing with bids?

Not yet. Both are in the design and not built.

See Procurement on  AI

Talk to us