Rydoo

How an expense gets into the system: a mobile app that photographs receipts, text recognition (OCR) that reads amount, date, merchant and VAT, receipts forwarded by email or pulled from suppliers, claims for out-of-pocket spending in any currency, mileage and trip entries, a substitute receipt (Eigenbeleg) when the original is lost, and duplicate detection.

0 — Not an expense capture tool; receipts and claims cannot be recorded in the product.

3 — Receipts uploaded as photos or files and attached to an expense by hand; text recognition, email capture or claims in other currencies are basic or not described.

5 — A mobile app that captures receipts with text recognition reading amount, date and merchant, receipts forwarded by email, expense claims for out-of-pocket spending submitted from the app, and foreign currencies converted.

8 — Extraction of VAT rates and amounts and line items, receipts collected automatically from email inboxes or named suppliers, duplicate and fraud checks on submission, a substitute receipt for lost originals, mileage with route calculation, and replacement scanning (ersetzendes Scannen) stated as GoBD-compliant so paper originals may be discarded.

10 — Capture without employee effort: e-receipts delivered directly by travel and merchant partners, extraction accuracy or review process published, a certified scanning procedure (for example an audit report to IDW PS 880 or a TÜV certificate) named, and every receipt traceable from capture to booking.

How spending is controlled before it happens: physical and virtual company cards with limits, single-use and subscription cards, limits by amount, merchant category and time, budgets per team or project, real-time notifications and receipt reminders — or, for a product that issues no cards of its own, live feeds from the company's existing cards with automatic receipt matching. The issuing institution and its licence count where cards are issued.

0 — Neither issues cards nor reads card transactions; only out-of-pocket claims exist.

3 — Card transactions imported from a statement file or a single feed and matched by hand, or a card offer with fixed limits; budgets, reminders and controls are basic or not described.

5 — Either own physical and virtual cards with per-card limits, freezing and real-time notifications, or live feeds from named corporate card schemes or banks with automatic matching of receipts to transactions; spending visible as it happens and employees reminded to submit receipts.

8 — Cards for every employee with limits by amount, merchant category and period, single-use and subscription cards, budgets per team or project that cards draw from, pre-approval of a purchase before the card is charged, feeds from existing bank cards beside the own cards, and the issuing institution and licence named.

10 — Spend control across the company: multi-entity and multi-currency card accounts, budgets and policies enforced at the moment of payment, card spend reconciled to the statement automatically, safeguarding of funds and credit terms stated, and cards and transaction history portable to another provider.

How the company's rules are applied: approval chains by amount, team, cost centre or project, delegation and deputies, an expense policy with limits per category and per country that the product checks, pre-approval of trips and purchases, roles and permissions, multi-entity set-ups, and an audit trail of who approved and changed what.

0 — No approval step; every expense goes straight to export or payment.

3 — A single approver per employee or one sign-off step; policy rules, deputies and audit history are basic or not described.

5 — Multi-step approval flows configurable by amount, team or cost centre, an expense policy with limits per category that flags violations, approval from the mobile app, and a history of who approved what.

8 — Rule-based routing by amount, project, cost centre and entity with deputies and escalation, policy checks before submission (limits per country, per diem rules, duplicates), pre-approval of trips or purchases, granular roles and permissions, several legal entities in one account, and an exportable audit trail.

10 — Controls that stand up to an audit: anomaly and fraud detection with its rules explained, separation of duties enforced, country-specific policies maintained centrally, every change to a claim versioned and attributed, and control reports offered to auditors.

How the employee gets money back and the company gets the tax right: reimbursement of approved claims by bank transfer or a SEPA payment file, mileage allowances and per diems at statutory rates per country (Verpflegungspauschalen, Kilometerpauschale, meal deductions), taxable and tax-free reimbursements separated for payroll, the input VAT captured per receipt for the deduction, and foreign VAT reclaimed.

0 — No reimbursement of employees; the product covers company cards only and out-of-pocket spending is out of its scope.

3 — Out-of-pocket claims recorded and paid back outside the product by hand; travel allowances and VAT handling are basic or not described.

5 — Approved claims reimbursed through the product or a SEPA payment file, mileage and per diems at configurable rates, and the VAT rate and amount captured per receipt for the input-tax deduction.

8 — Statutory per diems and mileage rates per country maintained by the vendor (German travel expense law named), meal deductions and multi-day trips calculated, reimbursement in several currencies within a stated time, VAT split per rate and receipts checked for the invoice requirements of the deduction, and foreign VAT reclaim offered or integrated with a named partner.

10 — Travel expense law and VAT handled end to end: country rules kept current with a stated process, taxable reimbursements passed to payroll, foreign VAT reclaim filed with the recovered amounts reported, and every reimbursement traceable to the claim and the rule that produced it.

What reaches the books: export or sync to DATEV (DATEV format, DATEV Unternehmen online, Belegbilderservice) and to named accounting and ERP systems, booking proposals with account, tax key and cost centre, receipts that travel with the booking, card statements reconciled, a GoBD-compliant archive, an API and webhooks, and a complete export of claims, receipts and booking data.

0 — No export of any kind; expenses have to be retyped into the books.

3 — A CSV or PDF export of expense reports; booking data, named integrations and the archive are basic or not described.

5 — Export or sync to at least one named accounting system (DATEV or another) with account and tax code per entry and the receipt attached, several accounting or ERP integrations listed, and a documented API.

8 — A DATEV interface with receipt images (DATEV Unternehmen online or the DATEV Marketplace named), booking proposals that learn account, tax key and cost centre, two-way sync with named ERPs (SAP, Microsoft Dynamics, NetSuite or similar), card statements reconciled for the month-end, a GoBD-compliant archive stated, and webhooks.

10 — The month-end close runs through the product: multi-entity bookings and accruals, a procedure documentation (Verfahrensdokumentation) or GoBD audit offered, a complete audit trail of every financial event, and a full export of claims, receipts and bookings that a successor system can import.

Who the contracting entity and the parent company are, where receipt, card and employee data are hosted, and who the subprocessors are (hosting, card issuer and processor, text recognition, open banking, email delivery). Independently sourced by the sovereignty pipeline; expense data is personal and financial at once and shows where employees travel, so the whole chain counts, not only the database.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.

3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.

5 — EU hosting available and an EU contracting entity or EU representative, but parts of the chain (text recognition, card processing, email, analytics, support) run through non-EU providers without a stated safeguard.

8 — EU hosting on named infrastructure, EU contracting entity and card issuer, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.

10 — Sovereign end to end and evidenced: European ownership, entity, issuer, hosting and every subprocessor, data export and deletion documented, and certifications published with their scope rather than implied.

Whether a buyer can compute the real annual cost from public pages alone: price per user or per active user, platform or base fee, which modules (travel, reimbursements, DATEV or ERP connectors, extra entities) cost extra, card fees (physical cards, foreign transactions, currency conversion, top-ups), minimum seats and term, and setup.

0 — No public prices at all; every customer is a sales call.

3 — A starting price or a free tier exists, but how cost scales with users, cards or modules is unclear.

5 — Tiers are public with their per-user or base price and main inclusions, but at least one commonly needed piece (extra users, physical cards, foreign-currency fees, ERP connectors) is unpriced or "on request".

8 — Every tier priced publicly with its scaling rule (per user, per active user, per card), card and foreign-transaction fees listed, add-ons priced, minimum term and VAT treatment stated.

10 — Complete price computability: annual cost derivable for a given headcount, card count and module set, with every add-on, setup, support, card and currency fee and the cancellation and data-return terms published.