New Cape Prepaid Assurance Product

Collecting cash and reconciling balances is often an area that revenue assurance departments opt to leave outside their scope. When considered with a postpaid mentality, cash collection is not particularly a specialist area; all businesses need people who chase debtors and keep a track of balances. Prepaid changes the dynamic somewhat. The cash is paid first, and the balance updated using a highly automated process where there is limited opportunity to correct mistakes later on. So it is no surprise that this is one area ripe for inclusion within the remit of revenue assurance. Read here for the press release from Cape for their new prepaid assurance product. They may be deploying the solution with just one European telco at the moment, but the demand for this kind of product should be strong.

TMF vs. GRAPA: Which Home for RA Standards?

The debate about who should issue revenue assurance standards is rumbling onwards, but has no end in sight. GRAPA are the new kids on the block, apparently keen to take on the role of standard-setters. Meanwhile, the much bigger TMF appears to be slow to appreciate they have competition in the area of revenue assurance. A few days back I posted my blog about the risk that GRAPA will split the revenue assurance world. Over at the TMF's community forum, I raised my concerns that the TMF has failed to get a high enough profile as standard-setters for revenue assurance. I believe many CSPs are joining GRAPA in the hope of obtaining guidance whilst unaware of the work already done by the TMF. You can see from the TMF community thread that some agree, others disagree. Maybe I am right, maybe I am wrong. Everyone makes mistakes. There would be no need for revenue assurance if people never made mistakes ;) Now would be a good time to determine the true extent of industry awareness of the TMF's revenue assurance standards. You can help the revenue assurance profession by responding to these questions:

  1. Did you know that the TMF has issued revenue assurance standards and guidance?
  2. If yes, how did you find out about the TMF's work?
  3. Should GRAPA adopt the existing TMF standards, or create new ones?
  4. Who are your preferred standard-setters for revenue assurance: The TMF, GRAPA or some other body?

To steer the TMF and GRAPA on the right course, let them know what you think by doing the following:

  1. Post your answers to the TMF web debate about this.
  2. Leave a comment with your answers on this webpage.
  3. If you can register with GRAPA's forums, post your views on whether they should co-operate with the TMF in setting standards.
  4. Share this with your friends and colleagues and get them to respond with their answers.

My worry is simple. Two standard-setting bodies is one too many. GRAPA is exclusive to communications providers, with no involvement from vendors or consultants apart from XiT, the tiny consulting company that founded it. TMF activity is mostly driven by vendors and consultants. If GRAPA and the TMF both issue standards without any mutual cooperation, they will split the revenue assurance profession down the middle. If you think that would be a bad thing, now is the time to let people know.

Network Planning Saves The Planet?

Every so often someone comes up with a fantastic new sales pitch for the same old product. Hats off to mobile network optimization business Actix who tell us that their product will, literally, help us save the planet. According to their press release they have done research which calculates that mobile network operators are creating a global annual excess carbon footprint equivalent to running nearly 3 million 3-bedroom family homes. So, not unreasonably, they argue that if you could cut the energy costs that would be good for the environment. It follows that they can help reduce energy costs through better planning the deployment of the network. All of which is true, though you have to decide for yourself whether mobile network optimization really is the most important battleground in the war on global warming. Here are a few alternative conclusions that Actix decided not to share with us:

  1. Nationalize all mobile operators and turn them into one big company. That should improve efficiency by allowing duplications in coverage to be stripped out.
  2. Do not nationalize, but force all mobile operators to allow any and all national rivals and service providers to roam freely on their network at a capped rate. The incentive for building network where somebody already has existing network coverage will be undermined.
  3. Make calls more expensive so people use their mobile phones less. Less use means less network is needed.
  4. Ban mobile phones and make everyone use fixed lines.

In case you could not tell, I am not entirely serious ;) All I want to say here is that jumping on an environmental bandwagon might give Actix a new sales angle, but is hardly the main reason for using their services. Cutting costs is a much more straightforward reason to optimize networks. And the energy spent on providing mobile phone networks is ultimately good for the environment, if it helps encourage people to communicate remotely and cut down on the energy expense involved in travel. That is where the real energy saving lies.

GRAPA-XiT Advertising

RA consultancy XiT fired out a promotional email yesterday - to all the members of the not-for-profit Global Revenue Assurance Practitioners Association (GRAPA). I guess it is no surprise that the membership list of GRAPA has ended up being used to boost sales at XiT, given that the boss of XiT is also the President of GRAPA. What is surprising is that XiT is already trying to enhance its sales pitch by claiming its products are based on GRAPA intellectual property. According to the XiT website, amongst the "unique assets" being sold by XiT are "industry standard benchmarks in cooperation with GRAPA". Which I guess means that GRAPA benchmarking must now be up and running for its members. No wonder that the person who tipped me off about the marketing spam from XiT is a little bemused: he has been waiting over a month for his GRAPA registration to come through ;)

Head of State Talks Revenue Assurance

