Skip to main content
Boermans Digital
Main menu

Process exampleMFT

The file was sent, but not processed: what next?

The transfer shows a green tick, but the receiving team cannot see any new orders. Sending the file again seems reasonable. Yet some records may already have been processed. First establish which part of the chain the green tick actually describes.

Fictional example: a file is sent but not processed.

Key terms explained

Transport means sending the file. Validation then checks whether its contents meet agreed rules. Processing is what the receiving system does with them, such as recording orders. Managed File Transfer (MFT) helps manage transfers; subsequent steps still need checking.

Agree what each status means

Define sent, received, accepted and processed. A file may be on the correct server while the import task has not started. An import may also accept only some records. Identify the system that confirms the business outcome.

Use a traceable reference that lets both parties identify the same delivery. A filename may be insufficient if reused every day. Compare the version, timestamp and expected contents rather than relying on the name alone.

Four checkpoints in a fictional order flow

On a narrow screen, scroll the table sideways. With a keyboard, focus the table and use the arrow keys.

The available signals depend on the implementation and agreements.
CheckpointPossible evidenceFollow-up owner
TransportTransfer result and timestampTransfer administrator.
ArrivalCorrect destination and identifiable file versionReceiving environment administrator.
ValidationFormat and required-data checksOwner of the import requirements.
ProcessingAccepted and rejected records plus business confirmationReceiving application or process owner.

Find the last confirmed stage

Start with the delivery reference and compare timestamps. Check time zones and whether processing was due to have completed. Then examine queues, rejections and partial results. Do not draw a conclusion from the most recent dashboard alone.

A format mismatch needs a different response from a task that has not started. Retain the original version for authorised investigation under the retention policy. Share only the information the relevant administrator needs.

Do not resend blindly

Establish which records have already taken effect before resubmitting a delivery. Some imports recognise repeated instructions; others do not. Replacing a file on disk does not automatically reverse business actions already performed.

Agree who authorises resubmission and how it is distinguished from the original delivery. Have the receiver confirm the intended result. Reconcile accepted and rejected totals again afterwards.

What belongs in the handover agreement?

  • Expected delivery and processing times.
  • The meaning and sender of each confirmation.
  • A contact and cover during absence.
  • A path for partial processing and corrections.
  • Access and retention rules for files and logs.

Detect missing expected deliveries too. No error message may mean that nothing started at all.

Start with one identifiable delivery

Map the systems, handovers and available confirmations for a single delivery. This often reveals gaps in evidence or ownership. An MFT platform can support transfer operations, but business processing still needs explicit agreements with the receiving application.

What would you like to clarify?

Describe the process step or open question. We can explore a practical next step together.

Discuss recovery arrangements

Explore your file transfers with the MFT Scan

Make an unknown processing status visible

Missing evidence of processing is different from evidence of failure. Record the last confirmed step and limit recovery to what it supports. This prevents an unknown outcome being treated as safe to resend.

On a narrow screen, focus the table and use the arrow keys to scroll.

From observation to decision
Established situationNext action
Arrival is confirmed; the import has not started.Investigate the receiving schedule and queue; a second file does not automatically fix this.
Some records have been processed.Compare applied, rejected and unknown records; agree recovery first.
Final confirmation is missing.Request evidence from the receiving system before authorising another delivery.

Fictional delivery: 100 records, 92 processed

Delivery L-240 contains 100 order records. The transport log reports success. The receiver confirms 92 processed and eight rejected records. Resending the whole file could submit the 92 applied orders again; whether this creates duplicates depends on the receiving configuration.

The process owner has the eight rejections investigated and agrees with the receiving administrator how a corrected delivery will be identified. After recovery, every original record needs an explained final status. Merely checking 92 + 8 = 100 is insufficient: also compare the agreed record references and business outcome. This is a fictional approach, not a recovery instruction for your environment.

Complete one transfer agreement

  • Which source confirms business processing, and within which agreed time window?
  • Who investigates missing evidence and who can authorise another delivery?
  • How can you trace the relationship between original delivery, correction and final status?

Record evidence and recovery in the transfer worksheet

Technical background on recognising repeated processing: Microsoft: Idempotent Consumer (consulted 14 October 2026). The chain and counts are fictional; safe handling of repetition must be established separately for the receiving application.

Boermans Digital / privacy

Your cookie preferences

You decide whether Google Analytics may load. The website, scans and calculator also work without Analytics.

Completed fields, scan answers and calculator results are not sent to Analytics.

Which data and retention periods?

We remember your choice on this device for up to 180 days, including a refusal. The _ga and _ga_* Analytics cookies are configured for up to 180 days. Retention at Google is configured separately in the Analytics account.

Storage for website functionsFunctional

The website remembers your privacy choice. Only when you choose to switch language can scans, the guide and calculator temporarily carry answers within the same tab. Contact details are not stored in that transfer.

Contact form protectionAt request review

Google reCAPTCHA loads when you open the review of your completed request. Google then processes technical data and may use security cookies. This is separate from your Analytics choice. Contact by email remains available.

Analytics is off.