Connect Bechtle procurement to requests, receipt and equipment records. Bechtle offers PunchOut/OCI and digital documents, among other services. Service Automation Suite can connect agreed data to the internal service workflow; we validate the interface first. This is an integration example, not an existing or certified Service Automation Suite connector.
The work between your applications
Supplier connected. Who handles execution?
A supplier connection makes data usable in your internal workflow. Service Automation Suite connects it to the activity, its owner and confirmed execution. Arrange receipt and handover, for example, and update records only after the agreed confirmation.
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.
Procurement & approval
From approved request to the agreed procurement route.
Connect Bechtle procurement to requests, receipt and equipment records. Bechtle offers PunchOut/OCI and digital documents, among other services. Service Automation Suite can connect agreed data to the internal service workflow; we validate the interface first. This is an integration example, not an existing or certified Service Automation Suite connector.
Service Automation Suite · Central coordination
Connect request, supplier reference and rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Request & context
Requester, location and required item
Supplier & feedback
Agreed electronic data exchange
Start with the approved requirement
Use a TOPdesk request, for example. Record who needs the item, its destination and the required approval. A request alone does not authorise an order.
Apply your rules
Compare the request with a shared register or matrix: role, location, permitted item and budget. Request missing information or a decision before proceeding with an exception.
Keep the appropriate procurement route
Bechtle documents PunchOut/OCI for procurement systems. This is not the same as a freely available REST API. Keep an existing procurement integration where appropriate and validate which data or documents Service Automation Suite can use for internal follow-up.
Delivery & records
Procurement and service share the same request.
A purchase must stay connected to its intended employee or workplace. Use available references and documents for receipt, records and handover. We validate with you and Bechtle which information can be transferred electronically.
Service Automation Suite · Central coordination
Match to request and confirmed receipt
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Supplier data
Available status, item and delivery references
Internal execution
Receipt task, equipment records and feedback
Match the same order and line
Match external references to the correct request and items. Handle partial deliveries separately when provided by the source; repeated status updates must not create duplicate records.
Coordinate receipt and handover
Request confirmation of receipt or handover. Then update agreed records, for example item, person and location in TOPdesk. Use only attributes that are actually available.
Return the outcome
Show the requester and responsible team what is complete and what remains open. Delivery status does not automatically close the internal request; your completion rules determine that.
Exceptions & follow-up
Something missing? Turn it into focused follow-up.
An unexpected item, missing delivery or return request needs follow-up. Keep the supplier reference connected to internal ownership.
Service Automation Suite · Central coordination
Connect request, supplier reference and rules
Combine the data with your policy, risk assessments and checks. Request information or a decision where needed, track actions and record the outcome.
Request & context
Exception, affected item and owner
Supplier & feedback
Available response or follow-up action
Identify the discrepancy
Compare available data with the request and confirmations. Record missing or inconsistent information without silently marking the entire workflow complete.
Assign the right person
Create a TOPdesk verification task, for example, including the request, item and supplier reference. Returns, replacement or additional information follow their agreed route.
Verify and update again
Use the confirmed outcome to update records and open activities. Configure any feedback to the supplier separately, using the agreed interface and permitted messages.
Under the hood
How to connect, test and manage the integration.
For administrators who want to understand how it works: connect Bechtle 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
Connect a supplier reference to internal execution
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.
Request, order and line reference
Store the relationship between the internal request and available external references. Recognise repeated updates before creating anything.
Item, person, location and available status
Map only available data and define the source for each field. Dispatch status does not confirm receipt or handover.
Confirmed receipt, exception and follow-up task
Update records after the agreed checks. Fitness-for-use decisions for protective equipment remain with authorised personnel. An uncertain order outcome requires review before retrying.
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.
Signature declined. Keep the process moving.
A request awaits a ValidSign signature. Declining, expiry and technical failure each need different handling.
Combine
Link the request, signing request and document. Read the available status and apply agreed conditions to determine the next action.
The outcome determines what follows
Signed: process the document and confirm the activity. Declined: route the reason to the owner. Temporary technical failure: retry only under the configured error rule.
The benefit
Appropriate follow-up for each outcome without counting a sent signing request as completed work.
A different name does not mean a new record.
A person or organisation has a different name in the source than at a customer or supplier. Matching text again can create incorrect or duplicate relationships.
Combine
Retain verified identifiers and source rules in a shared table. Reuse the relationship for requests, tickets and other integrations.
The outcome determines what follows
Known key: use the relationship. Multiple candidates or a missing identifier: request review. Once confirmed, reuse the established relationship.
The benefit
A consistent data foundation managed by your team instead of investigated again for every connection.
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
Bechtle in your workflow
Part of one workflow
From delivery to current asset records
Supplier data creates the initial record. Then compare with Intune, for example, and update TOPdesk selectively according to your source rules. Follow up exceptions and verify confirmed outcomes again.