On Monday, Philippine President Gloria Macapagal-Arroyo used the phrase "revenue assurance" in her 2007 State of the Nation Address. This may well be the first time that a Head of State has used the phrase in an official speech. Although this was a confirmation of an earlier Philippine government announcement about improving tax collection, the inspiration clearly came from the telecommunications and technology sector. The reference to revenue assurance was in a section of the address dedicated to how telecommunications and technology is driving the Philippine economy. This was what President Arroyo said:

Information technology will help the BIR bring in more taxes in the coming months. Its Revenue Watch Dashboard will monitor revenue collections in real time from the national level down to the examiners. The LGU Revenue Assurance shares information between the BIR and the LGUs to uncover fraud and non-payment...

In the same segment, President Arroyo also reflected on the fact that the Philippines had become a top off-shoring hub. Her emphasis was on maintaining the rapid growth in the business services sector by upskilling the services offered. She also commented on significant investment in new undersea broadband links to mitigate the risk of a natural disaster interrupting existing links via Taiwan.

That a Head of State for a developing country should use a phrase borrowed from telecoms should be no surprise. Changes in the world economy are being driven by technology "leapfrogging", where developing countries skip stages of technology implementation that the developed world went through. The simplest example is the high penetration of mobile in countries with poor fixed-line infrastructure. Rolling out mobile networks is simply more cost-effective than running lots of cables everywhere. Leapfrogging enables the developing world to close the gap on rich economies more rapidly. Levering new technology gives a superior infrastructure for business whilst also enabling direct competition for jobs with workers in the developed world. Take a look at this presentation which gives a summary of the economic growth caused by telecoms in the developed and developing world. It clearly highlights how telecoms is helping the developing world to catch up. It also shows that the higher rate of growth in developing countries like the Philippines correlates to higher rates of telecoms penetration. Modern electronic communications should be a priority for any leader in the developing world. So it is no wonder if a leader's thinking may also be influenced by the technology sector. If that means learning a few lessons from revenue assurance, and delivering systems and processes that are fast, efficient and accurate, that must be a good thing.

Vodafone Under Water

Flooding in the UK may not seem like the biggest issue in telcos, but it brings into stark relief the importance of business continuity planning no matter where you are or what you do. Take a look at these clips of the flood waters at Vodafone HQ.

Look here for more on the story of floodings at the headquarters of Vodafone and also 3.

You have to hope that if any business could cope with natural calamities, it would be a telco. Remote working, robust infrastructure, engineers ready to get equipment going again at short notice - all should help Vodafone keep working with only minimal disruption. According to some predictions, the world's weather seems set to become more extreme. Telcos need to be at the forefront of planning for the risks not only to secure their revenues, but also to support vital services.

At least there was some good news for Vodafone. These video clips show that Vodafone's employees know how to use those fancy handsets!

Governments Get Assurance

The other day I joked about the perils of allowing a former telco revenue assurance man to plug the leaks in the UK tax system. Now I see the Philippine government has also adopted the revenue assurance mantra. In this announcement from the Philippine government you even see the same language being used as you would find in most telcos. It is peppered with references to dashboards, leakages and analytics. Perhaps that is no surprise in a nation where telco offshoring is a valuable source of income. And with an annual revenue take of US$19.53 billion, perhaps the Philippinos are ahead of the game in appreciating that a few leaks here and there soon adds up to a lot of money.

Who Are GRAPA? (a.k.a. "Splitters!")

Who are the Global Revenue Assurance Professionals Association (GRAPA)? Apparently that is the big question on everyone's lips. It says so in GRAPA's own June newsletter:

The number one question asked by GRAPA registrants around the world: "Who is behind GRAPA?"

I cannot argue with that. I have received half a dozen emails asking me just that question. So please please do not email me to ask who is GRAPA. GRAPA is nothing to do with me. But if you want the answer, here it is.

GRAPA = people employed by telcos + Rob Mattison's XiT consultancy

There you have it. Nice and simple. GRAPA is the half of the revenue assurance industry you can trust (i.e. people who work for telcos plus Rob Mattison and his XiT outfit) and not the half you cannot trust (nasty scary vendors and consultants who need to sell to telcos to pay the bills, apart from Rob Mattison and his XiT outfit).

I have nothing against Rob Mattison and his XiT outfit. I have seen him speak a couple of times and even met him once, though I doubt he would remember me. Certainly Rob does a good job of promoting himself around the world, but there is nothing wrong with that. He works for a living and seems to work very hard as far as I can tell. Fair play to him. He writes big books about revenue assurance. There is no harm in that. His relentless promotion of the topic is an overall aid to revenue assurance professionals like me, even if I do disagree with some of the detail. If he and his colleagues in XiT want to volunteer their time and money to set up a new vehicle for their ambitions, I have no objection. However, am I a little bit annoyed that he set up a group for revenue assurance professionals that excludes me? Yeah, I find that annoying.

