ContainerHub
gate move reconciliation

Gate Move Reconciliation: Match Every Gate-In and Gate-Out

Gate move reconciliation explained for depots and shipping lines: what to match, a step-by-step routine, EDI timing rules, exception handling and KPIs.

Gate Move Reconciliation: Match Every Gate-In and Gate-Out

Gate move reconciliation is the routine of proving that every container that physically passed your gate matches a record in your yard system, a record on the shipping line’s side and, where it applies, a line on an invoice. The depots that do it well capture each move once, at the gate, in a structured digital record. They send that record to the line by EDI (electronic data interchange, the standard machine-readable messages carriers and depots exchange). They then review only the exceptions. That is the approach we built ContainerHub around: one platform for gate, yard, inspections, repair and billing, so the gate record is the single source everything else is checked against.

This guide is for depot operators, shipping lines, terminal managers and container fleet managers. It covers what gets matched, a routine you can run daily, the timing rules that apply in US ports, and how to handle the four exception types that cause most disputes.

Containerhub
containerhub.ai
Reconcile Gate Moves With Less Rework
ContainerHub connects gate, yard, inspections, repairs and billing, with EDI integrations and a client portal for operational visibility.
Visit

TL;DR

  • Gate move reconciliation means matching each physical gate-in and gate-out to your yard record, the carrier’s record and the billing record, so all of them tell the same story.
  • The core match keys are container number, direction, timestamp, booking or release reference, carrier and equipment condition.
  • Most disputes come from four exception types: missing, duplicate, delayed and conflicting moves. Work them from a daily exception queue with an owner and a reason code.
  • Capture once at the gate, transmit by EDI, and reconcile by exception. Reconciling everything by hand later is where the cost and the rework come from.
  • Track exception rate, time to resolve and OCR accuracy so you can see whether errors are shrinking.

Table of Contents

What gate move reconciliation means in a depot

A gate move is the event of a container crossing your gate: gate-in when it arrives, gate-out when it leaves. Reconciliation is the control that confirms those events are recorded completely, once, on time and with the same data in every system that cares.

The industry’s common language for this is the gate report. The UN/EDIFACT standard defines the CODECO message as the way a terminal or depot confirms that containers have been delivered or picked up by an inland carrier. It can also report internal movements and status changes that involve no physical movement. In North America the equivalent most operators handle daily is the ASC X12 322 transaction, the terminal operations (gate, load, discharge) report. If you want the depot-side view of what lines expect from these messages, our piece on CODECO EDI for empty container depots goes deeper.

So there are really three parties to every move:

  1. The depot or terminal, which sees the truck and the box.
  2. The line or equipment owner, which needs to know where its equipment is and who is responsible for it.
  3. The motor carrier or logistics company, which has its own dispatch record of what it delivered or picked up.

Reconciliation is what makes those three versions agree. When they do not, someone pays for the difference, usually in per diem, storage or a disputed invoice.

What you need to match

Not every field carries equal weight. Match first on the keys that identify the move, then on the fields that drive money and liability.

Record or field What it proves Typical mismatch
Container number and check digit Which box moved Keying error, OCR misread
Direction (in or out) and timestamp When custody changed Late or out-of-sequence message
Booking, release or work order number Authority for the move Missing, expired or wrong reference
Carrier name and SCAC code Who took or delivered the box Wrong or unregistered code
Size, type and equipment status What was received or released Wrong type on the release
Condition and damage record (EIR) Who owns pre-existing damage Inspection not linked to the move
Seal number, weight, reefer settings Cargo and compliance details Weight discrepancy, setpoint not carried
Billing event What can be invoiced and to whom Charge raised against the wrong party

The condition record matters more than many depots expect. The equipment interchange receipt (EIR) is the document that records a container’s condition at handover, and a digital one ties the inspection to the exact gate move. See our guide to the digital EIR for how that replaces paper.

Public port documents show how this looks at scale. The North Carolina State Ports Authority’s Container Operations Manual describes inbound gate processing in which OCR cameras record container numbers. Gate coordinators then check the data against bookings, bills of lading, regulatory status and equipment inventory. The gate application runs edit checks to flag discrepancies, and problem transactions go to a Trouble Office. That pattern is the model for any depot: automate the capture, automate the checks, and send only the exceptions to a person.

A daily reconciliation routine, step by step

Here is a routine that works for an empty container depot of any size. At each step we note where it goes wrong and what the platform handles.

1. Capture the move once, at the gate

Record container number, direction, time, carrier, truck and reference at the moment of the move, not at the end of the shift. Paper tickets and re-keying are the largest single source of mismatches, because every re-entry is a new chance for a typo.

