How Helm checks your filing data
When you create a filing in Helm, Verify works in the background to check the information Helm has filled in against what that data should actually look like, before you ever hit submit.
Why this matters
Filing data has rules. A container number only starts with certain prefixes depending on the steamship line. An HTS code needs to be valid and specific enough for the filing. A bill number needs to carry the right carrier prefix so it matches up correctly downstream. Verify knows these rules and checks your filing against them automatically, so you're not the last line of defense against a typo or a bad extraction.
What you'll see
As you review a filing, Verify flags anything that looks off. That can mean:
A value looks wrong. The data doesn't match the expected format or pattern for that field.
A value is missing. Helm didn't find the information it needed, so the field is left blank instead of guessed at.
A value needs a second look. Nothing is necessarily wrong, but it's worth a quick check before you move on.
Not every flag means stop and fix. Some are just a heads up, others are a hard block until you resolve them. Helm sets these levels based on what actually causes filing problems downstream, so you can trust that a flag is worth your attention.
Where the data comes from
Click into any field and Verify shows you where that value came from in your source documents. It highlights the matching text. So if something gets flagged, you're not starting from scratch to figure out why. You can see exactly what Helm read and decide if it's right.
What Verify looks at
Verify checks fields against what valid data for that field should look like. Here are a few examples, using fields from the ISF form:
Carrier SCAC: This needs to match the format for a valid carrier code. It also ties directly into your bill numbers, so if the SCAC is off, Verify may flag those too.
House Bill Number and Master Bill Number: The bill number needs to carry its SCAC prefix, and a house bill needs a valid master bill it's tied to. Without that structure, the bill won't match on the carrier's system, so Verify checks this before you submit instead of letting it fail later.
Owner Reference: This is more flexible since it's your own internal reference, but Verify still checks that a value exists so nothing goes out unlabeled.
ISF Type: This determines which rules and required fields apply to the rest of the filing, so Verify checks it early since everything downstream depends on it being right.
This isn't the full list of what Verify checks. It's meant to give you a sense of the kinds of issues it catches: formatting problems, missing required structure, and values that don't yet have what they need to be considered complete.
A reminder
Verify checks your filing data. It doesn't file or transmit anything to customs on its own. You'll still review and submit through your normal CargoWise process. Verify's job is to make sure what you're submitting is as clean as possible by the time you get there.