Design partners We're building agentic inventory management and are looking for design partners to shape it with us. Agentic inventory design partners Contact us
OrchaMoss

Orcha × Moss. Cards from Moss, finance work in Orcha.

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.

  • Moss issues the cards; Orcha handles expenses, invoices, journal entries and reconciliation
  • Card-paid invoices recorded as paid
  • Integration with Moss, details agreed in onboarding
Moss
Issues the cards
Orcha
Expenses, travel, reimbursement, supplier invoices, journal entries, reconciliation
Card-paid invoices
Recorded as paid, kept out of payment runs
Connection
Integration with Moss, details agreed in onboarding
Ledger
DATEV, or the system you book in
Availability
Set up during onboarding

Moss issues the cards. Orcha does the finance work.

Each tool does what it is built for. Together they cover all your spend, without anyone entering anything twice.

Orcha takes over
  • Supplier invoice intake from inboxes and uploads
  • Coding: account, tax code, cost centre, cost bearer
  • Approvals in the browser, in Slack or by email
  • Journal entries and export to DATEV
  • Bank reconciliation, payment runs and card-paid invoices marked as paid
  • Expenses, travel, per diems, mileage and reimbursement, with receipts by photo, WhatsApp, email or upload
Stays in Moss
  • Issuing the corporate cards
  • Card limits and the Moss app
  • Card payments
  • Moss's own export of card expenses

How Orcha and Moss work together.

Moss issues the cards, Orcha handles expenses, receipts and supplier invoices, and everything ends up in your books once.

InvoicesThrough Orcha

Supplier invoices are captured, coded and approved by Orcha, which prepares the journal entries for DATEV and reconciles the bank side.

CardsIssued by Moss

Moss issues the cards and processes the card payments. Orcha integrates with Moss; we agree the details in onboarding.

OverlapPaid by card

If a supplier invoice was paid with a Moss card, Orcha records it as paid and keeps it out of payment runs.

ObjectDirectionInterface
Supplier invoiceOrcha to DATEVRechnungsdatenservice 1.0
Card-paid supplier invoiceRecorded as paid in OrchaPayment method on the invoice
Card expenses and receiptsMoss to your ledgerMoss's own export
Moss expenses and transactionsMoss to OrchaPlannedMoss API, read access

What Orcha covers with Moss.

Cards from Moss. The rest in one process.

Many growing teams use Moss for cards and want expenses, reimbursement and proper accounts payable next to it. That is where Orcha comes in.

No double entryEach invoice booked once

We agree with you and your tax advisor which tool sends which documents to DATEV, so nothing is booked twice.

ApprovalsRules for supplier invoices

Approval rules by amount, supplier and cost centre for supplier invoices.

Purchase ordersMatching beyond cards

Invoices are matched against purchase orders and delivery notes, which card spend does not need.

Set up during onboarding. Moss still issues the cards.

  1. 01
    Map your spend

    Which suppliers are paid by card, which by invoice.

  2. 02
    Agree the DATEV split

    With your tax advisor, so nothing is booked twice.

  3. 03
    Connect Moss

    Orcha integrates with Moss. We agree the details, for example the statement or export format, in the onboarding meeting.

  4. 04
    Approval rules and master data

    Chart of accounts, cost centres and approvers.

  5. 05
    Go-live

    Supplier invoices run through Orcha.

Connected securely.

Cards stay in Moss

Orcha does not issue cards; cards and limits stay with Moss.

Your roles

Permissions per user for approvals, exports and bank data.

EU data residency

Hosted in the EU, processing under a GDPR data processing agreement.

GoBD and audit trail

Every coding and approval recorded with its author and reasoning.

Orcha and Moss: questions.

Anything else? Talk to the team that builds the integration.

Book a demo
Does Orcha replace Moss?

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.

What happens with invoices I paid by Moss card?

Orcha records them as paid, so they do not end up in a payment run.

Is there a live integration with Moss?

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.

How do we avoid booking an invoice twice in DATEV?

Before go-live we agree with you and your tax advisor which tool sends which documents to DATEV.