Client submissions Changes and hours Payroll software integration

Building a payroll processing and client administration app

Appfront builds apps that help accountancy firms get a grip on what their clients submit: hours, changes and sickness absence come in through a single portal instead of via email, chat messages and spreadsheets. Your employee sees at a glance which client is complete and which still needs to submit something.

What is a payroll processing and client administration app?

The payroll processing itself happens in your payroll software. What comes before it is still done by email at most firms: one client sends a spreadsheet, another a photo of a timesheet and a third phones to say someone has left. That submission stage is the part that takes time and where errors creep in.

A client submission app puts structure around it. Each employer gets their own entry point where they enter what has changed per period: hours worked, new employees, leavers, changes in hourly rate or contract, and sickness reports. Your firm sees per client whether the period is complete and where something is missing.

We build this as a custom solution because every firm divides its work differently. Which client submits what, which collective agreements are involved, which checks you want to enforce before anything comes in, and which employee is responsible for which portfolio. That is your set-up, and the app should follow it.

One entry point per employer

Your client submits hours and changes in a portal tailored to your firm, showing only the fields that apply to them.

Completeness per period

Your employee sees for each client whether everything is in, what is missing and who needs a reminder.

On to the payroll package

The submitted data goes to your payroll package in the format it expects, so nobody has to retype it.

How we build your payroll processing and client administration app

We start with your busiest week of the month and the clients who cost you the most chasing. That is where it becomes clear what the app needs to solve.

1
Mapping submission flows

Which clients submit what, in which form and when. We focus on the clients who are always late or incomplete, because that is where the gains are.

2
Portal per client

We build the input side so that an employer only sees what applies to them. A small client with five employees does not get a screen designed for a client with two hundred.

3
Upfront checks

Missing hours, an employee without a contract or a change without a start date are flagged at submission, not only during processing.

4
Integrating and taking over management

The data goes to your payroll package in a format it can handle. After that, we take over maintenance of the app and extend it where needed.

What a payroll processing and client administration app actually does

Which components you need depends on the size of your portfolio and how much your clients differ from one another.

Hours submission

Employers submit hours worked per employee and per period, with the option to confirm fixed schedules instead of filling them in again.

Payroll changes

Starting or leaving employment, changes to hourly rate, contract hours or job role, each with the effective date the processing needs.

Absence reports

Sick and recovery reports with dates, so that continued payment and the submission to the absence insurer are correct.

Completeness monitoring

For each client and each period, you can see what has come in and what has not, with a reminder sent from the system rather than from your memory.

Documents

Contracts, proof of identity and payroll tax declarations in the right place in the employee's file.

Payroll package integration

The submission is passed on to your payroll package in the format it expects, with feedback if something has been rejected.

Who we build a payroll processing and client administration app for

This app is intended for firms that handle payroll administration for multiple employers and depend on what those employers submit.

Accountancy firms

You do payroll administration alongside bookkeeping. The submission is the part that disrupts your planning, especially around the processing deadline.

Payroll administration firms

Payroll is your main activity and volume is your model. Every minute per client per period adds up to a considerable amount.

Accountancy firms

You have a payroll department alongside the compilation practice. The data must align with the rest of the client file.

Firms with many small employers

It is precisely with small clients that submission takes relatively the most time, because there is no HR department of their own to submit things properly.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

The app runs in the browser and on the phone, so an employer can also confirm their hours on the go. The payroll calculation itself stays in your payroll package; we build the submission process around it and the integration with it. For the integration with the financial administration, we have experience with e-Boekhouden, among others. If you work with time tracking at your clients, also look at time tracking software. Our approach is described on custom software development.

For the firm itself, with workload, checks and deadlines, there is our software for processing clients' payroll.

Web portal and mobile Payroll package integration Payroll journal entry UBL Single sign-on Two-step verification Document storage GDPR and special category personal data REST API Audit log

Why Appfront for your payroll and client administration app?

A portal your clients don't use doesn't lighten the work, it adds to it: you end up with a portal and a mailbox.

Built for your client, not for you

An employer who fills in five hours once a month must be able to do so without instructions. We design for that, because otherwise they'll just phone you anyway.

Checks where they belong

Flagging a missing start date at submission saves your employee a phone call afterwards.

Alongside your payroll package, not instead of it

Processing stays where it belongs. We build the layer around it, so you don't have to migrate.

Security and privacy in a payroll and client administration app

A payroll administration holds personal data and sometimes special category data, such as absence reports. An employer may not record anything about the nature of an illness, and we build it that way: the portal asks for a sick report with a date, not a reason. Access is strictly separated per employer, so clients can never see each other's data.

We use two-step verification for your employees, portfolio-based authorisation and watertight logging of who has viewed which file. Retention periods align with the statutory tax retention obligation and with what the GDPR permits, and documents are stored encrypted. What exactly you record, and for how long, we decide together in advance.

Frequently asked questions about a payroll and client administration app

Questions accountancy and payroll firms ask about submission and processing.

No, and that is a deliberate choice. The salary calculation, the payroll tax return and the processing stay in your payroll package, where legislation and regulations are kept up to date. We build the layer around it: submission by your clients, monitoring of completeness and the integration with the package you already use.

Through a dedicated entry point per employer, in the browser or on a phone. They see only their own employees and only the fields that apply to them. A client with fixed schedules confirms them, a client with variable hours fills them in. The form adapts to the client rather than the other way round.

You see it before it becomes a problem. For each period you can see which clients are complete and which are not, and reminders are sent by the system rather than relying on your employee's memory. You decide when the reminder goes out and to whom.

Usually, yes, and that is the intention. The submitted data is passed on to your package in the format it expects, so nobody has to retype it. What is possible exactly depends on the package; we investigate the integration options before committing to anything.

With restraint, because this involves special category data. An employer may record the sick report and the date, but not the nature of the complaint. The portal therefore doesn't ask for a reason. The data is strictly protected and only visible to those who need it for processing.

They can, for example to submit their own hours or retrieve their payslip, but they don't have to. Some firms deliberately want only the employer to submit. Both set-ups are possible, and we decide in advance which suits your way of working.

Yes. Which fields and rules apply can differ per client, for example for allowances or shift work. We set this up per employer, so the submission matches the agreements that apply to that client. Interpreting the collective labour agreement remains the work of your payroll adviser.

Want your clients' submissions under control?

Tell us how many employers you process and how submissions currently come in. We'll look at your busiest week and show you what a portal would change.

Edit content