I mean, I do not think I am evil. Perhaps I am. There is a fair share of people on either side of the love/hate Eric Priezkalns divide, so I will avoid stating an opinion about who is in the majority. Certainly I have been guilty of shooting my mouth off pretty freely at times. I prefer to describe myself as "plain speaking" or "straight talking". But if I am evil, it is not because of how I make my money. I used to be employed by a telco. I was working for a telco less than 2 years ago. When I worked for a telco I poured time into the TeleManagement Forum's revenue assurance program. Plenty of vendors benefited but I did not complain. I kept on working with the TMF even when I changed job from one telco to another. Now I have stopped working for a telco and work freelance, but I still continue to spend lots of time on that same TMF program. For example, writing this blog helps me put off the painful chore of reformatting an MS Word document to be consistent with a TMF template. Not very glamorous. Not as glamorous as sending out newsletters or appointing myself as Mr. President or videotaping Presidential addresses. It is just part of the ongoing saga to rework the revenue assurance maturity model. That will hopefully lead to a new maturity assessment tool and benchmark being offered soon. That effort has been spread across four years of my life, because I, like others, volunteer to do it in my spare time. It is also slow because it involves genuine collaboration, which means disagreements and compromises. My travails may end soon or they may continue. Sometimes it is hard to maintain my enthusiasm. However you look at it, that effort started out when I was working for a telco and continues today even though I no longer work for a telco. So, to my mind, there is something wrong with setting up a professional association that pretends people working for telcos can join and help whilst people working outside of telcos are bad and should be excluded (with the exception of Rob Mattison and XiT).

Some days I hate revenue assurance so much I do not want to have anything to do with it. Since the launch of GRAPA I have been having more days like that than usual. Rob says he needed to launch GRAPA because nobody provided a forum, but what was the TMF's RA discussion group for then? Rob says there is a need for GRAPA because nobody sets RA standards or offers benchmarks, which makes a nonsense of the work just done in the TMF, on a purely voluntary basis, to provide new standard RA KPIs and benchmarks. Rob says he wants a professional body for revenue assurance like those for accountants and doctors. I am an accountant. Unlike GRAPA, my professional body does not discriminate on the basis of my employer. I remain an accountant and a member of my professional body whether I work in industry or work for an accounting practice.

When I joined the TMF's revenue assurance effort, I may have been more of an idealist than I am today. I was not shy to point out at their first meeting the shortage of people employed by telcos; I was the only one. I have done my share of plain speaking about the token involvement of telcos in the work the team has done since. I have been guilty of straight talk whenever I thought vendors were co-opting the team's agenda. But somehow or other they have not thrown me out yet and I still keep trying to work with them. There are lots of obstacles for telco employees to work with the TMF's team, especially the costs. But rules is rules and I do not make the rules for the TMF. So the upshot has been a collaborative effort dominated by vendors with very limited involvement from telcos. Which is a shame. However, even when there were absolutely no barriers to telco involvement in the TMF's work, telcos still did not get involved. There is a perfectly good web forum provided by the TMF for free. But the number of posts from telcos to the revenue assurance discussion group is negligible. And 99% of those posts from telcos are of the "can someone tell me how to do something/give me free advice" variety. In short, the posts included a lot more questions than answers. And if an answer was posted to a question from a telco, chances are the answer came from a vendor. Maybe sometimes those answers were biased, but at least that is better than nothing.

I applaud Rob for trying to set up a association based on the idea of people freely volunteering their time and knowledge, even if the volunteers who do all the admin are strangely identical to the people on the payroll at his XiT consultancy. But all the data tells us that altruists who give up their time and knowledge for free, with nothing to gain, are very rare indeed. Statistically speaking, they are freaks. From my experience at the TeleManagement Forum, revenue assurance is no different from other activities looking for volunteers. You have to apply the 1% rule. For every 100 people who sign up, look on, or reads, only 1 person will be active, contribute and write. The internet age has offered up many interesting new sources of quantifiable data on how people work in collaborative groups. Some examples revolve around the encyclopedia Wikipedia. You can debate the stats on the distribution of contributors to Wikipedia (see here for a good discussion of just that topic) but on the whole it seems that a tiny proportion of a volunteer community do most of the work, whilst a larger minority may contribute to one or two things where they have specialist skills and talents. So splitting the community of professionals into two and excluding 50% at the outset looks like a bad start if you want to access the small band of people who give away something for nothing. Most people do not give away something for nothing, and the people behind GRAPA have yet to show they are any different.

The formation of GRAPA looks set to divide the revenue assurance community, not aid it. On one side, you have the all-new GRAPA, including all the telcos, Rob Mattison and XiT. They have no money and little incentive to be charitable, with the obvious exception of Rob and XiT who appear to be bankrolling GRAPA so far (somebody has to be paying for the software, website, legal costs and press releases). On the other side, you have the TMF's existing revenue assurance community but now with added Global Billing Association (do not ask me about the implications of that either - but at least it shows you can have mergers as well as splits). They are dominated by vendors and consultants, have some money, have done some stuff already, but telcos often steer clear because it is too costly to get involved or they fear they will become a sales target.

