Skip to content
Skip to content
All Numeo One docs

Importing loads

Power user

RateCon deduplication and reprocessing

Why the same rate confirmation won't create a duplicate load — the fingerprint, the 24-hour window, and how to reprocess.

4 min read

Brokers resend rate confirmations all the time — a forward here, a reply there, the same file twice. Numeo One makes sure you get one load per real rate confirmation, not one per email. This is the deeper look at how that works and what to do when you actually want a file re-read.

How duplicate detection works

When a rate confirmation comes in, Numeo doesn't just look at the filename — it fingerprints the file itself.

  • It takes a fingerprint of the rate confirmation's contents and ties it to the account it came in on.
  • If a rate confirmation with the same fingerprint shows up again within a 24-hour window, Numeo treats it as one it already handled and skips it — no duplicate load.
  • After the window passes, that fingerprint is no longer held, so a genuinely new send can come through.

The result is that resends, replies, and forwards of a confirmation you've already got don't clutter your board.

"Not a rate confirmation" results

Not every attachment is a rate confirmation, and Numeo won't turn a random document into a load.

  • If the AI reads a PDF and decides it isn't a rate confirmation, it returns a "not a RateCon" result and no load is created.
  • That's expected — a broker packet, an invoice, or an unrelated PDF simply won't become a load.

Reprocessing the same file

Duplicate protection is a deliberate tradeoff: it stops duplicates, which also means the exact same file won't be re-read within its window. If a load didn't land the way you expected:

  1. Check the board first. The load may already be there under Rate Confirmation — look before you resend.
  2. If the details changed, update the existing load rather than resending the same file. Editing the load you have is cleaner than fighting the fingerprint.
  3. If you genuinely need it re-read, wait out the 24-hour window so the new send doesn't collide with the earlier copy, or reach out to support.

Need a hand? Email support@numeo.ai or use the in-app Help option.

Was this helpful?