Product · Procure-to-Pay

Procure-to-pay software for global enterprises

An invoice is only paid once it has been checked against the order, the receipt and the rules you set.

Procure-to-pay software takes the invoice however it arrives, matches it against the purchase order and the goods or service receipt, and approves it only when eight disclosed conditions all pass. Anything that fails goes to a person with the reason attached.

Invoice INV-40912 received Illustrative
Supplier
Kestrel Drives Pvt Ltd
Against order
PO-118322
Channel
Supplier portal · PO flip
Lines
4 · tax captured per line
Arrived against the order it belongs toThe supplier flipped their own purchase order — nobody re-keyed itMatched
System updatedPortal and PO flip are live for every organisation
Match engine · seven checks Illustrative
Header reconciliation
Supplier, order, totals agree
Tax validation
HSN, rate, components · IRN present
Duplicate detection
No prior invoice on this order
Service receipt gate
Not a service line — does not apply
Quantity against receipt
120 invoiced · 120 received
Price against order
Within tolerance
Price against contract
Matches SA-4471
Result
Seven of seven
Rule appliedRuns on every invoice automatically, before anyone sees it
Service invoice INV-40918 · gate held Illustrative
Approved service entry sheetNone found for this milestone — the invoice cannot clear the checkBlocking
Invoiced quantity1 milestone · the confirmed quantity has to cover itWaiting
OverrideProcurement manager only · justification note required, written to the audit trailLogged
Human decisionOn by default for every organisation — a person confirms the work first
Approval decision · INV-40912 Illustrative
Under your threshold
Pass
Inside the order total
Pass
Goods receipt exists
Pass
Receipts quality-approved
Pass
No contract variance
Pass
Not a duplicate
Pass
No tax mismatch
Pass
Exchange rate present
Pass
Rule appliedEight of eight — approved with no human click. One failure sends it to a person, named.
Payment term and run · INV-40912 Illustrative
Term source used
Order’s frozen term
Contract, supplier, default
Not needed — a more specific term existed
Statutory cap
MSME · 45 days wins
Payment run
Next run that beats the due date
Run executionWaits for a person, with a shared payment referenceHuman
Human decisionNothing marks a payment run as paid on its own

However the supplier sends it, it lands against the order it belongs to.

Same invoice. Two different months.

Accounts payable work is mostly checking. The question is whether a person has to do it.

The problem
With Proconomy
The problemSomeone re-keys the invoice against a purchase order sitting in another system
With ProconomyIt arrives matched against the order, whichever channel the supplier used
The problemA site or warehouse is emailed to confirm the goods or the work actually arrived
With ProconomyThe receipt is already on the order, and a service invoice cannot pass the gate without a confirmed service entry sheet
The problemTax fields and payment terms are read and typed by hand
With ProconomyTax is structured data the engine validates, and the due date comes from the order, the contract or the supplier record
The problemA statutory payment deadline is missed because nobody tracks it centrally
With ProconomyA statutory cap overrides any longer term that was agreed, and a dashboard counts down to it
The problemA duplicate surfaces when the supplier calls about a doubled payment
With ProconomyA likely duplicate is flagged before the invoice can reach a payment run

How it works

From an approved order to a scheduled payment.

Nine stages. Five of them need nobody. The one that moves money always needs a person.

  1. 01 System

    The order reaches the supplier

    The moment an order is approved it is turned into a PDF and emailed to the supplier. This is on by default for every organisation, and a manual send is available for those that switch it off.

  2. 02 Human

    The goods or the work arrive

    A receiving clerk records the goods receipt, or a service owner approves a service entry sheet. Receipts can be partial, and stock can be held for quality inspection before it is accepted.

  3. 03 System

    The invoice arrives

    A supplier uploads it in the portal or flips their own purchase order into an invoice. Where an organisation has the channel switched on, email, EDI 810, PEPPOL and cXML routes feed it in as well.

  4. 04 Rule

    Seven checks run against it

    Header reconciliation, tax validation, duplicate detection, the service-receipt gate, quantity against receipt, price against the purchase order, and price against the contract. All of it runs automatically.

  5. 05 Human

    Anything that failed goes to a person

    A failed invoice does not stall. Accounts payable can accept it with a justification, reject it back to the supplier, or part-accept it pending a credit note. Each route is logged, and anything above a value you set escalates to a finance manager.

  6. 06 Rule

    Eight conditions decide the clean path

    An invoice that satisfies all eight is approved with no human click at all. Fail one and it goes to a person with that exact condition named. There is no partial automatic approval.

  7. 07 Rule

    The due date is set

    The payment term is resolved from the most specific source that exists — the order, then the contract, then the supplier, then your default — and any statutory cap is applied on top of the result.

  8. 08 System

    It is scheduled into a payment run

    Every approved invoice is assigned to the next run that still beats its due date, and anything at risk of a late or statutory breach is flagged.

  9. 09 Human

    A person executes the run

    Marking a run paid, with its shared payment reference, is a deliberate click. Nothing in the system marks a payment run as paid on its own, and that is a design decision rather than a gap.

