Data & Stuff // Neil Houston

This is my response to Publishing Itemised Local Authority Expenditure Advice, unfortunately the captcha appears to be broken when I attempted to post this.

These are just my personal thoughts, and may be incorrect, and they do not represent the thoughts of my employer.

Supplier Identification
I disagree with the phrase ‘Ideally publication would include the Companies House number (or equivalent in the case of foreign companies) or Charity registration number‘. This depends on the quality of data entered into the system, in my experience such level of detail (at least for private sector companies) is never recorded in a Supplier master. You will have the Supplier Name, Internal Supplier ID, Address fields, basic contact details (with a CRM system likely to be holding more details).

Such information is not easy to populate into a system if it’s not already present, I remember a case where we had to identify Dun&Bradstreet numbers for every supplier – it wasn’t an easy job.

I would say, this boils down to one thing – why do you require that level of information, what is wrong with the company name after all unless we are talking about data quality issues?

I’d also be wary of needing to publish the actual contact details for each company, depending how a companies supplier master is setup, you may have the contact details for the person in Accounts Payable. What use is that to the end user? It would need to be researched to understand exactly what data is present etc.

Payroll/Benefits
Dependent on how the Supplier master is setup, it is possible for employee expense reimbursements to be present (i.e every employee is setup as a vendor). Most systems allow you to identify these, not all do though. So it may be possible to anonymise these.

Payroll, at the General Ledger level is likely to be a few entries (the transactions hitting the GL Payroll account, and the bank account), the Payroll data of actual payments (BACS likely) may be held separately to that of where normal supplier payments are made (again, dependent on system structure – I’ve seen them a few ways).

Overall
The other thing to remember, is that in some cases, the data output is likely to be:

01/01/2010
CHQ
£2256.89
A1 Company
INVXYZ002 (or some document reference)
GL CODE
GL Description (i.e Transportation)
Cost Centre Code
Cost Centre (Parks Department).

The above shows that the Parks department paid A1 Company, £2256.89 on -01/01/2010, for a service that the invoice was booked to transportation, and the cost absorbed through the parks department budget.

You’d be surprised how many times there are some systems where it’s not totally easily to identify the payment, back to the relevant invoice (apart from a manual reconciliation), you need to know the invoice side of the transactions – as that is where the cost will be booked to (as the payment details will just be crediting cash, debiting Accounts Payable).

It all depends what level of detail you want to show, it’s easy enough to show a payment went out (but associated services, dependent on the internal reporting functions of the system – may be harder).

These are just my thoughts, from my experiences of working with a multitude of different financial systems from your SAP, to your BAAN and SunSystem.