Skip to content

Procurement and finance

Purchasing approvals with every level and exception

Your approval rules have grown out of your organisation, your compliance requirements and many individual decisions. An ERP system rarely captures them completely, so the route to the purchase order is often manual. With nexxcite it becomes a managed process: on your rules, fully documented and connected to your system of record.

  • Multi-level approval by amount
  • Connected to your system of record
  • Deadlines with reminders
  • Change thresholds yourself, no consultant needed

What matters

Your approval rules are knowledge your organisation holds

One rule Recorded in one place Amount, category, cost centre and capex are set out completely and readably in one place.
Changed in-house New thresholds If the limit rises from €1,000 to €2,500, you change the value in a draft and approve it.
No rekeying The ERP stays in charge Once approved, the order goes to your system of record through its interface.
Complete records Without extra effort A query shows who approved what under which rule. There's no need to search through inboxes.

Today and tomorrow

From approval by email to a documented approval process

Today

Half in the system, half in people's heads

Simple cases go through the tool, exceptions go by email. After a while nobody knows all the rules any more, and that shows in the audit.

  • Requisitions as PDFs in the department head's inbox
  • Only purchasing knows who has to approve next
  • Supplier certificates expire unnoticed
  • Invoices without a matching order pile up
  • Notice periods in one person's calendar
With nexxcite

One rule for every case

Every requisition goes through the same complete approval rules, and every approval happens in the system.

  • Approval level from amount, category and cost centre
  • Reminders and escalation in working hours
  • Certificates with expiry dates and follow-up
  • Mismatches are followed up and resolved
  • Contract deadlines with staged reminders

Typical processes

The processes before and alongside the ERP

Purchase orders, goods receipt and accounting stay in your system of record. nexxcite takes over the steps that run on email, spreadsheets and phone calls today.

Purchase requisition with approval process

From need to purchase order: capture line items, budget and justification, have AI suggest category and cost centre if you wish, approval levels by amount, category and cost centre, and finally hand-off to the system of record. Requesters track the status themselves, without having to ask purchasing.

  • Line items
  • Suggestion by AI
  • Multi-level approval
  • ERP hand-off
  • Status tracking

Supplier onboarding

Self-disclosure through a portal, document checks, approval by purchasing, quality and compliance, recurring evaluation.

  • Portal
  • Certificates
  • Evaluation

Invoice checking

Matching order, delivery and invoice, including the cases where something doesn't add up.

  • Mailbox
  • Four eyes

Contract deadlines

Terms, notice and renewal periods with staged reminders. Here, a missed deadline costs money directly.

  • Notice period
  • Amendments

Capital expenditure approval

Capex requests with justification and business case, approved all the way up to the executive board.

Budgets per cost centre

Views on the same data show what has been ordered, what has been approved and what is still open. No separately maintained list is needed.

Low code in practice

From request to order in the ERP system

A process almost every company knows: the purchase requisition with amount-based approval. Every step is set up in the editor without programming, and you can change it yourself later.

Purchase requisition with approval 1 / 6
  1. Submit request Form with validation Start
  2. Suggest commodity group AI support in the form AI
  3. Determine approval level Rule on the amount
  4. Request approval Task, reminder, escalation Deadlines
  5. Hand over order Call to the ERP interface
  6. Provide reporting Portal view and dashboard
  1. 01

    The request is captured

    A form you design yourself: required fields, picklists from your master data, attachments. Which fields someone sees depends on their role.

  2. 02

    The assistant makes suggestions

    From the description, AI suggests the commodity group and cost centre. The requester confirms or corrects. The entries become more accurate without anyone needing training.

  3. 03

    The amount sets the approval level

    Team leads approve up to €1,000, heads of department above that, and from €10,000 procurement as well. You can change these thresholds yourself later in the editor.

  4. 04

    Approval is requested

    The approver gets a task and an email. If nothing happens, the platform sends reminders and escalates according to your rule. Deadlines are counted in working hours.

  5. 05

    The order goes to the ERP system

    Once approved, the platform creates the order in the ERP system through its interface, using the values from the request. Nobody has to retype anything, and both systems show the same status.

  6. 06

    Status is always visible

    Requesters see their case in the portal, procurement sees its analysis in the dashboard. Both are views of the same data, so nobody has to keep a separate list.

This is how a process like this takes shape in the editor.

You make later adjustments yourself in the editor.

In depth · approval level

Why the approval level matters

  1. 01

    Rules that don't fit into a single field

    Up to €1,000, the team lead approves. Above that, the head of department. From €10,000, purchasing as well. IT purchases always need the head of IT, whatever the amount. Capital expenditure needs the executive board. And if the approver is also the requester, it goes one level up.

    • Amount
    • Category
    • Capex
    • Own request
  2. 02

    The usual way: half in the system, half in heads

    Simple cases go through the tool, exceptions by email. After a while nobody knows all the rules in full, and that shows when the audit comes.

  3. 03

    With nexxcite: one rule for every case

    The approval level is a rule that takes account of the amount, category, cost centre, capex flag and the requester. It sits in one place and is readable. You change the thresholds yourself, without waiting for a new software version.

    • Readable
    • Changed in-house
    • No consultant needed
  4. 04

    The result: records are created automatically

    Because every approval happens in the system, “Who approved this, and under which rule?” is a query rather than a search through inboxes.