The decision, in full

Eight conditions. All of them, or a person decides.

This is the complete list the approval step evaluates. If one fails, the invoice goes to a human review queue carrying the reason in the right-hand column. The value threshold ships at ₹1,000,000 and is yours to change.

  1. 1 The invoice is under the value threshold you set Refused asAmount exceeds threshold
  2. 2 Invoicing against this order, including this invoice, stays inside the order total Refused asCumulative invoicing exceeds PO balance
  3. 3 A goods receipt exists on the order, where three-way matching applies Refused asNo goods receipt
  4. 4 Every goods receipt on the order has been quality-approved Refused asQuality not approved
  5. 5 No line is flagged for a variance against the contract price Refused asContract variance detected
  6. 6 The invoice has not been flagged as a possible duplicate Refused asPotential duplicate
  7. 7 No unresolved tax mismatch is sitting on the invoice Refused asTax mismatch requires review
  8. 8 A foreign-currency invoice has an exchange rate Refused asFX rate missing, manual required

Core capabilities

What procure-to-pay software has to handle.

Multi-channel invoice capture

Invoices arrive on whatever channel the supplier already uses

A supplier can upload in the portal, or flip a purchase order they already hold into an invoice without re-entering anything. Email read by character recognition, EDI 810, PEPPOL and cXML are available as inbound channels and are switched on per organisation during implementation, so tell us which ones you need before you go live.

Structured tax and GST fields

Tax held as real data rather than a free-text box

Tax sits in proper fields at both header and line level: HSN codes, tax codes and rates per line, a multi-component structure that holds CGST, SGST and IGST together, TDS withholding, and cross-border and reverse-charge fields. The match engine validates all of it, and checks for a GST e-invoice IRN where a supplier requires one.

Service entry sheet gate

A service invoice waits for confirmation that the work was actually done

A service invoice cannot clear its check until an approved service entry sheet exists, confirming the work happened with a quantity that covers what was invoiced. This is on by default for every organisation rather than something you configure. A procurement manager can override it, but only with a justification note that is written to the audit trail.

Payment terms engine

Terms resolved in order of precedence, then capped by law

The due date comes from the purchase order’s frozen term, or the contract, or the supplier record, or your organisation default — whichever is the most specific one that exists. A statutory limit is then applied on top of that result. For a supplier registered as an MSME, the 45-day cap wins even against a longer term that was negotiated.

MSME and days-payable dashboard

A countdown to the statutory deadline, not a report after it

The payments view shows which MSME-registered suppliers are approaching their statutory deadline and which have already breached it, alongside days payable outstanding and cash out across the whole payables book.

Credit and debit notes

Raised by your team, or submitted by the supplier

Your finance team can raise a lightweight adjustment note against an invoice, an order or a supplier. Separately, a supplier can submit their own statutory credit note against an invoice they issued, through their own portal, and it arrives for your review. Origination can sit with either side; acceptance always sits with you.

Evaluated receipt settlement

Touchless invoicing, on the lines you choose to switch it on for

Evaluated receipt settlement is opt-in at organisation, supplier and purchase-order-line level. On the lines you opt in, a confirmed goods receipt creates an already-approved invoice directly — no invoice document from the supplier, no match and no approval step. It stays off until you turn it on, line by line.

