If you’re currently using SAP Biller Direct or SAP Cloud for Customer Payments, we have some news that might not be music to your ears: the clock is ticking.
What’s Happening?
SAP has officially put Cloud for Customer Payments into maintenance mode as of September 2024, removing it from their price list. But here’s the kicker: it’s not just winding down slowly—all instances will be shut down in 2027. That’s not a soft sunset; that’s a hard deadline.
While existing customers will continue to receive support until then, there’s no further development or investment happening. The message is clear: SAP is moving away from these legacy solutions and toward an API-based approach.
For Biller Direct users, the writing has been on the wall for a while. As SAP continues its push toward S/4HANA, the future of standalone payment portals looks increasingly uncertain.
The API Dilemma
SAP’s official recommendation? Build your own customer portal using their new S/4HANA APIs. Sounds simple enough, right? Well, not quite.
While APIs provide flexibility and the potential for customization, they also come with significant challenges:
- Development resources: Building a production-ready portal from scratch requires substantial time and expertise—we’re talking 6-12 months minimum with a dedicated team
- Ongoing maintenance: You’re now responsible for updates, security patches, bug fixes, and feature enhancements. Forever.
- User experience design: Creating an intuitive interface that customers actually want to use requires UX expertise most finance teams don’t have
- Integration complexity: Connecting payment providers, managing security compliance (hello, PCI DSS), handling data synchronization, and ensuring seamless SAP integration
- Hidden costs: Development, testing, staging environments, security audits, compliance certifications, ongoing support—it adds up fast
- Opportunity cost: Every hour your developers spend building a payment portal is an hour they’re not spending on features that differentiate your business
For many businesses, especially those without dedicated development teams or deep pockets, this isn’t just inconvenient—it’s a potential dealbreaker. You’re essentially being asked to become a software company on top of running your core business.
Enter the Customer Portal
This is exactly where Kumulon’s Customer Portal comes into play. Built on SAP Business Technology Platform (BTP), it’s designed as a ready-to-deploy replacement for both Biller Direct and Cloud for Customer Payments.
Why This Matters
Rather than starting from scratch with APIs, you get a complete, working solution that:
- Integrates seamlessly with your existing SAP landscape (whether you’re on ERP, S/4HANA on-premise, or S/4HANA Cloud, following a clean-core strategy)
- Provides essential functionality out of the box—invoice viewing, payment processing, dispute management, account information, and more
- Goes beyond payments: Unlike its predecessors, our Customer Portal is built for the future with features like order status tracking and other self-service capabilities. It’s not just a payment portal—it’s a comprehensive customer self-service platform
- Keeps data where it belongs: All your data lives in S/4HANA. No replication, no synchronization headaches, no data consistency issues. The portal connects directly to your system of record
- Connects with payment providers without you having to handle the technical complexity
- Supports credit card surcharging: This is a big one, especially for the US market. The legacy SAP solutions don’t support surcharging, which means companies are leaving thousands of dollars on the table every month by absorbing card processing fees they could legally pass to customers
- Maintains security compliance so you can sleep at night
- Offers customization to match your branding and specific workflow needs
- Leverages SAP BTP for scalability, reliability, and future-proof cloud infrastructure
The Real Cost of “Building It Yourself”
Let’s talk numbers for a moment. Building a custom portal isn’t just about the initial development:
Year 1:
- Development team (6-12 months): $150k-$400k
- Security audits and PCI compliance: $20k-$50k
- Testing and QA: $30k-$60k
- Project management: $40k-$80k
Every Year After:
- Maintenance and updates: $60k-$120k
- Security patches and compliance: $15k-$30k
- Feature requests and bug fixes: $40k-$80k
Plus the intangible costs: delayed go-live dates, distracted development teams, and the risk of building something your customers don’t actually want to use.
Compare that to a ready-made solution that’s already proven, tested, and actively maintained.
The BTP Advantage
Building on SAP Business Technology Platform isn’t just a technical choice—it’s a strategic one. BTP ensures your portal grows with your business, stays compatible with SAP’s evolving ecosystem, and gives you access to advanced capabilities like AI and analytics when you’re ready for them.
Plus, with identity provider flexibility (including Microsoft Entra), you can maintain secure, streamlined access control that fits your existing IT infrastructure.
Planning Your Transition
The good news? You have until 2027. The bad news? That sounds further away than it actually is, especially when you factor in evaluation, implementation, testing, and user adoption time.
Here’s what to consider:
- Assess your timeline: When does your current solution need to be replaced? Don’t wait until 2027 to start planning.
- Calculate the true cost of building: Factor in not just development, but ongoing maintenance, opportunity cost, and the risk of delays
- Evaluate build vs. buy realistically: Do you have the resources, expertise, and budget to develop and maintain a custom portal long-term? Be honest about this.
- Consider your requirements: What features are must-haves? What would be nice to have? Are you thinking beyond just payments to broader customer self-service?
- Think about data architecture: Do you want to replicate data or keep everything in S/4HANA? (Spoiler: keeping it in one place is almost always better)
- Don’t forget surcharging: If you operate in the US market, recovering card processing fees could save significant money
The Bottom Line
Change is never easy, especially when it involves critical business processes like customer payments. But SAP’s hard deadline for Cloud for Customer Payments in 2027 and the uncertain future of Biller Direct means that planning your transition now will save you headaches—and money—later.
The “build it yourself” path sounds appealing until you calculate the real costs: not just money, but time, resources, and risk. For most companies, a ready-made solution that’s already proven, maintained, and expanding its capabilities makes more business sense.
Whether you choose to build your own solution using SAP’s APIs or leverage a ready-made portal like Kumulon’s Customer Portal, the key is starting the conversation today. Your accounts receivable team—and your customers—will thank you for it.
Ready to explore your options? Let’s talk about how we can help you make the transition smooth, secure, and successful—without turning your IT team into a software development shop.