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 a bookkeeping programme for freelancers and small business owners, 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: vendors 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, record hours, invoice or sell. The invoices and revenue generated there are then retyped into the accounts by the business owner, or exported to their accountant. An invoice gets forgotten or booked twice, and the tax return does not match what the platform shows.
We build custom solutions because platforms differ: which data you have, how many users MoneyMonk has, and which route MoneyMonk allows for your application. In the first step, together with you and MoneyMonk, we look at which integration options exist and under what conditions. We do not promise an integration that MoneyMonk does not allow.
From platform to accounts
Invoices, revenue and expenses from your platform into the user's accounts in MoneyMonk.
No manual re-keying
The business owner gives consent, and bookings follow automatically, with no duplicate or forgotten invoices.
The right route
Via the access MoneyMonk offers vendors, or an import where that is the route.
How we build your MoneyMonk integration
We start with your platform: which data, how many users work with MoneyMonk, and how things currently run. Then we review with MoneyMonk which route is available. Sometimes that is vendor access, sometimes an import file the user uploads. We choose the route that works and that MoneyMonk supports.
Your data, your users, and how bookings currently reach MoneyMonk.
Agreeing with MoneyMonk the access or import route that fits.
Consent per user, bookings, and checks for duplicates.
Going live, monitoring, and maintenance when MoneyMonk changes.
What a MoneyMonk integration actually does
The components below come up in almost every MoneyMonk integration. Which ones you need depends on your platform.
Consent
The user connects their own account.
Invoices
Sales invoices to the accounts.
Revenue and expenses
Revenue, expenses and VAT per booking.
Duplicates
Checks for duplicate bookings.
Import
An import file where that is the route.
Audit log
Every message logged, including errors.
Who we build MoneyMonk integrations for
The integration is intended for platforms and accountancy firms with users on MoneyMonk.
Freelance platforms
Assignments and invoices. The invoices are the core.
Time registration
Hours that lead to invoices. Avoiding retyping matters most.
Webshops for freelancers
Revenue per day. The revenue booking is what's needed.
Bookkeepers
Lots of clients in MoneyMonk. The overview is the core.
Technology and integrations
This page is about integrations with MoneyMonk. For other bookkeeping software for small businesses, see our page on a Moneybird integration and our page on an e-Boekhouden integration, and for larger administrations our page on an Exact Online integration. You can read about our approach at custom software development.
If your freelancers use Tellow, see our page on a Tellow integration.
Why choose Appfront for your MoneyMonk integration?
An invoice that exists on the platform but not in the books is an error in the tax return. That is what we build around: entries from your platform flow into MoneyMonk with no manual retyping, using a route that MoneyMonk supports.
Fewer errors
No missed or duplicate invoices.
Time back for the business owner
Bookings without retyping.
Reconciled
Through a route that MoneyMonk permits.
Security and privacy in a MoneyMonk integration
The integration processes financial data of business owners. Each user gives their own consent, 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 a bookkeeping programme for freelancers and small business owners, with invoicing, bank integrations and VAT returns. It is aimed at business owners who do their own bookkeeping, sometimes with an accountant.
Not public for everyone. Vendors who want to build an integration can request access from MoneyMonk. In the first step, we look together with MoneyMonk at which options exist for your application. MoneyMonk does have integrations with banks and payment services; users arrange those themselves in MoneyMonk, and your integration does not need to do anything with them.
Then we look at an import file that the user loads into MoneyMonk, provided MoneyMonk supports that for your data. It is less automatic, but it still avoids manual retyping. We don't promise a route that doesn't exist.
Usually sales invoices, revenue and costs with VAT. What exactly is possible depends on the route. Sometimes only revenue per period is needed; sometimes each invoice separately with the client attached. We match this to what the business owner wants to see in their books. Data only goes to the account of a user who has given their own consent for it.
Each entry receives an identifier from your platform. The integration checks whether that identifier has already been sent, and skips it a second time. An error is reported, so the user or your support team can investigate.
Then we adapt the integration. In the management area we keep a record of changes, and we test the integration before any change at MoneyMonk affects your users. If a public API arrives 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 on MoneyMonk. For a single business owner with a few invoices, manual entry or an existing integration is often sufficient.
Want your users to book without retyping?
Tell us what your platform does, which data it generates and how many users use MoneyMonk. We will show you which route is available and what the integration would look like.