What it checks

What ProcureTrace checks across a procurement file

A purchase leaves records in several places: the order, approved changes, one or more invoices, a payment, and the paperwork that connects them. ProcureTrace reads those records together and reports what they do and do not establish.

Start with an invoice

When an invoice arrives

Does the bill match what was ordered?

ProcureTrace reads the purchase order and the invoice, links them on the order number both documents print, and compares the invoiced amount against what the order authorises.

The reviewer sees the two amounts, the difference, and the page each figure was read from.

  1. Purchase order CAD 42,000
  2. Invoice CAD 44,500
  3. Result Differences Found Difference of CAD 2,500
When the order changed after it was issued

The same invoice, with the approved change on file

Orders move. When an approved change is in the file, ProcureTrace folds it into what the order now authorises before comparing anything against it.

The invoice above has not changed. What changed is that the file now explains it, so nothing is reported as a difference.

  1. Purchase order CAD 42,000
  2. Approved change CAD 2,500
  3. Authorised now CAD 44,500
  4. Result Records Match The change accounts for it
When more than one invoice bills the same order

Billed in stages, reviewed together

Long orders are rarely invoiced once. ProcureTrace takes every invoice against an order as one set and compares the total billed so far against what the order authorises.

An order that has only been partly invoiced is not a shortfall. Nothing in the file says whether more invoices are still coming, so the review says exactly that instead of reporting the remainder as a difference.

  1. Invoice 1 of 2 received Part of the order
  2. Remaining on the order Not yet invoiced
  3. Result Insufficient Evidence Not reported as a difference
When a payment settles a bill

A bill and the money that settles it are different records

An invoice is a supplier asking to be paid. A payment record is money moving. ProcureTrace keeps them apart and compares each against the order on its own.

Treating them as one number would read an order billed once and paid once as though it had been claimed twice.

  1. Invoice A claim for payment
  2. Payment record A settlement
  3. Result Compared separately Never summed into one figure
When two records claim to be the same invoice

One invoice number, twice in the file

A re-sent invoice and a genuine second invoice can arrive carrying the same number. ProcureTrace cannot tell them apart from the documents, and does not try.

It declines to add them together, which is what would turn one bill into an apparent overcharge, and puts the question in front of the reviewer instead.

  1. Invoice INV-2231
  2. Invoice INV-2231
  3. Result Insufficient Evidence Not counted twice
When the file is missing something

The numbers agree, but the evidence does not carry them

A record the comparison needs may not be in the file. A document may be in the file and unreadable. Something may be legible and still impossible to place against the order without guessing.

Each of those is reported as what it is. A review does not come back as agreement because something relevant was quietly left out of it.

  1. Required record absent Missing Required Information
  2. Read, but cannot be placed Insufficient Evidence
  3. What is never done Reported as agreement An unread record is not a clean one
Also checked

Within the documents themselves

Some checks never leave a single record. They run whenever the file supplies what they need.

Total vs. line items
Whether the line amounts printed on an order add up to the total printed on it.
Line-item calculation
Whether a line's quantity and unit rate account for the line amount as printed.
Contract total after amendment
Whether the original value plus every recorded change equals the revised total the document states.
Order within agreement limit
Whether orders placed under a standing agreement stay within the limit that agreement sets.
What a result can say

Four answers, and no fifth one

Every check returns one of these. Each one carries the records and pages behind it.

  • Records Match The records compared agree on the values checked.
  • Differences Found They disagree, and the review shows by how much and where.
  • Missing Required Information A record the comparison needs is not in the file.
  • Insufficient Evidence The file cannot settle the question without assuming something it does not state.

Amounts on this page are illustrative. A review runs on the records you supply, and a reviewer confirms, dismisses or accepts each result.

See what one of these reviews actually looks like.

Walk through a complete example: the file it started from, the results it returned, and one finding opened up.