Skip to main content
Boermans Digital
Open menu
MFT in practice

File transfers in practice: a Korper case and examples

Explore Korper’s historical SNS Bank case, followed by four fictional situations. Use them to identify where your own chain needs better monitoring, ownership or recovery agreements.

Short answer

Managed File Transfer (MFT) helps organise and monitor file transfers. Think of a stock file for a supplier or orders for a warehouse. Look beyond whether a file was sent: does it arrive on time, get processed, and who steps in if it does not?

External Korper case · published 2016

SNS Bank: from difficult scripts to more manageable transfers

In 2016, Korper described SNS Bank replacing DOS file-transfer scripts with Automate Enterprise. The case reports that more staff could manage the transfers and that logging improved. The publication mentions 210 workflows.

Korper — SNS Bank case, 27 May 2016 (English; new tab). Source sections: The Challenge and The Benefits. Source content consulted on 15 October 2026.

This is a historical vendor case about Automate Enterprise. No involvement by Boermans Digital or Joshua is claimed. The publication provides no independent measurement of availability, recovery time or error reduction and does not describe the current setup.

Our interpretation for your transfer chain

The relevant question is whether maintenance can be handed over and events can be traced. That helps investigation but does not prove that the receiving application has processed everything. Missing-delivery and recovery arrangements need to be established for your own chain.

This example illustrates transfer automation; it is not a GoAnywhere deployment case or a current platform recommendation.

First conversation with Joshua: about 15 minutes, free and without obligation. Further work, responsibilities and costs are agreed separately.

Recognisable situations

01

The stock file arrives too late

A supplier waits for stock levels every morning, but nobody knows exactly when the file is ready or who follows up a delay. Map the source, destination, agreed time and owner to see where scheduling and monitoring are needed.

Agreeing monitoring and ownership
02

Several partners share one account

Customers or suppliers submit files through the same account. When something changes, it is unclear who still has access. Examine separate identities, least privilege and password and key management. Review access again when a partnership ends.

File-transfer access and management
03

The order was sent, but the warehouse cannot see it

The transfer reports success, but the warehouse system failed to import the file. The team only discovers this after a phone call. Separate receipt from processing, agree alerts and check whether an order has already been processed before retrying.

File sent but not processed: what next?
04

Only one colleague understands the transfer script

A recurring export relies on a poorly documented script. A change or absence can leave work stuck. Examine dependencies and exceptions first. Test a replacement without duplicate processing and agree when to fall back to the previous setup.

Preparing a file-transfer migration

From scheduled transfer to recovery

An MFT solution can support transfers and follow-up. The checks available also depend on the receiving system, the chosen configuration and agreements with partners.

  1. Scheduling: when does the file need to be ready?

    Agree which file is needed, when it must be ready and which next step depends on it. Decide who follows up a missing or late delivery.

  2. Receipt: has the right file arrived?

    Check the expected sender, destination and completeness. A successful transfer does not confirm that the receiving application has processed the contents.

  3. Processing: can the work continue?

    Agree how the receiving application reports a successful import or a rejection. Without that feedback, processing remains unknown even if MFT records the transfer as successful.

  4. Logging: what happened?

    Associate timestamps, statuses and alerts with the same transfer. This audit trail helps trace events. Define who can see the records and which data is necessary; do not log file contents unnecessarily.

  5. Recovery: who handles the failure?

    Decide when an alert is needed and who acts. Before resending, check whether anything was already processed to avoid duplicate orders or entries. Also test what happens when recovery fails.

Apply it to your own chain

  • Choose one file transfer and describe which work stops if it fails.
  • List the sender, recipient, systems involved and responsible colleague.
  • Describe the access required without sharing passwords or keys.
  • Decide how to check receipt and processing separately.
  • Discuss what should happen on failure before choosing a solution.

Frequently asked questions

What if I do not yet know where the transfer goes wrong?

Describe what you can see: which file is missing, when it was expected and who is waiting for it. System names and an error message without personal data may help later. In an initial conversation we identify what information is still needed and whether a technical follow-up makes sense. The MFT Scan is optional.

Further reading at Korper

Further reading at Korper

Boermans Digital is my personal initiative within my work at Korper ICT. I am your first point of contact and help clarify your process question and next step. Korper carries out agreed implementation projects and invoices for that work. We agree in advance what you receive, who does what and how any ongoing management will be arranged.

Origin and review status

The SNS Bank section and contact routes were prepared with AI assistance on 15 October 2026. Source statements and our interpretation are separated. Human subject review and publication approval for the additions are not recorded; earlier approval applies to the earlier version.