Moss issues your corporate cards. Orcha integrates with Moss and handles expenses, travel, per diems, mileage and reimbursement, with receipts captured by photo, WhatsApp, email or upload, next to supplier invoices, coding, approval, the journal entries for DATEV, bank reconciliation and payment runs. Invoices you paid by Moss card are recorded as paid, so they never end up in a payment run. We agree the details in our onboarding meeting.
Each tool does what it is built for. Together they cover all your spend, without anyone entering anything twice.
Moss issues the cards, Orcha handles expenses, receipts and supplier invoices, and everything ends up in your books once.
Supplier invoices are captured, coded and approved by Orcha, which prepares the journal entries for DATEV and reconciles the bank side.
Moss issues the cards and processes the card payments. Orcha integrates with Moss; we agree the details in onboarding.
If a supplier invoice was paid with a Moss card, Orcha records it as paid and keeps it out of payment runs.
| Object | Direction | Interface |
|---|---|---|
| Supplier invoice | Orcha to DATEV | Rechnungsdatenservice 1.0 |
| Card-paid supplier invoice | Recorded as paid in Orcha | Payment method on the invoice |
| Card expenses and receipts | Moss to your ledger | Moss's own export |
| Moss expenses and transactions | Moss to OrchaPlanned | Moss API, read access |
Many growing teams use Moss for cards and want expenses, reimbursement and proper accounts payable next to it. That is where Orcha comes in.
We agree with you and your tax advisor which tool sends which documents to DATEV, so nothing is booked twice.
Approval rules by amount, supplier and cost centre for supplier invoices.
Invoices are matched against purchase orders and delivery notes, which card spend does not need.
Which suppliers are paid by card, which by invoice.
With your tax advisor, so nothing is booked twice.
Orcha integrates with Moss. We agree the details, for example the statement or export format, in the onboarding meeting.
Chart of accounts, cost centres and approvers.
Supplier invoices run through Orcha.
Orcha does not issue cards; cards and limits stay with Moss.
Permissions per user for approvals, exports and bank data.
Hosted in the EU, processing under a GDPR data processing agreement.
Every coding and approval recorded with its author and reasoning.
No. Moss issues your corporate cards; Orcha does not issue cards. Orcha integrates with Moss and handles expenses, travel, per diems, mileage and reimbursement, plus supplier invoices, journal entries, approvals, the DATEV export and bank reconciliation.
Orcha records them as paid, so they do not end up in a payment run.
Yes. Orcha integrates with Moss. Card transactions come in through a live card feed or through statement import in PDF, CAMT, CSV or Excel. We agree the details, for example the statement or export format, in our onboarding meeting.
Before go-live we agree with you and your tax advisor which tool sends which documents to DATEV.