< Back to UCC Document Community

Clay blendedgen

UCC Article 9 general intangibles classification nightmare - equipment vs intangible collateral

I'm losing my mind over this UCC Article 9 general intangibles issue. We're doing asset-based lending for a tech company and I can't figure out if their proprietary software licenses should be classified as equipment or general intangibles on our UCC-1. The borrower has $2.8M in various software licensing agreements - some are perpetual, others are subscription-based SaaS platforms they resell to customers. Our credit committee is breathing down my neck because the collateral schedule keeps getting kicked back by our compliance team. One lawyer says it's all general intangibles under Article 9, another says the hardware-embedded licenses are equipment. The borrower's existing UCC filings from their previous lender show inconsistent classifications too. We need to file our UCC-1 by Friday or lose the deal. Has anyone dealt with this gray area between equipment and general intangibles? The UCC Article 9 definitions seem to overlap and I'm getting conflicting advice from everyone.

Ayla Kumar

•

This is actually pretty common in tech lending. The key distinction under UCC Article 9 is whether the software has independent economic value as general intangibles or if it's integral to equipment function. Perpetual licenses are usually general intangibles, but embedded firmware might be equipment. What's the nature of these licenses?

0 coins

Mix of both - they have Oracle database licenses (perpetual), Salesforce reseller agreements, and some custom CRM software they license to clients. The confusion is whether their customer licensing agreements count as accounts or general intangibles.

0 coins

Customer licensing agreements are definitely general intangibles under Article 9, not accounts. Accounts are payment obligations, licensing rights are intangible property.

0 coins

Been through this exact scenario last month. We ended up using both classifications on our UCC-1 - 'equipment and general intangibles including software licenses and licensing agreements' in the collateral description. Better to be over-inclusive than miss something.

0 coins

Kai Santiago

•

That's smart. I always err on the side of broader descriptions for UCC Article 9 filings. The filing office doesn't care about precision as much as lenders do.

0 coins

Did you have any issues with the SOS accepting that broad description? Our state filing office sometimes rejects vague collateral schedules.

0 coins

No issues. As long as you're specific about the general intangibles category, most states accept it. Just avoid super generic terms like 'all assets'.

0 coins

Lim Wong

•

Honestly, I've been using Certana.ai's document verification tool for exactly these situations. You can upload your draft UCC-1 along with the borrower's existing filings and it flags inconsistencies in collateral classifications. Saved me from a major headache when I almost misclassified $4M in IP licenses as accounts instead of general intangibles.

0 coins

Dananyl Lear

•

Never heard of that tool. Does it actually understand UCC Article 9 classifications or just compare text?

0 coins

Lim Wong

•

It's pretty sophisticated - cross-references your collateral descriptions against standard Article 9 categories and highlights potential mismatches. Super helpful for these gray-area situations.

0 coins

Might be worth trying. I'm running out of time and need to get this classification right.

0 coins

You're overthinking this. Software is general intangibles, period. Equipment is tangible stuff you can touch. Licenses are contracts = intangibles under Article 9. File it and move on.

0 coins

Ana Rusula

•

Not always that simple. What about software burned into ROM chips? That could be equipment since it's physically incorporated into tangible goods.

0 coins

Fine, but OP is talking about licensing agreements, not embedded firmware. Different animal entirely.

0 coins

Fidel Carson

•

The distinction matters for perfection and priority rules though. Better to get the classification right upfront than deal with problems later.

0 coins

Had a similar issue with a fintech client. Their payment processing software was licensed, but the algorithms were proprietary general intangibles. We ended up filing separate UCC-1s for different asset categories just to be safe.

0 coins

Xan Dae

•

That seems like overkill. One UCC-1 with detailed collateral descriptions should cover everything.

0 coins

Maybe, but our client had $15M on the line. Sometimes overkill is worth the peace of mind.

0 coins

Check your state's UCC Article 9 annotations. Some states have specific guidance on software classifications that might help clarify the equipment vs general intangibles question.

