Moss Security Whitepaper_Feb 2026.pdf

CFE-25-74390 - Nufin-27001-Cert - Issue 1.pdf

Professional Services

How Greyt helps growing companies gain control of spend with Moss

Moss helps Lemontree’s swamped finance team

RS Finance delivers 100% spend visibility for clients with Moss

Snap Finance improves spend governance with Moss

Tonny Media reduces production spend and saves time with Moss

Ebitwise saves up to 20 admin hours per month for their clients

Seibert Group saves 5 admin days per month with Moss

Venture Beyond reclaims £30k in VAT with Moss

These cookies collect information that helps us understand how visitors interact with our website in order to improve it. Your consent pursuant to Art. 6 (1) (a) GDPR is the legal basis for the processing of this data. If you agree to the use of these analytics cookies, please move the slider to “On.”

Moss Cards are issued by Moss GmbH pursuant to a license by Mastercard International Incorporated. Moss GmbH is authorised and regulated by the German Federal Financial Supervisory Authority (BaFin) as an e-money institution (license no. 159024). Mastercard and the circles design are registered trademarks of Mastercard International Incorporated.

These cookies are strictly necessary to provide you with services that work correctly. The website will not function properly without these cookies. You can change your browser settings to disable these cookies, but it may affect your ability to access and use the site.

Additional information is provided in the Cookie Policy on our website.

When you visit our website, it may store or retrieve information on your browser in the form of cookies to give you a more personalized web experience. You can choose not to allow some types of cookies. Certain cookies may be set by third party providers located in the US. By agreeing to such cookies, you also consent to the transfer of your data to the US according to Art. 49 (1) a GDPR. Please note that the US recipient may not provide a data protection level equivalent to the data protection level in the EU. Government authorities in the U.S. may have the right to access your data without effective legal remedy.

These cookies are used to make advertising messages more relevant to you and your interests. Your consent pursuant to Art. 6 (1) (a) GDPR is the legal basis for the processing of this data. If you agree to the use of these marketing cookies, please move the slider to “On.”

Modules

Platform

Integrations

By Workflow

By Role

Insights & Learning

Company

Featured

We use cookies that are necessary for the website to function. In order to provide you with the best browsing experience, some cookies also collect data to optimize our website, support our marketing and to analyze site usage. For detailed information, please refer to the settings.

Products

Customers

Resources

Pricing

Product

Hoodie Hoo Agency: Building Project Intelligence with Moss's API | Customer Story

Case Studies - What our customers say

For most finance teams, the goal is visibility. For Johannes Laß, Co-Founder at Hoodie Hoo Agency, visibility was only the starting point.

Hoodie Hoo Agency is an Essen-based fashion and fulfillment company that designs and produces textile products, runs e-commerce shops for its customers, and handles fulfillment end-to-end. With its own production facility in Turkey, a sourcing operation spanning multiple countries, and a customer base ranging from single-product brands to full-service clients, its cost structure is anything but straightforward. Every project has a different mix of production, procurement, sampling, logistics, and labour. Understanding whether a project was profitable meant manually piecing together data that lived in multiple systems, none of which spoke to each other.

Moss was already central to Hoodie Hoo's spending and invoice workflow. What it lacked, until recently, was a way out.

The problem with data that stays in one place

Before the API, Johannes had a clear picture of what was being spent, but not what it meant. Invoices were uploaded to Moss, processed, and exported to DATEV for the tax advisor. The data was accurate. It just stayed put.

The core challenge was project-level controlling. Hoodie Hoo uses project numbers as the connective tissue across its operations: each production run, sourcing order, and shop setup belongs to a project. Moss already supported custom dimensions, and Johannes had created a project number dimension to capture this. But populating it was a manual process. Project numbers lived in the ERP. Getting them into Moss meant someone had to type them in, which was always prone to error and always dependent on the right person being available at the right time.

The downstream effect was significant. With project numbers unreliably assigned, it was impossible to run a clean analysis of which projects were actually profitable. Sales decisions were being made on instinct.

With API access, Johannes built what he describes as a data hub: a system that pulls Moss transaction and invoice data, combines it with ERP data, and allows cost to be viewed, classified, and allocated at a project level.

The first thing he built was a Moss project sync tool that pushes project numbers from the ERP directly into the Moss dimension. Employees uploading invoices can now immediately select the correct project number. What had been a manual, error-prone step became automatic.

From there, the system grew. Johannes designed a classification framework on top of the Moss data, allowing every transaction to be tagged not just with a project number but with a cost type, a sales channel, and a set of custom attributes that reflect how Hoodie Hoo actually operates.

To handle the reality that not everyone knows, at the time of payment, what a cost belongs to, he built a task workflow on top of the classification layer. When an invoice arrives without sufficient context, the system generates a to-do, sends it via Slack to the relevant person, and surfaces the invoice with a dedicated view so they can classify it directly.

The result is a system that can aggregate across any dimension of the business: by project, by customer, by employee, by supplier. A project that runs for six to twelve months, involving sampling, procurement, production, fulfillment, and shop management, can now be assessed cleanly at close.

The near-term roadmap includes automated classification rules for recurring costs that do not need human review, freeing up attention for the exceptions that do. And when webhooks become available, the polling system Johannes built as a workaround can be replaced with real-time updates.

For Johannes, the broader point is about what becomes possible when financial data is no longer trapped inside a platform.

Experience modern spend management with Moss.

Hoodie Hoo Agency: building project intelligence with Moss's API

Hoodie Hoo Agency: building project intelligence with Moss's API

More stories

Experience modern spend management with Moss.