Stampli integrates with more than 70 ERPs. Why?
The other day, Stampli announced that it now supports more than 70 ERPs. Since then, we’ve gotten a number of questions that fall into two camps:
First, why do we support such a wide breadth of ERPs?
And second, why do we take the trouble to integrate so deeply with each one?
To help you understand the reasons, I want to tell you about two hypothetical companies, both in the manufacturing industry. From the outside, their businesses seem to be the same — they both deal with raw materials, they both run production processes, they both have similar corporate structures and composition, and they both have a large number of vendors to pay.
But these two businesses, both alike in dignity, both in fair Detroit where I lay this scene [who says you can’t use literary references in an accounts payable (AP) blog?] can still have wildly different AP processes on the inside.
Company A, for example — I’ll continue to entertain myself by calling them Capulet Cookware — might be using a legacy ERP system with manual invoice processing, batch payments, and a paper-heavy workflow. Their business model, which, like their rival Montague Microwavables, is reliant on a wide range of suppliers, may require rigorous verification processes and a hierarchical approval structure to ensure payment accuracy and prevent fraud. The CFO might prefer a high degree of visibility, with comprehensive reports and direct involvement in payment approvals.
Company B, Montague Microwavables, meanwhile, might operate on a modern, cloud-based ERP system that supports real-time data sharing and automation. Their lean business model might revolve around a smaller, tight-knit network of suppliers, allowing for simplified invoice processing and quicker payment cycles. This CFO might adopt an approach more oriented on delegation, focusing on exceptions and anomalies rather than day-to-day operations. For this company, their AP system would need to provide filtered, high-level data for decision making.
A rose is not a rose is not a rose
These two hypothetical companies illustrate that even within the same industry — AP processes, systems, and structures can vary greatly. Factors like the type of ERP system, the business model, and the management’s approach towards visibility and control can all significantly influence the AP landscape.
And that’s why Stampli approaches ERP integration in the manner that it does. As we stated in that press release:
Stampli’s philosophy to ERP integration stands in contrast {to its competitors}: It builds its integrations in-house, with support for the full range of functionality. As a result, Stampli is able to adapt itself to support a wide range of businesses across all industries, including complex multi-entity corporate structures and those in highly regulated industries such as healthcare. This configurability allows it to be deployed in days, not weeks, with no need to hire developers, adjust existing processes or reconfigure the ERP. It also allows Stampli to support customers that migrate from one ERP to another with no disruption of service.
What if two houses become one?
Stampli’s ERP integration philosophy becomes even more important if your company is involved in M&A. If you’re bringing together disparate systems, processes, and structures, and perhaps even different ERPs, you need an AP system that is completely adaptable.
Imagine if Capulet Cookware were to merge with Montague Microwavables. They’d face the formidable task of integrating two distinct ERPs, along with diverse AP processes (and testosterone-fueled family members). They’d need to reconcile the high-touch, highly visible approach of the Capulet CFO with the streamlined, exception-oriented approach of the Montague CFO. And they’d have to do all this without disrupting their day-to-day operations or their vendor relationships.
That’s where Stampli shines. Rather than forcing a time-consuming and costly reconfiguration of the merged companies’ ERP systems, Stampli can accommodate both. We can enable a seamless transition with no disruption of service. Here’s how our co-founder and CEO Eyal Feldman puts it:
Our belief is that an invoice management system should deploy in days, require no rework to the ERP, and be easy for users and approvers alike,” says Eyal Feldman, co-founder and CEO of Stampli. “Every business has its own processes, systems and structures, which is why we’ve extended our integration philosophy to more than 70 different ERPs. We don’t believe businesses should have to adapt to their software, so we’ve invested extensively in ensuring that our software adapts to the widest possible range of business scenarios.
The power of Stampli lies in our adaptability, our in-house integration, and our deep understanding that every business has its unique operational ‘DNA.’
Whether you’re a Capulet, a Montague, a family-run chain or a national giant, Stampli can equip your AP department with the tools it needs to streamline operations, enhance visibility, and achieve operational excellence. It’s not just about automation. It’s about AP automation that adapts to you.
