Custom Moss integration development
Appfront builds integrations with Moss, the platform for business expenses with company cards, invoices and expense claims. Moss has standard integrations with Exact Online, AFAS and Twinfield, among others. For organisations with their own ERP, purchasing system, project administration or reporting, we build the connection via the Moss API, so that expenses, cost centres and suppliers don't have to be transferred by hand.
What is a Moss integration?
Moss is a business expense platform built for European companies. Employees pay with a company card, supplier invoices come in and are approved, and expense claims are submitted with a receipt. Moss has standard integrations with accounting packages: with Exact Online and AFAS via an API, and with Twinfield via an export. In addition, there is its own API, accessed via OAuth 2.0, for expenses, accounting codes and dimensions, users and suppliers.
A standard integration covers the bookkeeping, but not always the rest. If you want to see expenses by project or assignment, you transfer them to project administration by hand. Cost centres and projects are created in the ERP and then again in Moss. And if you want to see expenses alongside budgets from another system, you combine spreadsheets every month.
We build custom solutions because organisations differ: which system is leading for cost centres and projects, which expenses should go where, and who needs to see what. We'll look at which data the Moss API offers for your situation together with you in the first step.
Expenses where they belong
Card transactions, invoices and expense claims in your own systems.
One source for dimensions
Cost centres and projects from your ERP in Moss.
Via the Moss API
An integration built on the API that Moss provides.
How we build your Moss integration
We start with your financial administration: which system is leading for cost centres and projects, which expenses need to go where, and where most transferring happens today. We often start with cost centres and projects, because good coding in Moss makes everything after that easier. Expenses flowing to project administration and reporting follow once the first integration runs well. That way you quickly see whether the integration saves time, and afterwards we maintain it when Moss or your own systems change.
Systems, dimensions and who is leading.
What the Moss API offers you.
Dimensions in, expenses out.
Go-live, monitoring, and maintenance when things change.
What a Moss integration concretely does
The components below come up in almost every Moss integration. Which ones you need depends on your administration.
Expenses
Card, invoice and expense claim.
Dimensions
Cost centres and projects.
Suppliers
In sync with your ERP.
Users
From your HR system.
Budgets
Expenses alongside budget.
Audit log
Every message recorded.
For whom we build a Moss integration
The integration is intended for organisations that work with Moss alongside other systems. The more expenses and dimensions there are, the more time an integration saves.
Project organisations
Expenses per project. Project administration counts.
Organisations with their own ERP
One source for dimensions. Avoiding double work is the core.
Controllers
Expenses alongside budget. Overview matters most.
Software suppliers
A product alongside Moss. The API is the core.
Technology and integrations
This page is about integrations with Moss. For bookkeeping there are our pages on the Exact Online integration and the AFAS integration, for purchasing our page on purchasing software, and for expense claims on the go our page on the expense claim app. You can read about our way of working at custom software development.
Why Appfront for your Moss integration?
A cost centre created twice, and expenses that are manually sent to project administration each month, cost time and cause discrepancies. We build on that: expenses in the right place, one source for dimensions, and an integration with the Moss API.
No manual re-entry
Expenses flow through automatically.
Coded correctly
Dimensions from one source.
Budget in view
Expenses alongside budget.
Security and privacy in a Moss integration
The integration processes financial data, employee data and supplier data. Access credentials are stored encrypted and used only by the integration, and every message is logged.
The integration runs in a European data centre, with encrypted storage and daily backups. We record the processing in a data processing agreement.
Frequently asked questions about a Moss integration
Questions organisations ask before they get started.
Moss is a business spend management platform for European companies. Employees pay with a company card, invoices are approved and expense claims submitted, and everything is coded for bookkeeping.
Yes, including Exact Online and AFAS via an API, and Twinfield via an export. If your software is among them and the integration does what you need, custom development isn't necessary. A custom integration is for a system that isn't on that list, or for data the standard integration doesn't carry.
Via the Moss API, with access through OAuth 2.0. The API gives access to spend data such as card transactions, invoices and expense claims, and to accounting attributes, dimensions, users and suppliers. We'll look at which data can flow in each direction in the first step.
Yes. A cost centre or project created in your ERP appears in Moss, so employees can select it straight away. If it is closed in your ERP, it also disappears from the selection list in Moss.
Yes. Expenses go to the project administration with their coding, per project or assignment, so you see the costs in one place. You choose whether that happens immediately or only after approval. An expense that is later coded differently is updated in the project administration, so project costs stay accurate.
The integration reports it and records what went wrong. The message is retried or set aside for review, so no expense is lost or booked twice.
For organisations with their own ERP, procurement system or project administration alongside Moss, and for software vendors who want to connect their product to Moss. If you only use a package that already has a standard integration, we'll first check whether that is enough.
Connect Moss to your own systems?
Tell us which systems you use alongside Moss and which data is currently transferred by hand. We'll show you what the integration would look like.