Integrating Onit with Finance, Procurement, and Corporate Systems
Swiftwater connected the Onit environment of an American-Asian global technology company with its finance, procurement, accounts payable, HR, authentication, and reporting systems, building proprietary middleware where standard integrations could not handle the company’s entities, data structures, and regional tax treatment.
At a glance
- Service
- Systems integration and middleware
- Scope
- Onit connected to finance, procurement, accounts payable, HR, authentication, and reporting systems across multiple entities and regions
- Outcome
- Information moved between systems; fragmented and manual workflows replaced
What the problem looked like
Legal technology sat apart from the corporate stack. Differences in systems, data structures, legal entities, tax treatment, and regional process created fragmented and manual workflows between Legal, Finance, Procurement, and AP.
Standard integrations covered part of the need and no more.
What Swiftwater did
Integration scope
ELM and finance system integration; procurement and vendor data; accounts payable workflows; organizational and employee data; reporting platforms; authentication and access management; data synchronization; enterprise system interoperability.
Proprietary middleware
Where standard integrations were insufficient, Swiftwater designed and built proprietary middleware and supporting processes so information moved between systems reliably, including the payment feeds to accounts payable systems around the world.
Coordination
Swiftwater coordinated Legal Operations, Corporate IT, Finance, Procurement, Accounts Payable, system vendors, and regional stakeholders, translating legal business requirements into enterprise technology delivery.
What changed
- Vendor, employee, cost center, and invoice data moved between Onit and the corporate systems.
- Fragmented and manual workflows between Legal, Finance, and AP were replaced by integrated ones.
- Legal had a counterpart that spoke both the department’s requirements and IT’s delivery language.
Best for
- Departments whose ELM is an island from ERP and procurement
- Global entities with multiple tax treatments
- IT teams that need a legal-side counterpart for integration work
Frequently asked questions
Which corporate systems should an ELM platform integrate with?
At minimum finance (invoice and accrual data), procurement and vendor master, accounts payable, HR or organizational data for users and approvers, authentication, and the reporting platform.
When is middleware needed instead of a standard connector?
When entities, data structures, tax treatment, or regional process differ enough that a standard connector cannot map the data correctly.
Who owns an ELM integration, Legal or IT?
Legal owns the requirements and the data definitions; IT owns the infrastructure and security standards. In this engagement Swiftwater sat between the two and carried the work through delivery.
Ready to run legal operations as infrastructure?
A 30-minute discovery call on how your legal operations run today and what a managed operating model around your team would look like.
Book a Discovery CallNo commitment. No pitch deck. Just a direct conversation with an expert.