X12 transaction guide · Government and regulatory
EDI 154 Secured Interest Filing
The X12 document used to file UCC financing statements, liens, judgments and other statements of secured interest, and to exchange related data.
- Sent by
- Lender, filer or filing service
- Received by
- Filing office, such as a secretary of state
- Standard
- ANSI ASC X12
What is an EDI 154?
The EDI 154 Secured Interest Filing is the ANSI X12 transaction set used to file Uniform Commercial Code (UCC) financing statement forms, liens, judgments and other statements of secured interest, and to exchange secured interest information.
Lenders that take collateral, such as equipment or receivables, file financing statements to perfect their security interest and establish priority over other creditors. Filing electronically speeds up perfection and returns filing numbers and dates the lender needs. Filing offices define the formats they accept.
How to read this diagram: the top row shows who sends the 154, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 154 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.
When it is used
- Filing UCC financing statements
- Filing amendments, continuations and terminations
- Searching or exchanging secured interest records
Where it fits in the document flow
Structure
Mandatory segments in the 154 (X12 release 008010)
The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.
- ST
- BGN
- N1
- LS1
- SE
Practical example
The 154 in practice
A bank makes an equipment loan to a manufacturer. Its filing service sends the secretary of state a 154 financing statement naming the debtor, the bank as secured party and the collateral. The office files it and returns the filing number and date, which the bank records in the loan file.
Implementation
Implementation considerations for the 154
- Use the debtor's exact legal name as registered.
- Track continuation deadlines to keep filings effective.
- File terminations when loans are repaid.
- Check which formats each filing office accepts.
How ECOM helps
Automate the 154 with ECOM
Industry
Financial Services
Secure file transfer and B2B integration for banks and financial institutions.
Solution
Financial Document Automation
Automate invoices, remittances, payment files and bank statements from capture to posting.
Solution
EDI Integration
Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.
More general questions about EDI are answered in the EDI FAQ.
Related transactions
Related government and regulatory documents
Need help with the EDI 154?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.