Moss is a Berlin spend management platform that puts corporate cards, supplier invoices, reimbursements and AI pre-accounting in one system for small and mid-sized companies in Germany, the Netherlands, the UK and other EEA markets, with exports to DATEV, NetSuite and Xero.
Independently scored, one dimension at a time. Every dimension is sourced, and we say whether a claim is published, reported, or estimated.
The AP page (checked 27 September 2026) lists multi-step approvals, a full audit trail, 3-way matching between PO, goods receipt and invoice, and GoBD certification. Help articles cover XRechnung and ZUGFeRD intake with EN 16931 checks, French e-invoice receipt through the accredited platform Invopop, duplicate checks and four-eye payment approval. Moss GmbH is a BaFin e-money institution and the security page lists ISO/IEC 27001:2022 and DORA, but the help center lists SOC 2 only as Type I (16 September 2025).
The integrations page (checked 27 September 2026) lists API connections to DATEV, NetSuite, Xero, Exact Online, AFAS, Business Central, Odoo, QuickBooks Online and SAP Business One. Help guides show chart of accounts, suppliers, VAT codes, cost centres and custom dimensions imported from the ledger and postings exported on demand, with supplier fields synced both ways in QuickBooks Online. Sage 50, Sage 200, SAP R3/ECC and Twinfield are CSV only, and Sage Intacct is listed as coming soon via CSV.
Moss published a four-week switch plan on 17 July 2026: ledger connection and approvals in week one, policy rules in week two, card rollout in week three and go-live in week four. Virtual cards work as soon as they are issued, and KYC aims to finish within two working days of complete documents (help center, 10 September 2025). No customer sandbox is documented, and a Business Central connection needs Azure administrator approval.
Pay with Moss sends SEPA Instant for EUR under 100,000 euros, Faster Payments for GBP, local-rail payouts through Airwallex including USD by ACH to US payees, and SWIFT on OUR terms otherwise (help center, 6 March 2026). Mastercard cards run on a prefunded debit wallet or an unsecured credit line at 0 percent interest when repaid on time. Card FX is 2 percent, payment fees are not published, and cashback is offered only to high-volume customers at an unpublished rate.
Customer support runs Monday to Friday, 9am to 5pm, by email and by phone lines in eight countries: the UK, Germany, the Netherlands, France, Italy, Belgium, Spain and Austria (contact page, checked 27 September 2026). Paid plans include 1:1 onboarding. Trustpilot shows 4.1 of 5 from 212 reviews with 13 percent one-star ratings (reported, 27 September 2026). No paid support tier or response-time target is published.
Moss said on 5 August 2026 that more than 5,000 businesses use it (its site footer says 7,500+), and TNW and FinTech Global reported ARR above 70 million euros and more than two million transactions a month handled by AI agents. Multi-entity works through linked company accounts under one login with a consolidated view. The limit is geography: Moss Debit covers nine European countries, Moss Credit three, multi-currency accounts come only in EUR and USD, and there is no US product.
The pre-accounting agent trains a model per organisation after 150 exported card transactions or 25 invoices and leaves low-confidence fields blank (help center, 29 June 2026); Moss claims 98 percent plus coding accuracy on one page and 90 percent plus on another. A first-party MCP server answers at mcp.getmoss.com with OAuth and only a read scope, and no docs or tool list are public (probed 27 September 2026). The REST API v1.44.0 has 30 operations with read and write scopes, but writes reach only suppliers and dimensions.
Only the free plan is published: 3 users, unlimited cards and 20 invoices a month (pricing page, checked 27 September 2026). Paid plans are quote only, built from modules and add-ons plus a variable fee on monthly card, invoice and reimbursement volume. The 2 percent card FX fee is published, but Pay with Moss payment fees appear only in a fee schedule at onboarding, and T&C clause 14.3 allows one fee change a year.
Written by the Audit Friendly research team. No vendor edits, no sponsored placement.
You are buying one European platform for Mastercard corporate cards, supplier invoices with approvals and PO matching, employee reimbursements and purchase requests. An AI pre-accounting agent learns how your team codes spend, and exports go to DATEV, NetSuite, Xero, Business Central, Exact and other ledgers. In the EEA the cards are issued by Moss GmbH under its own BaFin e-money licence; in the UK they come from Transact Payments Limited. Moss said on 5 August 2026 that more than 5,000 businesses use it, and it closed a 35 million euro Series C at a 1 billion euro valuation.
The catch is the price and the map. Paid plans are quote only: a platform fee set by modules and add-ons, plus a variable fee on monthly transaction volume. Card FX is 2 percent, and payment fees sit in a schedule you see only at onboarding. The T&Cs let Moss change its fees once a year, and discounts lapse at renewal. Moss sells only in the EEA and the UK. Its MCP server is live but undocumented: it advertises only a read scope, and Moss has published no tool list or setup guide for it (checked 27 September 2026).
Before signing, get these in writing: the included monthly transaction volume and the rate above it, a renewal price cap (clause 14.3 allows a yearly rise of up to CPI plus 2 points without your consent), the Pay with Moss fee schedule and any cashback threshold. Also confirm whether the API and MCP are in your plan, which MCP tools you get, and the format for your data export, which must be requested within 30 days of termination (clause 20.5).
Jobs, mapped to how finance teams actually buy.
The pre-accounting agent predicts expense account, VAT rate, cost centre, cost carrier and custom dimensions on card transactions, invoices and business expenses. It trains after 150 card transactions or 25 invoices, highlights low-confidence fields in yellow and leaves uncertain fields blank. Moss claims 98 percent plus accuracy, so test it on your own chart of accounts.
The AP module routes invoices through multi-step approvals, matches them to purchase requests and goods receipts, and builds payment runs once approved. Payments need multi-user authorisation and two-factor sign-off. Since 10 August 2026, credit notes are separate AP objects that net against invoices at payment.
Moss reads XRechnung and ZUGFeRD files from the document inbox, flags invoices that fail EN 16931 and lets you exempt suppliers during Germany's transition. French entities receive Factur-X, UBL and CII invoices through Moss's accredited partner Invopop. Moss receives e-invoices only; it does not issue them.
Paid plans include unlimited users and virtual cards, with limits by card, team, merchant category and time, and receipts fetched from Gmail and Outlook. Cards draw on a prefunded debit wallet or on credit after underwriting in Germany, the UK or the Netherlands. UK teams can hold EUR and USD accounts with cards that settle 1:1 in those currencies.
Pay with Moss routes payments over local rails through Airwallex when the currency matches the payee's account, including USD by ACH to US payees, and uses SWIFT with the sender paying all charges otherwise. Reimbursements usually reach employees in one to two business days after release. Fees vary by rail and country and appear only in the onboarding fee schedule.
The public API returns expenses with coding, VAT and export history, plus bank transactions and attached files, and scheduled SFTP transfers push CSV files on a timetable you set. Moss suggests BigQuery, Looker Studio or Metabase for cash and entity reporting. The API terms let Moss restrict, change or start charging for a free API at any time.
Forget the 40-row feature grid. Pick a finance workflow and see how this tool and its closest peers actually do it, with our verdict on who wins for whom.
Here's what it really costs: published rates where a vendor lists them, aggregated quote data where they don't, plus a path to your own number.
Up to 3 users with unlimited cards, up to 20 invoices a month, customisable approval and verification steps, and a debit-only Moss wallet.
Unlimited users and cards, advanced approvals and budget controls, accounting and HR integrations, 1:1 onboarding, and debit or credit funding subject to eligibility.
Every package includes the Moss platform and the Corporate Cards module; Reimbursements and Accounts Payable are added per module.
Budgets and flexible approvals, purchase requests and POs, native ERP connectors with controlling dimensions, and AI pre-accounting with mandatory fields.
Variable fee on card transactions, invoices and reimbursements each month; unused volume carries over only within a fixed term of 12 months or more.
Charged by the card issuer on foreign-currency card payments on top of the Mastercard rate, on both the EU and UK sites.
Vary by country, currency and whether SWIFT or a local rail is used; listed in a fee schedule shown during onboarding.
Unsecured credit line for eligible companies in Germany, the UK and the Netherlands, repaid daily, weekly or up to 30 days by direct debit.
Moss Debit is available to companies in Germany, the UK, the Netherlands, Ireland, France, Italy, Spain, Austria and Belgium (help center, 25 August 2025). Moss Credit serves only Germany, the UK and the Netherlands (7 October 2025). The KYC process covers EEA and UK entities, and the site's location menu lists no US option (checked 27 September 2026). A US subsidiary needs another tool, although Moss can pay US suppliers in USD over ACH.
Moss T&C v11.0 (status 1 January 2025) lets Moss change fees once a calendar year with a month's notice (clause 14.3). A rise more than 2 percentage points above CPI needs your acceptance, but clause 17.4 deems it accepted if you do not object in writing within a month and keep using Moss, and under clause 17.5 Moss can apply it despite an objection and give you a right to terminate. Discounts apply only for the agreed fixed term and lapse on automatic renewal (clause 14.1). Fixed terms renew for the same length unless cancelled a month before (clause 19.2). Trustpilot reviewers cite cost increases after introductory offers (reported, checked 27 September 2026), so negotiate a written renewal cap.
mcp.getmoss.com answers with OAuth metadata that advertises a single read scope (probed 27 September 2026), and Moss markets the server on four product pages: the homepage, Moss Intelligence, Moss Accounting and AI at Moss. A May 2026 customer story says LI.FI reaches the Moss API through an MCP connection to Claude, but the developer portal, help center, product announcements, official MCP registry and the getmoss GitHub organisation say nothing about the server. innFactory, a German integrator, flagged the same gap on 25 August 2026. Ask Moss which tools it exposes, which plan includes it and whether it logs agent queries before building on it.
Paid plans are priced partly on monthly transaction volume, and the T&Cs count each card payment, invoice, reimbursement, cash expense, mileage claim or per diem as a transaction. On fixed terms of 12 months or more, unused monthly volume carries over, but it expires at the end of the term even if the contract renews, and it is non-refundable (clause 14.2, status 1 January 2025). Size the volume on actual history.
The Moss API T&Cs (status 6 February 2026) define AI agents and automation tools as users of the customer and attribute every agent action to the customer. They require least-privilege keys and say Moss does not keep customer-specific audit logs of API usage or reconstruct actions for you. If an agent writes suppliers or dimensions, log its calls on your side.
Moss's security resources article (updated 16 September 2025) lists SOC 2 Type I, ISO 27001 and GDPR. The homepage says SOC 2 audited, and the security page lists ISO/IEC 27001:2022 and DORA compliance (checked 27 September 2026). The trust center at trust.getmoss.com is a JavaScript app that showed no report to a public request. If your auditors expect a SOC 1 or SOC 2 Type II report, ask for it before signing.
Scored on what an outside agent can actually reach: the documented API, how it authenticates, and whether the vendor ships an MCP server.
Inside the product, Moss Intelligence covers a pre-accounting agent, automated receipt chasing, a policy agent and pre-payment checks on VAT, duplicates and IBAN changes. The coding agent trains an organisation-specific model once 150 card transactions, 25 invoices or 25 business expenses have been exported, and leaves a field empty when its confidence is low (help center, updated 29 June 2026). Moss claims 98 percent plus coding accuracy on its Moss Intelligence page and 90 percent plus from day one on its homepage; no independent account confirms either figure.
Exists: yes. https://mcp.getmoss.com returns a 401 with OAuth protected-resource metadata that names getmoss.com as the authorization server; sign-in runs through getmoss.com/mcp/connect with PKCE and client ID metadata documents, and no dynamic client registration endpoint is advertised (probed 27 September 2026). Moss markets the server on its homepage and its Moss Intelligence, Moss Accounting and AI at Moss pages, and a May 2026 customer story says LI.FI reaches the Moss API through an MCP connection to Claude. The developer portal, the help center (no results for MCP in English or German), product announcements, the official MCP registry and the getmoss GitHub organisation carry nothing on the server; the portal's use-case page only suggests building a custom MCP server on the API. Searches for a Moss MCP mostly surface an unrelated product at moss.dev.
Scope: the only scope advertised is read, and the tool list sits behind sign-in, so which objects it exposes is unverified. The documented alternative is the public REST API, v1.44.0, first released 9 February 2026, at https://public-api.getmoss.com. Its 30 operations read expenses, suppliers, expense accounts, dimensions, tax rates, payment terms, users, teams, departments, bank accounts, bank transactions and files. Writes are limited to creating and updating suppliers, dimensions and dimension items; nothing touches cards, approvals or payments.
Turnkey: unclear for MCP. The OAuth flow implies each user signs in with a Moss login, but Moss publishes no setup guide, plan requirement or admin switch. The API needs an admin to generate a key in Settings and confirm it in the Moss mobile app; tokens carry read or write scope, with limits of 180 reads and 20 writes a minute. Moss's API terms (6 February 2026) treat AI agents as users of the customer, make the customer liable for them, and say Moss keeps no customer audit log of API calls.
Who wins for whom: A German, Dutch or UK company that wants card limits by team and merchant category alongside GoBD certification: Moss. A UK or EU small business that wants merchant-locked vendor cards and approvals from £14 a user: Pleo. A French, German, Spanish or UK company that wants unlimited single-use, recurring and multi-use cards with top-ups routed through approval: Spendesk.
Granular card limits, GoBD certified. Paid plans give unlimited virtual Mastercard cards with limits by card, team, merchant category and time, issued in the EEA under Moss GmbH's BaFin e-money licence, alongside GoBD certification and four-eye payment approval.
Where it loses: The help center lists SOC 2 only as Type I with no Type II report visible, and Moss sells only to EEA and UK companies, with no US product.
Source: AF score rationale: Compliance depth 82; Moss use cases and watch-outs.
Watch: Moss Corporate Debit Cards Explained 0:45 · Review · Business Expert on YouTube (Moss partner link)
Merchant-locked cards, approvals from Build. Mastercard physical and virtual cards come on every plan, vendor cards lock to one merchant, Build at £14 a user a month adds approval workflows and an internal controller role, and Scale adds advanced card controls.
Where it loses: The trust page names no SOC 1, SOC 2 or ISO 27001 report and offers reports only under NDA, and Start has no approval workflows.
Source: AF score rationale: Compliance depth 66; Pleo pricing tiers, use cases and watch-outs.
Watch: When it comes to company money, it's important to feel in control of your team's spending. 0:35 · Customer story · Pleo on YouTube (official)
Unlimited cards on its own licence. Foundations includes unlimited physical, single-use, recurring and multi-use Visa debit cards with budgets, card top-ups run through the approval flow, and cards in the EEA come from Spendesk's own ACPR-licensed payment institution.
Where it loses: The public security page names ISO 27001:2022 and no SOC 1 or SOC 2 report, and multi-condition approval workflows are a quoted add-on.
Source: AF score rationale: Compliance depth 79; Spendesk pricing tiers, use cases and watch-outs.
Watch: AI DemoDay Summit 2025: Spendesk 13:21 · Official demo · CFO Connect on YouTube (Spendesk's own community)
Who wins for whom: A German, Dutch or UK company on DATEV, AFAS or SAP Business One that wants card spend AI pre-coded before export: Moss. A UK or EU company on Business Central that wants dimensions and vendors synced both ways: Pleo. A European company on Sage 100, ACD or Pennylane that wants expenses and payments pushed to the ledger: Spendesk.
DATEV-ready, AI pre-coded exports. API connections reach DATEV, NetSuite, Xero, Exact Online, AFAS, Business Central, Odoo, QuickBooks Online and SAP Business One, importing accounts, VAT codes, cost centres and dimensions, while an AI agent pre-codes card spend before export.
Where it loses: Sage 50, Sage 200, SAP R3/ECC and Twinfield are CSV only, Sage Intacct is still listed as coming soon via CSV, and native ERP connectors are a quoted add-on.
Source: AF score rationale: GL / ERP fit 80; Moss use cases, pricing tiers and watch-outs.
Watch: With a patchwork of tools, Hive needed a unified solution for spend control. So they turned to Moss. 1:15 · Customer story · Moss spend management on YouTube (official)
29 connectors, depth varies by ledger. Pleo lists 29 accounting systems: the NetSuite SuiteApp imports tag groups, accounts and VAT rates with scheduled exports, Business Central syncs dimensions and vendors both ways, and Xero pulls tracking categories.
Where it loses: QuickBooks is described only as one-click exports, FreeAgent, ADDISON, BMD, Netvisor and SIE use CSV templates, and multi-entity management starts on Scale at £249 a month.
Source: AF score rationale: GL / ERP fit 72; Pleo pricing tiers and watch-outs.
Watch: Pleo - Chift Customer Stories 2:44 · Customer story · Chift on YouTube (Pleo's integration vendor)
European ledgers, no Intacct or SAP. Native connectors to NetSuite, Business Central cloud, Xero, DATEV, Sage 100, Exact Online, Odoo, ACD and Pennylane pull accounts, tax codes, suppliers and dimensions and push expenses and payments back to the ledger.
Where it loses: No Sage Intacct or SAP connector is listed, NetSuite lacks SuiteTax and project support, Business Central takes draft-only purchase invoices, and ERP integrations are a quoted add-on.
Source: AF score rationale: GL / ERP fit 76; Spendesk pricing tiers and watch-outs.
Watch: AI DemoDay Summit 2025: Spendesk 13:21 · Official demo · CFO Connect on YouTube (Spendesk's own community)
Spenders are prompted for purpose, participants and tips on client meals and team events, and the pre-accounting agent detects hospitality expenses for tax compliance.
Credit notes get a workflow and lifecycle, net against invoices at payment and keep the link through export.
Portage led the round with Cherry Ventures, taking total funding over 200 million euros. Moss said the money goes to Finance AI for spend, receivables, journal entries and the month-end close.
Moss added a Purchaser role, admin-defined sender lists for PO imports by email and default verifiers for deliveries.
Teams can send POs, payment confirmations and invoice queries to suppliers from Moss, with each email logged against the record.
API v1.0.0 shipped read endpoints for expenses, suppliers, expense accounts, dimensions, tax rates and users; dimension writes followed on 18 and 19 February 2026 and supplier writes on 13 and 25 March 2026.
Moss publishes no price for paid plans. The free plan covers up to 3 users, unlimited cards and 20 invoices a month. Above that, a quote combines a platform fee set by the modules and add-ons you choose with a variable fee on monthly transaction volume, and there is no per-user charge (pricing page, checked 27 September 2026).
Public benchmarks are thin. Vendr's Moss page carries one undated buyer note of 30 percent off an Enterprise plan with 600 transactions plus a free month, and no median. To compare quotes, give Moss your monthly count of card transactions, invoices and reimbursements, and ask for the platform fee, the included volume and the rate above it.
Without a fixed term, the platform agreement can be cancelled at any time, or with one month's notice if payment services are included. Fixed terms renew automatically for the same length unless cancelled a month before renewal, and discounts lapse at renewal (T&C v11.0, clauses 14.1 and 19). Moss may adjust fees once a year.
On exit, Moss can block access on the termination date and expects you to back up data first. If you ask within 30 days after termination, it provides your data in a common format of its choosing, and extra data preparation is charged (clauses 20.4 to 20.6). Scheduled SFTP exports and the API are practical ways to keep your own copy while you are a customer.
Moss's own switch plan targets 30 days: ledger connection, chart of accounts and approval flows in week one, policy rules in week two, card rollout and subscription moves in week three, and go-live with a short parallel run in week four (Moss magazine, 17 July 2026). Paid plans include 1:1 onboarding from Moss.
Your side supplies KYC documents for each entity, which Moss aims to process within two working days. You also need an accountant or tax advisor to map accounts, VAT codes and dimensions, and an admin for HR and SSO sync. A Business Central connection needs Azure administrator approval.
Partly, and mostly read only. Moss runs a first-party MCP server at mcp.getmoss.com that signs users in through Moss with OAuth and advertises only a read scope. Moss has published no tool list or setup guide for it (checked 27 September 2026).
The documented route is the REST API. An admin creates a key, and a write-scoped token can create and update suppliers, dimensions and dimension items; reads cover expenses, files, bank transactions, users and master data. Neither route can approve invoices, manage cards or release payments, and the API terms make the customer liable for anything an agent does.
Answered only from our own published research on this tool, never from general internet noise. If we cannot answer it well, our research agents will dig in and publish a sourced answer.