We use Agresso Business World software to generate this data. The data is exported into an excel spreadsheet and checked manually for completeness and for redaction of personal data. It is then saved as a comma delimited file (.csv) for publication on our website on a monthly basis.
All mandatory data and some recommended and optional data is included:
| Col | Field name | What is required | Reason for inclusion | Inclusion status |
|---|---|---|---|---|
| 1 | Body name | Name of organisation making the payment | Aids readability for casual reading | Optional |
| 2 | Transaction date | The transaction date as recorded in the general ledger in the UK date format (dd/mm/yyyy) | To identify the date that the transaction took place | Mandatory |
| 3 | Supplier (beneficiary) | The full name of the supplier | To identify the recipient of the spend | Mandatory unless redacted |
| 4 | Transaction number | A unique reference number for each individual expenditure transaction | To act as a reference number when dealing with enquiries or FOI requests | Optional |
| 5 | Net amount | The actual value of the transaction inclusive of irrecoverable VAT | To identify the full cost of the transaction | Mandatory |
| 6 | Irrecoverable VAT | The value of the VAT that cannot be recovered | A mandatory requirement of the code | Mandatory |
| 7 | Department or service where expenditure occurred | Department or service responsible for spending the money | To improve accountability | Mandatory |
| 8 | Procurement category | Describes the purchased goods and services | To identify the general nature of the spend | Mandatory |
| 9 | CIPFA expenditure code | The account code which represents the expenditure type | Publishing the CIPFA SeRCOP subjective accounting code allows expenditure types to be matched even when the wording of the description has changed | Recommended |
| 10 | Purpose of expenditure (narrative) | A description in words for the details of the transaction | To help explain the payment | Mandatory or recommended unless redacted |
| 11 | Card transaction | Whether the transaction was completed using a Government Procurement Card (GPC) | The code makes it mandatory to publish all GPC transactions including those with a value of less than £500 | Mandatory |