Implementation Partner for Rossum: A Case Study

Most case studies show one project. This one shows a year of them.

For the past year, one of our biggest engagements has been working as the delivery arm for Rossum. Rossum sells the platform; we implement it for them. It’s the clearest example of what our partner services pillar does: we act as a SaaS company’s outsourced delivery team and ship the implementations it doesn’t have the capacity for.

Each story below is one of Rossum’s enterprise customers. What I want to show is both what we built and why Rossum chose us. That second part is what any SaaS company working with us benefits from.

---

Who is Rossum, and what does Inovaflow build for them?

Rossum is an AI-first intelligent document processing (IDP) platform that extracts structured data from invoices and other business documents, and in May 2026 it was acquired by Coupa to extend IDP across Coupa’s source-to-pay platform. Rossum’s extraction engine is strong out of the box. The hard part is everything around it, and that hard part is the work Rossum needs a delivery team to own.

Extraction gets you text off a document. Touchless accounts payable — where an invoice flows from inbox to posted in the ERP with no human touch — needs matching logic against purchase orders and master data, validation rules that catch bad data before it posts, calculated fields that synthesize values the document never printed, and most importantly, an integration that delivers the result into the customer’s ERP in exactly the format it expects.

That integration almost always runs both directions. Master data flows in (suppliers, subsidiaries, purchase orders, tax codes) so the platform can match against live ERP data, and validated documents flow out, formatted for the ERP’s API. Getting both sides right against a real enterprise system is where most IDP projects stall, and it’s where our ERP background earns its place. A typical account we deliver carries 15+ calculated fields and 20+ validation checks, all custom to that customer.

For an outside read on the partnership, check what Rossum’s own Solution Architects say about our work on G2.

---

How do you keep an enterprise rollout from falling apart when scope explodes?

You absorb the change and deliver anyway, instead of pointing at the contract. Our biggest Rossum engagement was a pan-European online-grocery group running six-plus legal entities across multiple countries, and partway through, the scope expanded hard. New requirements surfaced. Tension rose about what had been missed early.

We stepped in as the steady hand. We took on the extra scope, kept building, and brought the project to a clean, formally signed-off delivery. Then the customer hired us again for the next phase. For Rossum, that’s the outcome that counts: a strained flagship account that could have churned instead ended in sign-off and a second SOW.

The work underneath was real too. The group enforces a strict “no PO, no payment” policy, but POs often get approved after the goods arrive, which left AP staff manually checking day after day whether they could finally release a payment. We automated that wait: invoices now release the instant their PO is approved, with no one watching for it. We added processing that pushed their automation rate up, and we got from kickoff to a working solution in weeks, not the two to three months an in-house build of this depth would have taken. That kind of speed is what lets Rossum give a customer a date and keep it.

---

How do you find the root cause of a problem the original build missed?

You know the platform well enough to diagnose what’s actually broken, and Rossum trusts the diagnosis because its own architects can’t always spare the time. Our second major account was a global food-delivery platform running Coupa and NetSuite across EMEA and APAC, where we extended an existing automation.

Credit notes were failing. Rather than patch symptoms, we traced it to the source: partial credits had never been supported in the original solution at all. That was the moment our role changed from the team building quietly in the background to the one Rossum leans on to explain what’s really wrong. A delivery partner you can hand a customer’s hardest problem to, and get back the real answer, takes load off your own engineering and support.

The everyday value was just as concrete. Several countries the platform operates in don’t print a supplier tax number, which quietly broke vendor matching and forced manual work; we made those invoices resolve on their own. As new e-invoice formats arrived, we routed them through the same validation as scanned PDFs, so neither the customer nor Rossum had to run a second process.

---

How do you automate spend that has no clean purchase order to match?

Recurring spend is the invoice category most AP teams give up on, so you build matching for it that a demanding customer can rely on. Our most engineering-intensive engagement was a global proprietary-trading firm, technical enough to run its own issue tracker against the project, automating recurring and subscription spend into NetSuite.

A monthly software or services invoice rarely carries a tidy PO number, so it falls out of standard matching and lands on someone’s desk every month. We closed that gap with matching that works the way a seasoned AP clerk would: start strict, relax step by step until exactly one PO fits, inside tight tolerances so it never matches the wrong one. A large slice of formerly manual spend now posts on its own.

