Author Archives: thedoctor

Why You Have to Find that Fraud in Big Spend Stacks …

We recently published a piece on how it’s hard to find fraud in big spend stacks, and it is an important one. While fraud in most organizations might be relatively small, and might be mostly controllable by the right culture, processes, and systems (but that’s a subject for a future post), it’s still going to be there, and the most common form of fraud you are not going to detect is collusion fraud.

But this can be the most costly. Let’s say Bill and Ted both have invoice approval rights in the services procurement system and can singlehandedly approve services procurements up to 20K. Let’s say Bill’s buddy Bob has a services firm and let’s say Ted’s buddy Tim also has a services firm. Let’s also say that the organization also has a great need for temporary contingent labour to man the warehouse, clean the offices, and guard the assets of the company.

Let’s say that oversight of these services is left up to the approver for verification. Let’s say that Tim routinely sends two services guards when the general policy is to have three guards on duty and that Bob typically sends only two janitors to do the work that would typically be done by four by the old services provider. Who’s to say that Tim doesn’t send two guards but bill for three? And who’s to say that Bob doesn’t send two janitors and bill for four? And if these invoices are sent bi-weekly, they are going to fall well within approval limits.

Moreover, who’s to say that Ted doesn’t know about Tim’s over-billing and Bill doesn’t know about Bob’s over-billing? And who’s to say that Bill and Ted don’t have a deal to approve the over-billings for each other because their wives are getting an “efficiency consulting” fee from Tim and Bob’s companies?

Maybe this doesn’t happen in your company, but it happens more than one thinks, and just because you never detected this, how do you know it’s not happening? Invoices from real suppliers for real services at approved rates can still contain fraudulent over-billings for services not actually delivered, and those proceeds can still be partially kicked back through indirect channels to organizational employees.

But how do you detect this? Very sophisticated AI-based algorithms that detect unusually high approval patterns between two organizational employees, for amounts that should have been reduced with new contracts, that don’t match typical, anonymized, organizational patterns. And then human investigation to find the truth.

So why is this so important? Besides plugging the leaks? Because if you can’t find internal collusion, how will you ever detect potential cases of external collusion? And gather enough corroborating evidence to at least get an investigation going? If industries collude, and jack prices above market prices, the organization will lose considerably more than it will lose to Bill and Ted (from the evil, parallel, universe). And this happens more than you think too, it just doesn’t always get detected and investigated. Fortunately, sometimes it does, and sometimes, even if there is no certainty that fraud happens, regulators, presented with enough evidence still investigate — like they are doing now among the German automakers (which led to a surprise raid on BMW headquarters as recently reported in the New York Times) that are suspected of conspiring to hold down the prices of crucial technology (as initially reported in July). Regardless of the outcome, technology that can identify potential fraud and gather correlating evidence will keep everyone more honest, and that’s a good thing.

Are You Doing Your Own Quality Spot Checks? And Should You Be?

By now, if you haven’t heard of the Kobe Steel Scandal, you’ve been living in a cave. (Which, in some organizations, is highly probably given that one of the tricks the CFO likes to do to Procurement when fiscal year end is approaching is to lock them in the basement until the mandatory savings objective is reached … hence our post yesterday on why every day is Halloween for some Procurement departments.).

This scandal is scary. Not only because the data falsification on strength could go back as far as 10 years on some batches, and who knows what bridges, high-rises, and busses that steel has gotten into (and even a .1 degradation, while not enough to jeopardize immediate safety, can impact expected life span and increase susceptibility to decay, making safety a concern down the road before inspection and maintenance schedules kick in).

But this brings up a good point? If more companies were doing more spot checks on shipped product and quality, instead of just trusting Kobe, would it have been 10 years before the scandal was exposed. Even if only a small percent of batches are affected, I highly doubt this would have been undetected for 10 years, even if only one bar or sheet in multiple shipments were tested.

This is an example of what happens when finance tries to get too greed or supply chains to lean by centralizing a function downstream. When one party is responsible for everything, one failure can reverberate up multiple chains undetected — and have potentially disasterous consequences. Now one might say this problem is solved by co-locating people on-site, but if those people never leave the site, even though you pay their salary, their work family is the people they work with day in and ay out and the existence of that company is their livelihood. Are you sure they won’t bow into the local culture and, if the culture dictates, defer to authority or collectively hide the shame?

Just like third party audits are needed, for critical materials, so are third party quality tests. Doesn’t have to be you, could be an independent organization set up between your co-opetition that does random independent quality spot-checks on 1 in 10 shipments and shares the data with everyone.

Just like a good Chef would never use an ingredient without insuring it’s quality, a good Procurement organization should never let a shipment be accepted without a high degree of confidence that it’s a quality shipment. And confidence like that only comes from organizational testing or trusted third-party independent testing. So don’t get too lean or too cheap — your organization, and the lives of its customers, could depend on it.

For Some Procurement Departments, Every Day Is Halloween!

