Moss API Integration Research

Date: 2026-04-29 Product: Moss (getmoss.com) -- Spend Management Platform by Nufin GmbH, Berlin Purpose: Evaluate Moss's API capabilities for Orcha integration

Important Context: What Moss Actually Is

Moss is NOT an ERP or accounting system. It is a spend management platform that handles:

• Corporate credit cards
• Supplier invoice capture & AP workflows
• Employee reimbursements
• Pre-accounting (AI-powered coding of expenses)
• Payment processing (SEPA, international)

Moss sits upstream of the ERP -- it captures, codes, and approves expenses, then exports the pre-accounted data to the customer's actual accounting/ERP system (DATEV, SAP, NetSuite, Business Central, etc.).

Implication for Orcha: Moss is not a target system where Orcha would push invoices into. Rather, Moss is a competing or complementary system to parts of what Orcha does (invoice capture, OCR, pre-accounting). The integration question is: can Orcha read data from Moss, or does it make sense for Orcha to sit alongside Moss in a customer's workflow?

1. Summary -- Capability Matrix

Overall assessment: Moss has a REST API focused on reading and updating expense data with accounting attributes. It is primarily an export-oriented platform (Moss -> ERP). The API does not appear to support pushing invoices into Moss programmatically -- invoices enter via email inbox or UI upload. For Orcha, Moss is more of a peer system than a target ERP.

2. API Landscape

API Layers

Authentication

Scopes & Rate Limits

Rate limit headers: X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-RateLimit-Scope. HTTP 429 with Retry-After on exceeded.

Known Endpoints

Note: The developer portal explicitly mentions these resources but only /v1/expenses is shown as a concrete URL. The exact paths for other resources need to be confirmed from the full API reference (which appears to require developer portal access). The apitracker.io listing also mentions "webhooks management API" but this is unconfirmed.

Pagination

Offset-based: page and page_size parameters. Response metadata includes totalPages, totalItems, hasMore.

Error Format

RFC 9457 Problem Details: type, title, detail, pointer, status, instance.

3. Write Capability Verification

Confidence: MEDIUM -- Write operations exist but are limited in scope.

Key finding: The API appears designed primarily for reading expense data and updating accounting attributes (cost centers, account codes, tax rates) on existing records, then exporting. It is NOT designed as an inbound invoice-push API.

4. iPaaS & Middleware Findings

No iPaaS connectors exist for Moss. Moss's integration strategy is built around native connectors to specific ERPs (DATEV, NetSuite, Business Central, SAP Business One, Xero, etc.) and CSV/SFTP exports.

5. Alternative Channels

SFTP (Scheduled Data Transfers)

• Direction: Outbound (Moss -> customer SFTP server)
• Data: Transactions, reimbursements, purchase requests, attachments
• Format: Ready-to-use format for BI tools, ERPs, document archives
• Schedule: Customer-configured delivery schedule
• Relevance for Orcha: Could read Moss export data from shared SFTP if the customer configures it

DATEV Integration (Official Partner)

• Direction: Bidirectional for some data
• Moss -> DATEV: Card transactions, reimbursements, invoices, payments, receipts with line-item accounting (tax rates, accounts, KOST1/KOST2)
• DATEV -> Moss: Suppliers, account codes, cost centres, tax rates (automatic daily sync)
• Products supported: DATEV Unternehmen Online (standard), DATEV Rechnungswesen (advanced, requires ERP add-on)
• Method: API connection (official DATEV partner since Feb 2026)

CSV Export

• Direction: Outbound (Moss -> file)
• Features: Custom CSV templates, configurable field mappings
• Delivery: Manual download or SFTP
• Format: Configurable separator, encoding, date format

Email Inbox

• Direction: Inbound (invoices -> Moss)
• Method: Dedicated Moss email address per customer
• Relevance: This is how invoices enter Moss -- not via API

Native ERP Integrations

Moss has built-in connectors for:

HRIS Integrations

Moss connects to 30+ HR systems for user management sync (Workday, SAP SuccessFactors, BambooHR, Personio, etc.).

6. Licensing & Access Requirements

API Access

Pricing Structure

Customer Setup Checklist

1. Customer has active Moss paid plan with relevant modules (Cards, AP, or Reimbursements)
2. Admin generates API Key ID + Secret Key in Settings -> Company Settings -> API Keys
3. Choose appropriate scope: read (180 req/min) or write (20 req/min)
4. Test OAuth 2.0 token generation
5. If ERP add-on needed, customer must purchase and configure

