Invoices and hours from your platform into the accounting No retyping for the entrepreneur The route MoneyMonk allows

Custom MoneyMonk integration development

Appfront builds integrations with MoneyMonk, the accounting software for freelancers and small business owners. MoneyMonk has integrations with banks and a number of other services, but no public API open to everyone: suppliers can request access. For platforms and apps that want to let their users book entries without retyping, we build the integration via the route MoneyMonk offers for this.

What is a MoneyMonk integration?

MoneyMonk is accounting software for freelancers and small businesses, with invoicing, bank integrations and VAT returns. It has integrations with banks, payment services and a number of other packages. There is currently no public API for everyone: suppliers who want to build an integration can request access, and MoneyMonk has indicated it is considering an API for users.

Many freelancers use a platform alongside their accounting: to find assignments, log hours, invoice or sell. The invoices and revenue generated there are then retyped into the accounting by the entrepreneur, or an export is sent to the accountant. An invoice gets forgotten or booked twice, and the tax return doesn't match what the platform shows.

We build custom because platforms differ: what data you have, how many users use MoneyMonk, and which route MoneyMonk allows for your application. We look at which integration options exist and under what conditions in the first step, together with you and with MoneyMonk. We don't promise an integration that MoneyMonk doesn't allow.

From platform to accounting

Invoices, revenue and costs from your platform into the user's accounting in MoneyMonk.

No retyping

The entrepreneur gives permission, and entries arrive automatically, with no duplicate or forgotten invoices.

The right route

Through the access MoneyMonk offers suppliers, or an import where that is the route.

How we build your MoneyMonk integration

We start with your platform: which data, how many users have MoneyMonk, and how it works today. Then we look with MoneyMonk at which route is available. Sometimes that is supplier access, sometimes an import file the user loads in. We choose the route that works and that MoneyMonk supports.

1
Mapping your platform

Your data, your users, and how entries currently reach MoneyMonk.

2
Agreeing the route

The access or import route that fits, agreed with MoneyMonk.

3
Building the integration

Permission per user, entries, and a check for duplicates.

4
Go-live and maintenance

Go-live, monitoring, and maintenance when MoneyMonk makes changes.

What a MoneyMonk integration actually does

The components below appear in almost every MoneyMonk integration. Which ones you need depends on your platform.

Permission

The user connects their own account.

Invoices

Sales invoices to the accounting software.

Revenue and costs

Revenue, costs and VAT per entry.

Duplicates

A check for duplicate entries.

Import

An import file where that is the route.

Log

Every message logged, including errors.

Who we build a MoneyMonk integration for

The integration is designed for platforms and firms with users in MoneyMonk.

Freelance platforms

Assignments and invoices. The invoices are the core.

Time registration

Hours that lead to invoices. Not having to retype matters most.

Webshops for freelancers

Revenue per day. The revenue entry is what is needed.

Accountants

Many clients in MoneyMonk. The overview is the core.

Technology and integrations

This page is about integrations with MoneyMonk. For other accounting software for small businesses, see our page on a Moneybird integration and our page on an e-Boekhouden integration, and for larger organisations our page on an Exact Online integration. You can read about our approach on custom software development.

If your freelancers use Tellow, see our page on a Tellow integration.

MoneyMonk Supplier access Import file Permission per user Sales invoices Revenue and costs VAT per entry Duplicate check Error monitoring Log per message

Why Appfront for your MoneyMonk integration?

An invoice that is on the platform but not in the accounting software is an error in the tax return. That is what we build around: entries from your platform in MoneyMonk, no retyping, and a route that MoneyMonk supports.

Fewer errors

No forgotten or duplicate invoices.

Time for the entrepreneur

Bookkeeping without retyping.

Agreed

Through a route that MoneyMonk allows.

Security and privacy in a MoneyMonk integration

The integration processes entrepreneurs' financial data. Each user gives their own permission, 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.

Frequently asked questions about a MoneyMonk integration

Questions platforms ask before getting started.

MoneyMonk is accounting software for freelancers and small businesses, with invoicing, bank integrations and VAT returns. It is aimed at entrepreneurs who do their own bookkeeping, possibly with an accountant.

Not publicly for everyone. Suppliers who want to build an integration can request access from MoneyMonk. We look at what is possible for your application in the first step, together with MoneyMonk. MoneyMonk does have integrations with banks and payment services; the user arranges those in MoneyMonk themselves, and your integration does not need to do anything with them.

Then we look at an import file that the user loads into MoneyMonk, if MoneyMonk supports that for your data. It is less automatic, but it still avoids retyping. We do not promise a route that does not exist.

Usually sales invoices, revenue and costs with VAT. Exactly what is possible depends on the route. Sometimes only the revenue per period is needed, sometimes every invoice individually with the customer attached; we align this with what the business owner wants to see in their accounts. Data only goes to the account of a user who has given their own consent for it.

Every entry gets a reference from your platform. The integration checks whether that reference has already been sent, and skips it the second time. Any error is reported, so that the user or your support team can look into it.

Then we update the integration. We track changes in the admin panel, and we test the integration before a change at MoneyMonk affects your users. If a public API becomes available later, an integration that started with an import can switch over without your users having to do anything.

For platforms and apps with many freelancers who use MoneyMonk, and for accountancy firms with many clients in MoneyMonk. For a single business owner with a few invoices, retyping or an existing integration is often enough.

Want your users to book without retyping?

Tell us what your platform does, what data it generates and how many users use MoneyMonk. We'll show you which route is available and what the integration looks like.

Edit content