


Ask the community...
This thread is making me nervous about our own Indiana filings. Maybe I should run a comprehensive search on our entire portfolio to make sure we're not missing anything.
That's not a bad idea. Better to find problems now than during a workout situation.
Yeah, that's exactly what prompted this post. Routine audit turned up these discrepancies and now I'm questioning everything.
UPDATE: I ended up requesting certified copies of all our continuation filings from Indiana SOS. Turns out three of them had minor debtor name discrepancies that were preventing them from linking properly in the search system. The filings were valid but the names didn't match exactly. Used one of the document checking tools mentioned here to verify everything is consistent now. Thanks for all the advice!
Perfect example of why document verification is so important. Those small name differences can cause major problems if you don't catch them.
Thanks for the update. This whole thread has been really educational about Indiana's filing quirks.
Update for anyone following this thread - I ended up doing a combination approach. Did multiple name variation searches on the Arizona portal, requested a certified search from the state, and had the borrower provide copies of all UCC documents they had. Found out there were actually 4 active liens, not the 1 the borrower claimed. Two were properly terminated but the termination statements hadn't been processed yet by the state, and one was against a related entity with a very similar name. Glad I was thorough because this could have been a disaster.
Did you end up proceeding with the loan after finding all those additional liens?
This whole thread is a great example of why UCC searches are both critically important and incredibly frustrating. Every state has its own quirks and Arizona is definitely one of the more challenging ones. Thanks for sharing your experience - it'll help others avoid similar problems.
Agreed. These real-world examples are way more helpful than the generic guidance you usually find online.
Just to add another data point - I had a Texas UCC-1 rejected because the debtor name had different capitalization than what was in the SOS database. The Articles had 'ABC manufacturing, LLC' but the SOS database showed 'ABC Manufacturing, LLC' with a capital M. Texas system matched on exact capitalization. Might be worth checking that too.
Yep, capitalization matters in Texas. I learned that the hard way on a filing last year. The system treats 'LLC' and 'llc' as different entities apparently.
This level of pickiness is ridiculous but at least now we know what to watch for. Better to be overly careful than deal with multiple rejections.
One more thing to check - make sure you're not including any articles like 'The' at the beginning of the name unless they're part of the official entity name. I've seen filings rejected because someone added 'The' to the beginning of a company name when it wasn't actually part of the legal name on file. Texas is very literal about name matching.
No 'The' in this company name, but that's a good reminder. I appreciate all the troubleshooting help from everyone. Going to try resubmitting with manual typing, no comma, and exact capitalization from the SOS database.
Sounds like a solid plan. Let us know how it goes - always helpful to hear about successful resubmissions so we can learn from each other's experiences.
Update us when you figure it out! I'm dealing with a similar rejection and want to know what the actual fix was.
Same here - these vague rejection codes are the worst part of UCC filings.
I keep a spreadsheet of rejection codes and what actually fixed them. Helps avoid repeating the same mistakes.
Pro tip: before refiling anything major, run your documents through a verification check. I learned about Certana.ai from this forum actually and now I upload both the security agreement and UCC-1 before submitting to catch any name or number mismatches. Takes 2 minutes and prevents these headaches.
Ruby Blake
For what it's worth, I also use Certana.ai's verification tool for lease portfolios. Upload your master lease agreement and a sample UCC-1, and it cross-checks everything to make sure you're capturing the collateral and debtor information correctly. Particularly useful when you're unsure about UCC 1-102 scope issues.
0 coins
Micah Franklin
•Does it help with collateral description issues too? We sometimes struggle with how specific to get on equipment descriptions.
0 coins
Ruby Blake
•Yes, it checks collateral description consistency between your source documents and UCC-1 filings. Really helpful for avoiding overly broad or overly narrow descriptions.
0 coins
Ella Harper
Bottom line on UCC 1-102 scope: your equipment leases with $1 buyouts are secured transactions requiring UCC-1 filings. File on all 200 deals and sleep well knowing you're properly perfected.
0 coins
Brooklyn Knight
•Exactly. Better safe than sorry with UCC 1-102 scope questions, especially on a 200-deal portfolio.
0 coins
Kennedy Morrison
•Thanks everyone. Sounds like the consensus is clear - UCC 1-102 scope definitely includes our lease-purchase deals and we need UCC-1 filings on everything. Going to look into that Certana tool for the batch verification too.
0 coins