7. Orcha-Specific Deep Dive

Critical Question: What Role Does Moss Play Relative to Orcha?

Moss and Orcha have overlapping functionality in the AP workflow:

Integration Scenarios

Scenario A: Orcha reads from Moss API (Export Orcha-processed data into Moss)

• Feasibility: LOW
• The Moss API's write scope allows creating/updating expenses, but the API does not appear to support pushing raw invoices (PDFs) into Moss for processing
• Invoices enter Moss via email inbox or UI upload only
• This would require Orcha to email invoices to the customer's Moss inbox -- fragile and indirect

Scenario B: Orcha replaces Moss for invoice processing

• Feasibility: HIGH (for AP-only customers)
• If the customer only uses Moss for invoice management, Orcha could replace that workflow
• Orcha would push directly to the customer's ERP instead of going through Moss
• Does NOT work if the customer also uses Moss for corporate cards or reimbursements

Scenario C: Orcha and Moss coexist, both push to ERP

• Feasibility: MEDIUM
• Orcha handles invoice extraction + pre-accounting
• Moss handles corporate cards + reimbursements
• Both export to the customer's ERP independently
• Risk: duplicate or conflicting data if invoices are captured in both systems

Scenario D: Orcha reads expense data from Moss for analytics/reconciliation

• Feasibility: HIGH
• Use Moss API (read scope) to pull expense data, card transactions, supplier info
• Combine with Orcha's invoice data for comprehensive spend analytics
• Non-conflicting use case

Orcha Integration Capability Summary

8. Recommended Path Forward

Assessment: Moss is NOT a Primary Integration Target for Orcha

Unlike traditional ERPs (SAP, NetSuite, DATEV, Scopevisio), Moss is a spend management tool that competes with rather than receives data from Orcha's invoice processing pipeline.

When Moss Integration Makes Sense

1. Customer uses Moss for cards/reimbursements + Orcha for AP: Both push independently to ERP. No Moss API integration needed -- just coordinate with the customer's ERP.

2. Customer wants Orcha to enrich Moss expense data: Use Moss API read scope to pull expenses, enrich with Orcha's extraction data, then PATCH back accounting attributes. This is a niche use case.

3. Analytics/reconciliation: Pull Moss expense data into Orcha's reporting for a unified spend view.

What NOT to Build

• Invoice push to Moss: The API does not support this. Don't invest in a Moss "write" integration for invoice ingestion.
• Approval workflow automation: Not API-accessible.
• Replacing Moss's ERP connectors: Moss already has native connectors to 20+ ERPs. Duplicating this adds no value.

Architecture Decision

Recommendation

For most customers using both Moss and Orcha: no integration is needed. Orcha should focus on pushing data to the customer's actual ERP/accounting system (which Moss also connects to). The two tools coexist at the same layer of the stack.

If a specific customer requests Moss integration, the API read scope provides clean access to expense data for analytics or reconciliation purposes.

9. Sources

Official Documentation

• Moss Public API Documentation
• Moss API on apitracker.io
• Moss Integrations
• Moss Pricing
• Moss Advanced Accounting
• Moss Product Announcements

Integration-Specific

• Moss + DATEV Integration
• Moss E-Invoice Processing
• Moss Accounts Payable
• Moss DATEV Partnership Announcement
• Moss + Business Central Integration
• Moss + SAP Integration

Third-Party Reviews

• Moss on GetApp
• Moss on Capterra
• Moss on Vendr (Pricing)
• Moss on DATEV Marktplatz

Addendum 2026-05-14 — Defense, Cannibalization, Funding Model

Context: Supplementary research for a German defense-sector customer who currently uses Pleo (cards), DATEV (accounting) and Orcha (AP). They want to replace Pleo. Updated priorities: (1) employee credit cards must be excellent, (2) good mobile receipt-capture app, (3) strong read+write API for Orcha, (4) prefers NOT prepaid — wants a charge card / credit line, not a pre-funded wallet. Methodology and table format follow the Qonto-vs-Pleo master assessment (§1).

A. Defense-sector posture — Verdict: AMBER

B. Cannibalization risk vs Orcha — Rating: HIGH

Moss is the most directly competitive vendor in the researched set — more so than Qonto or Pleo.

