Every commercial vessel entering the Suez Canal from the Mediterranean has to clear the SCA's northbound boarding logic at Port Said — and for the bulk of the fleet, that decision is made on the basis of three pre-arrival records (SCNT, ISPS, and the booking confirmation) and a fourth anchor (the onboard documentation set) that all have to reconcile at the same time. Operators whose SCNT record and the onboard paperwork disagree end up paying for an outer-anchorage wait on top of an SCA documentation discrepancy that flags the vessel on subsequent northbound convoys.
This piece focuses specifically on the Suez Canal northbound convoy requirements — what the four boarding checks actually cover, how the northbound convoy window and the SCA boarding logic interact, the SCNT pre-arrival declaration mechanics for northbound transits, and the SCNT / ISPS scenarios that produce a rejection at Port Said boarding in 2026. The aim is a tightly-scoped second read after the broader Suez Canal filing requirements piece, so the cluster stays coherent for fleet managers working through both posts.
Validate Your Suez SCNT + ISPS Before You Submit
SCNT and ISPS reconciliation against the SCA boarding logic is the single biggest avoidable cost on a northbound convoy. CanalClear's Suez validator runs the SCNT pre-arrival declaration against the ISPS Security Level declaration and the onboard documentation set, and flags any field that would trigger an SCA rejection before your agent hits submit.
Validate Suez FilingWhat the Suez Canal Northbound Convoy Requirements Actually Cover
When an operator says they have "the Suez Canal northbound convoy requirements," what they actually mean is the four-channel boarding logic the SCA runs at Port Said to decide whether a vessel is allowed into the northbound convoy window. It is not one document and it is not one channel — it is four converging records that all have to be in the same state at the same moment. Northbound heading vessels that fail any one of the four are held at the Port Said outer anchorage until the next northbound convoy window opens.
Four channels make up the boarding logic that defines the Suez Canal northbound convoy requirements on a typical vessel profile:
- Channel 1 — SCNT pre-arrival declaration. The SCNT (Suez Canal Net Tonnage certificate and pre-arrival notification) is the operator's filing-channel declaration that the vessel is ready to transit. It carries vessel particulars, the cargo manifest, the crew list, the Dangerous Goods declaration (if applicable), the SCT form set, and the slot the vessel is requesting on the northbound convoy manifest. A vessel without a landed SCNT is not on the SCA's manifest and is therefore not a candidate for boarding regardless of how cleanly the rest of the channel is set up.
- Channel 2 — ISPS pre-arrival declaration. The ISPS pre-arrival declaration tells the SCA what Security Level the vessel is operating under. Security Level 1 is the default, with Security Level 2 or 3 added only when the prevailing security posture requires. The declaration has to reconcile to the onboard posture — the Security Level the bridge team is actually running — because a vessel declaring Level 1 on the ISPS record but running Level 2 on board is a boarding rejection.
- Channel 3 — Booking confirmation. The booking confirmation is what places the vessel on the SCA's northbound convoy manifest. It is confirmed once the SCNT is accepted at the portal layer and the operator's slot request can be honoured inside the published northbound boarding window. The booking confirmation is the link between the SCNT record (the operator's view) and the manifest (the SCA's view) — and a booking confirmation that disagrees with the SCNT forces a portal-level reset.
- Channel 4 — Onboard documentation set. The SCT forms, the Dangerous Goods declarations, the International Tonnage Certificate, the Classification Society documents, the Minimum Safe Manning Document, and the ISPS Ship Security Plan all sit on board and have to align with what was filed via the operator's channel. Any gap between the on-board document and the SCNT/ISPS record is what a SCA boarding officer inspects first at Port Said.
The mental model: The SCNT is the operator's view. The booking confirmation is the SCA's view. The ISPS is the security layer. The onboard documentation set is what the boarding officer sees. All four have to agree at the same moment, or the vessel sits at the outer anchorage.
For operators approaching the SCA boarding logic from a comparable framework, the next-clause context is the form-level mechanics of the SCNT itself — see the full Suez Canal filing requirements piece for the broader filing stack. For convoy timing and slot allocation, the Suez Canal convoy scheduling piece covers how the northbound and southbound convoy windows interact at Port Said and at Suez.
The Northbound Convoy Window and the SCA Boarding Logic
The SCA runs northbound convoys out of Port Said on a published schedule that gives operators a single daily boarding window under normal SCA practice — and the entire SCNT/ISPS/booking-confirmation logic is anchored to that window. The window has structure: vessels file the SCNT ahead of the window, the SCA books the vessel into the manifest, and at the window the boarding officer reconciles the SCNT, ISPS and onboard documentation set in real time. A vessel arriving at the window without all four channels aligned is held until the next window opens.
Three things make the SCA boarding logic distinct from paper-based filing regimes elsewhere in the cluster. First, the SCNT pre-arrival declaration is the anchor record — without a landed SCNT, none of the other channels can be completed, and the booking confirmation cannot be issued. The SCNT is therefore the upstream gate of the northbound convoy workflow, and operators who file SCNT late end up with a confirmed-but-not-booked slot that the SCA does not honour at the next window.
Second, the northbound and southbound convoy windows have different slot allocations: the northbound window typically has more vessel slots per day because Mediterranean-to-Suez traffic carries heavier ISPS workload at the entry node, and the southbound window typically has fewer slots because Suez Bay-to-Mediterranean traffic is already inside the canal system when the southern stretch of the transit begins. A vessel that tries to file a southbound booking against the northbound window — or vice versa — is rejected at the portal layer.
Third, the SCA's pre-arrival declaration window is more strictly enforced on the northbound side, because there is no fallback leg between Mediterranean arrival and Port Said boarding. Southbound operators have a flatter workload because the vessel enters the canal system at Suez before the southern paperwork leg, but northbound operators are reading the SCA paperwork for the first time at the boarding lane with no buffer between arrival and boarding.
Practical rule of thumb: File the SCNT ≥96 hours before boarding under typical vessel profiles, and tighten to ≤48 hours before boarding for tighter vessel categories. Late SCNT filings cascade to booking-confirmation reset to manifest reset.
Vessel age, flag, classification society, and ISPS record all feed into the SCA's evaluation of whether the boarding logic accepts the vessel, but they are eligibility modifiers rather than eligibility gates. A vessel can have a perfect ISPS record but a SCNT lodged inside the wrong window, and the booking confirmation is refused regardless. Conversely, a vessel with a marginal ISPS record but a clean SCNT, a clean booking confirmation, and reconciled onboard documentation can still clear the boarding logic.
SCNT Pre-Arrival Declaration Mechanics for Northbound Transits
This is the part of the Suez Canal northbound convoy requirements that most operators miss. The SCNT pre-arrival declaration is one record — but the activation of its effect (i.e. the booking confirmation that places the vessel on the manifest) is a separate step that the SCA runs at the portal layer, with a strict window binding the two. The SCNT has to declare the vessel particulars, the cargo, the crew, the Dangerous Goods posture, and the slot request explicitly, so that the SCA can verify at convoy confirmation that the vessel has a current SCNT and slot it onto the northbound manifest.
If the SCNT is lodged outside the pre-arrival declaration window, includes a corrupted vessel particulars field, references a slot request that does not match the available northbound window, or improperly packages the Dangerous Goods declaration, the booking confirmation logic does not fire. The SCA treats the vessel as a non-manifest transit and holds it at the outer anchorage at Port Said. The intuitive reaction — "but the SCNT was filed, look at the receipt" — does not change the outcome: the system has already moved past the SCNT check because the portal-layer verification failed.
The full set of Suez Canal filing requirements covers the broader SCNT/ISPS/SCT paperwork stack and the supporting certificate set behind each form. The Suez Canal northbound convoy requirements stand inside that stack as the boarding-channel-specific subset — the four checks the SCA runs at Port Said — so the cluster is coherent for fleet managers working through both posts.
What the SCA portal layer actually does at convoy confirmation: Pulls the SCNT record, checks the booking confirmation against the manifest, reconciles the ISPS layer, and either places the vessel on the boarding lane or holds it at the outer anchorage. There is no appeal on the spot. The decision is system-level.
ISPS + Security Level Alignment Before Northbound Boarding
The ISPS pre-arrival declaration is a separate document from the SCNT but it loads into the same boarding-logic check the SCA runs at Port Said. The declaration tells the SCA what Security Level the vessel is operating under — Security Level 1 as the default, Security Level 2 when the SCA's prevailing security posture has been raised, and Security Level 3 only under specific operating conditions that the SCA defines. The declaration has to reconcile to the onboard posture: the Security Level the bridge team is actually running at the boarding moment.
Three ISPS/SP posture failures are the most common causes of a boarding rejection on a northbound Suez convoy. First, an ISPS declaration that declares Level 1 while the master is running Level 2 on the bridge — the SCA sees the discrepancy at boarding and holds the vessel. Second, an ISPS declaration that uses a valid Security Level but references a Ship Security Plan that does not match the actual SSP carried on board. Third, a Security Level change that has not been re-declared to the SCA between SCNT acceptance and the boarding lane — the SCNT is correct at filing; the SCNT is stale at boarding.
For a fully focused treatment of ISPS on the Suez, the Suez Canal ISPS compliance guide covers the form-level mechanics, the SSP/Security Officer declarations, and the ISPS rejection scenarios that surface most often. The ISPS work is not optional and it is not decoupled from the SCNT — both load into the same boarding-logic decision the SCA runs at Port Said.
What "reconcile to onboard posture" means in practice: The Security Level on the ISPS declaration has to match the Security Level the bridge team is actually running, with the SSP accessible on board that justifies the level, and the Ship Security Officer's signed record consistent with the declaration. Any discrepancy at any of the three layers is a rejection trigger.
Onboard Documentation Set That Must Reconcile to the SCNT Record
The fourth channel — the onboard documentation set — is what a SCA boarding officer inspects first when the vessel enters the boarding lane. The SCNT record is the SCA's view of the vessel, and the onboard documentation set is the operator's. The two have to agree at every field that has a counterpart on the SCNT. The SCT forms, the Dangerous Goods declarations, the tonnage and class certificates, the crew list, and the ISPS Ship Security Plan all sit on board and all have to align with what was filed via the operator's filing channel.
- SCT forms. The basic Suez Canal Transit forms — vessel particulars, cargo summary, crew list — that have to be on board and aligned with the SCNT record. A crew-list SCT that disagrees with the SCNT crew declaration is a documentation discrepancy.
- Dangerous Goods declarations. If the vessel is carrying DG cargo, the DG declaration has to match the SCNT's DG summary field by field. A DG declaration that lists a cargo category not on the SCNT is a boarding rejection trigger.
- Tonnage and class certificates. The International Tonnage Certificate and the Classification Society documents sit on board and have to align with the SCNT tonnage and class references. A SCNT that cites a Suez Canal Net Tonnage number that does not match the ITC carried on board is rejected.
- Crew list. The crew list on the SCNT has to match the crew list on the SCT forms on board. A master or a chief officer change between SCNT acceptance and boarding is a common source of onboard/SCNT drift.
- ISPS Ship Security Plan. The SSP carried on board has to support the Security Level on the ISPS declaration, and the Ship Security Officer's signed record has to be consistent with the on-board posture. The SSP layer is what ISPS reconciles to — and an SSP that does not support the declared level is the most common ISPS-layer rejection.
Foreign operators cannot file SCNT directly. The SCNT pre-arrival declaration is filed via a registered Suez shipping agent with SCA credentials — the same agent that handles the SCT forms and the booking confirmation on the vessel's behalf. The agent's scope is therefore broader than just SCNT: the agent owns the SCT paperwork, the booking confirmation, and the SCNT/ISPS reconciliation at the portal layer.
The SCNT is reviewed by the SCA portal layer continuously. Acceptance is confirmed via the booking confirmation that places the vessel on the manifest, and the agent passes the booking reference to the operator. Without that booking-confirmation bridge, the SCNT is filed but the vessel is not booked. A vessel that arrives at Port Said with a SCNT but no booking confirmation is held at the outer anchorage regardless.
Cost of a Northbound Convoy Rejection at Boarding
Every SCNT/ISPS mismatch generates the same downstream effect — an outer-anchorage hold at Port Said, a documentation discrepancy logged against the vessel, and a booking-confirmation reset to the next northbound convoy window — but the upstream causes vary enough that operators need a working catalogue. Six scenarios below cover what 2026 fleets are reporting most often.
| Scenario | What went wrong | Downstream effect |
|---|---|---|
| 1. SCNT landed but outside the pre-arrival window | The operator filed the SCNT but the timestamp is outside the SCA's pre-arrival declaration window (typically ≥96 hours before boarding under most vessel profiles). Late SCNT filings cascade to booking-confirmation reset because the manifest slot clock has already passed. | Vessel held at Port Said outer anchorage; booking-confirmation reset to next northbound window; SCNT documentation discrepancy logged against the vessel. |
| 2. SCNT valid at filing but stale at boarding | The SCNT was correct at filing; the crew list, cargo, or vessel profile has changed between SCNT acceptance and the boarding moment. The SCNT is stale; the operator did not refile. | Vessel held; resubmission required inside the next window; agent fee for the SCNT amendment plus an outer-anchorage cost layer for the bridge time lost. |
| 3. ISPS Security Level mismatch | The ISPS declaration declares a Security Level that does not match the onboard posture — declaration says Level 1, bridge is actually running Level 2 — or the SSP carried on board does not support the declared level. The four-channel boarding logic requires all four to agree at the boarding moment. | Vessel held; ISPS layer reset; closer scrutiny on subsequent northbound convoys because the discrepancy is logged at the SCA portal layer. |
| 4. Booking confirmation unset against manifest | The SCNT was landed but the booking confirmation was not issued because the slot request did not match the available northbound window. The vessel is filed but not booked; the SCA manifest does not include the vessel. | Vessel held at outer anchorage; operator must resubmit the SCNT with a slot request that fits the next window, adding a full SCNT cycle to the anchor wait. |
| 5. Onboard documentation diverges from SCNT | At boarding, the SCT forms, the Dangerous Goods declarations, or the tonnage and class certificates on board do not match the SCNT record field by field. The SCNT is the SCA's view; the onboard documentation set is what the boarding officer sees; the gap between the two is the rejection trigger. | Vessel held; documentation discrepancy logged; operator must either realign the onboard documentation set or amend the SCNT before the next window. |
| 6. DG declaration does not match SCNT DG summary | The Dangerous Goods declaration on board lists a cargo category, UN number, or DG class that does not match the SCNT's DG summary. The four-channel boarding logic has a specific DG reconciliation check that runs at the manifest layer. | Vessel held; DG amendment required at the next window; the DG layer is the most aggressive field of the SCA's reconciliation logic and the most consistent source of late-stage rejections. |
When the SCA holds a vessel at the Port Said outer anchorage because the SCNT paperwork diverges from the onboard record, the operator faces three separate cost layers — none of which are recoverable after the fact. The costs are real but their numbers depend heavily on the voyage, the charter party, the agent fee structure, and the DG posture, so framing is qualitative here rather than a hard dollar figure. Three layers are worth tracing:
- Operating cost at anchor. A vessel that misses its northbound convoy slot because the SCNT or ISPS record was held has to anchor at Port Said until the next northbound window opens. Operating cost at anchor in the Port Said approach is non-trivial — bunker consumption continues, crew rotations slip, and the vessel charter clock continues to run. The longer the anchor window, the more pronounced the cost.
- Charter party delay exposure. For time-chartered vessels, a missed northbound slot is a demurrage-style event under most standard charter party clauses. For voyage-chartered vessels, it is a laytime event. Either way, the delay flows through to the commercial record of the transit and is visible to the charterer's operations team.
- Agent fees and SCNT amendment cost. The Suez agent submits the agent-fee line for the additional work caused by the SCNT amendment or the ISPS paperwork reset, and the SCNT amendment itself is billed as a separate line. Both lines are invoiced and reconciled after transit.
These cost layers are not theoretical: a northbound Suez vessel whose SCNT and onboard documentation diverge and goes uncaught before boarding will incur all three on a single miss. The cheapest path through this risk is a pre-submission validator that runs the SCNT and ISPS against the onboard documentation set before the agent hits submit.
Validate SCNT + ISPS Before Your Agent Hits Submit
CanalClear's Suez validator runs the full SCNT pre-arrival declaration — including the ISPS Security Level declaration and the SCT paperwork stack — against the onboard documentation set and simulates the SCA portal layer's reconciliation logic. The validator surfaces SCNT/ISPS mismatches before they become outer-anchorage costs on the next northbound convoy window.
Download Free Suez Primer →Practical Pre-Submission Checklist for Fleet Operators
Before every Suez northbound convoy filing, the bridge team and the Suez agent should run through the same checklist. Every item on it is a yes/no — if the answer to any item is "no," the SCNT should not be submitted until the gap is closed.
- SCNT lodged within the pre-arrival declaration window. Filed ≥96 hours before boarding under typical vessel profiles, and tightened to ≤48 hours before boarding for tighter vessel categories. A late SCNT is treated as "not filed" by the SCA portal layer.
- SCNT vessel particulars match the on-board SCT forms. No transcription error in LOA, beam, draught, GT/NT, hull form, propulsion type. The SCT forms have to line up with what is on the SCNT.
- SCNT cargo manifest matches on-board cargo summary. Cargo type, quantity, and IMDG class have to reconcile across the SCNT cargo manifest and the on-board cargo summary — including any DG declaration layers.
- SCNT crew list matches the on-board crew list. Master and chief officer continuity assumed since SCNT filing; a master change without refile is a documentation discrepancy at boarding.
- ISPS Security Level declaration matches on-board posture. Declaration Security Level aligned to the actual level being run on the bridge, with the Ship Security Plan that supports the level accessible on board.
- Booking confirmation issued against the northbound manifest. The vessel is on the SCA's northbound manifest at the slot requested. A SCNT without a booking confirmation is filed but not booked — and a vessel that arrives at Port Said without a booking confirmation sits at the outer anchorage.
- DG declaration matches the SCNT DG summary. If the vessel is carrying DG cargo, the DG declaration lines up with the SCNT DG summary field by field. The DG layer is the most aggressive field of the SCA's reconciliation logic.
- Original SCNT receipt accessible on board. The SCNT receipt and the booking confirmation have to be in the bridge folder, accessible at boarding. A missing receipt at the boarding lane is a documentation discrepancy.
Why the checklist is yes/no: SCNT/ISPS reconciliation against the SCA boarding logic is not graded on a curve. A SCNT lodged outside the pre-arrival window, an ISPS level that does not match the on-board posture, or a SCNT/ISPS field that diverges from the on-board documentation set is sufficient to hold the vessel at the outer anchorage with no override at the portal layer.
Working with Your Suez Canal Agent on Northbound Paperwork
The single most common cause of a SCNT/ISPS mismatch is operator-agent discontinuity: the SCNT pre-arrival declaration is managed by one team inside the operator organisation (or by a separate agent office), the ISPS declaration is prepared by another team inside the operator organisation (or by another agent office), and the two streams meet only at submission time. When the streams disagree, the SCA reads the SCNT — not the operator's intent — and acts on it. The fix is structural:
- Same agent for SCNT and ISPS. The Suez shipping agent handling the SCNT should be the same agent on file with the SCA as the ISPS layer's holding agent. Two-agent chains introduce one or two translation steps between the SCNT and the ISPS declaration, and every translation step is a chance for a digit to be transposed or a field to be left blank.
- Booking confirmation visible in the operator's pre-filing checklist. The booking confirmation reference should be visible to the operator's pre-filing validation team — not buried in the agent's filing packet — so that the operator can confirm the vessel is on the SCA northbound manifest before boarding.
- Agent errors in either layer block both layers. Errors in the SCNT record (a transposed cargo summary entry, an incorrect crew list field) do not surface until the SCA portal layer hits them at the next window. Errors in the ISPS declaration (a Security Level that does not match the on-board posture, an SSP that does not support the declared level) surface immediately at the next boarding.
- Single source of truth on SCNT vessel particulars. The vessel particulars on the SCNT should be referenced from a single canonical record that both the agent and the operator draw from. A shared vessel record, an internal compliance register, or a structured vessel dataset all work — what does not work is two copies that have to be kept in sync manually.
Downstream Compliance: Northbound Convoys in a 7-Waterway Fleet Operation
The northbound convoy boarding logic is a Suez-specific construct but the underlying pattern — four converging records (filing-channel declaration, security layer, manifest slot, onboard documentation set) all reconciled at the boarding moment — is not unique to the SCA. Other waterways in the cluster run comparable four-channel logic at their own boarding nodes: Cape Town for ISPS pre-arrival at the Cape of Good Hope, VTSC for SP-1 at the Turkish Straits, MPA OCEANS-X for STRAITREP at the Strait of Malacca. Each waterway has its own form-level mechanics, its own pre-arrival declaration window, its own ISPS or security layer, and its own manifest slot allocation — and the four channels for one waterway are not interchangeable with another. But the operational pattern (filing-channel declaration, security layer, manifest slot, onboard documentation set) is directly comparable, and operators running a 7-waterway fleet have to maintain each waterway's four-channel record set independently and confirm each waterway's reconciliation at its respective boarding lane.
For a focused primer on the Kiel Canal regime — which is the most parallel four-channel framework in the northern European cluster — the free Kiel Canal Compliance Primer walks through the equivalent field-level mechanics, the dimensional constraints that govern NOK transit (notably the Brunsbüttel and Kiel-Holtenau locks), the ELWIS/WSV pre-arrival declaration stack, and the rejection scenarios that surface most often for Kiel-bound vessels. The Kiel primer is the natural companion to this Suez northbound convoy piece for fleet operators running both the Mediterranean-to-Suez and the northern European routes.
Get the Free Kiel Canal Compliance Primer
The free Kiel Canal Compliance Primer covers the NOK eligibility gates, the equivalent pre-arrival form mechanics, the Brunsbüttel and Kiel-Holtenau lock constraints, and the rejection scenarios that surface for Kiel-bound vessels. The primer is the natural companion to this Suez northbound convoy piece — especially for operators running both the Mediterranean-to-Suez and northern European routes.
Download Free Kiel Primer →Frequently Asked Questions
What are the Suez Canal northbound convoy requirements?
The Suez Canal northbound convoy requirements are the four SCA boarding logic checks that determine whether a vessel is allowed into the northbound convoy at Port Said: the SCNT pre-arrival declaration lodged within the SCA's pre-arrival window (typically ≥96 hours before boarding), the ISPS pre-arrival declaration with the Security Level aligned to the onboard posture, the booking confirmation that places the vessel on the SCA northbound convoy manifest, and the onboard documentation set — SCT forms, Dangerous Goods declarations, tonnage and class certificates — that must reconcile to the SCNT record. A vessel that passes all four enters the convoy; a vessel that fails any one of them is held at the Port Said outer anchorage until the next northbound convoy window opens.
When must the SCNT pre-arrival declaration be lodged for a northbound transit?
The SCNT pre-arrival declaration has to be lodged via the operator's filing channel ≥96 hours before boarding for many vessel profiles, with a tighter window (typically ≤48 hours) for certain vessel categories or for vessels carrying DG cargo. The pre-arrival window is more strictly enforced on the northbound side because there is no fallback leg between Mediterranean arrival and Port Said boarding. A late SCNT filing is treated as not filed by the SCA portal layer — the booking confirmation is refused, the manifest slot is not issued, and the vessel has to be refiled inside the next window.
How are northbound and southbound convoy paperwork windows different?
The northbound and southbound convoy paperwork windows share the same SCNT/ISPS structure but the northbound and southbound legs apply at different arrival nodes (Port Said for northbound, Suez for southbound) and carry different ISPS workloads. The pre-arrival declaration window is the same in both directions — typically ≥96 hours before boarding — but the booking confirmation step is leg-specific. Northbound has heavier ISPS workload at the entry node; southbound has a flatter workload because the vessel is already inside the canal system when the southern stretch of the transit begins.
Why are SCNT rejections more common on northbound convoys?
SCNT rejections are more common on northbound convoys for three reasons that compound at boarding: northbound vessels carry heavier ISPS workloads because Port Said is the entry node; the SCA's pre-arrival declaration window is more strictly enforced on the northbound side, where missing or late paperwork has no fallback leg; and the booking confirmation step ties the SCNT record to the manifest at Port Said, so a typo in either layer cascades to a documentation discrepancy. Operators who file SCNT without a pre-submission validator running the SCNT and ISPS records together are the most exposed.
What happens if a vessel misses the SCA northbound boarding window?
A vessel that misses the SCA northbound boarding window — by arriving late, by failing the SCNT paperwork check, by failing the ISPS Security Level reconciliation against the onboard posture, or by failing the booking confirmation step — is held at the Port Said outer anchorage until the next northbound convoy window opens. Missing a single northbound window typically means a 12–36 hour anchor window, during which bunker consumption continues, crew rotations slip, the charter clock continues to run, and the vessel burns the SCNT submission it already lodged. Multiple missed windows pull a vessel back from an already-tight Mediterranean-to-Suez schedule and produce documentation discrepancies that follow the vessel on its next northbound convoy.
Can CanalClear validate Suez northbound convoy filings before SCA submission?
CanalClear's Suez validator runs the full SCNT pre-arrival declaration against the ISPS Security Level declaration and the onboard documentation set, and surfaces any field that would trigger an SCA rejection before the agent hits submit. The validator simulates the SCA portal layer's reconciliation logic and flags the four northbound convoy boarding checks individually: the SCNT record, the ISPS record, the booking confirmation, and the onboard documentation set. A vessel that passes the validator before submission enters the northbound convoy window with the SCNT and ISPS records aligned and the onboard documentation reconciled to the SCA manifest.