Sign in
Request a demo
Talk with an accountant.
Connect with us:
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
When Mirage closed its Series C, the company had roughly 20 million users, three separate revenue rails, Stripe, Apple, and Google, and outsourced accounting to Pilot. One of the conditions coming out of their round was to deliver audited financial statements to the board. So when Jourdan Canete was hired as the first accounting hire on the team, he knew exactly where to focus his efforts, passing an audit.
The initial mandate was narrow by necessity: select auditors, get through the first-year audit, deliver a GAAP set of financials. That happened and Mirage completed its first audit with no prior in-house accountant on staff, which is a genuinely tall order.
But getting through the audit surfaced the bigger question: how do you mature and modernize an accounting function that's still a department of one, while the business keeps adding complexity on top? Mirage is now implementing Rillet as its ERP and HubiFi as its revenue-to-cash subledger, a deliberate move to pull work back in-house and reduce reliance on outsourced bookkeeping through Pilot.
Jourdan described weighing three options for every problem: software, AI, or headcount. Headcount is starting to lose ground as the default answer, with the massive shortage of accounting talent out there. As Jourdan put it, the conversation is "moving further away from adding more headcount unless that's around very complex technical things" that current tools can't yet replace.
The exceptions matter as much as the rule. Two areas got called out specifically as not ready for automation: accounting policy judgment and tax expertise involving direct dealings with authorities. An AI tool can help draft a first pass, but it can't yet own the judgment call on how a monetization model should be recognized, or bring the lived experience of negotiating with a tax authority.
That judgment has to be set, and signed off on, by a human before any automation layer is worth building on top of it. Get the policy or the tax position wrong first, and you're just automating the mistake faster.
That's the sequencing a lot of finance teams skip: policy and technical judgment first, then the systems to scale it.
It's worth separating the two challenges Mirage is actually solving, because they're not the same problem wearing the same name.
Revenue recognition has been a challenge for high volume companies since ASC 606 was adopted in 2017 and 2018. Mirage's team has gotten more fluent in ASC 606 over time, but "fluent" doesn't mean the risk goes away as the business adds enterprise contracts and new revenue streams. The risk of restatement, or an auditor flagging a material misstatement because of inaccurate revenue recognition, is an outcome nobody wants to explain to the board.
Order-to-cash is the operational side: how efficiently invoices and orders reconcile with money that’s in the bank. Too often high volumes of consumer transactions running through Stripe, Apple, and Google collide with something processors were never built to do, resulting in finance not having a full accounting-grade view of what happened.
Stripe and the app stores are excellent at processing and collecting but they're not built to handle accounting fees, margins, FX gain/loss, or withhold tax, in the way that’s needed to close the books and pass an audit. That gap is exactly why a dedicated order-to-cash subledger, not just processor reporting, becomes necessary for teams with high transaction volumes and complexity.
There's a category difference between "how do I recognize revenue on this invoice" and "how do I audit, control, and report on order-to-cash when it's scattered across systems that were never built as one accounting envelope." It takes a transaction-level layer built specifically to reconcile and explain that middle ground.
With the right layer, teams experience less manual reconciliation, creating more time to actually explain what's driving the business: which regions are profitable, where margin is leaking, where to invest next. For a lean accounting team supporting a fast-growing consumer business, that's the difference between reporting the past and helping shape what's next - all of which Jourdan was able to do with HubiFi.
Accounting Automation | Product | Technical Accounting | Accounting Systems Nerd
Cody Leach, CPA is a technology and automation focused CPA helping finance leaders bring their processes into the 21st century. He's advised finance teams around technical accounting and automation - such as Cursor, Meta, Strava, and many others and has helped SaaS and AI finance teams turn messy and usage data into clean, automated revenue reporting that actually matches how the business runs. Former KPMG auditor, Cody holds in Masters in Accounting from North Carolina State University. He is a CPA.
Meet with an expert in revenue recognition and order-to-cash accounting and automate revenue close.
*Or watch 2 minute demo here.
Power your high-volume business's revenue compliance and reporting needs with one platform.