• Moss's AP / invoice-management module is a first-class product line, not a side feature: "Moss AI automates invoice coding, matching, and approvals," OCR-based capture, multi-step approvals, direct payment in 70+ currencies.
• The trajectory is actively expanding into Orcha's exact territory. 2026 product announcements added Purchase Order management, Goods Receipt Notes (3-way matching), prepaid-expense period accruals, and an enhanced DATEV Rechnungswesen integration with two-way master-data sync (suppliers, account codes, tax rates). That is precisely the deep-coding, GoBD-grade, DATEV-push workflow Orcha sells.
• Moss explicitly markets itself as the "all-in-one" platform unifying AP automation + cards + reimbursements + accounting — the consolidation pitch is structurally anti-Orcha (a customer buying "all-in-one" is predisposed to question a separate AP tool).
• Mitigant: Moss's extraction depth and tax-compliance rigor are still lighter than a dedicated product, and German GoBD/tax-compliance depth is Orcha's moat. But unlike Pleo ("stays in its lane," rated low-medium) and Qonto ("rising," medium-high), Moss is already in the lane and accelerating. Rated HIGH — recommending Moss to an AP customer hands a credible AP competitor a foothold in the account.

C. API read/write refresh — still primarily read; thin but improving write

The original conclusion holds, with nuance. The public API is actively developed — changelog shows 33 releases between v1.0.0 (9 Feb 2026) and v1.18.0 (13 May 2026). That cadence is the real change since the original doc: this is no longer a static minimal API.

Net: Moss has meaningfully expanded write coverage on reference data (suppliers, dimensions) — Orcha can now sync those bidirectionally. But the two things Orcha would most want are still missing: no invoice/attachment upload (can't push invoices into Moss via API) and no card API. Read side is solid; write side is limited to expense accounting attributes + reference data. No webhooks. Verdict vs the customer's "very good read+write API" priority: partial — better than the original doc implied, still short of full read/write CRUD, and notably weaker than Qonto's API.

D. Card funding model + cards/app UX

Funding model — directly addresses the customer's "not prepaid" priority:

• Moss offers two card products: Moss Credit and Moss Debit.
• Moss Credit is a true revolving credit line — "always 0% interest," flexible repayment daily/weekly/up to ~30–60 day terms, spend now and settle from the company's bank account on a cycle. Marketed credit lines up to €2,500,000, payment terms up to 60 days. Limit set by Moss's own underwriting (cash flow, bank balance, spend history). This is exactly the charge-card / credit-line model the customer wants — NOT prepaid.
• Moss Debit is the prepaid option — draws from a pre-funded Moss wallet you top up in advance. The customer would simply not choose this product.
• So Moss satisfies the funding-model requirement well — it natively offers the non-prepaid model, unlike a pure prepaid-wallet tool. (Note: Moss Credit eligibility is subject to a credit check / underwriting — standard for a credit line.)

Cards & mobile app UX — per G2 / Capterra / Trustpilot reviews:

• Cards product is a core strength: unlimited physical + virtual Mastercards per user, per-card and per-transaction limits, real-time controls, instant freeze, automatic card-blocking if receipts aren't submitted. Reviewers consistently praise card management ease.
• Mobile receipt capture is well-reviewed: automatic OCR data capture "saves 10–15 minutes per receipt," reliable receipt recognition, smooth web↔iOS app sync. AI auto-suggests suppliers, cost centers, GL codes and VAT rates.
• Overall review sentiment: strong on receipt automation, card management and ease of use — Moss's cards+app is genuinely one of the better products in this category.
• Verdict on cards/app UX: STRONG. This is where Moss is most competitive and most aligned with the customer's #1 and #2 priorities.

Addendum Sources

• Moss Security page — ISO 27001:2022, GCP Frankfurt hosting, DORA
• Moss GmbH receives e-money licence, partners with Deutsche Bank for safeguarding
• Nufin GmbH T&C v11.0 INT-de, 1 Jan 2025 (PDF)
• Nufin GmbH T&C v10.1 EEA-de, 1 Sep 2024 (PDF)
• Nufin GmbH T&C UK v2.4, Dec 2022 — legacy, contains "arms trading" exclusion §3.2 (PDF)
• Moss Public API documentation + changelog (v1.18.0, 13 May 2026)
• Moss Corporate Credit Card — Moss Credit vs Moss Debit
• Moss Accounts Payable / AP automation
• Moss Product Announcements — 2026 PO management, Goods Receipt Notes, DATEV ReWe 2-way sync
• Moss reviews — G2
• Moss reviews — Capterra
• Deutsche Bank extends support to defence sector (2025)
• Moss raises Series A — Valar Ventures led (funding context)