A week from tomorrow is Halloween. While until recently meant to celebrate All Hallows’ Day, it’s common observance today is to provide an opportunity for kids to trck-or-treat, high school and college students to throw parties, and adults who miss their childhood an opportunity to play dress-up once again.

As part of this festival of tricks and treats, celebrants (regardless of religion), will carve pumpkins into jack-o’-lanterns, light bonfires, bob for apples, attempt to divine (and contact the dead), play pranks, purposefully visited haunted attractions (whether supposed to be fake or real), tell scary stories, and even watch horror films.

But for some Procurement departments, this is every day. Every day they are beaten up by the CFO and feel like they are being carved up like jack-o’-lanterns as their performance is dissected with biology lab precision. (Performance that’s not as good as it should be since the CFO won’t let them buy the best tools.)

Stakeholders, who bring (new) requirements, are constantly lighting fires under the team at the last minute, not realizing that great results takes great planning, and that doesn’t happen overnight. That sometimes strategic acquisitions take 3 to 6 months of hard work to find and unlock the hidden value, and that one cannot expect miracles when Procurement, already at 100%, is asked to (re)source a category 30 days before contract termination (and the date was known 1065 days in advance when the last contract was signed without Procurement involvement.

Senior buyers are constantly bobbing for new opportunities, checking out random whims because they don’t have a modern spend analysis system to help them identify the best possibilities for savings. At some point they will get so desperate they will go to gypsy diviners in their quest to identify savings opportunities, and even ask to speak to dead business gurus of ages past.

They will feel like they are constantly being pranked by sales people as they won’t have the insight to build true-cost models, the IT dungeons they have to go to for help normalizing market data from the free feeds they have access to will feel like haunted houses, every new request made from them is a scary request, and their entire
existence feels like a horror movie.

And the scariest part of this story, is that it’s not just a few departments, it’s a sizeable number of Procurement departments. Remember, 40% don’t have modern Supply Management tools, and of those that do, the majority have major holes in the Source to Pay to Delivery Cycle.

So, CFO, this Halloween, only you can change Procurement’s existence by giving them a treat — the budget to acquire new systems next fiscal year. Trust me, Procurement needs them.

Want to Know Another Great Thing About SolutionMaps?

It doesn’t give broad, generic, totally useless Software Advice on categories so vague that they compare head-to-head vendors doing 3rd party logistics and vendors doing catalog based procurement!

SolutionMaps are on specific Supply (Chain) Management categories, that are precisely defined and tailored to a specific Sourcing, Procurement, or Supply Chain business process.  Right now, they are defined for e-Procurement (e-Pro), Invoice-to-Pay (I2P), and the broader Procure-to-Pay (P2P) areas, (Strategic) Sourcing, Analytics, SRM, and Contract Management with Contingent Workforce Management and Services in the pipeline.  Future areas may include GRC (Governance, Risk, and Compliance), Direct Sourcing (focussing on BoM, Should Cost Modelling, Production Planning, Etc.), WIMS (Warehouse and Inventory Management Systems), and Logistics/Freight Management.

We do not compare apples to oranges (as such a comparison is pretty useless) in SolutionMaps, but we definitely don’t compare apples to bananas, peaches, pears, and oranges in a single market basket.  They might all be fruit, but that’s about all they have in common.

Granted, there are analyst firms that think that pretty much all Supply Chain Management Solutions are the same.  One even has a big bold advertising page which says it can help you compare the following 12 vendors:

3PLCentral, Bellwether, CobbleStone, Coupa, CongaNovatus, ContractWorks, Deltek, Fishbowl, FreightView, Halo, Kinaxis, and Procurify.

If you ever compare more than any set of three of these at a time, either you don’t know what you’re doing or the advisors don’t know what they are doing.  These vendors fall into the falling seven distinct categories:

  • Business Intelligence
  • Contract Management
  • ERP
  • Freight Management
  • Procurement Software
  • Supply chain Management
  • Warehouse Management

SolutionMaps only evaluates vendors in a defined market segment, and then it only evaluates demoable product.  We know that some (not all) analyst firms review the solution component of vendors based largely off PowerPoint and other documents.  Given some of the hyperbole the marketing gurus at the market leaders can generate with the flick of the wrist, this is also quite scary.  Just because a new cloud-based SaaS solution can provide you with community intelligence, that doesn’t mean it does.  The crowd has to buy into the solution in order for its wisdom to be shared.  That usually takes time.  But forcing demos forces reviews on real functions, not perceived capabilities.

And, finally, as we hinted at in yesterday’s post, rose colored glasses have no influence on the scoring.  It doesn’t matter how much we like, or do not like, a vendor, it only matters whether or not they can meet the binary requirements to advance up the scoring scale.

SolutionMaps are based on the existence, or nonexistence, of functionality, in a well defined domain, tailored to real-world buyer needs.  And even the customer questions, and scores, are meaningful to other real world buyer needs.  SolutionMaps are different.  And that’s why they are awesome.

And if you adopt a SolutionMap methodology in evaluating your potential vendors, when asked how you came up with the best solution, you will be able to honestly say, “Because I’m Awesome”!