.svg)
Reporting with AFAS: what the ERP can do itself, where it hits its limits and how to fill the gap (2026)
AFAS is broader than accounting alone — HR, payroll and workflows run in the same environment. For management reporting, though, the package gets less far than that breadth suggests. What it offers as standard, where the limits sit and how to put a management report on top of AFAS without a setup project.
.png)
Reporting with AFAS: strong at administration, HR and payroll — but a custom reporting layout, cash flow statement and group picture come ready-made from Finstack, from EUR 39/month.
Reporting with AFAS: what the ERP can do itself, where it hits its limits and how to fill the gap
From the setup question to a report that is simply there — dashboards, 2-way Excel sync and consolidation on top of AFAS.
TL;DR
AFAS is a broad ERP — accounting, HR and payroll in one environment — but the reporting lags behind that breadth: what there is depends on the setup and requires admin knowledge and maintenance. A management report with a custom layout, budget comparison, KPI trends, cash flow statement and group picture is not there as standard — not even for businesses with a single administration. Finstack connects AFAS directly — read-only, at transaction level, with the allocation dimensions included — and delivers that reporting layer ready-made from EUR 39/month.
What can AFAS do for management reporting itself?
AFAS is more than an accounting package: it is a broad ERP in which HR, payroll and workflows run alongside the financial administration. For reporting, that means a rich foundation — personnel costs, usually the largest cost item, originate in the same environment as the bookings.
The financial side delivers the familiar set per administration: a profit and loss statement and balance sheet, a trial balance, the VAT return and receivables and payables overviews with an aging analysis. A strength of AFAS is its allocation model: cost centers are full-fledged dimensions on which bookings are tagged — the basis for reporting per team or location. Recording budgets is possible as well. And because payroll runs in the same environment, personnel costs reconcile directly with the accounting — without a monthly import from a separate package.
On top of that, AFAS offers dashboards and analyses. In practice, that delivers less for management reporting than the breadth of the package suggests: what you get to see depends on the setup, and reports, analyses and authorizations have to be configured and maintained — admin knowledge not every finance team has in-house. Businesses with a single administration run into this just the same.
With a well-configured environment and an in-house AFAS administrator, something can certainly be built. But a management report — the seven fixed sections from the main article on the good management report, in a custom layout, with comparisons against budget and last year, every month within 5-10 working days — is here too something other than a printout or a cockpit. Where exactly the line sits is covered in the next section.
Where does AFAS hit its limits in management reporting?
AFAS hits its limits in management reporting at the same five points as every package — with as the AFAS-specific color that whatever is there has to be configured first — and that practice often turns out more modest than the breadth of the ERP suggests.
The layout. The standard reports follow the chart of accounts and the setup. Much can be adjusted, but a custom reporting structure — a margin bridge, calculated lines such as an EBITDA line, the sequence management is used to — is not there as standard and takes setup work per change.
The comparison. Recording budgets is possible, but the full setup — month and year-to-date next to budget, last year and a latest estimate, as the variance analysis asks for — is not something you build in as standard.
The KPIs and the cash flow. A fixed KPI set with twelve-month trends and budget comparison is not part of the standard, and neither is a full cash flow statement — for many readers the most important section of the report.
Multiple administrations. Managing multiple administrations in one environment is possible, but that is management, not consolidation: an added-up group picture cleaned of internal deliveries is not there as standard; more on that further down.
Sharing. Internally, employees can look along through the own environment — provided it is authorized and configured. Giving external stakeholders such as investors or the accountant structural access to just the steering information is another story: in practice the report leaves the package as a PDF or export.
And the management question. Whoever manages the environment determines how fast reporting changes happen — with AFAS often an in-house application administrator or a consultant, as with other packages sometimes the accountant. No unwillingness, but every change is a job in the queue. Exactly why the reporting question deserves its own answer.
Why a reporting layer on top of AFAS — even with a single administration?
Because what can be built in AFAS for reporting rarely leads to a full management report in practice — and whatever is there requires setup that is never finished. Every new breakdown, every changed KPI definition and every new reader means configuring, testing and authorizing again. For the ERP’s core processes that thoroughness is a strength; for steering information, which should move with the business, it becomes a brake.
A reporting layer flips that ratio. The finance logic you would otherwise have to configure yourself — a custom reporting layout, the budget comparison, the cash flow statement, consolidation with eliminations, click-through to the booking — ships as standard, and control sits with finance itself: adjusting a mapping is an action, not a change request. And because the layer sits read-only on AFAS, nothing can go wrong with the source along the way: the ERP’s setup stays exactly as the administrator built it.
The three routes from the overview per accounting package apply here too. The Excel route works, but keeps the monthly export-and-paste work alive — how to automate that is covered in automating management reporting. The BI route fits a data team, but moves the setup question to another tool with the same maintenance burden. The data-layer route delivers the reporting ready-made, with AFAS as the reliable source beneath it.
That this is not just a group question shows in practice: businesses with a single administration — without any consolidation need — put a reporting layer on AFAS too, purely for the custom layout, the cash flow statement, the KPI trends and the sharing with stakeholders. And important: this is not either-or. AFAS remains the system where the administration, HR and payroll run — exactly what it is strong at. The reporting layer only takes the figures out and turns them into steering information, without a single setup change in AFAS itself.
How do you connect AFAS to a reporting tool?
The connection between Finstack and AFAS runs through GetConnectors: you install them once in the AFAS environment, then authorize the access and the first synchronization runs. That is a bit more setup work than with other packages, but it remains a one-time step — in consultation with the in-house administrator where there is one; after that everything runs automatically.
The connection is read-only and works at transaction level. Finstack retrieves not just period balances but the underlying general ledger transactions with date, journal, contra account, description and currency — plus the chart of accounts, the open items and the cost centers. Those sync along and stay available as a dimension in the reporting. Writing back is not possible: bookings, HR and payroll stay entirely within AFAS.
The first synchronization pulls in the full history — not just the current financial year but the years before it, so trends and analyses work across the entire history — and after that the actuals refresh automatically every day, with a manual refresh at any moment: useful right before the reporting deadline or after a correction that needs to show immediately. The sync is as light for AFAS as a regular export.
Then comes the step that makes the difference: the mapping. The AFAS accounts are linked to your own reporting structure — the layout management understands, with a dedicated mapping per cost center where wanted: handy for spreading personnel costs across functional lines, for example. The budget and the latest estimate live where they already live — in your own Excel or Sheets model — and sit next to the actuals through the 2-way sync. One-off work, typically within a day, managed by finance itself.
How do you report next: dashboards, Excel and sharing with stakeholders?
Reporting then runs along two equal roads — and most teams use both.
From the platform. The Finstack dashboards show the P&L, the balance sheet, the cash flow statement and the KPIs continuously current, in your own reporting layout and with every line clickable through to the source booking in AFAS. Filtering and grouping on cost centers works along — including across administrations. And working capital gets the insights the package itself only partly offers: a direct cash flow overview, a customer-and-supplier overview, and the aging analysis — for a group across all administrations. All without setup work in AFAS itself — and every change in the reporting is visible immediately for everyone with access.
In your own Excel or Google Sheets model. Through the 2-way sync, the actuals from AFAS refresh in the existing model in one click, next to the budget columns. The structure and formatting stay untouched — only the monthly export-and-paste work disappears. That works identically in Excel and Google Sheets.
Nor does it have to stay one structure: parallel reports — your own management layout next to the fixed template of an investor or bank — run simultaneously on the same figures; see parallel reporting for SME CFOs.
Sharing closes the chain. Management, investors and the accountant get access to the dashboards and reports through Finstack, with rights per user: every reader sees what is meant for them and can change or break nothing — and nobody needs an AFAS authorization for it. The question “where does this number come from?” is answered during the meeting with one click.
What changes with multiple AFAS administrations?
With two or more administrations — a holding with operating companies, multiple labels or locations — the difference between managing and consolidating becomes visible: multiple administrations in one AFAS environment is convenient management, but not yet a group picture.
Adding up alone is not enough either. A management fee from the holding, salaries recharged from a payroll entity or internal deliveries sit in two administrations at once and count twice in a simple addition. Those intercompany flows have to be eliminated at group level before group revenue and margin are right. What that group report looks like in substance is covered in management reporting for a holding company with multiple entities.
Finstack handles the processing side: every AFAS administration connects separately, is mapped to one group chart of accounts, and the intercompany relations are recognized and eliminated automatically — from 1 to 50 entities, without setting up separate IC accounts. Mixing works too: a group with the operating companies on AFAS and a subsidiary on another package simply runs in one consolidated report. The month-end close per administration meanwhile simply keeps happening in AFAS, exactly where it belongs. For groups already working with multiple administrations in one AFAS environment, the step is small: the same source and the same closing routine — only the merging and eliminating comes on top as an automatic layer.
For the deeper consolidation mechanics with AFAS — IC detection, reconciliation, eliminations in the consolidation layer — there is a dedicated deep-dive: consolidating with AFAS. This reporting article deliberately does not duplicate that; here the result counts — the group picture and per-entity figures from one process, with the working-capital insights at group level included.
What does reporting on top of AFAS cost and how fast are you live?
Finstack starts from EUR 39 per month for the first entity, with no implementation fees. The connection with AFAS takes only a one-time installation of GetConnectors, and the full setup — mapping to your own reporting structure, dashboards, Excel sync — typically stands within a day. For a package where reporting otherwise quickly means a setup project, that is the biggest difference: no change project in AFAS, no authorization round, no test environment — the reporting layer stands loosely on top.
Control then stays with finance: you adjust mappings and structures yourself, without a change request to an administrator or consultant and without an invoice per adjustment. If you would rather hand off the setup entirely, you can opt for guided onboarding: the Finstack team then sets up the report together with you.
Set that against the alternatives. The Excel route costs export days every month. The BI route and the AFAS setup route both carry implementation and maintenance costs, and move the dependency rather than solving it. And switching packages is not on the table at all: AFAS does the administration, HR and payroll well — that is what you want to keep. The comparison that counts is not AFAS versus reporting tool, but manual work versus automation on top of the same ERP.
The payback period is practically the first month: the export days disappear immediately, and the report gains reliability and shareability at the same time. If an administration or entity joins later, you simply connect it — the subscription grows with the structure, not the other way around. How this works for other packages sits in the overview of reporting solutions per accounting package.
Use cost centers in AFAS consistently — per team or location. The reporting tool picks up that dimension automatically, and you get a P&L per unit without extra setup work, with a dedicated mapping per cost center where wanted.
Explore Finstack.
Free trial for 14 days.
Access to all features. No credit card required.
.png)
The 3 most common mistakes in reporting with AFAS
Three patterns we see again and again at AFAS users. Each costs time or trust; each is preventable with the right setup.
Turning every reporting wish into a setup job
Having every new breakdown or KPI configured by the administrator or consultant means waiting, testing and maintenance — so the report quietly goes stale. Steering information should be managed by finance itself: adjusting a mapping should be an action, not a change request.
Mistaking a cockpit for the management report
An internal dashboard shows the state, but a management report tells the story: the seven fixed sections, the comparison against budget and last year, the cash flow statement and the commentary. Whoever mistakes the cockpit for the report discusses figures without context — and decides on them.
Exporting and pasting every month
The monthly export-and-paste routine from AFAS costs days, introduces version differences and starts over with every late booking. The model may stay — the feed has to go: a direct connection puts the actuals in automatically every day, and the freed-up days shift to analysis and commentary.
Frequently asked questions
Can't find your question? Let us know
Can I build a management report in AFAS?
To a limited extent. AFAS offers standard reports per administration and — depending on the setup — dashboards and analyses, but a custom reporting layout, full budget comparison, KPI trends, cash flow statement and group picture are not there as standard. A reporting tool on the data layer delivers that layer ready-made.
Why a reporting tool next to AFAS?
Because the reporting in AFAS lags behind the rest of the ERP in practice: reports and dashboards require setup, admin knowledge and maintenance per change. A reporting tool ships the finance logic as standard — custom layout, budget comparison, consolidation, click-through — and puts control with finance itself; businesses with a single administration use that layer too.
Does AFAS have a cash flow statement?
Not as standard a full cash flow statement the way the management report asks for it: where cash came from, where it went and what the expected position is. A reporting tool on the data layer does deliver that — including a direct cash flow overview and, with multiple administrations, consolidated across the whole group.
Do cost centers from AFAS carry over into the reporting?
Yes. Cost centers from AFAS sync along through the connection and stay available in the reporting: filtering and grouping per cost center, including across administrations, with a dedicated mapping per cost center — for example to spread personnel costs across functional lines instead of one collective item.
How do I get figures from AFAS into Excel without manual work?
Through a 2-way sync: the actuals from AFAS refresh in the existing Excel or Google Sheets model in one click, next to the budget columns — the structure and formatting stay untouched. The monthly exporting and pasting disappears, and the model always reconciles with the administration.
Can I combine multiple AFAS administrations into one report?
Managing multiple administrations is possible in AFAS, but a consolidated group picture takes a reporting tool. Finstack connects every administration separately, maps to one group chart of accounts and eliminates intercompany flows automatically, from 1 to 50 entities. The group picture and per-entity figures come from one process.
What does reporting on top of AFAS cost?
Finstack starts from EUR 39 per month for the first entity, with no implementation fees. The connection with AFAS takes only a one-time installation of GetConnectors, and the full setup typically stands within a day, managed by finance itself. The payback period is practically the first month: the export days disappear immediately.
CFO turned Founder - Finstack
Sources and provenance
- Finstack — Integrations with AFAS and other packages: finstack.io/solutions/integrations
- Finstack — Reporting & insights (dashboards, Excel/Sheets sync): finstack.io/solutions/reporting-insights
- Finstack Help Center — Sources & connections (sync frequency, security, read-only): help.finstack.io
- Finstack — Pricing (from EUR 39/month): finstack.io/pricing
- AFAS — product information: afas.nl
Last reviewed: 28 July 2026 · Next review: October 2026
Consolidated reporting and forecasting.
