Procurement audit trail software that nobody can rewrite.

Procurement audit trail software should record who did what, to which record and when, along with what the record looked like before and after the change. Bollard's audit trail captures each of those for every change, listed by time, user, action and entity.

An entry that only says a record was edited by a user tells an auditor that something changed, but not what. The before and after values answer the next question: was the price on this purchase order always this figure, or was it raised after the quote was chosen?

An append-only log only ever adds entries. Nothing in it can be edited or deleted, so the history stays exactly as it was written.

In Bollard, a correction is a new entry that sits after the original, and each entry is sealed to the one before it. That matters in procurement, where the people who approve spend are also users of the system. A log that can be edited is weak evidence. An immutable audit log lets an auditor rely on the sequence they are reading.

The procurement dashboard shows the value in flight at each of the seven stages and a needs-attention queue for each role.

Value in flight is money committed but not yet settled: requests waiting for approval, orders awaiting delivery, invoices waiting to match. Seeing it by stage tells finance where cash will be needed and tells procurement where purchases are stuck. The needs-attention queue puts the items waiting on each role at the top of their screen.

For questions the dashboard does not answer, the assistant takes plain-language questions, such as which invoices failed the match this month, and answers from live data within the user's role.

Each person sees only the records their role allows. Site managers see their own site, and head office and finance see the network.

This is enforced with row-level security in the database, so no export, report or determined user can see more than they should. The same rule applies to the assistant, which only answers with what the user's role may see.

The audit trail runs underneath all seven steps of the loop: request, approve, source, order, receive, match and pay. Every step leaves its mark in the same place.

At the start, it holds the requisition with its budget code and reason. Through approval, every decision and every rejection remark. At ordering, the purchase order as raised from the chosen quote. Then come receipts with accepted and rejected quantities, the match verdict and the payment. An auditor following one purchase reads a single sequence instead of collecting emails, spreadsheets and module logs.

In a spreadsheet anyone can overwrite a cell, and in a typical ERP the logs are spread across modules. Bollard keeps one append-only log for the whole loop.

Spreadsheet version history can show that a file changed, but tying a change to an approval or a payment is detective work. Spreadsheets are also error-prone: field audits found errors in 91% of real business spreadsheets (Panko, 54 spreadsheets audited). ERP logs are usually sound within a module, but following one purchase can mean reading the purchasing, inventory and payables logs separately.