Use cases

From approval to payment, see what does not match.

ProcureTrace compares the records behind one completed procurement project. See where values agree, where they conflict, and what is missing.

Capital project closeout

When the review happens: Before final project and financial closeout.
Records typically supplied: Approval records, quotes or bids, contracts, purchase orders, change orders, delivery records, invoices, payments, and asset records.
What ProcureTrace compares: Compare what was approved, contracted, ordered, delivered, invoiced, paid, and recorded.
What the reviewer receives: Cited findings showing where values agree, disagree, are missing, or do not support a conclusion.
Current pilot boundary: ProcureTrace does not certify that the project is legally or financially compliant.

When the review happens: Before grant reporting, reimbursement, or audit.
Records typically supplied: Funding approvals, procurement approvals, quotes or bids, contracts, purchase orders, invoices, and payments.
What ProcureTrace compares: Compare amounts, quantities, dates, suppliers, and identifiers across the supplied records.
What the reviewer receives: A review record linking each finding to the document, page, field, value, and calculation.
Current pilot boundary: ProcureTrace does not determine cost eligibility or certify grant compliance.

When the review happens: Before an internal audit, external audit, or year-end review.
Records typically supplied: The completed procurement file, including approvals, sourcing records, contracts, orders, delivery records, invoices, and payments.
What ProcureTrace compares: Identify conflicting values, missing required records, and questions that the available documents cannot answer.
What the reviewer receives: A cited review that a named reviewer can confirm, dismiss, or accept as an approved exception.
Current pilot boundary: The review supports preparation. It does not replace an auditor or provide an audit opinion.

When the review happens: After a disputed change or before closing a project with contract amendments.
Records typically supplied: Original contracts, purchase orders, change requests, approvals, revised orders, delivery records, and invoices.
What ProcureTrace compares: Compare the invoiced scope, quantity, amount, and date against the supplied approval and change-order records.
What the reviewer receives: Cited differences and missing records for reviewer resolution.
Current pilot boundary: ProcureTrace does not interpret contractual rights or provide a legal opinion.

When the review happens: Before responding to a request involving a completed procurement project.
Records typically supplied: The procurement records selected by the organization for review.
What ProcureTrace compares: Identify inconsistent values and missing records within the supplied project file before disclosure.
What the reviewer receives: A traceable record of the comparisons performed and the reviewer’s decisions.
Current pilot boundary: ProcureTrace does not determine disclosure obligations, exemptions, or legal privilege.

Bring the completed procurement records. ProcureTrace will compare them and return cited findings for review.