October 18 ,2015 | by Hari Sri

Reporting guidance concerns raised by accounting regulator

_Content

The Financial Reporting Council (FRC) is consulting on draft guidance regarding on going concerns about the quality of information that investors receive about businesses.

The new consultation will focus on the assessment and reporting of accounting, solvency, and liquidity risks over the longer term.

Help for directors

The accounting regulator aims to produce new guidance to help directors when it comes to applying relevant requirements in company law and accounting standards. These moves come in the face of the introduction of new UK and Ireland regulatory developments.

Last year, the FRC updated the UK Corporate Governance Code in light of the recommendations of the Sharman Inquiry that reported on liquidity risks. The guidance was for companies applying the Code, and now the new draft guidance is the best practice advice for non-Code companies which was also promised at the time.

Executive director of codes and standards at FRC, Melanie McLaren, said: "The Sharman Inquiry highlighted the need for clarity by all companies on the going concern basis of accounting. It identified the need to consider liquidity and solvency when analysing the principal risks a company faces and the need to take a broader longer-term view."

Practical aim

By following the new guidance, directors will have to use their own judgement to determine how to meet their legal responsibilities. The FRC says it will encourage the use of assessment techniques and disclosures that directly relate to the size and scope of the company.

However, the new guidance is not directed at SMEs and micro companies who do not need to prepare a strategic report. 

Hari Sri

Hari is the LSBF Blog's News Editor. He manages the editorial content on the blog and writes about current affairs, SME, entrepreneurship, energy, education and emerging market news.

Share on Facebook Share on LinkedIn +1
There are no comments posted yet. Be the first one!
Please write your comment, minimum length 50 characters
Please insert your name
Please insert a correct email address
We couldn't process your comment, please try again later