AI with people deciding
From claims email to controlled claims intake
A cargo claim usually starts as an email with attachments. Reading the document is not enough: the system has to understand what it means operationally.
Ultimate Maritime Logistics4 min read
Where a cargo claim starts
Claims rarely arrive in a neat structure. A customer sends a message, a claim form and supporting evidence, and someone has to work out which shipment it concerns, whether the details are complete and what should happen next. Everything that follows depends on that first step.
Document recognition can speed up the typing. It does not answer the questions that matter: does this B/L exist, does this container belong to it, and does the evidence support what the claim says?
Understand before creating
The goal is not just document recognition. Incoming forms and supporting evidence must first be linked to the right B/L, container and operational context before structured data is accepted.
In practice that means three checks before anything is created: does the B/L exist, does the container belong to it, and is the supplied evidence consistent with the claim? When the answers line up, the claim enters the workflow with its operational context attached. When they do not, the exceptions go to a person instead of becoming an incomplete record.
Six steps, one controlled action
An illustrative flow: email and evidence come in. The information is read and structured. The B/L is confirmed in Dynamics 365. The container is validated against the B/L, voyage and operational data. Evidence and exceptions are checked.
Only then is an action prepared, which is carried out in Dynamics 365 after review by an employee.
How the claims workflow is divided
In Flex Maritime Logistics the work is split across the products. Flex Intelligence handles intake: it extracts the claim details, summarises the email and attachments and flags missing information. Flex Connect can add external enrichment where needed, for example shipment or vessel data retrieved from carrier or AIS sources via APIs.
Flex Run manages the claim workflow on Dynamics 365. It adds the operational context of B/L, ship, voyage, cargo and containers, keeps the claim log, assigns an owner, tracks the status and supports review of the claim and evidence. Dynamics 365 Finance & Operations records the claim liability accrual and adjusts or releases it on resolution. Teams review and approve the outcome.
Preserve evidence and exceptions
Original documents remain part of the case file, while validation results and missing information become visible for controlled follow-up.
If information is missing, the case does not stall unnoticed. The gap is visible, someone can request what is needed, and the claim moves on with a clear record of what was checked and by whom.
From claims intake to claims performance
Once claims are captured in a structured way, they become management information. Open claims and claim value are useful starting points, but cycle time, ageing, missing evidence and stage distribution show where the process slows down. Flex Performance can report claim volumes, cycle time, costs, trends and liability accruals.
Connecting claims to customers, B/Ls, containers, voyages and operational events can help identify recurring causes. Flex Intelligence can then summarise the context, point to patterns and suggest preventive actions for people to consider.
The same pattern beyond claims
Claims are one example of a wider pattern. Shipping instructions also often arrive as email and attachments. The opportunity is not simply to read the document, but to compare it with the relevant booking and maritime context, highlight discrepancies and only then create or update the controlled transaction.
In both cases the original document stays connected to the transaction, so a user can see where information came from and review the source when an exception occurs.





