TimeTell supports time tracking, planning, leave and expenses. Service Automation Suite connects employees and projects to the right records and passes approved time and expenses to payroll or accounting. Less re-entry, with checks for missing data and discrepancies.
The work between your applications
Time approved. Administration follows through.
TimeTell supports time tracking, planning, leave and expenses. Service Automation Suite connects employees and projects to the right records and passes approved time and expenses to payroll or accounting. Less re-entry, with checks for missing data and discrepancies.
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?
Start with one integration, register or check. Build on the same data and rules.
HR & records
Employee changed? Keep TimeTell aligned.
Use your HR source for employees, departments and employment details in TimeTell. Keep time tracking and planning aligned with confirmed employee changes.
Service Automation Suite · Central coordination
Relate data, verify and determine follow-up
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Agreed source
Employee or project data
Process & verify
Records in TimeTell
Choose the HR source
Agree the authoritative employee fields and the effective date of each change.
Compare and match
Match the same employee and map department and cost centre. Review missing or duplicate relationships.
Update and confirm
Update agreed data in TimeTell and verify processing. An employment end date does not mean deleting historical time records.
Projects & planning
The right project alongside recorded time.
Connect project and customer data from your administration to TimeTell. Teams can record time against agreed projects and accounting can receive approved actual time.
Service Automation Suite · Central coordination
Relate data, verify and determine follow-up
Add a central register and source-of-truth rules. Check differences, request missing data and determine what gets updated.
Agreed source
Microsoft Dynamics 365
Employee or project data
Process & verify
Records in TimeTell
Define the project and owner
Choose the source for project codes, customer relationships and validity. Agree which projects may be available.
Connect the records
Map available project data to agreed TimeTell records. Validate the relationship before passing time entries on.
Return approved time
Return agreed actual time to the correct project. Route discrepancies to the project owner.
Time & accounting
Approved time. Ready for payroll or invoicing.
Combine approved TimeTell time and expenses with the correct employee, period and project or customer agreement. Deliver validated data, for example to AFAS or Exact Online.
Service Automation Suite · Central coordination
Relate data, verify and determine follow-up
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Agreed source
Approved time and expenses
Process & verify
Payroll or accounting, with confirmation
Select approved entries
Use only the agreed period, time and expenses with the required approval.
Validate the destination
Map project, time type and cost centre to the correct administration. Keep payroll and invoicing as separate routes.
Deliver and track the outcome
Check acceptance and use stable references to prevent duplicate delivery. Correct rejected entries before processing them again.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect TimeTell to your other applications, map the data and use the response in the next step. Configure it centrally in Service Automation Suite.
Agree access and application scope
TimeTell describes API integration and FTPS file exchange using XML/CSV. We agree modules, data, read/write permissions, approval and frequency for your environment, then test the chosen route. These examples illustrate possible configurations, not a pre-tested or certified Service Automation Suite connector.
Choose 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.
Build 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.
Configure 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.
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.
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.
Need 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
TimeTell in your wider 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.
