Project

£15/mo +VAT · included from Core

Purchase orders with real delegated authority

Numbered POs against a job and a supplier or subcontractor, routed for approval against limits you set per role. Deliveries get booked in line by line, with the date and who took them. When the supplier’s invoice arrives, each line is checked against the order and against what was delivered before anybody approves it for payment. Where the order is a subcontractor payment, it holds the CIS rate and the deduction. Every authorisation gets written to an event log nobody can edit afterwards, which is the bit an auditor cares about. Included from Core up.

A purchase order to a merchant with line items priced against the job
A purchase order to a merchant with line items priced against the job

What the Purchase Orders module does

  • Numbers each PO and attaches it to a job, a supplier and, where it applies, a subcontractor.
  • Prices lines with description, quantity, unit, unit price, total and category, and records quantity received and a received timestamp per line.
  • Keeps every delivery booked in as its own record: what came on each line, the day it arrived, who took it, a note and a photo of the signed ticket.
  • Books deliveries in from the iPhone and Android apps with no signal, the ticket photo following its delivery when the phone is back in range.
  • Records the supplier’s invoice with its lines, VAT and the PDF, against one order, several, or none, and can read the PDF into the form for you to check before saving.
  • Matches each invoice line three ways, against the order’s price and against what was delivered, and says which of four things it found: matched, price differs, more invoiced than received, or not on the order.
  • Lets you set a matching tolerance as a percentage and an amount. A difference inside both still counts as matched.
  • Approves a matched invoice for payment with the purchase approval permission and the approver’s own limit. One that does not match needs a written reason, kept with the approval.
  • Puts an approved invoice on the job as actual cost and takes it off the order’s committed cost, so the cost report never counts the same money twice.
  • Shows each order’s deliveries and supplier invoices in both phone apps, where an invoice can be queried, approved with a reason, or marked paid.
  • Runs through eight statuses including pending approval, approved, rejected, sent, partially received and received.
  • Two separate limits per role: how much that role can commit on its own signature, and how much it can authorise on somebody else’s.
  • Either limit can be overridden for one person, so the site manager you trust with a big order gets it without everybody on their role getting it too.
  • Ships with conservative defaults and lets you replace them: a field worker can commit £500, an office member £1,000, a manager £10,000 and an admin £25,000, and only an owner is unlimited out of the box.
  • Judges the order on its VAT-inclusive total, which is the number that actually leaves the bank.
  • Writes an approval event for every action that nobody can go back and change: who, what role, the order total, the limit applied, and a note.
  • Flags a PO as a CIS payment and holds the deduction rate and amount on the order.
  • Carries Xero and QuickBooks bill references, so a pushed bill can be traced back.

Purchase Orders: how it works

How do purchase order approval limits work?

Two powers per role, because they aren’t the same thing. A raise limit is what somebody can commit on their own signature. An approve limit is what they can sign off for somebody else. Go over your raise limit and the order can’t be issued until somebody with the authority approves it.

RoleRaise on own signatureApprove for someone else
OwnerUnlimitedUnlimited
Admin£25,000Unlimited
Manager£10,000£25,000
Office member£1,000None
Field worker£500None
ViewerNoneNone
  • Those are the starting figures. Set your own per role, and override either one for a single person.
  • Left blank on a role, the limit is unlimited. Left blank on a person, they keep whatever their role allows.
  • The test runs on the VAT-inclusive total of the order.
  • A PO carries its own approval-required flag and threshold.
  • Submission, approval and rejection each record a user, a timestamp and, on rejection, a reason.

NoteThe defaults are pitched low on purpose. A limit set too low costs somebody an approval request; one set too high costs money.

Why keep a separate purchase order approval log?

Because the order only tells you where it ended up. When somebody asks who released a £500,000 order, and under what limit, the current status is no help at all. Each authorisation is written as its own record, unchangeable, carrying the person, their role, the order total at that moment and the limit applied.

How are purchase order deliveries received?

Line by line. Each delivery is booked in with what arrived on each line, the day it came, who took it, a note and a photo of the signed ticket. The order keeps a running total per line, which turns partial receipt into a real status instead of a note in a comments box. A part-delivered order sits at "partially received" until the rest turns up.

  • On the iPhone and Android apps, Record a delivery opens each line at what is still to come, so a complete delivery is one press.
  • It works with no signal. The delivery and its photo are sent when the phone is back in range, and the order shows them as waiting until then.
  • A delivery sent twice from a phone on one bar of signal is booked in once.

