Custom RGS integration
The Referentie GrootboekSchema, or RGS for short, is the Dutch standard coding for general ledger accounts. By linking your accounts to RGS codes, you make administrations readable for reporting software, accountants, banks and the SBR chain, even when every client has its own chart of accounts. Appfront builds the integration that handles this in your own software: every ledger account with an RGS code, the mapping managed per administration, and updated whenever a new version of RGS is released.
What is an integration with the Referentie GrootboekSchema?
An RGS integration links the ledger accounts in an administration to the codes of the Referentie GrootboekSchema. Every account, whatever it is called or numbered at a client, gets a reference code that says what it means: liquid assets, revenue, staff costs. This allows reporting software, a dashboard or a credit assessment to read the administration without anyone first having to work out the chart of accounts. The integration reads in the chart of accounts, suggests a code for each account, lets an employee check the mapping and maintains it per administration.
Without an integration, every firm and every supplier does it their own way. The accountant keeps a translation table per client in a spreadsheet, a dashboard only works for clients with the standard chart of accounts, and a bank asks for the figures in its own format. When a client adds an account, it falls outside the translation. If a new RGS version arrives with new or discontinued codes, someone has to work out by hand which mappings need to be adjusted.
We build custom because your software and your clients determine what the integration needs to do. It makes a difference whether you are a firm with hundreds of client administrations in different packages, a vendor who wants to build RGS into your product, a bank that wants to read submitted figures, or a group with its own charts of accounts. RGS falls under SBR governance and gets a new version every year; the integration follows those versions and connects to the RGS taxonomy, so the link with SBR reports comes along.
Every account
An RGS code.
Comparable
Across all administrations.
Updated
With every new version.
How we build your integration with the Referentie GrootboekSchema
We start with your administrations: which packages they are in, how many there are, whether they already use RGS and where you need the codes. Then we build the first integration, reading in charts of accounts and mapping them to RGS codes with review by an employee, because that is where most of the work lies. You work with it for a while. Reporting at RGS level, the transition to new versions and exchange via audit file and SBR follow if that goes well. After that, we keep the integration up to date with every new version of RGS.
Packages, schemas, usage.
The first integration.
Expansion.
Go-live, monitoring, and maintenance when things change.
What an integration with the Referentie Grootboekschema (RGS) actually does
The components below appear in almost every RGS integration. Which ones you need depends on your role and the number of administrations.
Import
Chart of accounts from any package.
Proposal
One RGS code per account.
Validation
Integration reviewed and recorded.
Versions
Moving to the new RGS.
Reporting
Figures at RGS level.
Exchange
Audit file and SBR.
Who we build a Referentie Grootboekschema integration for
The integration is intended for organisations that work with many administrations or many charts of accounts and want to compare, report or submit figures without translating them client by client.
Accountancy firms
Hundreds of client administrations.
Software vendors
RGS in your own product.
Banks and lenders
Reading submitted figures.
Groups
Comparable operating companies.
Technology and integrations
This page is about the Referentie Grootboekschema (RGS) in your administrations. For sending messages via Digipoort, see our page on SBR integration; for XBRL outside Digipoort, our page on an XBRL integration; and for software for the whole firm, our page on accountancy software. If you use Exact Online, also take a look at our Exact Online integration. You can read about our approach on building custom software.
Why Appfront for your Referentie Grootboekschema integration?
A dashboard that only works for clients on the standard schema, a mapping table nobody maintains any more, or a new RGS version that has to be processed by hand every year costs a firm or supplier time and produces figures that cannot be compared. That is what we build against: every account with a code, the integration checked, and every new version processed.
Comparable
Every administration on RGS.
Checked
Proposal plus approval.
Up to date
New version processed.
Security and privacy in a Referentie Grootboekschema integration
The integration works with your clients' financial data. Only the chart of accounts is needed for mapping; balances and transactions are retrieved only when a report requires them. Access is set up per role and per administration, and every change to a mapping is recorded with a name and timestamp.
The integration runs in a European data centre, with encrypted connections and storage and daily backups. For the processing, we enter into a data processing agreement with you. Previous mappings are kept per version, so you can show how a report was produced.
Frequently asked questions about a Referentie Grootboekschema integration
Questions that accountants, controllers and software suppliers ask before getting started.
The Referentie Grootboekschema (Reference General Ledger Scheme), a Dutch standard coding for general ledger accounts. Each account gets a reference code that states what it means, so that administrations with different charts of accounts can still be read in the same way.
RGS is a public-private partnership and falls under the governance of SBR. A task group releases new versions, and working groups manage the content and the technology. The RGS Taxonomy is maintained by a management group that includes the Tax and Customs Administration, Statistics Netherlands (CBS), the Chamber of Commerce (KvK), banks and Logius.
A new version is released every year, with an alpha, beta and final release. Codes are added, replaced or withdrawn. For each version, the integration shows which mappings need to be adjusted.
RGS is about the coding in the accounts, SBR about exchanging reports with government and banks. The RGS Taxonomy connects the two: accounts coded to RGS are easier to convert into an SBR report.
Many packages, such as AFAS, SnelStart and Twinfield, support RGS. Custom work is needed if you combine accounts from different packages, if ledger accounts have not yet been mapped, or if your own software needs to be able to read RGS.
Yes. Based on the name, the number and previous mappings, the integration suggests a code for each ledger account. An employee checks and confirms; the software does not decide on its own.
For firms, suppliers and financiers that work with many sets of accounts or charts of accounts. For a single set of accounts in a package that already supports RGS, the standard feature is usually enough.
All your accounts on RGS?
Tell us how many sets of accounts you have, which packages they are in and what you want to use RGS for. We'll show you how an integration can handle it.