Where it goes wrong: a driver reads the number out, a clerk types it, and a transposed digit creates a phantom container and a missing one at the same time. ContainerHub digitizes gate-in and gate-out activity, and OCR capture at the gate removes the typing step. Our article on OCR container number capture at the depot gate covers how that works in practice. For the wider gate workflow, see our gate management software for depots.

2. Validate against the authority for the move

Before or as the truck is processed, check the box against the booking, release or work order and the equipment inventory. A gate-out with no valid release is the most expensive kind of exception, because the box has already left.

Where it goes wrong: releases are updated by the line after the truck is already in the queue, and the gate works from a stale copy. Validate at the gate, with current data, and block or flag moves that fail.

Attach the condition record to the gate move it belongs to. If damage is found at gate-in, the record should show it was there when the box arrived. ContainerHub supports damage inspections, including AI-assisted container damage inspection, within the same workflow as the gate, so the inspection and the move are not two separate files.

4. Transmit the event to the line

Send the gate report to the line’s system by EDI as soon as the move is complete. Timing matters here, and we cover the published standards in the next section. ContainerHub supports EDI integrations with shipping line systems, so the move recorded at the gate is the move reported.

Where it goes wrong: batch files that go out once a day, or messages that are rejected for a bad code and nobody notices. Treat every rejection as an exception that has an owner.

5. Compare the three records

At a set time each day, compare the gate log, the yard inventory and the line’s acknowledgement or status. Every gate-in should have a yard position. Every gate-out should have removed one. Any gate-in without a matching outbound or inventory record should be explainable.

A practical check: for each container, the sequence of events should alternate in and out. Two gate-ins in a row means a missed gate-out, a duplicate, or a wrong container number.

6. Work the exception queue

Anything that fails a comparison goes into one queue with a reason code, an owner and a due time. Do not resolve exceptions in email threads: the evidence (gate photo, timestamp, driver, reference) should sit on the exception itself.

7. Reconcile billing last, from clean moves

Only moves that have passed steps 1 to 6 should drive invoices and per diem calculations. Billing from unreconciled moves turns every gate error into a customer dispute.

8. Review the pattern weekly

Look at which reason codes repeat, which carriers or lines produce most exceptions, and which gate lane or shift. Fix the cause, not the instance.

EDI timing and message rules in the US

The speed at which you report matters as much as accuracy. A late gate-out report can leave a box showing as in your yard, and the line may keep charging or planning against it.

Published rules show how tight expectations can be. Port rules adopted by the City of Los Angeles require terminals to transmit EDI 322 gate and offload movement data within 30 minutes of the movement event. They set the same 30-minute window for EDI 315 status updates. Those rules apply to marine terminals at that port, not to every depot, but they show the direction of travel: near-real-time reporting is the norm that lines and ports are built around.

The message types in the NCSPA manual show the two-way nature of the exchange. The carrier receives 322 gate, vessel and rail moves. It sends back 315 freight hold and release, 301 bookings and 310 manifest data, and reefer temperatures arrive via the 301 booking and print on the EIR at the interchange gate. In other words, the data you reconcile against often originates with someone else, so your gate needs to consume it as well as send.

If you work with intermodal partners in Europe, the ECTA and UIRR best practice guideline (October 2025) lays out numbered message flows for gate-in and pick-up between terminal and operator, alongside booking flows. The takeaway for any region is the same: define which message confirms which event, and reconcile against that definition.

Sending the right data to the right system also depends on the rest of the chain. Teams that connect terminals, depots, inland carriers and intermodal operators need dependable gate movement data exchange so each party’s records start from the same event. Our blog category on container depot terminal integration collects more on that.

Code details that cause rejections

A few details commonly trip up 322 files. One published implementation guide for chassis pool locations requires GS-08 to be 004010, ST-01 to be 322, and SCAC codes to be validated against NMFTA registered codes (CCM 322 implementation guide, 2018). Each partner has its own guide, so keep one mapping per partner and treat a rejected message as an exception, not as noise.

Handling the four exception types

Almost every reconciliation problem is one of four things. Seaboard Marine’s January 2026 request for proposals for a gate operating system is a useful checklist of what a gate must handle: OCR misreads, weight discrepancies, damage alerts, missing or invalid appointments and compliance flags. It also calls for manual overrides that are role-based, auditable and configurable, with configurable tolerances for weight, damage severity and OCR confidence.

Missing moves

A container is in the yard but has no gate-in, or left but has no gate-out. First check the gate photos and timestamps around the time of the last known event. Then check whether the move was recorded under a different container number, which is the usual cause. Correct the record with a reason code and keep the evidence attached.