This customer had the in-house skill to judge our work closely, and they came back for a second SOW. For Rossum, that’s proof the team it sent in can satisfy an account it can’t afford to disappoint.

---

How do you automate invoicing across China and Western operations into one ERP?

You take on the regulatory and matching complexity most teams won’t touch, so Rossum doesn’t have to staff for it or risk losing the deal. Our hardest-geography engagement was a global thermal-systems manufacturer with significant China operations, automating end to end into QAD ERP.

China AP is its own animal: Chinese Fapiao tax documents, multiple currencies, and inventory arrangements where invoices routinely arrive before the matching goods receipt or PO exists. Most automation stops there and hands the document to a person. We built it to wait intelligently instead, holding a document that can’t match yet and retrying over time, then clearing it the moment the missing piece lands. We added the inventory reconciliation and three-way matching the setup needed and exported clean data into QAD.

Accounts like this are hard to staff and easy to lose. The fact that Rossum can route one to us and know it’ll get delivered is the whole point of the partnership.

---

How do you migrate accounts payable to a new ERP without stopping the business?

You re-platform the automation in phases while invoices keep flowing, and you work as one team alongside everyone else on the program. Our largest single engagement, live right now, is a global hospitality and members’-club group moving invoice processing from Sage to Oracle Fusion across the UK, US, and EMEA, delivered alongside Accenture.

You can’t pause accounts payable to swap ERPs; suppliers still need paying. We rebuilt the automation on the new ERP’s master data and rolled it out region by region so the business never stopped, co-building the Oracle integration directly with Accenture and retiring the legacy logic as each region went live. It’s running at around 1,500 invoices a week.

What matters here is how we operate inside a multi-party program. We sit in the room with the customer and their integrator, run requirements directly, and own the integration end of the work. Rossum can drop us into a complex enterprise engagement and trust us to represent the platform well, not just close tickets.

---

Why would a SaaS company hand delivery to an outside team?

Because the right team makes its delivery faster, deeper, and broader than its own headcount allows, without giving up control of quality. After a year inside Rossum’s accounts, the same reasons come up on every engagement.

We’re fast. We get from kickoff to a working solution in weeks, which lets Rossum commit dates to its customers and hit them. We’re committed: when scope expands or a rollout strains, we absorb it and deliver, which is why hard accounts end in sign-offs and repeat work instead of churn. We know Rossum well enough to diagnose problems the original build missed, which takes load off Rossum’s own engineers and support. And we can talk to customers, not just code behind the scenes, so we can run requirements calls and represent the platform in multi-party programs without being babysat.

The integration is where these projects usually stall, and it’s our home ground. Our team built enterprise ERP integrations for years, so connecting Rossum into NetSuite, Oracle, SAP, QAD, Coupa, or Navision in both directions is the part we find easy. Put together, a handful of senior engineers let Rossum take on more enterprise accounts, in more geographies, against more ERPs, than it could staff on its own.

---

What does Inovaflow’s Rossum delivery record actually look like?

17 projects across 13 enterprise customers, integrating into eight different ERPs, delivered by a small, senior engineering team. The customers span grocery e-commerce, food delivery, semiconductors, industrial and automotive manufacturing, proprietary trading, hospitality, utilities, and commercial finance, across Europe, the US, China, and APAC.

The list of downstream systems is the integration story on its own: NetSuite, Oracle Fusion, SAP, QAD, Coupa, Microsoft Dynamics Navision, Adaco, and Sage. Whatever ERP the enterprise runs, we become the layer between the platform and that system — the same capability we bring to direct API integration work outside the Rossum channel.

Two facts matter most to any SaaS company weighing us. Four of our largest customers came back for a second engagement, which is the clearest signal of satisfaction in B2B services. And Rossum’s own Solution Architects route delivery to us and lean on our technical judgment, rated 4.9 out of 5 across public G2 reviews.

If you’re a SaaS company whose enterprise deals stall in implementation, or whose services team can’t scale to every customer’s ERP, that’s the gap our partner services close. We plug in as your delivery team and ship.

---