AI in procurement

Purchasing maintains its own rules, with AI to help if wanted

When making changes: from now on, every order over €25,000 is also to be approved by the executive board. Purchasing makes this change in the editor. If you wish, the assistant takes over the implementation from a short description and updates the rule, workflow, role and notification as a draft. Requests already in progress are unaffected, and the change takes effect only once you approve it.

Day to day: from a requisition's description, AI suggests the category and cost centre, and the requester confirms or corrects them. The team lead can ask: “Which open requisitions over €5,000 are still waiting for my approval?” The answer comes back as a sorted list, compiled with her permissions.

Because suitable values are already suggested, data quality improves without the need for dedicated training.

  • Rule changes from a description, in a draft and reversible
  • Category and cost centre as suggestions
  • Pending approvals analysed in plain language
  • Summaries of long clarification threads
  • Within the permissions of the person asking
  • Your own access keys, no separate AI licence

In depth · invoice checking

When the invoice doesn't match the order

The normal case is done quickly. What matters is what happens to the exceptions.

  1. 01

    The invoice lands in the mailbox

    A monitored mailbox receives invoices and opens a case for each one, with attachment, sender and date received.

    • Monitored mailbox
  2. 02

    Matched to the order

    The case is matched to the purchase order, partially if need be. If quantity and amount fit, it goes straight to approval.

  3. 03

    Mismatches are clarified

    If something doesn't match, the case goes to whoever placed the order with a specific question and comes back with their answer. Nothing sits unnoticed.

    • Query
    • Deadline
    • Escalation
  4. 04

    Four-eyes approval

    Two independent approvals, recorded with time and person. Then the invoice goes to accounting.

    • Four eyes
    • Hand-off to accounting

Your own workspace

Procurement gets an application of its own

On nexxcite, procurement is a workspace of its own: navigation built around requisitions, suppliers, contracts and budgets, a home page with everything waiting for your approval, its own colour scheme and a procurement assistant that knows only procurement data.

Access rules reach down to the individual record: each department sees only the requisitions for its own cost centre, division heads see their division, purchasing sees everything.

Suppliers get access with an interface of their own, where they see only their own self-disclosure and their own certificates.

  • Read and edit limits per cost centre
  • Field permissions, e.g. for pricing terms
  • Its own navigation, home page and colour scheme
  • A procurement assistant with its own tools
  • Supplier access with its own role
  • HR and IT data invisible to procurement

Integration

Your ERP stays in charge, and nexxcite supplies it

ERP system

Approved requisitions become purchase orders in your system of record, with the values from the request.

  • Secured interface
  • Calls to other systems
  • Common data formats

Invoice intake

Invoices and supplier mail from monitored mailboxes, notifications to everyone involved.

  • Exchange Online
  • IMAP and SMTP

Master data

Cost centres, categories and suppliers from your system of record, synchronised on a schedule.

  • Excel and CSV
  • Schedules
  • Monitored background tasks

Objections

What procurement and finance want to know up front

Our ERP already has an approval workflow. Why nexxcite?

For everything that doesn't fit into it: rules with many exceptions, requesters without ERP access, clarification cases, supplier certificates, contract deadlines. The ERP stays in charge. nexxcite makes sure that what arrives there is complete and approved.

Does nexxcite replace our ERP or accounting?

No. Purchase orders, goods receipt and accounting stay in your system of record. nexxcite creates no ledger entries and no balance sheet. Nor does it replace a large-scale procurement portal with electronic supplier catalogues. nexxcite takes over the steps before and alongside: from requisition to approval, the clarification cases and the deadlines, in other words everything that runs on email today.

Who changes the thresholds when the policy changes?

You do. The approval level is a readable rule. A new threshold is changed in a draft, reviewed and approved, with no new software version and no consultant. Requests already in progress are unaffected.

Does every requester need a licence?

No. You license the platform and the number of users signed in at the same time, not every person who occasionally raises a requisition.

How does data get into the ERP?

Through its interface: once approved, the platform calls your system of record and passes on the values from the request. If the hand-off fails, this is shown on the case.

Can suppliers maintain their own data?

Yes, through their own access with their own role. They see only their own self-disclosure and certificates. Internal evaluations and notes don't exist for that access.

Will it stand up to an audit?

Every approval happens in the system and is recorded on the case with time, person and rule. How that fits your audit and retention requirements is something we're happy to work through on your specific case.

Live demo

We'll rebuild your approval rule in the demo

The more exceptions your rule has, the further apart your current system and actual practice are. Bring your rule along. We'll build it in the demo, exceptions included.

  • Your approval rule, not a sample
  • Built live, in the editor or with AI
  • Remote or on site