Duplicate moves

Two identical gate-ins within minutes usually mean a retried transmission or a double scan. The fix is to give each move a unique identifier and ignore a repeat of the same one, rather than deleting rows by hand. Duplicates that reach a line’s system can create duplicate billing events.

Delayed moves

The truck left at 2:10 p.m. and the report arrived at 6:00 p.m. Delays break the sequence: a status can arrive before the gate event that should precede it. Reconcile by event time, not by arrival time, and monitor the lag between the move and the transmission so you can see when it drifts.

Conflicting moves

The depot says the box left with carrier A, the line says carrier B picked it up. Conflicts like this are expensive because they decide who is billed. In its published ocean carrier billing process, DCLI describes how the depot or terminal generates an EDI 322, which is parsed and matched gate-in to gate-out, with a pre-audit step to confirm the billable party before invoicing. The lesson is that the carrier on the gate record decides responsibility, so capture it carefully and validate its code.

Controls and measures that keep errors from coming back

A reconciliation process that only fixes yesterday’s errors will fix the same ones tomorrow. Add these controls:

  • Reason codes. Every correction carries one, so you can count causes.
  • Named owners. Each exception type has a person responsible, with a time limit.
  • Audit trail. Who changed what, when and why. Overrides should be permission-based and recorded.
  • Tolerances. Decide in advance which differences (weight, OCR confidence) can pass and which must be reviewed.
  • Separation of duties. The person who edits a gate record should not be the only person who approves the invoice built from it.

For measures, the same Seaboard RFP asks for reporting on truck turn times, gate throughput, OCR accuracy, and exception and rejection rates, with live dashboards for lanes and queues. Those are the right numbers for a depot too. Add two of your own: the percentage of moves reconciled by the end of the day, and the median time an exception stays open. If the first rises and the second falls, your process is working.

For an overview of how gate flow, queues and automation fit together, our blog covers depot gate queue management and depot gate automation.

Our perspective

Most depots we talk to do not have a reconciliation problem. They have a capture problem that shows up later as a reconciliation problem. If the gate record is typed from a paper ticket, then re-typed into a yard sheet, then re-typed into an invoice, you will spend your mornings finding out which version is right.

We built ContainerHub so the gate, the yard, the inspection, the repair and the invoice all work from the same record. Gate-in and gate-out are digitized, inspections are linked to the move, and EDI integrations with shipping line systems report what the gate actually saw. Our Agentic AI copilot is there to help your team work through the day’s operational questions instead of hunting through spreadsheets.

Our view is simple: reconcile by exception, not by effort. When the data is clean at the source, your team spends its time on the handful of moves that really need judgment, and your customers see the same status you do through a client portal.

William Carley

Put the routine on one platform

If you are running the routine above with paper tickets, spreadsheets and separate billing tools, the quickest gain is to put gate, yard, inspections, repair and billing on one system. ContainerHub’s container depot software is built for that, with EDI integrations to shipping line systems and a self-service client portal so lines and truckers can see move status without calling your office.

Plans are published on the pricing page: Free at $0 per month, Starter at $199 per month, Growth at $499 per month, and Enterprise from $999 per month. Pricing scales with usage, such as gate movements, depots, users and advanced modules.

FAQ

What is gate move reconciliation?

It is the process of matching each physical gate-in and gate-out to the yard record, the carrier or line record and the billing record. The goal is that every move is recorded once, accurately and on time. Exceptions are the moves that fail a match, and they are investigated and corrected with evidence.

How often should a depot reconcile gate moves?

Validate each move at the gate as it happens, and run a full comparison of gate log, inventory and line status at least once a day. Fix exceptions before invoices are produced. Some US port rules expect EDI movement data within 30 minutes of the event, so reporting delays should be monitored continuously.

Which EDI messages are involved?

In North America, the ASC X12 322 reports gate moves, 315 carries status updates, and 301 and 310 carry bookings and manifests. Internationally, the UN/EDIFACT CODECO message confirms gate-in and gate-out. Check each partner’s implementation guide for required codes and formats.

What causes most gate move discrepancies?

Manual re-keying, wrong container numbers, stale release data, late or out-of-order messages and incorrect carrier codes account for most of them. Capturing the container number by OCR and validating the move against the release at the gate removes many of these at the source.

Who should own reconciliation exceptions?

Assign each exception type to a named role, such as the gate supervisor for missing moves and the billing lead for conflicts that affect invoices. Give every exception a reason code and a due time. Review the codes weekly to find the causes that keep recurring.

Sources