AFAS
I investigate how AI can prepare work around AFAS files, using agreed sources and an employee who decides.
Review my software and processProcess example 01
Authorised file details, workflow status and supporting documents.
A short summary with open points and source references.
Process example 02
An agreed data selection and the finance team checklist.
A list of missing fields or deviations from fixed rules.
Process example 03
A minimal selection of file details and an agreed document checklist.
An overview of available documents and items still to request.
Suppose a supplier emails an updated service agreement as a PDF. The workflow extracts the supplier, reference, start date, amount and term, each with a source reference. It compares those fields with the permitted selection from the AFAS file. An unfamiliar reference or changed amount becomes a review item; a missing start date stays empty.
The file owner sees the document beside the extracted fields and differences. They correct a wrong match, request missing information and approve the next step. Only then can an agreed write route update the file. See the approach to document checks.
Your administrator decides which file data the workflow may read. AFAS uses GetConnectors to retrieve data and UpdateConnectors to add or change it. We first establish which fields and actions are available through your App Connector and test the permissions, logging and fallback. Read access does not imply write access.
Sources: AFAS connectors and Jonas documentation.
We choose one recurring process and measure its current workload. I define the sources, matching rules and approval step, then build the preparation. We test ordinary cases and exceptions together. Your team receives the workflow, instructions and a manual fallback.
A file overview refers to approved SharePoint documents. The reviewer receives the documents and open questions together, within agreed permissions.
A file owner receives a draft request for missing documents. They check the content and recipient before sending it through Outlook.
Jonas can analyse workflow information and fill fields automatically. We first check whether that built-in function solves the task. My work starts where preparation is still needed between a mailbox, another system and AFAS, with an agreed approval step. See what your software already does.
Tamboer does not claim a certified AFAS AI integration. We first investigate permissions, the connector route and partner requirements. This page describes process exploration. Whether and how these processes can work in your AFAS environment is established with your administrator and, where needed, your AFAS partner.
We start with read access to the minimum required data. Every prepared result refers to its sources. Missing information triggers a review. Writing changes or sending messages requires a separate, explicit approval step. Access, logging and the fallback are part of the agreed design.
No. We start with the software and working methods you already use. A new subscription is only discussed if the chosen process requires it.
We first check whether an existing feature solves the task. Tamboer adds process design and preparation between systems where work still remains.
Tamboer does not claim a certified AFAS AI integration. We first investigate permissions, the connector route and partner requirements. This page describes process exploration. Whether and how these processes can work in your AFAS environment is established with your administrator and, where needed, your AFAS partner.
These examples prepare work for review. Changes and external messages require human approval and a separately agreed route.
Bring one recurring task and the names of your systems to your free AI plan. We examine where preparation can help and what needs checking first.
With Joost
Start with a free AI plan: an AI plan for your whole business, three tailored examples and a demonstration. Bring one task that keeps returning.
Request your free AI plan