Buck shot or machine gun; assurance

With news about the slow but steady adoption of SBR everywhere (but mostly on related sites…), it suddenly struck me that with this Standard Business Reporting we see a move from single firings of buck shot to the machine gun age in assurance.

First, this:
DSCN4309[Yup, actual business lurking in the background. Date this pic]

By which I mean that until now, and for a short bit of time to come, accountants of the annual accounts certifying type issue(d) single assurance statements about a whole number of individual reporting items; in conjunction with each other but hence (!) also about all of them individually. The single blow of much data, in multiple but somewhat related directions.
Now, with XML, and XBRL as a common ‘subset’ taxonomy definer, and SBR on the back of that, we suddenly have the possibility of firing a great many but single data points in all sorts of directions. Where each bullet data point has to stand on itself, and be assured separately, aimed at, well, a single recipient.
Which makes a change necessary from the cover-all assurance of yesteryear to a single data point assurance thing of today. Where one cannot rely on context – or the context is re-created by a recipient collecting the data points they want …! – one has to provide assurance on … does this end up with a system-of-production assurance thing again ..?

Hope not. Since that is too far off of any real application. Since assurance of systems misses the vast enormity of details that matter when one wants to give assurance on … details. What then? Both. Both systems assurance overall, not circling on the ledgers only. And detailed assurance per data point or tinysubset. With SBR for target audiences as intermediate [stage?].

And, will we not need the ‘traditional’ assurance over annual reports anymore …? Well, we will, for sure as we seem to need more than ever true and fair views of how business in general was conducted, to establish credibility of management control for the (near) future. But then, such reports would be enormously much more qualitative by nature. To be qualified in a very non-quantified since by second opinion givers like accountants. [And/or others …!?] What lyrical prose we’ll have, what market push to cut the cr.p, what difficulty of accountants to grapple with the auditees’ sheer poetry enlisted to window dress.

Moar will follow, especially re single point assurance…

On assumed guilt, innocence to be proven

An interesting piece (in Dutch) on documentation and the requirement to prove innocence under totalitairan presumed guilt: http://www.accountant.nl/Accountant/Opinie/Meningen/Naar+de+bliksem.aspx
How true, the story. Now go apply the gist to your auditees as well! They‘re the ones under presuure, that accountants et al are only starting to feel in the past couple of years..!

And here’s another picture for your viewing pleasure:

Trust statistics

“Never trust any statistic that you haven’t forged yourself” as Winston Churchill put it.

With today’s tools, computing capabilities and speed, why wouldn’t accountants draft their own annual accounts statement of their clients’ accounts ..? These could then be published alongside the ones of the clients themselves. The differences would be transparent to investors, and when (not if I guess) the clients can explain the differences to their stakeholders, there’s no pain in anything.

When accountanst would complain that it would be impossible to re-do the annual accounts, they only claim their incompetence. If they truly understand what’s on the books, really understand the underlying processes in every detail required (and note, this would be a very, very hard requirement already!), they would have no problem at all to recreate the sum total of it all. Or they end up with apparently differing interpretations of the processes, and may explain to stakeholders.

So, either the accountants go do this or they declare to not know nearly well enough what they’re signing off. There’s no in between.

Maverisk / Étoiles du Nord