Tag Archive for: static data

Static Data – unsexy, but imperative to workflows

| 23-04-2018 | treasuryXL |

We live in the world of Big Data – we are told that there is so much potential that can be unleashed by embracing Big Data. This can lead to business efficiency, increased revenue, reduced expenditure, earlier identification of fraud etc. But for all this to reach fruition, we need to rely on the most basic building block – Static Data. Many companies have grand ideas of how to maximise revenue with data streams, yet fail to grasp the essential need for good, sound, structured Static Data.

Definition

This is data that remains constant (mostly) during the lifetime of its use; once input and recorded it becomes static and is used as reference data. The most logical example would be the data on relationships – when a company starts trading with a new supplier, a new record needs to be added to the bookkeeping system.

Types of data include:

  • Legal name of counterparty
  • Short name
  • Legal address
  • Telephone number
  • Fax number
  • Email
  • Contact persons
  • IBAN
  • BIC Code
  • KvK number
  • BTW number

Once the Static Data has been input it should only be changed by authorized staff. Dynamic data – the lifeblood of Big Data – can later be input (trades, invoice numbers, delivery dates, amounts etc.), but it needs good Static Data to make the data consistent. The complete data set for a counterparty must always be unique – there can not be 2 entities with the same set of data.

The structure of the data is also important – it could quite easily be the case that a company has one large client with the same bank details, but relationships with 5 different divisions. It is therefore essential that the correct protocols are in place for consistent data – whilst the legal name will be the same the importance of the short name becomes evident.

When it goes wrong

Inter company communication does not always involve use of a bookkeeping system. If staff start referring to a counterparty by another name than is in the system or use a name that is in the system but not the name they mean, problems can occur. Incorrect bookings arise which can lead to incorrect exposure levels or limits being breached. It can also be that a legal entity in a different country is referenced as they have offices in more than 1 country and issues such as VAT (BTW) can suddenly appear.

The need for secure Static Data is very high – the consequences of errors should never be underestimated. Data entry should be undertaken by people who do not enter any other data into the systems – in other words it should not be undertaken by the same staff that work in debtor and creditor administration.

Furthermore, a clearly defined protocol needs to be implemented to determine when and how Static Data can be changed.

In a little more than 1 month from now, GDPR comes into effect. The urgency to understand Static Data and to appreciate its significant contribution to daily operations has never been greater.

If you have any questions, please feel free to contact us.

[button url=”https://www.treasuryxl.com/contact/” text=”Contact us” size=”small” type=”primary” icon=”” external=”1″]

[separator type=”” size=”” icon=””]

Internal Fraud – or how not to cheat yourself

| 22-02-2018 | Lionel Pavey |

Most companies, regrettably, experience internal fraud. The financial value of the loss can be small or large – however the impact is the same. Internal investigations, procedural reviews, the time spent on detection, possible prosecution, together with the potential loss of reputation are significant factors above and beyond the monetary loss. Fraud can never be eliminated, but the threat can be minimised through proper procedures.

Fraud is normally caused by false representation, failure to disclose information and abuse of power and position. As fraud is performed by people and their actions, a first step to prevent fraud would be to look at the current working environment within a company. If a company is putting extra stress on employees – bigger targets, loss of overtime payments, reductions in secondary benefits, no pay rises nor promotions etc. whilst the directors receive bonuses– this can lead to employees becoming aggrieved  and seeking retribution. Furthermore, employing more temporary staff and external contractors, can distance the remaining employees and challenge their allegiance and loyalty.

Internal procedures

One of the least sexy components within a company is internal procedures. They need to be drafted, amended, agreed, published, implemented and reviewed on a rolling basis. Very few people enjoy writing these manuals, but they are essential to ensure that everyone is aware of the correct procedures that have to be followed to perform any tasks. Often there is talk of a “four eyes principle”. Personally, I have always believed in a “six eyes principle” as it requires more independent control and makes fraud less easy to perform. Most of the procedures are, of course, built  around common sense. Duties should be segregated – different departments have different roles to perform in ensuring the complete procedure is followed throughout the company. Even within a single department, attention should be paid to segregating duties.

An example would be the administrative function relating to a purchase. There are 4 distinct stages – procurement, arrival, warehousing and dispatch/shipment. If one member of staff was responsible for the relevant data input for all 4 stages, there is an increased risk that fraud could take place. This is not to say that work should be segregated that one employee only ever does one function – this could also lead to fraud either through disenchantment or over familiarity of the systems and procedures used at one specific point in the production chain.

External procedures

Certain departments within a company have contact with external sources – suppliers, clients, financial institutions. Anyone who has contact with an external counterparty can be swayed by opportunity if the controls are not in place. In respect of purchasers – what contact do they have with suppliers outside the office? Are they entertained – restaurants, sports events etc? How often do they have contact? In respect of sales – are they responsible for determining the sales price? How often do they see clients and spend money on them? The same also applies to treasurers, cash managers, risk managers etc.

The necessary checks and balances need to be put into place. A record of all contact with external parties needs to be kept, updated, verified and stored. Temptation can be caused by personal hardship, flattery or grievance at how the person is perceived to being treated by the company.

Standing up to the boss

As stated, a healthy company should have procedures and statutes in place. These need to be adhered to at all times – there can be no exceptions. However, a mechanism for escalation is often missing. Example – someone sends in an expense claim approved by their manager. The treasurer or controller might question the veracity of a particular entry. A proper mechanism to escalate the discrepancy needs to be firmly established. That a manager has signed off on the expense claim does not mean it is correct.

Even directors have to make sure that their claims are signed off by other members of staff. Being at the top does not mean that the procedures do not apply. Requests for a priority payment outside of the agreed procedure should always be questioned. If everyone has agreed to the standard procedures, then there can be no justification to make a payment outside of the normal procedure, just because it has been deemed a priority. If truly deemed necessary, then authorisation must be given not only by management and directors, but also by the legal department. If this occurs, then the existing procedure needs to be examined as to why the incident occurred and where the procedure broke down. This all has to be detailed in writing – fraud can happen at the highest level as well as low down with an organisation.

Static data

Every contact both inside and outside of the company should be recognised and recorded in a data system. Static data refers to all relevant data concerning an entity – full name, registered address, bank details, contact details etc. This data should be fed into all other systems, but data input should be restricted to a small number of employees. These employees should not have access to any of the systems that are used to input data relating to daily operations.

Another key area is in the cash management side – book keeping can be complex and differences not noted until the yearly audit. However, cash movements contain plentiful details – name of beneficiary, account numbers etc. This can be reconciled against the prevailing static data – are the bank account numbers the same?

Fraud can never be eradicated, but by being open, allowing questions to be asked, even performing unexpected checks on the system and its integrity, and creating an atmosphere where staff know that they can question without fear of reprisal, then at least everyone will know that the company is alert and vigilant.

That knowledge and awareness will make a potential fraud think twice.