The Secret CFO

11.1K posts

The Secret CFO banner
The Secret CFO

The Secret CFO

@SecretCFO

Sharing real world insights as the former CFO of a multi-billion dollar company. Opinions, not advice.

Sign up to newsletter 👉🏻 Katılım Temmuz 2021
511 Takip Edilen128.7K Takipçiler
Sabitlenmiş Tweet
The Secret CFO
The Secret CFO@SecretCFO·
How did one VP of Finance bring Macy's to its knees with a $151M accounting scandal? Here’s how I think it all went down… (THREAD)
The Secret CFO tweet media
English
60
150
1.5K
902.4K
David Beck
David Beck@David_Beck_Atty·
As a restructuring lawyer, I have to say that @SecretCFO’s discussion of management compensation and retention incentives in yesterday’s newsletter was really good. His newsletter is worth reading not just for accountants, but for those of us in adjacent jobs also.
English
1
1
15
7K
The Secret CFO
The Secret CFO@SecretCFO·
@David_Beck_Atty David I appreciate that. It’s nice to know it passed muster with someone who knows what they are talking about!
English
0
0
5
1.3K
The Secret CFO
The Secret CFO@SecretCFO·
I'm more talking about the internal fabric of financial reporting and contrl. The more AI penetrates that (which it will) the more the review mode for CFOs will need to change. Seeing through bullshit from outsiders is certainly nothing new. That's been part of the job for CFOs forever. But dealing with it from 'insiders' will be new. interesting challenge.
English
1
0
2
243
The Crusty Old Man
The Crusty Old Man@TheCrustyOldMan·
@SecretCFO You have dealt with this before. They were called consultants. Those who blindly believed everything a consultant told them will struggle. Those who inspected and evaluated what they said with discernment will be fine.
English
1
0
1
277
The Secret CFO
The Secret CFO@SecretCFO·
CFOs are going to have to think differently when reviewing AI-produced work. Shit work performed by humans most often looks and smells like shit work. Easy to spot. Shit work performed by AI can look and smell like great work. Hallucinations delivered with confidence, beautiful formatting, fake citations, etc. That's a new threat model... one CFO’s aren’t used to. How CFO’s review work internally (THE core skill for serious CFOs) is going to have to evolve fast. Strap in... there will be plenty of embarrassing headlines before many figure this out.
English
19
8
121
16.5K
Josh Perera
Josh Perera@tourcontinues·
We have to get away from natural language prompting. That is the most inaccurate way to engage with an LLM. We can add the same workflows—footing against known truths—to AI that we ask of any analyst. We just need to adopt language that hasn’t historically been as relevant to corporate finance [markdown, JSON, etc]. Eventually, this will be unnecessary too, but until the tooling is ready, we have no choice if we want to extract maximum leverage and maintain accuracy.
English
1
0
1
494
Bobby Mays
Bobby Mays@Bobbymays·
@SecretCFO I’m just waiting for the first Fortune 500 company CFO that gets caught not properly reviewing the outputs 😬
English
1
0
2
379
The Secret CFO
The Secret CFO@SecretCFO·
A huge amount of time in the typical finance function is spent grinding. Spreadsheets and systems to get data in a format it can be useful. Location 1 codes payroll taxes to one code, location 2 to another code. Or the unit of measure is set in 1,000s instead of singles in a product masterfile somewhere, That creates manipulation work to produce quality information downstream. Multiply that by thousands of examples and it creates a whole industry.
English
0
0
1
81
The Secret CFO
The Secret CFO@SecretCFO·
Revisiting this one year on… and number 1 remains the single biggest opportunity for tech builders for corporate finance teams. And I don’t see anyone building it ?!
The Secret CFO@SecretCFO

