Work → invoicing
Transfer approved time and items for finance review and processing.
All integrations
Financial data
Bring approved hours, items and customer data together for invoicing in AFAS Profit. Finance reviews the data before it is processed.
From product to process
How to use the integration
Keep customer records aligned
Share agreed customer and contact details with service or accounting applications.
Exceptions → tasks
Route missing information or discrepancies to the team responsible for follow-up.
Combine into one controlled process
Data → rules → execution-
Combine
Customer + approved time + contract
-
Determine & check
Check and prepare invoice data
-
Execute & report back
Finance review · Update accounting · Return status
Check sources and rules, test changes and track the outcome. Manual tasks get an owner and confirmation.
Build visually. Manage easily.
Reuse building blocks, adapt your process and test the change. Manage it yourself, together with us or let Scope4mation take care of it.
More process examples & technical details
The work between your applications
Records updated.
Why still compare spreadsheets?
Service Automation Suite connects AFAS with your other applications, people and rules. Keep data aligned, work moving and outstanding actions visible.
A change, request or alert
Service Automation Suite
Data, people, assets and relationships on one foundation.
- Compare
- What exists? What should exist?
- Determine what is needed
- Matrix · policy · legal requirements
- Coordinate the next steps
- Checks · tasks · approvals · actions
Execution ↔ feedback
Your people and tools
For example. Also with other teams, suppliers and applications.
Verify. Inform. Report.
What is complete? Who needs to act? Which exception needs attention?
Time entries to AFAS Popular
Service work in TOPdesk. Processing in AFAS.
Connect time recorded on tickets, changes and activities to the right customer or project in AFAS. Current person and company data provides the foundation.
Match customer, project & processing
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Time entries & service work
Time accounting or invoicing
Collect service time
Use agreed time records and their related person, organisation and work.
Match customer and project
Match the sales relationship and project in AFAS. Route missing data for review.
Process after the agreed review
Connect data to time accounting or invoicing. Finance retains review responsibility; the workflow receives the outcome.
From AFAS to TOPdesk Popular
Keep people and companies current in TOPdesk.
Use AFAS as the source for people, branches or companies in TOPdesk. Service Automation Suite matches relationships and updates agreed fields, giving tickets and requests the right context.
Match, relate & map
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
People, branches & companies
Person and company records
Read the right source data
Read relevant people and organisation data from AFAS. Use agreed identifiers to match the same relationships.
Update TOPdesk selectively
Create missing records and update changed fields and relationships. Data managed elsewhere stays with its authoritative source.
Build on that context
Use current person and organisation data in service requests, changes and employee lifecycle workflows. Data sync is the foundation; workflow execution is the next step.
Back to AFAS Popular
Return the outcome to AFAS too.
AFAS can supply data and receive outcomes. Have a completed workflow step update agreed data in AFAS. This is a separate route, not an automatic reversal of every sync.
Check & map the outcome
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Completed activity or workflow status
Agreed fields or records
Identify confirmed execution
Use the confirmed completion of an activity, such as account creation. The outcome, not merely the command, triggers feedback.
Define what AFAS should receive
Service Automation Suite applies matching, mapping and processing rules. Only selected data is written back.
Update and record the outcome
Process through the available AFAS interface and link success or failure to the original workflow.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect AFAS to your other applications, map the data and use the response in the next step. Configure it centrally in Service Automation Suite.
Example configuration · shaped by your process
Process time entries or transactions and return acceptance
Connect and test
API ComposerChoose the API method, URL and authentication. Manage the host and credentials in an environment. Test a request in Discovery and inspect the fields actually returned by the API.
Combine and compare
Data Flow ComposerSelect fields, translate codes and relate records using shared data. Compare source and target to identify new, changed or incomplete records.
Execute and use the response
API ComposerBuild the request body from validated data and inspect Body Preview before testing. Use the result ID in Data Context for the next request or save output to an entity. Configure write-back separately.
Recognise errors and follow up deliberately
API ComposerConfigure error rules by HTTP code and/or message. A temporary API failure can use bounded retries. A missing relationship or rejection needs another route: record the cause and configure a verification task for the appropriate team, for example.
Which data do you maintain?
An example configuration, not fixed field names or a mandatory combination.
- Entry reference and source ID
- Retain the relationship to external processing so existing results can be recognised.
- Customer, project code and period
- Enrich and validate entries using shared master data before executing the write operation.
- Acceptance or rejection
- Process the reference or rejection reason from the response and route incomplete entries for correction.
Sent ≠ processed. Use the response and agreed validation to determine the next step.
Need to publish data yourself?
Use Endpoint Composer to publish a configured Service Automation Suite data object. Choose read and write methods and security profiles so a customer can retrieve agreed service data or a supplier can submit information, for example. Configure data selection and subsequent processing separately.
Endpoint ComposerFrom data to a complete process?
Combine the integration with a form, a shared matrix, a review or collaboration between service teams. For example, an approved request leads to execution in Microsoft Entra, a ValidSign signature request and feedback in TOPdesk. Your process determines the steps needed; not every use case requires all these components.
Explore the connected building blocksBeyond the first integration.
Use the same data and rules in your next process.
Start with one use case. Connect customer, employee and asset data, for example, and agree which source is authoritative. Reuse those relationships, a matrix where needed and configured actions in the next workflow. Agree who maintains the data and rules. Expand without repeatedly connecting and maintaining the same information.
Time recorded, but not yet accounted for.
Service work is complete but time entries do not match a known customer, project code or agreed processing route.
- Combine
- Combine time entries with central customer and project relationships and accounting rules. Request specific missing information.
- The outcome determines what follows
- Accepted: retain the accounting reference. Rejected: have the owner correct the cause. Resending an entry requires checking whether it was already processed.
- The benefit
- Less investigation and correction between service and finance without automatically treating errors as billable work.
Ordered, delivered and actually in use?
Procurement, a supplier and technical inventory each hold part of the picture. A delivered asset is not automatically assigned to its correct owner.
- Combine
- Compare orders, delivery details, serial numbers and inventory with central ownership relationships. Keep missing confirmations part of the workflow.
- The outcome determines what follows
- Matching data: update the agreed records. Unknown device, unexpected owner or unconfirmed delivery: create work for the correct support group.
- The benefit
- Fewer gaps between administrative and technical records and targeted follow-up of discrepancies.
Refreshing a report does not guarantee reliable data.
A source request can succeed while data is missing, differently coded or not yet fully retrieved.
- Combine
- Combine pagination and output mapping with agreed data checks. Use shared relationship tables to connect sources.
- The outcome determines what follows
- Checks passed: prepare the dataset. Deviation: request review and expose freshness. Temporary API failures follow a bounded recovery path.
- The benefit
- A clearer distinction between a technically successful import and information fit for decision-making.
Your process needs more than a standard action?
Configure the missing API request, input and output in API Composer. Use its response in the next step and combine it with data tables, forms and automations. Extend the same product and reuse the configured building blocks.
Use Service Automation Suite to update a ticket in TOPdesk, for example, with fields available through its API, such as category, priority, status and support group. For another application, configure its request and field mapping. The outcome determines the next action: confirm, add information or request review, not merely check whether the request arrived.
Build it yourself: explore the technical approachNeed to publish data or let others submit it? Endpoint Composer exposes a configured Service Automation Suite data object with selected methods and security profiles. Other building blocks handle subsequent processing.
From product to workflow
AFAS in your workflow
Pull up a chair. Or join us online.
Over coffee, tea or online: tell us what you are working on.
We can help with the integrations, automation and coordination your process needs, even if your application is not listed yet.
