Expenses booked
like invoices.
Rydoo captures the receipt. Cortena codes the expense, routes it through the same pipeline as every supplier invoice, and pushes it export-ready to your accounting system.
| Description | Net | Account | Gross |
|---|---|---|---|
| Reise · Flug FRA-BER | 267,23 | 6640 | 318,00 |
| Adobe CC · Team | 46,13 | 6810 | 54,90 |
| Bahn · 1. Kl. | 102,86 | 6640 | 122,40 |
Rydoo expenses enter the same coding pipeline as invoices.
Scheduled or manual sync pulls export-ready expenses from Rydoo. Each one is coded, merged, and reviewed by the same rules you already use for supplier invoices.
Sync
Cortena pulls expenses from Rydoo on a schedule or on demand. Only export-ready items with receipts attached are imported.
Code
AI maps each expense to your GL account, cost centre, and VAT code using the same briefing rules and precedent learning as supplier invoices.
Review
Field-level merge lets you follow Cortena or keep Rydoo values. Any mismatch outside tolerance is flagged as Needs review before it books.
Export
Settled expenses (paid, reimbursed, or company-paid) are marked as settled and included in the posting batch for your accounting system.
Your data, your rules.
Every synced field can follow Cortena coding or preserve the Rydoo value. You decide per field, per category, per team.
Per-field merge
Choose whether Cortena or Rydoo wins on account, cost centre, and category. No all-or-nothing override.
Needs review flag
When a synced value conflicts with a Cortena coding rule, the expense is held for manual review. Nothing books until you clear it.
Receipt-less types skipped
Expense types that carry no receipt (mileage claims, per-diem allowances) are excluded from the sync. They never enter the posting pipeline.
Payment status mirrored
Paid, reimbursed, and company-paid statuses map to settled in Cortena. The booking reflects the actual settlement state in Rydoo.
Same duplicate detection
The same duplicate engine that protects your invoice inbox also checks expenses. A Rydoo item that was already booked manually will be flagged.
Full audit trail
Every sync event, field change, and review decision is logged per expense. GoBD-aligned record keeping, same as every invoice.
Rydoo integration: common questions.
Cortena imports expenses that are export-ready in Rydoo and have a receipt attached. Expense types without a receipt document (mileage, per-diem) are skipped to keep the posting pipeline clean.
Sync runs on a configurable schedule (typically daily) and can also be triggered manually at any time. You control the cadence.
The expense is flagged as Needs review. It will not enter a posting batch until a reviewer resolves the conflict. The reason for the flag is shown in the activity log.
Yes. Once an expense is coded and approved in Cortena, it is included in the same DATEV posting batch as your supplier invoices. It follows the same GoBD-aligned export format.
Yes. Cortena has its own expenses module for teams not using Rydoo. The Rydoo integration is an add-on for teams who already manage employee spending there. See the expenses product page for details.
- Still have a question?
Expenses. Invoices. One pipeline.
Stop copying Rydoo exports into your accounting system by hand. Book a demo and we will show you how it works in 30 minutes.
Book a demo