I notice that XiT is not listed as a member of the TMF. That is very confusing as the XiT homepage says they advise clients on following the Telecommunication (sic) Management Forum's eTOM process standard. So Rob is aware of the TMF and its role in setting standards; it is a shame he decided not to get involved in the RA standard-setting initiative that the TMF started years ago. Probably Rob set up GRAPA because it was cheaper to create a new association from scratch than pay the TMF's membership fees ;)

There is an hilarious sequence in Monty Python's Life of Brian that is all about the rivalry between various groups. They all have the same goal (to overthrow the Romans), but they cannot agree to work together. Instead they despise each other for being "splitters".*

* Warning: I am not trying to make any point about any religion here and certainly do not want to upset anyone - I just think it is funny. And excuse the bad language too.


REG: Right. You're in. Listen. The only people we hate more than the Romans are the fucking Judean People's Front.
P.F.J.: Yeah...
JUDITH: Splitters.
P.F.J.: Splitters...
FRANCIS: And the Judean Popular People's Front.
P.F.J.: Yeah. Oh, yeah. Splitters. Splitters...
LORETTA: And the People's Front of Judea.
P.F.J.: Yeah. Splitters. Splitters...
REG: What?
LORETTA: The People's Front of Judea. Splitters.
REG: We're the People's Front of Judea!
LORETTA: Oh. I thought we were the Popular Front.
REG: People's Front! C-huh.
FRANCIS: Whatever happened to the Popular Front, Reg?
REG: He's over there.
popular_front_splitters.jpg
P.F.J.: Splitter!

So painful though it often is, I believe we have to find a way to bury our differences, avoid the splits, and get along. GRAPA needs to open it doors to all revenue assurance professionals, including the good people working for the many small and big businesses selling advice, equipment and software to telcos. Benjamin Franklin had loftier concerns, but I think his words also apply to revenue assurance professionals, however they pay the bills:

"We must all hang together, or, most assuredly, we shall all hang separately."

And finally, with teeth gritted, in the spirit of hanging together, here are all the relevant links, including the ones to my competitors and to industry associations that I cannot join....

GRAPA
XiT
The TM Forum's revenue assurance community discussion group
The TM Forum's revenue assurance team

Revenue Assurance KPIs

There are a few problems with setting generic Key Performance Indicators (KPIs) for revenue assurance in telcos. First, nobody can agree what they should be. Second, even if they could agree, they would not suit every kind of telco business. Third, even if they did suit every kind of business, most of them do not have all the data to calculate their performance. However, the TM Forum's RA team has gamely battled on with a project to standardise RA KPIs all the same. Never slow to jump on the TMF RA standards bandwagon (in fact, they are normally the ones steering them), RA vendor cVidya has incorporated the TMF's RA KPIs into its offerings. In fact, cVidya has been so fast that the TMF cannot keep up: I can find no sign of the new KPIs on the TMF's website yet. So one business has adopted the standard. The problem with standards, though, is that they are not really standards until most people have adopted them. We shall have to see if others follow suit.

One Customer, Many Devices

Thanks to Mark DiCamillo of Primal Solutions who posted a very interesting comment to an old blog on assuring WiMax. As Mark points out, our understanding of the relationship between customer, device and network is changing. The usual rule is that one subscriber has one device on one network. This means you can identify fraud by detecting when multiple devices in different locations are using the same customer's account. But the rise of Municipal Wi-Fi, coupled with the proliferation of Wi-Fi enabled devices, challenges the preconception. Customers should reasonably expect to keep just one account whilst sharing allowances, charges, etc across multiple laptops, phones and whatever. But whilst customer expectations will force the industry to offer multi-device subscriptions, it poses a big threat in terms of revenues. For a start, prevention of fraud will need to become more sophisticated to stop criminals from posing as genuine customers. But perhaps more importantly, revenues may be seriously eroded by something far less sinister: the natural tendency to share. A large portion of the market may prefer to have one subscription, in one name, but to share the service between husband and wife, parents and children. Mobile phones made it common for everybody to have their own number, but you can imagine that people would be willing to return to a model where there is a single number per household. It may be pot luck who picks up the phone first, but that may be small inconvenience when compared to the reduction in bills. So charging models are also going to have to become more sophisticated to enable telcos to get a fair return when servicing large households. Despite predictions from Arun Sarin and co that flat-rate monthly charges will become universal, there may still be need for telcos to keep counting the usage.

Her Majesty's Revenue Leakage

