CBMGO prepares the filing. CBMGO does not send it.
CBMGO builds the ISF, AES and AMS records on the house, runs the pre-checks before they leave, and writes the response back onto the shipment when it comes. It does not transmit to CBP, and CBMGO is not an ABI broker. That is a decision rather than a gap, and stating it here rather than in the demonstration avoids wasted time on both sides.
What preparing but not sending means
What that means in daily operation
The ten elements are entered once, on the house, and the pre-check reports what is missing while there is still time to obtain it. The record is then handed to whoever holds the ABI filer code — the broker, or the forwarder’s own filer if it holds one. When the ITN or the rejection comes back it goes on the shipment, where operations and the morning queue can both see it.
Why the transmission was not built
Being an ABI filer is a licence, an obligation and a support burden, not a feature. Most forwarders of the size this system is built for already have a broker they trust and no wish to change that relationship for a software subscription. CBMGO would rather be the place the record is built correctly than a second-rate pipe to CBP.
What it replaces
Mostly retyping, and mostly the same ten fields.
Seven screens, and the eighth is the one CBMGO did not build.
ISF-10 and ISF-5, per house
Ten data elements on the house record, not on the master, with a pre-check that runs before the record goes anywhere. The rules behind that check are four hundred lines of their own.
Commodity lines, then the file
AES commodity lines on the shipment, and the AESTIR file written the way the format is specified: one record per line, eighty characters, blanks and all. Seven hundred lines of code decide where each character sits.
Ocean and air, against the 24-hour rule
The AMS record, the deadline the 24-hour rule puts on it, and the name of whoever filed. When the deadline has passed the line stays on the screen instead of dropping off it.
The ITN, or the reason it was rejected
What comes back through ACE WebLink is read onto the shipment: the ITN when it is accepted, and the rejection with its reason when it is not. A rejection nobody can write down is a rejection that gets forgotten.
25,939 entries, priced at zero
Every party on the record checked against the United States consolidated screening list. The decision is recorded, and the screen shows how old the list itself is.
The date, before it matters
A power of attorney has an expiry, and the day it is needed is never the day it is checked. It sits on the customer with its date, so the queue can raise it before a filing depends on it.
A determination for 33 destinations
Whether a low-value consignment clears under the destination’s de minimis threshold, for 33 destinations. Not for cargo arriving in the United States: Federal Register 2026-12670 suspended that exemption for every mode except mail, effective 24 June 2026.
No transmission to CBP
There is no send button anywhere in this system, because there is nothing behind it. No ABI filer code, no direct connection, no queue of things waiting to go. A company that needs software that files needs a broker’s system, and CBMGO will say so on the call.
Build, check, hand over, record.
Four steps, and it is stated plainly which one is not CBMGO’s.
Build it on the house
The parties, the container and the commodity are already on the house record from the booking. The filing reads them rather than asking for them a second time.
Run the pre-check
It reads the record as it stands and reports which elements are missing or contradict each other. It cannot report facts nobody has entered yet, and it says so plainly instead of reporting a clean result.
Hand it to the filer
The broker files it, or the forwarder does if it holds the filer code. CBMGO is not that connection and does not pretend to be one.
Write back what came
The ITN, or the rejection and its reason, lands on the shipment. One of the twenty release checks found this exact hole once: the screen knew how to draw the rejection box and there was no button anywhere that could write one.
One house, and every filing that touches it.
Every time on this screen names its clock
PT, not “09:05”. One of the twenty checks that can stop a release fails a build that stamps a time without saying which clock it is on. That check exists because a four o’clock delivery in Los Angeles once appeared on a customer’s screen as 23:00 the following day.
And the screening line shows two dates, not one
When the check ran, and how old the list was when it ran. A check from yesterday against a list from six months ago passes an audit and has confirmed nothing at all.
What passes between systems — and what does not.
SCM
The filing reads the house record: parties, container, commodity. It goes back the other way too — the morning queue counts import consolidations past the ISF deadline with no filing number, and says which of them have already arrived.
Portal
The customer sees documents and where their shipment is. They do not see the filing screens, and no customs record is published to the portal.
Parcel
The same de minimis determination, for the same 33 destinations, is what a courier consignment gets. One rule, used in two places, rather than two rules drifting apart.
QMS, WMS and LiveTrack
Nothing passes. A filing does not need a price, a warehouse location or a push alert, and no connection was invented so that this grid could look fuller.
Asked on the first call.
Do you file our customs entries?
Then who sends it?
Is party screening extra?
What does the pre-check actually catch?
A filing rejected last month makes a useful demonstration.
It is built on a house record and the pre-check is run against it, to show whether the rejection would have been caught before the vessel sailed. ABI is one switch, priced per company, and screening inside it is priced at zero.