There is so much low hanging fruit for AI in accounting and finance functions. Here are a few ideas for anyone with accounting domain expertise and the engineering skills to build: 1. Master Data Bleach Master data is a train wreck in most businesses; product data, customer data, inventory data, etc. The basics (i.e. prices, product codes, etc) are normally correct (because they have to be to get cash in and out), but the attributes that drive quality reporting are often inconsistent. This is often the limiting constraint on reporting (rather than reporting capability itself). And can be tens of thousands of records across hundreds of fields. So not easy to keep live. A bot that crawls all company master data looking for inconsistencies in naming, taxonomy, coding etc. And then produces a list of proposed changes, which are then reviewed by the human to accept or reject those changes. The bot then goes and makes the changes. It does this daily / weekly learning each time and improving it's accept %. Probably doesn't save any heads in master data management in the short term, as there will be an increased review workload. But this would unlock huge reporting capability and time savings downstream where the data is being worked many times at different touch points in the organization. Solve the problem at source. 2. Accounts Payable Support AP teams have to maintain contact centers to answer - what is normally - some variation of the question 'when will I get paid?' Quite a bit of the AP function has been automated through RPA bots over the last 15 years or so. (I.e. supplier statement reconciliations). But handling supplier queries and inbound has been mostly untouched. And hearing how fast voice powered AI is coming for customer call centers (first and second level support) - feels like a small leap to stretch this tech across to AP functions. I expect it will be slower on the accounts receivable team (B2B at least), because businesses will be more reluctant to hit their customers with AI generated outbound. (And the cost of a mistake is higher - i.e. don't get paid on time and it blows the cashflow up) 3. Automated Preparation of Annual Reports Preparing 10-K/Qs is a pain in the ass. There are a number of inputs. There are the numbers (which are jsut mapped from the GL). Then there is coordinating a good quality commentary (MD&A), making sure your risk factors are up to date. Control disclosure, regulatory changes, Etc. Different jurisdictions for multi-nationals. And the formatting is a pain too. There is a surprisingly large number of people involved. It's inefficient, and hard to bring together. So this would be cool ... A dedicated tool that takes previous annual reports, control reports, audit report, board packs, local regulation etc and prepares a draft of the annual report. It would asking any questions of management it needs to (as if it were the controller preparing it) and helps manage version control, and workflow to completion. It will still need verifying, but getting to a good quality first draft is most of the work - and crucially is the bit that takes time. 4. Contract Review & Payment Terms Optimization It's hard to track inconsistencies in terms and conditions across thousands of commercial contracts. So many times I've found $$$ left on the table thorugh inconsistencies. It's left me wondering "how many other contracts do we have where we've lost 15 days like this". I presume it would be easy to create an application to: a) review new contracts before approval to find inconsistencies with previous contracts / house terms b) review all contracts to synthesize where your procurement / sales teams are leaving money on the table I know what you are thinking... Chat GPT / Claude, etc can do this already. You just have to know how to prompt it, etc. Or there is already some software tool that does this. That misses the point. Outside of tech circles, no-one in accounting and finance teams are really thinking about AI. They are too busy doing what they've always done. They need the solution put into their hands that works perfectly alongside what they already have. It just needs to take some existing human work, and do it faster and better. Low friction roll out. These are also (by definition) the least efficient teams where all the people / cost savings are - i.e. it's where the money is. Plus there is the issue of needing a safe and compliant private environment on which to manage the data. This will be crucial for getting CFOs on board (who need to get theit baord and auditors comfortable with it.) So a static application / environment that is fool proof for the user (and in time can become trusted) is the key. Any other ideas? Forget the long term ... I know there are way more transformational ideas than the above. I'm interested here specifically on what could be at us VERY quickly... anything else?

English
13
2
46
37.4K
Dan Thompson
Dan Thompson@DanThompsonIV·
@SecretCFO 1/ Income statement variance every period for a department -> ai crawled general ledger and inventory control ledger to produce what I call chains of executions for specific transactions. Sorry I don’t know the accounting term. Found 3 issues combined to create the variance.
English
1
0
1
32
The Secret CFO
The Secret CFO@SecretCFO·
AI could definitely play a huge role in the feedback loop in improving core system data quality. Identifying transaction coding inconsistencies, product to account / cost center mapping etc. All of that stuff is handled typically a) manually b) badly and c) to great downstream cost (in information quality)
English
1
0
2
160
The Crusty Old Man
The Crusty Old Man@TheCrustyOldMan·
There are three big challenges with Master Data. AI doesn't really solve them. Ownership - The hardest part about Master Data is driving alignment on who gets to decide on the definition. Teams often use a definition that serves them best - that could mean it meets their unique needs or it could mean it makes them look good to others - and will fight tooth and nail to keep it. Detecting definition variances - I had an system integration project as a result of an acquisition that went 9 months before it was realized that a "closed" claim meant something different in the two companies. It was only detected when we walked through the claims life cycle for several products in detail. Teams had been talking past each other for months thinking they were agreeing when they weren't. The business rules with the differences are buried in legacy code in the front end systems, back end systems, and data integrations and transformations. Funding Master Data Initiatives - Federated teams don't "need" master data. They have the data they need to do their jobs. It only helps those dang centralized teams like Finance who need to combine the data from all the BU's. Why should a federated team pay for that (tor even dedicate precious SMEs to it) when it won't help them and will only change their world. Let Finance pay for it. What? Finance doesn't have their own P&L and wants to allocate the expense to me? What am I getting in return?
English
1
0
0
231
The Secret CFO
The Secret CFO@SecretCFO·
@SligoBrian1994 I’ll take the other side of this … Nested IF formulas are not the future of enterprise data integrity. Lol.
English
2
0
22
3.4K
brian
brian@SligoBrian1994·
Depends on the org really but data being a mess isn't actually that big of a hurdle for reporting, the best approach we had was to categorise P&L line items by nested IF of what we wanted to produce, you'd only have 30-40 PC/contract numbers to add per month to the master list
The Secret CFO@SecretCFO

