Payroll to finance
AFAS to Oracle Fusion ERP integration: the payroll journal as a Journal Import in Oracle General Ledger
With an integration between AFAS Profit and Oracle Fusion ERP, the payroll journal goes to Oracle General Ledger automatically as a Journal Import after every approved payroll period, spread over the segments of the chart of accounts. KoppelHet follows the import in Oracle to the end, so a rejected line reaches finance straight away instead of sitting unnoticed in the interface table.
What the integration does
Organisations that run payroll in AFAS Profit and keep their ledger in Oracle Fusion Cloud ERP fill in Oracle's Excel template for journals by hand after every payroll run. If a line fails, it sits in the interface table until someone in Oracle opens the error overview.
- Payroll approves the period in AFAS, as today.
- KoppelHet fetches that employer's journal and converts every line to the Oracle segment combination, with a fixed journal source and category for payroll.
- The journal goes to Oracle as a file and is loaded into the interface table and imported there.
- KoppelHet follows the import job. If the import succeeds, the journal is in General Ledger; if a line fails, finance gets an alert with the Group ID to look up the error in Oracle.
- The KoppelHet platform shows the request ID and import status for each AFAS period.
What to watch for with AFAS Profit and Oracle Fusion ERP
- Oracle imports a journal in two steps. First the file lands in the interface table, then the Import Journals process turns it into a journal. KoppelHet only marks an AFAS period as posted once both steps have succeeded, not as soon as the upload is done.
- The import in Oracle runs asynchronously. Oracle returns a request ID on submission and can send a callback when done. KoppelHet stores that ID with the AFAS period, so finance can find exactly the job belonging to that payroll run in Oracle.
- Finance corrects failed journal lines in Oracle through a corrections worksheet, searched by source and Group ID. The integration therefore uses a dedicated journal source for AFAS and a Group ID per employer and period, so an error in the payroll journal can be found in one search.
- In AFAS the cost centre hangs on the journal line as an analysis dimension. Oracle wants a full segment combination per line, including company, cost centre and account. KoppelHet assembles that combination from account, analysis dimension and employer, and checks beforehand whether every combination exists in Oracle.
- If an organisation has several AFAS employers that sit in different ledgers in Oracle, KoppelHet imports per ledger separately. The journal of one employer then never waits for an error at another.
- If a file was loaded wrongly while the lines are still in status new, Oracle can remove them from the interface table without anything reaching the ledger. The integration offers finance that route before an AFAS period is offered again, so the same payroll journal never appears twice.
- Oracle's journal template has a fixed column order; columns may stay empty but may not disappear. KoppelHet creates the file in that form and puts employer and AFAS period in the journal line descriptive flexfield, so a posting in Oracle stays traceable to AFAS.
How we build and run it
- The integration runs on the KoppelHet platform, hosted in a data centre in the EU.
- Every sync and every error is visible in the functional log; on an error your administrator is notified.
- A change that cannot go through is not half-applied but queued for another attempt.
- KoppelHet is ISO 27001 certified. Data travels encrypted and stays on the platform no longer than needed.
- After go-live we manage the integration and adjust it when your process changes.
- The integration fits next to your existing integration layer. Only the fields in the design are transferred; the platform keeps no register of its own.
Implementation and price
This is not an app you switch on. We build the integration for your organisation on our platform, with building blocks we reuse on every project. So it is custom work that does not start from scratch.
A consultant prepares the intake and analyses both systems. We then record the mapping and exceptions field by field, test in the test or acceptance environment and go live at a moment you choose. Costs are a one-off amount for the setup and a monthly amount for platform, monitoring and support.
Frequently asked questions
Do salaries per employee end up in Oracle?
No. KoppelHet sums per segment combination. Per-employee detail stays in AFAS.
What if a cost centre does not exist yet as a segment value in Oracle?
Then the integration does not submit the journal and reports which combination is missing. After the fix in Oracle the whole journal goes through.
Is Oracle HCM running alongside Oracle ERP?
At many organisations yes, but this integration assumes the Dutch payroll is in AFAS. Cost centres from Oracle to AFAS can be added later as an extension.
Technical details for IT
For those who want to know how it works under the hood: APIs, fields and sources used.
- AFAS is read with a dedicated GetConnector on the journal data per employer and processing line, summed per account and analysis dimension.
- To Oracle through the ERP Integrations REST resource (POST /fscmRestApi/resources/11.13.18.05/erpintegrations with OperationName importBulkData, DocumentContent as a Base64 zip, ContentType zip, JobName and ParameterList); the response contains a ReqstId. Then Load Interface File for Import with Import Journals on GL_INTERFACE, and Import Journals per ledger. Errors in GL_INTERFACE through Correct Import Errors on source and Group ID; lines in status NEW through Purge Interface Tables.
- An integration user in Oracle with rights to import files and start the journal process.
Which fields are transferred
The key fields. The full mapping is agreed per customer.
| Field in AFAS Profit | Field in Oracle Fusion ERP | Notes |
|---|---|---|
Grootboekrekening | Natural account-segment | Through a lookup table |
Kostenplaats (verbijzondering) | Cost centre-segment | |
Werkgever | Ledger en company- of balancing-segment | Fixed mapping per employer |
Bedrag debet of credit | Entered debit of entered credit | |
Laatste dag van de salarisperiode | Accounting date | |
Vaste waarde | Journal source en journal category | For example a dedicated source for AFAS payroll |
Werkgever, jaar en periode | Group ID en descriptive flexfield op de journaalregel |
Related
ADP Workforce Now → AFAS Profit
ADP Workforce Now to AFAS integration: Dutch employees from the US HR system in AFAS Profit
AFAS Profit → 4PS Construct
AFAS to 4PS Construct integration: payroll journal per employer in the right 4PS company
AFAS Profit → Adobe Creative Cloud
AFAS to Adobe Creative Cloud integration: users and product profiles from AFAS Profit
AFAS Profit → AG5
AFAS to AG5 integration: employees, employments and absence from AFAS Profit in the skills matrix