Features

Procure-to-pay software that holds its own rules.

Five groups of features, and not one of them depends on someone remembering the policy.

Invoice decisions you can read

Deterministic rule code, and every refusal names the condition that failed.

  • The approval step is rule code, not a model — it replaced an earlier model-based version
  • Every refusal names the condition that failed, so the queue is a list of reasons
  • It is all-or-nothing: there is no partially approved invoice and no confidence band
  • Above the value threshold you set, a person always decides
  • A likely duplicate is never quietly skipped; it is flagged for someone to clear

How the decision is made

Rules you can read. Not a model you cannot.

  • The approval step is deterministic rule code. It replaced an earlier model-based version, and we would rather tell you that than market it as AI.
  • Every refusal names the condition that failed, so an exception queue is a list of reasons rather than a list of low scores.
  • It is all-or-nothing. There is no partially approved invoice and no confidence band in the middle.
  • A service invoice cannot reach approval without a confirmed receipt. The only way past is a named role leaving a logged justification.
  • Above the threshold you set, a person always decides. That is not a default we ship; it is a condition inside the rule.
  • A likely duplicate is never quietly skipped. It is flagged for someone to clear.

What it will not do

The boundaries are deliberate.

Some of these are design decisions and some are simply not built yet. Each one says which it is, because you will find out either way.

It does not move your money

This is a boundary rather than a gap. Proconomy schedules payment runs and records them as executed, but it is not a payment rail: there is no ACH, wire or card disbursement from inside the platform, and no virtual card issuance. Your bank or your ERP still pays the supplier.

It does not push anything into your ERP on its own

This one is simply not built. There is no automated outbound sync of purchase orders or invoices into a customer ERP today, so the handoff is a deliberate step rather than a background job. It is also the easiest place in this category to overclaim, which is why we are saying it on the page rather than in your implementation kick-off.

It is not a general ledger or a payables sub-ledger

Another deliberate boundary. Proconomy owns matching, exception handling, approval, payment terms and run scheduling, up to the point a run is executed. Your finance system keeps the books.

It does not track your inventory

On-hand quantities, availability and replenishment stay in your ERP. That is a boundary, not a gap.

It does not analyse category spend from invoice lines

Not built, and for a reason worth knowing. The overwhelming majority of invoices arrive with no line-level breakdown at all, so any category analysis built on invoice lines would describe a small and unrepresentative slice of your spend. Spend analysis belongs to Spend Intelligence, which works from order and contract data instead.

It does not enforce separation of duties on invoice approval

Also not built. Exceptions do escalate to a finance manager above a value you set, and that is a real control. A mandatory second human signature, independent of the rule engine, is not one of them.

Three invoices. Three different endings.

1

A clean catalogue invoice nobody touches

A supplier flips an order they already have into an invoice. The seven checks pass, all eight approval conditions are satisfied, the due date resolves from the order’s frozen term, and it lands in the next payment run that beats that date. The first person to see it is whoever executes the run.

2

A service invoice that stops until the work is confirmed

A contractor invoices for a completed milestone before the service entry sheet is approved. The gate holds it. Once the service owner confirms the work and the quantity covers what was invoiced, the check clears and the invoice continues. If it has to move sooner, a procurement manager can override — and the override and its reason are both on the record.

3

A foreign-currency invoice with a missing rate

Everything else about the invoice is in order, but no exchange rate is available for the day. Condition eight fails, so nothing is approximated and nothing is approved. It goes to accounts payable labelled “FX rate missing, manual required”, which is a one-line fix rather than a hunt.

Bring us a month of real invoices.

Give us one supplier and one month of invoices as they actually arrive. We will show you which ones would have cleared on their own and, for the rest, exactly which condition stopped them.

Request a demonstration

Where it actually goes

Approved orders reach your supplier. Automatically, every time.

Four rows, because the differences between them matter more than a diagram would suggest.

Automatic, no human click The supplier

The moment an order is approved, it becomes a PDF and is emailed straight to the supplier. On by default for every organisation, with nobody re-keying or re-sending it by hand.

On demand, a click The buyer

