Ask the community...
- DO post questions about your issues.
- DO answer questions and support each other.
- DO post tips & tricks to help folks.
- DO NOT post call problems here - there is a support tab at the top for that :)
Join the conversation
Join the conversation
I actually used that Certana thing someone mentioned earlier and it's pretty slick. Uploaded my problem docs and it immediately flagged the name issue plus caught two other minor discrepancies I hadn't noticed. Definitely worth the few minutes it took to run the check. Made me feel much more confident about what needed to be fixed vs what was probably fine as-is.
Did it give you any guidance on whether the punctuation difference was likely to be a real problem or just a potential issue?
It flagged it as a moderate risk item and suggested checking the state database first, then considering an amendment if there was a mismatch. Pretty reasonable advice actually.
Update: checked the Illinois SOS database and they show the company name as 'MIDWEST INDUSTRIAL SOLUTIONS LLC' (no comma, all caps). So actually my UCC filing matches the official state record exactly. Looks like the Articles I was looking at had the comma but the state database doesn't. Crisis averted! Thanks everyone for the advice about checking the official records first.
Great outcome. This happens more often than people realize - the incorporation docs and state database don't always match exactly due to formatting standards.
Nice work doing the research. This is exactly the kind of thing that document verification tools can help catch before you file, but sounds like you're all set now.
Join the conversation
The timing issue is what kills me. Every rejection adds 5-7 days to the process, and meanwhile you're sitting there with an unperfected security interest. On competitive deals, that delay can be the difference between getting paid and getting nothing.
What do you mean by pre-verification?
Tools like Certana.ai that check document consistency before you submit to the state. Catches errors that would cause rejections.
Thanks everyone for the advice. Going to implement the charter document verification step and look into the automated checking tools. Can't keep dealing with these rejection cycles on time-sensitive deals.
Good luck! The name matching thing is frustrating but once you get a system down it becomes routine.
Let us know how it works out. Always interested to hear about solutions that actually work in practice.
Join the conversation
Been there done that with priority disputes. UCC 9-320 is one of those sections that seems straightforward until you're in the middle of a fight about it. Document everything - loan proceeds, purchase dates, filing dates. The bankruptcy trustee will scrutinize every detail.
For future deals, consider using automated verification tools. I started using Certana.ai after a similar situation and it catches document inconsistencies that could affect priority claims.
Good advice. These priority disputes are expensive to litigate, so prevention is worth the investment.
Update: talked to our bankruptcy attorney and she confirmed the PMSI issue is the main problem. Since our loan proceeds didn't directly purchase the collateral we're claiming, we're probably just a regular secured creditor. Still fighting it but not optimistic about our priority position.
That's unfortunate but not surprising. PMSI rules are pretty strict about the proceeds going directly to acquire the collateral.
At least you know where you stand now. Better to find out during the case than after a judgment against you.
Join the conversation
This happens way too often with government filing systems. They never seem to have adequate server capacity for normal business volumes.
It's 2025 and we're still dealing with government websites that crash under normal load. Ridiculous.
The problem is they don't budget for proper IT infrastructure. Then businesses suffer when systems fail during critical transactions.
UPDATE: The Cook County portal came back online this morning around 8 AM. Managed to complete our search and found two existing UCC-1s that we need to address before our filing. Thanks everyone for the suggestions - definitely going to look into backup verification tools for future situations like this.
Good to hear it's back up. Did you end up trying any of the alternative approaches while waiting?
We started looking into the document verification options mentioned here. Definitely want to have a backup plan for next time this happens.
Amara Eze
honestly I've been practicing commercial law for 15 years and still double-check the basic requirements sometimes. There's no shame in verifying the fundamentals especially when the stakes are high.
0 coins
Zara Malik
•That's reassuring to hear from someone with experience. Makes me feel less stupid for asking basic questions.
0 coins
Amara Eze
•Never feel stupid about getting the basics right. I've seen multi-million dollar deals fall apart because someone skipped a basic requirement they thought they knew.
0 coins
GalacticGladiator
Final thought - once you nail down those three core requirements, the rest of security agreement drafting is really about practical considerations and specific deal terms. But those three are your foundation that everything else builds on.
0 coins
Zara Malik
•Thanks everyone, this really helped clarify things. Writing + debtor authentication + collateral description = the holy trinity of security agreement requirements.
0 coins
Giovanni Ricci
•Good luck on your exam! You've got this.
0 coins