Businesses spend a lot of time worrying about revenue. But as individuals we all need to worry about Revenue with a capital R, by which I mean the taxman. If you think telcos have a bad time keeping a track of all those transactions, feel some pity for Her Majesty's Revenue and Customs (HMRC) a.k.a. the UK taxman. The latest figures from the National Audit Office show that fraud and error in the UK tax credit system caused losses of around UK£1bn during 2004/05. Here is the story from the BBC. Of course, the new prime minister, Gordon Brown, may try to argue that is actually good news. For a start, he could point out that the original overpayments were UK£1.8bn, which I guess means HMRC eventually clawed about half of the overpayments back. Or he could say the figures represent a big improvement on previous years. According to The Guardian, well over UK£9bn has been lost in the four years since Gordon Brown, then Chancellor, first introduced the tax credits scheme. But if I was Gordon I would point out that a cool billion represents leakage of less than 0.25%. Per the Public Finances Databank, the taxman's net collections for 2004/05 totaled UK£427bn.

Tax has a lot in common with telcos. They both involve complicated and obscure rules to work out who owes what. They both deal with lots of transactions with lots of people. They are both very unpopular. They both generate lots of complaints. They are both prone to attack from fraudsters and both have problems with collection. They both spend lots of money on IT systems only to find that their data is all messed up. So perhaps the taxman should hire some telco experts to run systems, clean data and stop leaks. With 10,000 people now employed to work on tax credits, it might provide a useful refuge for telco employees worried about downsizing or off-shoring. But if telcos really do lose somewhere between 2% and 10% of revenues (as discussed in my last blog) then HMRC should avoid telco people like the plague. If the figures are to be believed, leakage of 0.25% means HMRC represents revenue assurace best practice when compared to telcos. Which means your typical telco guru is not good enough to deserve a job in the public sector. Now that is truly worrying.

Scandalous Advice from the Big Four

I was reading this interview with an Ernst & Young Director responsible for risk management and revenue assurance, and I did not know whether to laugh or cry. Maybe the journalist mixed everything up. Maybe some quotes are out of context. But it sounds strangely like the same mix of good and bad advice that the Big 4 has offered for years. To put it plainly, I think it is shameful to see a Big 4 representative confusing the distinct topics of accounting integrity and business profitability. But when the Big 4 starts talking about corporate governance and revenue assurance in the same sentence, that is what routinely happens.

Now, we all know that revenue assurance has something to do with revenues. The clue is in the name. For the most part, it is about employing people to do things that increase revenues. So far, so uncontroversial. You may also have read about, heard about, or know someone responsible for accounting scandals. Most scandals are to do with exaggerating revenues. Pretty straightforward. Which is why I struggle to see why the Big 4 are so keen to link revenue assurance to corporate governance via the fear of accounting scandals. Because you do not need to be an accounting sophisticate to see that services sold on the promise of increasing revenues may be ill-suited to stopping the dishonest exaggeration of those revenues. But the Big 4 turns a blind eye to this contradiction. They do so to either to increase their sales as business advisers, or to mitigate some of the risk they bear as auditors by putting extra, but ineffective, burdens on their clients. Either way, they have lost objectivity.

The article begins by referring to recent accounting scandals. In this case, the context is Malaysian and the businesses are Transmile Group Bhd and Megan Media Holdings Bhd
. As is the norm for these scandals, both businesses employed dishonest individuals who falsified and mispresented transactions in order to boost revenue numbers. Our E&Y Director observes that businesses need to manage risk and try to prevent fraud, and he will get no argument from me on either score. He then goes on to say:

"As part of good governance, executives must be able to say they have full control over revenue figures and are not leaking revenue all over the place...

Having a framework for risk management and revenue assurance not only plugs revenue leakage and maximises revenue, but also protects your brand."

Where do I begin in pulling this apart? Let us start with one important word: revenue. The word revenue has a different meaning when you are talking to different people. Accountants have a precise definition of the word, the rest of the world a rather less precise definition. Put simply, for an accountant to recognize revenue from a sale, there has to be reasonable confidence that the business will eventually get the cash owed to them. So in accounting scandals, dishonest people pretend that some cash will be coming, even though they know full well it is not. They may intend to leave the company before the irregularity is discovered. If some unexpected extra cash does turn up, they may get away with the crime by pushing a few numbers around and hoping nobody notices anything odd. However, if that cash does not turn up, you end up with a scandal, the restatement of accounts and quite possibly an insolvency. But most people use the word "revenue" in a much less precise way. They just mean "good stuff that we like". So when people talk about "revenue leakage" they mean "bad stuff we do not like". It is perfectly possible to accurately report the revenues in the accounts whilst also suffering very large "revenue leakages". Revenues are apples and revenue leakages are pears. Linking the accuracy of reporting revenues with the challenge of reducing revenue leakages is bogus. You might as well argue I cannot accurately report how many apples I have if I do not know how many pears I am losing.