Downloading the purchase order regenerates or fetches the PDF on request. It does not re-notify the supplier, so a buyer checking the document cannot accidentally resend it.

Manual, deliberate The supplier

A “send to supplier” action exists for organisations that have switched automatic dispatch off, and for a buyer who wants to resend an order on purpose.

Not available today Your ERP

There is no automated outbound push of a purchase order or an invoice into a customer ERP, in any configuration. Moving an approved outcome into your finance system is a deliberate step today.

Security, compliance and recognition

Checked by auditors. Judged by the industry.

Where each compliance programme stands, and what the procurement industry has given us so far.

Security and compliance

Awards

Five, presented on stage at three industry events.

  • Autonomous Procurement Platform of the Year
  • Procurement Technology Innovation Award
  • Unified Procurement and Supplier Management Platform
  • Procurement Startup of the Year
  • AI in Procurement or Supply Chain Award — Solution Provider

See the events and the trophies

Before you book anything. Answered honestly.

What is procure-to-pay software?

Procure-to-pay software covers the stretch between an approved purchase order and a scheduled payment: getting the order to the supplier, recording what was received, taking the supplier’s invoice, matching it against the order and the receipt, routing whatever does not match, applying the right payment term, and grouping approved invoices into payment runs. The value is not that it stores those documents — your ERP already does. It is that the checking in between stops being somebody’s afternoon.

What actually stops a wrong invoice from being paid automatically?

Eight conditions, all of which have to pass. The invoice has to be under the value threshold you set; invoicing against the order, including this invoice, has to stay inside the order total; a goods receipt has to exist and have been quality-approved where three-way matching applies; there can be no contract-price variance; it cannot be flagged as a possible duplicate; there can be no unresolved tax mismatch; and a foreign-currency invoice has to have an exchange rate. Any single failure sends it to a person with that reason attached. It is never a partial automatic approval.

Does the system pay our suppliers?

No. It schedules approved invoices into the next payment run that still beats the due date, and a person executes that run with a shared payment reference. The actual disbursement happens in your bank or your finance system. Nothing in the platform marks a run as paid without someone clicking, and no background job can.

How does this sit alongside our ERP’s accounts payable module?

Proconomy owns matching, exception handling, rule-based approval, payment terms and payment-run scheduling up to the point a run is executed. It is not a general ledger or a payables sub-ledger replacement. It also does not automatically push approved orders or invoices back out into your ERP today — that handoff is a deliberate step rather than a background sync. Ask us for the current integration scope for your specific ERP rather than trusting a logo on a slide.

What happens if a service invoice arrives before the work is confirmed done?

It is blocked. The match engine requires an approved service entry sheet confirming the work happened, with a quantity that covers what was invoiced, before a service invoice can clear that check — and this is on by default for every organisation rather than something you switch on. The only way around it is an explicit override by a procurement manager, which is recorded with a mandatory justification note. There is no silent bypass.

Can we meet statutory payment-term rules automatically, such as India’s MSME 45-day cap?

Yes. The payment-terms engine resolves the due date from the most specific source available — the purchase order’s frozen terms, then the contract, then the supplier record, then your organisation default — and then applies any statutory cap on top of that result. For a supplier registered as an MSME, the 45-day limit wins even if a longer term was negotiated. A dashboard also tracks how close each of those invoices is to its deadline, so the number arrives before the breach rather than after it.

Can a supplier submit their own credit note, or do we have to raise it for them?

A supplier can submit their own statutory credit note against an invoice they issued, through their own portal. It arrives as a document pending your finance team’s review rather than something your team has to construct on the supplier’s behalf. Your team can also raise lightweight adjustment notes internally. Origination can sit with either side; acceptance always sits with you.

Is the approval decision made by AI?

No, and we would rather be precise about it than borrow the word. The approval step is deterministic rule code — it replaced an earlier model-based version specifically so that every decision is reproducible and every refusal can name the condition that caused it. You can read the eight conditions on this page. A confidence score cannot be read that way.

One supplier. One month of invoices.

No slides. You will see which ones clear themselves and which condition stops the rest.

Someone from client success replies, not a sales sequence. If we are not a fit we will say so on the first call.