Revisiting this one year on… and number 1 remains the single biggest opportunity for tech builders for corporate finance teams. And I don’t see anyone building it ?!

English
2
0
1
6.3K
Matt Arderne 🌊
Matt Arderne 🌊@mattarderne·
1 generalises to a problem that very few businesses get right and almost never solved by 3rd party tech companies occasionally do a good job of what you describe as an internal project, but it requires a very good data engineering team. I know someone tried to get a startup off the ground doing it. Not easy. Best ROI is a bespoke consulting project in most instances, maybe AI changes that
English
1
0
0
321
The Secret CFO
The Secret CFO@SecretCFO·
@prab_hub That’s because those are easy to build and don’t require domain expertise
English
1
0
1
226
Prabhu 🕊️
Prabhu 🕊️@prab_hub·
Is 4th problem of contract review and revenue leakage prevention still big pain point? Also, most people are busy building frontend and easy SaaS like social media schedulers or content generation tools. Nothing wrong with it but there is seriously lack of interest in back office automations for majority of builders.
English
1
0
0
332
The Secret CFO
The Secret CFO@SecretCFO·
That’s the key point imo. I’ve sat opposite private credit negotiating A&E deals a couple of times. It’s very tough. All the leverage for the credit house comes from the CFO and their Board believing that the shop could and would take the keys in a heartbeat. If scaling private credit has diluted that (and it makes sense it would). It’s a very different balance of power I think.
English
0
0
1
106
Edward Robson
Edward Robson@27XVII·
@OnlyCFO I agree, it's better to be conservative. However, let's be real, Golub doesn't want to take the keys. These credit shops lost their teeth when they focused on scalability over sustainability.
English
2
0
1
166
The Secret CFO
The Secret CFO@SecretCFO·
@27XVII Absolutely right. + it sets the incentive structure for some truly awful behavior, without any of the protection of the transparency requirements of public markets.
English
0
0
0
1.2K
Edward Robson
Edward Robson@27XVII·
The stay private for longer narrative, when combined with the push for retail to have access to private markets will structurally change how the IPO market operates in the future. If you expand access in the private markets, that will partially consume the exit liquidity provided by the public markets. Ultimately, you will need to see indices adds (e.g., S&P) to provide buying support from ETFs to ensure a strong launch. This is what SpaceX is pushing for.
Edward Robson@27XVII

Yet, we really believe the private markets are properly valuing assets today? Based on the momentum trade in private markets, with VC asset managers, all making concentrated bets into a handful of names. All of the complaints about PE and PC today will eventually come for the VC/GE asset classes. The liquidity constraints facing PC right now will eventually come for the large private companies (e.g., Stripe, Databricks). There will be a reckoning. Liquidity is priced at a premium now more than ever.

