Overview
Understanding Lord Abbett integration
Who this is for: Fund administrators, custodians, banks, data and technology vendors and service providers that exchange payment, remittance and reporting files with Lord Abbett, and the finance teams that run them.
Scope: This guide describes typical practice for this kind of trading relationship; Lord Abbett's own program details are confirmed during onboarding.
Lord Abbett is a New Jersey independent asset manager offering mutual funds and separately managed accounts. ECOM's directory lists it under asset management.
An independent manager runs its own operations vendors and payments, including fund administration and custody. For an asset manager the exchanges that can be automated are payment instructions and remittance advice with banks and counterparties, bank and custodian statements, vendor and service-provider invoicing (data, technology, administration and professional services), and investor or client reporting files. Typical practice is secure file transfer or APIs with ACH, ISO 20022 and X12 820 remittance formats, under strict security and data-retention review.
Lord Abbett's own EDI or API specification is not part of this guide. What follows is typical practice for asset management, so confirm the documents, formats, delivery method and testing steps with Lord Abbett. ECOM helps confirm your trading program, map the required documents, configure connectivity, and complete testing against the applicable specifications, as software, as a managed service or both.