In the phrase "revenue leakage" we are talking about what might be called "could have been revenue" or "should have been revenue" or "might have been revenue". For the accountant, it is only revenue when you can be confident it will eventually turn into cash. Confidence is important. Accountants are prudent. If they are worried that the cash will not come in, then they cannot count the revenue. So fixing a revenue leakage may never lead to revenues. Take a simple example. Imagine some sales data gets lost underneath the billing system or down the back of the sofa. The revenue assurance man looks around and finds it a year later. Hoorah! A leakage spotted and a pat on the back for him. Now all we need to do is to raise a backbill. Surely we can be sure we will get the money and hence claim the increase in revenues immediately? No. Perhaps we discovered the customer was a fraudster and we have no way of sending them a bill, never mind any hope of having it paid. Or the sales refer to lines that the customer did not know they had because the telco failed to keep and communicate proper inventory records, and the customer has since ordered and paid for alternate lines. That customer cannot be expected to pay twice because the telco's goof caused it to effectively supply the same service twice. There are 101 reasons why fixing the "revenue leakage" may not lead to extra revenues.

The important point here is prudence. When people say they lose 2%, 5%, 20%, 50% of their revenues in leakage, they are doing no such thing. They are losing exactly 0.0% of their revenues. You cannot lose something you never had in the first place. What they are losing is "could have been/should have been/might have been revenues", which is quite different. A revenue leakage is no different to a salesman who is rude to a customer and so loses a potential sale. If they had been a bit nicer they would have got the sale and the revenues would have been higher. But that is a big "if". Truth is, they were not nice and so they did not get the sale. Similarly with revenue leakages, if you had fixed some bug in some system you might have raised a bigger bill. But if the telco did not fix the bug, it did not raise a bigger bill and it did not get the revenue. Meanwhile, in the accounting world, the revenue figure reported is perfectly accurate irrespective of leakage, because it is supposed to exclude all those could have beens, maybes or ifs. So it is a confusion to suggest you need to fix revenue leakages to get accurate revenue reporting. Fixing revenue leakages is just about running a business well, in the same way that training staff not to be rude to customers is about running a business well. Calling it a "governance" issue gives it a mystique, but it is no more a governance issue than offering good customer service or motivating employees.

The next, more serious observation about the quote above is that the emphasis is all wrong. Risk management is supposed to be driven by risk. The clue is in the name again. Risk has a direction, because people are inclined to do naughty things one way, but not the other. An employee stealing company property is a risk. An employee making a charitable donation to the company is not a risk. Accurate financial reporting is about telling the shareholders how much revenue has been earned. The risk is that the revenues are exaggerated because execs, managers and employees may get rewarded for good results and fired for bad results (I can think of situations where execs might want to understate revenues, but they are the exception to the rule). So good risk management will focus on controls to prevent overstatement of revenues. However, in the quote we get an explicit reference to maximisation of revenue. How odd is this? In less than a few sentences we have done a complete u-turn. Taking the example of businesses with inadequate controls to prevent overstatement of revenues, we end up with an argument for spending time and effort on activities to increase revenues. Admittedly, these are sometimes one and the same, but often they are not. From a governance perspective, shareholders want the revenues reported in the accounts to be no more maximised than they want them minimised. What they want first and foremost is accuracy and reliability. The risks of inaccurate financial reporting are distinct from operational risks related to poor data integrity. One is about the deliberate intention to deceive. The other is about data processing errors that nobody is aware of or responsible for correcting. Safeguards to prevent dishonesty have little to do with safeguards over processing.

Imagine you are an exec (or if you are an exec, just read on). What is the risk if you understate revenues? You wake up one morning and discover that because of some screw-up the company has more cash in the bank than expected. You quickly work out where all the extra cash came from, or at least dream up a plausible story. You tell the shareholders and they seem very happy. The sun shines on the nice new car you buy to celebrate.

What is the risk if you overstate revenues? You wake up one morning and discover you are Bernie Ebbers. You can ask for parole in 2028, when you will be 85 years old. The sun shines through the bars of your prison cell.

Being lousy at running a business is not a crime. Lying to the owners of the business by making up numbers that make the business look healthier is a crime. Revenue assurance helps execs run businesses better. Corporate governance scandals are about a failure of honesty. Linking the two by saying there is a simple win-win relationship betweeen revenue assurance and corporate governance is wrong. The Big 4 sometimes do not draw a line between being accountants and being business advisers. As accountants they should be mindful of their responsibility to shareholders, whose goal is accurate reporting so they make informed investment decisions. As business advisers they market their services to executives, whose goal is to enhance business performance. These interests are not harmonious. That is why we have financial audits, and hence why we have the Big 4 accounting firms. Excessive attention on increasing apparent shareholder returns and insufficient concern for controls over reporting leads to dishonesty. Trying too hard to devise solutions to improve performance and increase control at the same time will put one or both of those goals in jeopardy.

Poor old Bernie Ebbers. During his trial, the lawyers for the former Worldcom boss deployed an "aw shucks" defence. They argued that Bernie was an old-fashioned cowboy. They said he did not understand accounts and numbers and stuff like that. Well, he has a lot of time to learn about them now, because that argument did not impress anyone. But if there is any risk that CEOs really are so daft, you would think the Big 4 should try to avoid giving daft advice to them. But that is exactly what they do.

