Epicor Kinetic · Rydoo integration by PSE

About Epicor Kinetic

Epicor Kinetic is a modern ERP platform designed for international and local manufacturers, distributors, and service organizations. It brings finance, manufacturing, supply chain, sales, and service operations together on a single, integrated platform.

Epicor Automation Studio, available with recent Kinetic versions, provides a native integration and automation layer. It enables customers to build, manage, and run their own integrations within their Epicor environment and under their own governance.

This is where the connector operates, eliminating the need for an additional integration platform while keeping business and expense data within the Epicor ecosystem. It supports both Epicor Cloud and on-premises Kinetic deployments.

Key features of the connector

13 ready-to-use actions · 2 triggers · Custom action for additional API routes.

Master data, both ways. Synchronize users, groups, projects, branches, expense categories and custom fields between Epicor and Rydoo.
Expenses ready for Epicor. Approved expenses are transformed into structured staging data, ready for validation and posting.
Choose how you book. Create AP invoices, Kinetic Expense Management transactions, GL journal entries, or combine them to match your business process.
Epicor-driven lookups. Find Rydoo records using familiar Epicor references such as Employee ID or Project ID.
Close the loop automatically. Write the Epicor document number back to Rydoo as the payment reference, for complete traceability.
Native to Automation Studio. No additional integration platform to host or license. Your IT team controls, monitors and audits every integration run.

How it works

Epicor Automation Studio is part of the Epicor Kinetic platform, providing a native environment for integration and automation.

The PSE Rydoo to Epicor Kinetic connector runs directly within Automation Studio and communicates securely with Rydoo through its public API. Automation recipes then transform approved expenses into the required Epicor transactions: AP invoices, Expense Management transactions, journal entries, or a combination of these.

There is no separate integration platform to deploy or maintain. The entire integration is managed within your Epicor Kinetic environment.

See the full walkthrough

The connector actions, the master data mapping, what the solution includes and the prerequisites. Tell us who you are and it opens on this page.

Where the expenses land

Three destinations, built as separate recipes.

Destination 1

AP invoice

Expenses are grouped into a supplier invoice, so reimbursement runs through Accounts Payable with your normal payment process.

Destination 2

Expense Management

Each expense becomes an employee expense entry, so you continue the flow in the Epicor module you already use.

Destination 3

Journal entry

Expenses are posted straight to the General Ledger when no sub-ledger step is needed.

The three are built as separate recipes, so you pick the one that matches your flow, or combine them. Because the recipes live in your own tenant, they are adapted with you during the onboarding rather than fixed inside the connector.

Inside the connector

What a recipe builder sees in Automation Studio once the connector is installed. The names are the ones in the product.

Triggers

New Rydoo master data recordFires on records this recipe has not seen before

New expense ready to book in KineticFires when Rydoo flags an expense as exported

Expenses

Get expenses ready to book in KineticPull exported Rydoo expenses as flat staging rows

Get one expenseFull Rydoo detail: receipt ID, multi-VAT children, attendees

Mark an expense reported in RydooMove an expense in or out of a Rydoo report

Reject and send back to the employeeReject in Rydoo when Kinetic validation fails

Write the Kinetic document number backClose the loop: stamp the AP invoice or GL journal reference

Master data

Find a record from its Epicor keyLook up by refId, name or email, no Rydoo GUID needed

Get one recordFull record; the list endpoints only return a summary

List recordsUsers, groups, projects, branches, expense categories, custom fields

Set the departments of an employeeReplaces the whole assignment list

Sync a Kinetic code listCost centres, lines of business, any Kinetic dimension

Sync a Kinetic department or projectGroup = department or cost centre, Project = Kinetic project

Sync a Kinetic employeeEmployee EmpID to Rydoo user

Reverse flow and extension

Create an expense in RydooReverse flow: company card or Kinetic-originated cost

Custom actionBuild your own Rydoo for Epicor Kinetic action with an HTTP request

Master data, and what it maps to in Kinetic

Six object families, synchronised from Kinetic so that an expense carries the right references from the moment it is captured on the phone.

Rydoo object	In Epicor Kinetic
Users	Employees, matched on the EmpID rather than on the email address
Groups	Departments and cost centres
Projects	Kinetic projects
Branches	Companies and sites, so a multi-company estate stays separated
Expense categories	Read from Rydoo, where they are maintained
Custom fields	Any other Kinetic dimension you need to carry on an expense

Each synchronisation action runs in one of three modes: create or update, update only, or create only. Update only is the safe mode on a live tenant, since an unmatched key writes nothing.

What the solution includes

Three parts, delivered together.

The connector

A private connector for Epicor Automation Studio, built and maintained by PSE: thirteen actions, two triggers and a custom action.

The recipes

Starting recipes for the master data synchronisation and for each Kinetic destination, delivered as a base rather than a black box.

Integration onboarding

A short engagement where PSE adapts those recipes to your own flow and your approval practice in Kinetic.

Good to know

Constraints that come from the platforms, not from the connector. Better said now than discovered during the project.

Master data changes The Rydoo API offers no "updated since" filter on master data, so polling detects new records rather than modified ones. A periodic full comparison covers that when you need it.

Categories are read-only Expense categories are maintained in Rydoo. The connector reads them and never writes them back.

See it running

One pass through the integration, from the connector in Automation Studio to the finished document in Kinetic. Click a step, or use the arrows.

Every screen above is from a working build. The company, the people and the merchants have been replaced by demonstration data, so nothing here identifies a real employee or a real supplier.

What we need from you

A short list, settled during the integration onboarding.

An Epicor Kinetic version that supports Automation Studio.
Employee references in Rydoo matching your Epicor EmpID.
Group, project and branch references aligned with your Epicor departments, projects and companies.
The destination you want — AP invoice, Expense Management, journal entry, or a combination.
Your grouping rule — one document per employee, per period, or per currency.
A Rydoo API client for the environment we connect to.

See it on your own flows

Every Kinetic estate is configured differently, so the right answer depends on your version and on where you want expenses to land. A 30-minute call is usually enough to tell you which destination fits and what the onboarding looks like.

Write to pserydoo@pse.be.