English
2
1
6
4.3K
The Crusty Old Man
The Crusty Old Man@TheCrustyOldMan·
Led enterprise data risk for 4 years at a Fortune 100 in a heavily regulated industry before retiring last year. It's long, but here was our journey. Foundational data monitoring & controls were always in place. Cyber, PII, education, etc. If not, really bad things can happen. Get the basics in place first. When ChatGPT hit, we manually monitored usage including PII & IP in the chats. Usage grew and we made the decision we wanted to encourage responsible experimentation. This was key to almost everything else we did. It had CEO-level alignment and was recognized future issues would arise because of it. When they did, the CEO didn't waiver and it was treated as a learning exercise and not a finger-pointing exercise and a reason to de-risk everything. First policy locked down ChatGPT access and required explicit approval and education before gaining access. Automated monitoring. Alternatives came on board. Aligned on closed solution for broad use. Locked down access to alternatives for most. Research use cases were approved by working group of the risk committee and discussed in risk committee. Use cases drove the development of a much more robust AI risk framework encompassing and balancing cyber, regulatory, legal, analytics and other risks. Controls existed for some risks but not for others. Controls that existed crossed teams and risk committees. Others like decision repeatabilty, defensibility, and proven non-discrimination needed more maturation, although existing standards and guidelines around things like model validation and drift provided the basis to build on. Enter a lot of cross-domain education, valid disagreements and perspectives, and yes, some turf wars. This was the long slog. Triaged use cases into "safe w/ agreed upon controls" and "more complex, needs discussion that will eventually lead to agreed upon controls" to keep most things moving while still having more focused insight on the "high risk" use cases. By the time I left we had about 80% of UC's going through the "safe" path and 20% going through the "more complex" path based on priority. Foundational controls were in place throughout the journey and continued to find unreported instances "in the wild" that need actions/decisions. Most recent was OpenClaw on some personal devices, networks, and even some side-loaded on work laptops. There is always something new emerging that will introduce new risk or work outside your controls. We made the decision we wanted to encourage responsible experimentation. Taking the lowest risk approach of locking everything down until we it completely controled wouldn't let us do that. Trusting eveyone to act responsibly also wasn't realistic and wouldn't hold up to external scrutiny. We tried to strike a balance. The multi-domain risk framework took time but got everyone up to speed and on the same page, or at least a page they could all live with. Not waiting until it was "done" allowed most work, and the most important work to move forward. We realized we had a lot of the needed foundation, it was just spread across a lot of different domains and no one had the complete picture. Based on my participation in data and analytic forums, most F100 firms touch on similar steps, although the order in which the attack them may be different depending on where they are starting, how their enterprise risk committees are organized, and organizational decision making dynamics. Some have the risk committees already. Some don't. Some are top-down decision oriented. Some are very federated. Seems like almost all eventually need to work through the cross-domain alignments. Huge variance on the length this took and when it was done based on the corporate culture. I may have some contacts. If interested, DM me and we can discuss more.
English
2
0
7
204
The Secret CFO
The Secret CFO@SecretCFO·
On the topic of data privacy, and compliance concerns for enterprises in the age of AI… Who are the voices to follow / the smartest people for best practice on this topic?
English
6
1
28
33.6K
Right-Side M&A
Right-Side M&A@rightsidema·
@SecretCFO Most of what I’m seeing online is the big corps use Copilot as the primary tool given more robust privacy standards (that’s what Microsoft is saying at least). Not sure its actually true but seems like its working for them.
English
2
0
1
1K
RMontyBizGuide
RMontyBizGuide@BzNav_R_Mont·
@SecretCFO When I was dealing with our first compliance audit, the best advice came from other founders in private Slacks. Skip the influencer crowd. Find the CTOs who've actually failed audits and fixed them.
English
1
0
2
584
The Secret CFO
The Secret CFO@SecretCFO·
@TheCrustyOldMan Big enterprises (outside the tech bubble) are mostly stuck on AI entirely on this point. I have the data. I’m looking for someone who understands the truth about the risks who can help unblock it for my audience.
English
2
0
0
990
The Crusty Old Man
The Crusty Old Man@TheCrustyOldMan·
@SecretCFO Anyone following "best practices" is moving too slow. Anyone moving fast enough is is relying on a non-scalable solution.
English
2
0
2
1.1K
The Secret CFO
The Secret CFO@SecretCFO·
@KevinEspiritu Totally. The dude in charge of product who just manually tweaks payments as he sees fit is a dreadful look.
English
0
0
2
1.4K