Insights · 27 September 2026

Procure-to-pay that refuses the wrong bill: a buyer's checklist

The best procure-to-pay system is the one that refuses the wrong bill before anyone pays it. Judge it by what it stops, from the day a supplier is created to the day money leaves. We counted twenty refusals in the code of our own ERP, across five stages, and they make a checklist you can take into any demo.

Judge the system by what it refuses

Every procure-to-pay demo shows a purchase order turning into a bill and the bill turning into a payment. That is the easy path. Money goes missing on the other paths. A supplier gets created twice under two spellings. An order gets approved by the person who raised it. A challan is received twice, or two clerks enter the same bill.

The list below comes from Neauron Intelligent Core, the ERP we built and run our own building-materials trade on. Each item is a check in the code, not a line on a slide. Some are hard stops. Others let a person with the right permission go ahead with a written reason, which stays on the record. Both are fair controls, as long as you know which is which.

When the supplier is created

Five refusals before a supplier can be ordered from.

  1. A GSTIN that cannot exist. A GSTIN with a wrong check digit or a state code that does not exist is refused.
  2. A PAN that does not match. Characters 3 to 12 of a GSTIN are the holder's PAN. If the PAN entered is different, the record is refused.
  3. A second copy of the same supplier. A GSTIN or MSME (Udyam) number already held by another active party is refused.
  4. Approval without a PAN. A supplier cannot be approved while its PAN is missing or malformed.
  5. An employee as a supplier. An employee set up to be paid as a vendor cannot be authorised to supply goods.

In the demo, create the same supplier twice, the second time with a typo in the trade name. See whether the GSTIN catches it.

When the order is raised and approved

Five more before an order can commit money.

  1. A supplier who cannot trade. An order to a supplier that is inactive, blocked or not yet approved is refused.
  2. A dead GST registration. If the supplier's GSTIN shows as cancelled, suspended or inactive, the order is refused. The same check runs again when their bill is entered.
  3. A product outside the supplier's authorisation. Where a supplier is authorised for named products, an order for anything else needs a written reason.
  4. An order past the project budget. Approving an order that takes the project's committed spend past its approved budget needs a written reason on record.
  5. Approving your own order. Above a value each business sets, ₹1 lakh by default, the person who raised an order cannot approve it.

Raise an order in the demo, then try to approve it with the same login.

When the goods arrive

Four at receipt, where weight and paper most often disagree.

  1. A receipt without an order. A goods receipt must cite an approved purchase order that is still open.
  2. More than the order has left. The receipt starts from the quantity still open on the order and cannot go past it.
  3. The same challan twice. A supplier challan already received against the order in the same financial year is refused.
  4. No weighment. A product marked for weighment cannot be received without one.

A warehouse can also require a gate entry before any receipt, and hold the truck at the gate until its receipt is done.

When the bill comes in and the money goes out

Four refusals on the bill, and two on the payment.

  1. A bill for more than was ordered. A bill line above the order line is refused.
  2. A bill for more than was accepted. Billing past the quantity accepted at receipt needs a written reason from someone with finance permission.
  3. A bill that does not match. Where the bill disagrees with the order or the receipt on rate or quantity, it carries a typed variance and cannot be submitted or approved until someone accepts the difference with a reason.
  4. The same bill twice. A second bill with the same supplier and bill number is stopped unless someone writes down why it is different.
  5. Reviewing your own payment. The person who reviews a bank payment instruction must be someone other than the person who asked for it.
  6. Releasing it too. The person who executes the instruction must be someone other than both of them.

Neauron also holds a bill's input credit until it matches the supplier's filing in GSTR-2B exactly. Under section 16(2)(aa) of the CGST Act, credit depends on the supplier reporting the bill.

Two we would add, and how to run the test

For a buyer, we would add two more. First, we would tie every payment route to the bill's match status, so a bill with an open variance cannot be paid by any path. Second, we would put the MSME clock on every bill. In India a registered micro or small supplier must be paid within 15 days, or the agreed period up to 45 days, or the expense is not deductible until you pay, under section 37(2)(g) of the Income-tax Act 2025.

To test any system, take one real month and pull its most awkward documents. Take a supplier with two registrations, an order over budget, a part delivery, a bill that does not match the receipt and a bill entered twice. Give the same set to every vendor and ask them to process it live.

Score each system on how many of the twenty it refuses. For each override, ask who can give it, whether a reason is required, and where that reason is kept. A system that lets the wrong bill through looks faster in the demo and costs more at audit.

Sources

THE PROMISE

We stay until the ROI you were promised is the ROI you get.

Most projects fail after go-live, not before it: the software works and nobody uses it. So we do not stop at delivery. We advise, build, implement, operate, and only then transfer, with change management and adoption run as hard as the code.

ADVISE→BUILD→IMPLEMENT→OPERATE→TRANSFER
THE FORCE

A force of AI agents, on one framework that fits any business.

Named, scoped, switchable agents that read, reconcile, forecast, flag and draft, taking the work off your people’s desks and putting revenue back on your books. A person approves every move that touches money.

See the framework →

Read next: Operations and supply chain · Neauron Intelligent Core · Finance, billing and compliance · Choosing an ERP for a mid-size business · All insights