How does invoice matching work?

Each line of the supplier’s invoice is checked against the order line it bills and against what has been booked in. The price is compared with what the order’s price gives for the quantity invoiced. The quantity, together with anything already approved on another invoice for that line, has to be no more than has arrived. That last part is what catches the same delivery invoiced twice.

  • Matched: on the order, at the order’s price within your tolerance, and no more than has arrived.
  • Price differs: the amount is further from the order’s price than your tolerance allows, higher or lower.
  • More invoiced than received: the goods have not all been booked in yet. Book in the rest and match again.
  • Not on the order: a delivery charge, a substitute, or something nobody ordered.

NoteEstimark records that an invoice was paid. It does not pay suppliers, and an approved supplier invoice is not sent to your accounts package.

A supplier invoice in query, each line matched against its purchase order and what was booked in: the studwork billed in full when only part has arrived, and the sheet priced above the order, with the box for the reason it should be paid anyway.
A supplier invoice in query, each line matched against its purchase order and what was booked in: the studwork billed in full when only part has arrived, and the sheet priced above the order, with the box for the reason it should be paid anyway.

Can supplier invoices be approved from a phone?

Yes. In the iPhone and Android apps, supplier invoices are under Browse, then Money, and each purchase order lists its own. An invoice shows each line’s match in words with the figures it was judged on, and the supplier’s PDF.

  • Approve a matched invoice, or write why one that does not match should be paid anyway.
  • Put it in query, match it again, mark it paid, or reopen it with a reason.
  • Where your approval limit is below the invoice, or a cost for the same order was typed into the job by hand, the app says so where the button would be.
  • A decision made with no signal is sent when the phone is back in range.

NoteA new supplier invoice is recorded on the web, where the PDF is. The phones read, query and approve them.

How do purchase orders and CIS interact?

Flag the PO as a CIS payment and it carries the deduction rate and the amount. With the CIS module on, that deduction feeds the monthly return, so the commitment and the tax treatment sit on one record instead of two.

Purchase Orders: at a glance

Plan
Included from Core
Add-on price
£15/month +VAT
Statuses
8
Authority
Raise + approve limits
Bundled module

Purchase Orders

£15per month +VAT

Purchase Orders is a bundled module. Plans are a ladder, so it comes with Core and with Pro, Enterprise. On a lower plan you can switch it on by itself for £15 a month.

Included from Core, £129 a month

  • Included on Core and above at no extra cost.
  • £15 per month as an individual module on a lower plan, excluding VAT.
  • Included in full during the 14-day free trial.
  • No implementation fee and no minimum term.

Every module and price →

Questions

Purchase Orders: frequently asked

Which plan includes purchase orders?

It’s included from Core up. On a lower plan it’s £15 a month +VAT on its own. Deliveries come with it either way.

Can I stop someone raising a PO above a certain value?

Yes. Set a raise limit and a separate approve limit against the role, then override either of them for one person if that individual needs a different ceiling. Out of the box a field worker can commit £500 and a manager £10,000. Every approval action goes into an event log that can’t be edited, along with the limit that applied at the time.

Can I pay a supplier invoice that does not match the order?

Yes, with a reason. Somebody with the purchase approval permission, inside their own approval limit, writes down why it should be paid anyway, and that reason is kept with the approval alongside their name and the tolerance in force at the time.

Can I approve a supplier invoice on my phone?

Yes, in the iPhone and Android apps. Each line shows whether it matched, the price differs, more was invoiced than received, or it is not on the order. Approve it, with a written reason if it does not match, inside your own approval limit, and the decision is sent when the phone has a signal.

Do purchase orders push to Xero or QuickBooks?

A PO holds bill reference fields for Xero and QuickBooks, so a pushed bill can be traced back to the order it came from. Estimark doesn’t post journals to any accounting package.

Build on a solid foundation.

Run the whole business without an implementation project and without legacy baggage. Every plan starts with 14 days free. No card needed.

Estimating · Jobs · Invoicing · CIS · H&S · Reactive maintenance