As SAP’s 2027 support cutoff nears, Pranay Raj Kanakala shows what compliance-ready SAP migration actually looks like

In 18 months, the software many of the world’s largest companies rely on to run their finance and operations stops receiving security updates and official support. That is the reality behind SAP’s 31 December 2027 deadline, the point at which mainstream support for its older ECC system ends. The stated fix is simple: move to SAP’s newer platform, S/4HANA. Getting there is not. Recent benchmark research puts it starkly: only 34% of companies have fully completed the transition, even as 55% report deploying the new system at some level, which leaves a large share of SAP’s customer base running old and new systems side by side with the clock running down. Most coverage of the deadline fixes on the platform switch itself. For regulated industries, a quieter risk sits alongside it: getting revenue accounting right while everything underneath it is moving.

Pranay Raj Kanakala came to that problem from an unusual direction. He spent the first stretch of his career in telecom radio engineering, tuning 4G networks for national rollouts, including Telenor’s greenfield LTE build across Myanmar, a country of more than 54 million people, and work at Nokia on the design of over 100 macro cell sites for Vodafone’s 4G expansion in Gujarat, serving 72 million people. Today, he works as a SAP Revenue Accounting and Recognition (RAR) consultant at MytekX Inc., an SAP consultancy focused on cloud transformations and S/4HANA migrations for healthcare clients. Pranay Raj Kanakala’s high level of expertise earned him a Gold Award at the NextWave Awards 2026, an international competition for innovation in business, science, and technology.

Pranay Raj Kanakala won in the Artificial Intelligence and Machine Learning category and was recognized by the jury as an outstanding specialist. He holds AWS Solutions Architect Associate credentials and, as a Certified Scrum Master, a role in which he leads cross-functional teams spanning finance and IT, facilitating sprint planning, managing delivery cadence, removing blockers that slow complex SAP programmes, and keeping stakeholders aligned through each phase of implementation. He carries two master’s degrees in computer science and in science and engineering, and has published research on secure multi-cloud architecture, CLOUD-OF-CLOUD: A Novel Protocol for Secure Data Storage and Sharing in Multi-Cloud Environment, published in the Journal of Interdisciplinary Cycle Research in 2022, that has since been cited by other researchers in the field.

What ties it together is one instinct: understand the process before you automate it.

The reason platform migration and accounting compliance are two problems, not one, comes down to how revenue recognition works. Under standards such as IFRS 15 and ASC 606, which govern when a company can book revenue, contracts that bundle several products or services together need careful, judgement-heavy handling. They have to be split into separate components, priced individually, and recognised on their own timelines. Get that wrong in a complicated case, say a multi-year deal renegotiated partway through, or a licence sold alongside implementation support, and a company can book revenue too early or in the wrong period, which is exactly what draws an auditor’s attention. Deloitte’s Q4 2025 CFO Signals survey found that 50% of North American CFOs now rank digital transformation of finance as their top priority for 2026, naming automation as the lever for getting processes like this right. What decides the outcome is whether the revenue logic itself was automated, tested, and built for these scenarios, whichever SAP version runs underneath.

“Companies sometimes treat the technical migration and the accounting logic as one project, and they are two,” Kanakala says. “Moving to S/4HANA gives you new infrastructure, but the logic it runs on has to be built and tested separately, and that is usually the part nobody looks at until the audit forces the question.”

That gap is what his most recent project set out to close. At MytekX, Kanakala led the design, configuration and implementation of a revenue accounting transformation for a global healthcare and MedTech company operating across North America, Europe and Asia-Pacific, an organisation carrying thousands of customer contracts and revenue transactions across regions. The build connected SAP systems that normally sit apart: the core platform, sales, contract quoting, and revenue accounting, so contract data flowed straight into revenue calculations instead of being carried by hand between disconnected tools. At the centre of it was a custom SAP BRF+ rule framework that automated how the system identifies fulfilment items and triggers revenue events.

Done by hand, that logic would put an accountant on every contract change that comes through, making a judgement call each time. The framework does it automatically, and the same way every time. Because the client operates across regions, the same framework also had to satisfy two standards at once, IFRS 15 and ASC 606, rather than running separate logic for each. The result was one automated system handling the client’s full range of contract scenarios consistently everywhere, in place of case-by-case manual review.

“Healthcare and MedTech contracts are hard because they so often combine equipment, software and an ongoing service obligation in the same deal,” Kanakala says. “In a regulated industry, getting the timing wrong on any one of those components creates errors that take months to unwind.”

The 2027 deadline makes this kind of disciplined, parallel work harder to pull off, not easier. SAP’s own 2026 benchmark research warns that demand for experienced S/4HANA talent could reach three times the available supply by 2027, with consulting rates set to spike in the deadline’s final year. More companies chasing fewer specialists in less time is the exact condition under which compliance work slips from designed-in to bolted-on.

Kanakala’s project runs the other way. Working as SAP RAR Consultant and Scrum Master at MytekX Inc., his team worked through a structured SAP Activate and Agile delivery cycle across five phases, from discovery and requirements through solution design, build and configuration, testing and validation, and deployment with post-go-live support. Revenue recognition accuracy rose 95%, turning an error-prone process into a dependable one. Manual accounting work fell 70% and overall processing time dropped 60%, taking much of the case-by-case review off the finance team. Audit readiness improved too, on the back of automated revenue traceability and reporting controls. Those results are what brought the recognition his award marks.

The method traces back to the radio network, where every fix began with a physical why: what was it about this antenna tilt, this frequency band, that solved the coverage gap in front of him. He brings the same test to SAP. Rather than script the automation and move on, he maps the business process it is meant to protect, so the rule framework validates the logic that actually matters. It is how he trains the team of 15 consultants he now leads, and the thinking behind his published work on secure multi-cloud storage, a problem close to the SAP cloud platforms these migrations increasingly run on.

“My advice to any CFO or CIO racing towards 2027 is to treat revenue recognition as its own workstream from day one, not something you add once the platform is live,” Kanakala says. “The migration gets the attention because it has a hard deadline on it. The accounting logic underneath is just as critical, and far harder to fix after the fact than to build the first time correctly.”

By the end of 2027, thousands of companies will have made some version of the decision SAP has forced on them. Whether they get there by design or by scramble is still theirs to decide. The platform switch will take the headlines and the budget lines. For anyone in a regulated industry, the decision that matters more is the quieter one underneath it: whether the revenue accounting was built as a problem worth solving in its own right, or left to sort out once the new system was already live.