In many companies, indirect procurement runs in a surprisingly fragmented way. Supplier invoices are processed through procurement or accounts payable workflows, while expenses land in a separate tool in finance or HR. On paper, these are two different types of expenditure. In practice, both involve the same core: company spending that needs to be managed, approved, posted, and analyzed.

This is exactly where the problem of system separation lies. Anyone processing invoices and employee expenses in different platforms will rarely get a reliable overall picture of actual spend. That's not just a reporting issue. It affects budget management, compliance, process costs, and ultimately the question of how consistently purchasing policies are followed in day-to-day operations.

Ardent Partners puts the effect of integrated procurement and expense processes at 25 percent less maverick spending. That figure is plausible because it confirms a well-known mechanism: as soon as approvals, categories, supplier data, and payment flows converge within a shared management framework, exceptions become visible — and therefore manageable.

Where the separation becomes costly

DThe classic division of responsibilities sounds reasonable at first. Procurement handles suppliers, purchase orders, and invoices. HR or finance manages travel costs and employee expenses. In daily practice, however, this separation leads to breaks in the process.

A typical example: a team needs software licenses at short notice. Formally, the purchase should go through a negotiated supplier contract. In reality, an employee takes out a monthly subscription via corporate card and submits it as an expense. This spend never appears in the invoice system. In the expense tool it is posted, but not evaluated as a procurement transaction. The result: the expenditure sits outside the purchasing volume, framework agreements are bypassed, and the spend category is underrepresented in analysis.

The same applies to smaller office supply, hospitality, or mobility costs. As long as these expenses disappear into the expense process, procurement is missing part of the picture. And finance has to manually reconcile accounts payable, card statements, and cost centers.

The consequences are well known: duplicate master data maintenance, inconsistent approval rules, weak policy enforcement, and high reconciliation effort at month-end.

Complete spend visibility is more than a dashboard

The most powerful lever of an integrated solution lies in transparency — but not in the sense of a pretty management graphic. Rather, it means operational management capability.

When supplier invoices, purchase orders, corporate card transactions, and employee expenses converge in a shared data model, spend can be cleanly analyzed by supplier, category, cost center, country, or policy violation. Only then does it become visible where companies are spending money outside defined procurement channels.

This is particularly relevant for DACH companies, where compliance and traceability have traditionally carried significant weight. Whether it's input tax audits, GoBD-compliant archiving, audit-proofing, or internal approval matrices: an isolated expense process quickly creates blind spots.

An integrated platform, by contrast, creates consistency. The same cost center, the same approval logic, the same supplier and tax attributes — regardless of whether a spend arrives as an invoice or was pre-financed by an employee. This reduces discussions in finance, relieves business units of burden, and improves the quality of posting data.

Less maverick spending, stronger compliance

Maverick spending rarely arises from bad intent. It is frequently the result of cumbersome processes. When the official procurement route seems too slow, teams take the path of least resistance: credit card, expense receipt, direct online booking.

That's exactly why tightening rules alone is not enough. Companies need to make the official procurement path easier than the workaround. An integrated procurement and expense solution helps in two places.

First, policies can be anchored before the purchase — through catalog-based procurement, preferred suppliers, or budget checks. Second, downstream expenditures — such as card payments or expenses — can be automatically mirrored against these rules. This allows the system to identify whether a hotel was booked outside the travel policy, whether the same SaaS solution is repeatedly being purchased in different parts of the organization, or whether a supplier appears both through invoices and employee expenses.

The 25 percent reduction in maverick spending is therefore not an abstract benchmark, but the expression of a clear principle: those who see all expenditure in the same management system can identify policy violations earlier and organize procurement more consistently.

How to achieve a technically clean integration

Technically, bringing the two together is no longer a major project today — but it does require discipline in the data model. Four building blocks are critical.

The first is a shared master data core. Cost centers, entities, accounts, VAT codes, suppliers, and employees must be consistent across systems. Without this foundation, even the best integration will only produce new reconciliation errors.

The second building block is event logic. Companies should define which types of expenditure are treated as a procurement case, an expense case, or a hybrid case. An overnight receipt is different from an unplanned software purchase on a corporate card, even if both initially appear as expenses.

Third, a reliable ERP connection is needed. In the DACH region, SAP integration is often the central pivot point — whether SAP S/4HANA, SAP ERP, or complementary finance and procurement modules. What matters most is the clean handover of posting documents, tax information, creditor master data, controlling objects, and approval status. Anyone merely transferring PDF documents or CSV exports here is giving away the benefits of integration.

Fourth, companies should favor API-based architectures. These are more flexible than point-to-point custom interfaces and simplify later extensions — for card providers, travel management, OCR, e-invoicing, or analytics.

What DACH companies should keep in mind during implementation

Implementation rarely fails due to technology — it fails due to unclear governance. It therefore pays to bring procurement, finance, HR, and IT together early. Each of these functions sees only part of the process. But the real value creation only emerges from end-to-end design.

A proven approach is to start with two or three specific spend categories where the media break is most painful — for example, travel expenses, IT subscriptions, and smaller operational purchases. There it can quickly be demonstrated how shared approvals, automatic account assignment, and better visibility reduce the workload.

Equally important is translating policy into the system. Travel policies, spending limits, mandatory fields, VAT logic, and approval thresholds need to be not just documented, but technically mapped. Only then does a policy become a manageable process.

Why this topic belongs on the agenda in 2026

Companies in 2026 face a dual pressure: costs must be managed more precisely, while employees expect simple, fast processes. Separate systems for invoices and expenses are poorly suited to this tension. They create friction, hide expenditure, and burden finance with reconciliation work that is avoidable today.

The integration of procurement and expense is therefore not a comfort project. It is a management project. Bringing supplier invoices and expenses together in one system creates the foundation for genuine spend visibility, less maverick spending, and reliable compliance.

This is exactly where expense intelligence becomes interesting: not as an isolated expense function, but as part of a networked spend management framework. For companies with SAP-adjacent ERP landscapes and high demands on transparency, this is no longer a vision of the future — it is a very concrete architectural decision.

Subscribe to the Edi Newsletter in German

The German Newsletter keeps you up to date about Edi: simply register using your e-mail address and never miss an article. Of course, you can unsubscribe at any time.