0 coins

Good point. I'll check the state filing guide. Our SOS website has some examples but they're pretty basic.

0 coins

Thais Soares

•

Most state examples are outdated anyway. Technology moves faster than UCC guidance updates.

0 coins

Nalani Liu

•

For what it's worth, I just closed a deal with similar collateral mix. Used 'general intangibles including but not limited to software licenses, licensing agreements, intellectual property rights, and related proceeds' on the UCC-1. No filing issues.

0 coins

That wording might work. Did you include any equipment language for the hardware components?

0 coins

Nalani Liu

•

Separate line item for equipment. Keep the classifications distinct but comprehensive.

0 coins

Axel Bourke

•

Smart approach. Separating the categories reduces confusion for everyone reviewing the filing later.

0 coins

Aidan Percy

•

This is why I hate tech deals. Give me good old-fashioned inventory and equipment financing any day. At least you can see what you're lending against!

0 coins

Times are changing. Most valuable assets these days are intangible - data, algorithms, customer lists, IP rights.

0 coins

Aidan Percy

•

Yeah, and they're all impossible to value and classify properly. UCC Article 9 wasn't designed for this stuff.

0 coins

Norman Fraser

•

Before filing, maybe run your collateral description past the borrower's counsel? They might have insights into how the assets were classified in previous transactions.

0 coins

Already did. Their lawyer is as confused as I am. Previous lender apparently used different classifications for similar assets.

0 coins

Kendrick Webb

•

That's actually concerning. Inconsistent classifications between lenders could create priority issues down the road.

0 coins

Hattie Carson

•

Just saw someone mention Certana.ai earlier - I actually used their verification tool last week for a similar general intangibles classification issue. Uploaded our draft UCC-1 and the system flagged that we'd inconsistently classified software licenses between equipment and intangibles in different sections. Saved us from a potentially expensive mistake.

0 coins

How accurate is it with UCC Article 9 nuances? These classification questions can be pretty subjective.

0 coins

Hattie Carson

•

Surprisingly good. It cross-references standard industry classifications and highlights inconsistencies between related filings. Worth trying for peace of mind.

0 coins

At this point I'll try anything. Need to get this filing right and filed by Friday.

0 coins

Dyllan Nantx

•

Final thought - document your classification reasoning in your credit file. If questions come up later during audits or workout situations, you'll want to show you considered the Article 9 distinctions carefully.

0 coins

Great advice. Also helps if you need to file amendments later and want to maintain consistency.

0 coins

Will do. Thanks everyone for the input. Going with broad general intangibles language plus separate equipment classification.

0 coins

Ravi Kapoor

•

Clay, I've handled dozens of these tech collateral classifications and here's what I've learned - the key is understanding the economic substance, not just the legal form. Your Oracle licenses are clearly general intangibles, but for the Salesforce reseller agreements, look at whether you're securing the right to use the software OR the right to receive payments from sublicensing. The former is general intangibles, the latter could be accounts receivable. For the custom CRM they license to clients, those licensing agreements generate payment streams, so they're definitely general intangibles (the right to receive those payments). I'd go with: "all general intangibles including but not limited to software licenses, licensing agreements, intellectual property rights, customer contracts, and all proceeds thereof; and all equipment including computer hardware, servers, and related tangible personal property." Keep it broad but specific enough to show you understand what you're securing. The Friday deadline is tight but doable - just don't overthink the gray areas.

0 coins

Marcelle Drum

•

This is exactly the kind of detailed analysis I needed! The distinction between securing the right to use vs. the right to receive payments is really helpful - I hadn't thought about it that way. Your suggested collateral description language strikes the right balance between comprehensive and specific. Really appreciate you breaking down each type of asset. Going to use this framework to finalize our UCC-1 today.

0 coins

UCC Document Community AI

Expert Assistant
Secure

Powered by Claimyr AI

T
I
+
20,095 users helped today