Of course, I could criticise all those revenue assurance vendors who claim that implementing their software enhances corporate governance. I could, but I will not. The people they employ to sell their products are not qualified accountants. It must be very tempting to simply repeat what they hear elsewhere. No, the criticism belongs with the Big 4 and accountants who are the source for these claims. They are responsible for creating spurious connections where none exist. Or at least, they are guilty of not correcting the basic mistakes in understanding that take place in their presence.

To be fair, the article also talks about overcharging. Which is rather the point. So why talk about maximising revenues whilst also admitting that you need to implement revenue assurance controls to prevent overcharging? Fixing overcharging could just as well be described as minimising revenues. Why set a biased expectation that revenue integrity will lead to increased revenues when there is an acknowledged possibility that revenues may fall as a result of correcting overcharging errors previously missed by both the business and its customers? The article also discusses the prevention of fraud. But again, the frauds described have nothing to do with financial reporting scandals. The examples given did not involve the accounts; they are all revenue neutral. They all involve crimes where no additional revenue had been recognised by the business and where the fraudsters would never have intended to pay for the services acquired anyhow.

There are three kinds of lies: lies, damned lies, and statistics said Disraeli. 90% of statistics are made up goes an old joke. In the article, our director describes estimates of telco revenue leakage between 2% and 10% as "research". Ahem. What were we talking about, again? Risk, bias, misreporting and that kind of thing. So what is this research he refers to? Surveys of estimates made by people who get paid to fix revenue loss. No risk of bias there then ;) Better still we find out that a good risk management and revenue assurance framework could cut those leakages by half [my emphasis]. :D Hilarious. I had a good laugh about that. I mean, where does that stat come from? And why only by half? Why not more? Is that half of 2% or half of 10%? This director's dictionary must omit the word "irony". It is perverse to make up phony business statistics in an interview seemingly about accurate reporting and good corporate governance.

This interview was with a director from E&Y, but I do not mean to pick on E&Y. You could level these criticisms at most of what the Big 4 says about the link between revenue assurance and corporate governance. I was browsing the web a short while back and I stumbled across KPMG's micro-site for "Margin Enhancement" (which is code for "revenue assurance but even better!"). It does not look like it has been updated for a while, but has some interesting content (one article described itself as an "advertorial" - is that like "infotainment"?) One download in particular grabbed my eye, because it was the slides for a presentation I had attended back in 2005. It was a panel discussion of the linkages between revenue assurance and Sarbanes-Oxley, hosted by KPMG and including a panel of three leading personalities from telco revenue assurance. After a half hour of listening to KPMG spiel on how well the two complemented each other, with not a mention of the possible conflicts between the two, you can imagine how keen I was to throw a spanner in the works. Luckily I got my chance when I asked the panel to answer, in a word, whether complying with SOX now meant they had eliminated all material revenue leakages. To their credit, all three telco panelists - Lionel Dawson of O2, Patrick Halbach of Qwest and Moly McMillan of ntl, answered the question frankly with a resolute "no!" Which only begged the question of how much advantage there really is in trying to link the objectives of revenue assurance to those of good corporate governance. The most useful synergy is in marketing for the Big 4 - if they cannot sell their services by promising it will deliver compliance with obligations, they sell it by promising extra revenues.

The scandal here is that a business can decide to invest in enhancing profits or in better governance, but they cannot have two for the price of one. The Big 4's pretension to offer both at the same time is a folly. There are as many conflicts as synergies. Motivating people to increase revenues is good for business, but the essential problem is that some people also become motivated to cheat. Programs to install safeguards over accurate reporting cannot start out on the pretext that higher revenues will follow as a natural consequence. And programs to increase revenues will not eliminate the worst kinds of misreporting. Shame on the Big 4 for not saying that.

Patni Acquires Logan-Orviss

The centre of gravity for the telecoms industry continues to move eastwards. Patni Computer Systems, headquartered in Mumbai, has just purchased the European telecoms consultancy Logan Orviss International. With Patni's 2006 annual revenues of US$569m dwarfing LOI's US$16m, the intention must be to enhance the profits and sales potential of Patni's IT services by using LOI to open up new opportunities. Here is the press release on both the Patni and LOI sites.

Indigestible Taxes

Billing can be complicated. Taxes are usually complicated. Mix billing and taxes into a spaghetti of rules, systems and processes and you might find yourself in a stew. Add a spoonful of reliance on a business with a poor attitude towards data integrity. Then add a dash of the usual lack of internal controls within telcos. You get a recipe that left some Qwest customers being charged too much sales tax. Well done to Margaret Smith, the local county official in Spokane County, Washington, USA, who unraveled the mess. Because of her hard work, Qwest will be serving up a refund. Read the story here and here.

The Grudge

In this day and age, software to weed out spam is a must. The only problem is that it is never fool-proof. You have to be careful that genuine mail does not get deleted with the junk. So I still have to check my junk folders on a regular basis. A quick look today in the junk folder shows the usual assortment promising to make me more attractive, forward me the proceeds of a Nigerian banking transaction, increase my "potency", and sell me cheap software. Ho-hum. But what is this? It is an advert for revenue assurance software. An unsolicited and unwanted advert from a business I did not know existed. So what should I do? Should I

  1. just delete it and not waste my time worrying about it?
  2. or
  3. write a blog about it?

