Skip to the main content

For property, hospitality and construction teams

Purchase approval, from the request to the receipt

Raise a request, have it authorised by the people your own rules name, place the order, and record what arrived — with an audit trail that explains every decision afterwards.

Your team joins by invitation — nobody sets up an account they were not asked to.

Example: a request on its way through its approval chain

PR-0042 · Reception refit

Harbour House

€12,500.00

  1. Project managerApproved
  2. Finance directorWaiting
Within the approved budget62%

Order PO-0107 sent to the supplier

  • Hosted in the EU
  • Append-only audit trail
  • Your rules, without a release
  • English, German and Dutch

From a need to a delivery, in one record

Four steps that used to live in four places — a mail, a spreadsheet, a signed PDF and a delivery note — now follow one request from start to finish.

  1. 1

    Request

    Describe what is needed, compare the options and state the budget it comes from.

  2. 2

    Authorise

    The people your own policy names are asked, in order, and can answer from the mail.

  3. 3

    Order

    The approved option becomes a numbered order, sent to the supplier to acknowledge.

  4. 4

    Receive

    Confirm what arrived on site, with a photo if you like, and the commitment follows.

Built for the way purchasing actually happens

Not a form with a signature box — a record of who decided what, against which budget, and why.

Approval rules are yours, not ours

Levels, thresholds, who signs and in what order are configured per organisation and take effect without a release. A decision keeps the rules it was taken under, so changing a policy never rewrites what somebody has already approved.

Everything is on the record

Every state change is written with who did it, when, through which channel, and what changed — append-only, and readable long afterwards by somebody who was not there.

Decisions are chased, not buried

Each person chooses when they are reminded. A requester can push a decision that is waiting, and escalation makes sure nothing sits unanswered for ever.

The budget, at the moment of decision

Approvers see the budget position beside the request — what is committed, what is forecast and what is left — instead of finding out at month end.

Orders that stay what was sent

An issued order never changes. A change is a numbered revision with its own acknowledgement, so the supplier and you are always reading the same thing.

Your client, on their own project

Invite an external decision-maker to exactly one project. They answer what is asked of them and see nothing else of yours.

Kept in the EU

Database, documents, mail and processing stay on European infrastructure, and each organisation's data is isolated from every other's by the database itself rather than by a query somebody remembered to write.

  • Each organisation's data is separated by the database itself.
  • Links in a mail are signed, single-use and short-lived.
  • A person can be erased without breaking the record of what they approved.
  • Mail and documents can be hosted on your own European servers.

Bring your next purchase through it

Set up your organisation, write your approval rules and invite your team. Everyone else joins by the link they are sent.