# Rydoo integration

What Cortena imports from Rydoo, how sync works, and how payment status is shown.

Finance teams and programme owners who use **Rydoo** with Cortena can see **what arrives in Cortena**, **how often**, and **how payment status is shown**.

## How Cortena connects to Rydoo

Your organisation connects Cortena to Rydoo with the credentials and permissions you approve. After that, Cortena can **read expense information** Rydoo makes available for your workspace. Imported expenses then follow the **same Cortena processing path** as documents you upload yourself (bookkeeping, workflow, review, and export).

## When synchronisation happens

- **Scheduled updates:** Cortena **checks for new expenses** from Rydoo on a **regular schedule**, so your workspace stays up to date without daily manual work.
- **Manual refresh:** Where your workspace allows it, an authorised user can **run a sync on demand**, for example after a large batch was finalised in Rydoo and you want the latest items in Cortena sooner.

## What Cortena imports

For expenses that Rydoo has **prepared for export** and that Cortena has **not imported before**, Cortena typically brings in:

- The **receipt** (image or file), when Rydoo provides one
- **Key expense details** from Rydoo, such as dates, amounts, categories, and the allocation-related fields your workflow uses

**Note:** Some expense types that **do not use a receipt in the same way** (for example certain mileage or allowance entries) may be **skipped**, so your Cortena inbox stays focused on document-backed spend.

Each newly imported expense is then handled by your **standard automation and workflow rules**.

## How payment status is determined

Cortena **does not infer payment from your bank**. Payment information comes **from Rydoo's view of each expense**, including whether the spend is **reimbursable to an employee** or **company-paid**.

**Paid or settled in Cortena** when Rydoo indicates, for example:

- The expense is **reimbursed**, **paid**, or in a **completed payment** state, **or**
- The expense is **not reimbursable to the employee** (company-paid), which Cortena treats as **settled without a separate reimbursement step**

**Not yet paid / still in progress** when Rydoo shows the expense as **reimbursable** but still in **submission, approval, control, or processing**, or **not yet reimbursed**.

**Not payable** when Rydoo marks the expense as **rejected**, **recalled**, **duplicate**, or similar. Cortena reflects that it should **not be treated as a normal payable reimbursement**.

**Dates** shown alongside paid status follow the **expense and date information Rydoo supplies**, so what you see in Cortena stays aligned with Rydoo rather than with separate banking data inside Cortena.

## Tips for day-to-day use

- Treat **approval and reimbursement in Rydoo** as the source of truth; Cortena **mirrors** those outcomes for routing and review.
- After major changes in Rydoo, use **manual sync** (if available) if you need Cortena to catch up immediately.
- For **which allocation fields** follow Cortena versus Rydoo after bookkeeping, see [Expense workflow: allocation and routing](https://help.cortena.ai/guides/workflows/expense-workflow).
- To limit which expenses Cortena imports (branch, group, project, custom field, or status), see [Rydoo sync filters](https://help.cortena.ai/guides/integrations/rydoo-sync-filters).