Unlike most people, I opt for (2). Fortunately, it says I can unsubscribe at the bottom of this first email, thus avoiding the "series of short emails" that I am promised would otherwise follow. So I do unsubscribe. But, sucker that I am, I still feel compelled to check out the company's website. It turns out they sell the first software engine that blah blah saves millions blah blah marketing guff. That is a cleverly worded claim. I do not know if they really were the first (though I have my suspicions), but they are certainly not the only ones to offer a product like this. I think straight off the top of my head of a few rivals selling very similar kinds of tools. I check out the date of when they attained this "first", and it was this year. Ummmm. Without doing lots of investigation I cannot work out why they think they were first at anything. Perhaps in the long sentence describing the product there is some feature they feel is unique to their offering. Or perhaps they have no idea (and do not care) if anyone else offers something similar. After all, it is not like there is a simple industry-wide product index that tells you who makes what.

The question that is still bugging me, of course, is where did they get my email address from? Or rather, how did I became a subscriber to these blasted marketing emails? There are lists floating around with my name on it, of course. I am not just talking about the lists written in shaky handwriting that begin with "come the revolution..." or "first against the wall..." and which have doodles in the margin of me suffering some gruesome form of torture. I know about those of course. It gives me great satisfaction to be at the top of so many of those lists ;) No, I mean the ones with lots of contact details that get sold to a certain kind of telecoms vendor so they can cold call or send me junk in the post. Perhaps this firm bought one of those lists. It would certainly fit with their company motto (here is where the bright sparks amongst you can work out who spammed me) which is "competitive advantage from data". Rather. But does blasting out unwanted marketing material work? Or is it counterproductive?

Here is some games theory from my university days. Take a population with a finite number of people. Any person can do a favour for anyone else. A favour is not a zero-sum transaction: the recipient benefits by more than the amount it costs the giver. Favours never happen simultaneously. Because only one can happen at a time, it means if two people swap favours, then someone has to go first. Divide the people into one of two characters: good people do favours at random, bad people receive favours and never do any. Who wins the game? You got it. The bad people. Because they receive charitable favours, but never give them, they win. So how do you change the rules so the good people win? Well, one way is to give them a memory - let the good people remember who paid back and who did not. Then, also let them hold grudges, so they never do favours to people who have not paid them back for a previous favour. If the population is relatively small, and you play the game long enough, the grudge-bearing good people will eventually win, because they keep doing more and more favours for each other but never do more than one favour per bad person. If you then add another feature, allowing grudge-bearing good people to share information on their grudges, and to act collectively, they win the game faster. Because the grudge-bearing good people have some knowledge of who will not pay back, even before they give a favour, they reduce the number of favours given to bad people. That is what I think of when I hear the phrase "competitive advantage from data".

You can drastically change the outcomes of a game by playing with the mix of good, bad, grudge-bearers and non-grudge-bearers, or by introducing in some or all a probability of being "good" or "bad" or of bearing a grudge. Which strategy is best will depend on the strategies being played by others. So which strategy should I apply to the junk email revenue assurance software company? Should I bear a grudge? Or should I (forgive and) forget? Should I share info about them, or keep it to myself? If I forget and do nothing, that means blasting out unwanted marketing material does work - because of the possible upside but with no downside. On the other hand, this being the real world, if I bear a grudge and share it with others, I know that others may not really care, and that more likely it will just rebound on me ten-fold. So it feels like my world (at least in terms of revenue assurance) is very uncharitable: do not expect favours and do not give out favours probably being a better strategy for "success" than looking to trade favours and then holding grudges against the "bad" guys. But that means we cannot have such things as collective data - the ability to readily share information. Which is going to make it harder and slower to improve, as it means everybody has to learn from their own experience, and their own mistakes. What a very uncharitable bunch we are.

And then, as I am finishing off this entry, I hear the postman at the door. "What junk mail am I getting now?" I think to myself. This time it is not an invite to a conference where I can learn from the usual bunch of industry thought leaders and operator case studies. Instead, it turns out to be a letter from Oxfam telling me of people that depend on rain that may not come. I am suitably chastened by this reminder that there is a very important place for charity after all, and that there are some distribution lists I am happy to be on. Which put it all into perspective.

The Other Side of the Coin

For every person working to help telcos make more money from their customers, there is somebody working for the customers trying to find ways to spend less. Telecoms Expense Management (TEM) is revenue assurance through the looking-glass. What you see in one world is just a reflection of what you see in the other. So it is fascinating to read this story written from the TEM perspective. It says that the average business could reduce the cost of its telecoms services by 20%. If true, that means telcos would see their revenues from business customers fall by 20%. Perhaps the best form of revenue protection would be to speak to customers before they turn to a TEM consultant for advice. But how would you measure the value of that? ;)