Skip to main content
Field-level reference for every file exchanged with Lead over SFTP — the file counterpart to the API Reference. Concepts, workflows, and object semantics live in Products; this section is formats only. Exchanging files with Lead — SFTP setup, delivery mechanics, validation errors, and document delivery. Files you submit — schemas for the data you report to Lead: your customers (Customer file → the Entity object), their accounts, balances & transactions, applications, cards, collateral, authorized users, plus the Sales Response you submit to confirm each day’s receivables purchase, and X9 for checks. This is your customers’ data — the reporting side of Executing vs. Reporting — delivered by file where the equivalent API doesn’t exist yet (Integration Surfaces by Product). Reports Lead delivers — schemas for what Lead sends you: Daily Balance, Daily Activity, ACH Cash Reconciliation, Platform Reconciliation, network settlement reports, and the daily Sales Request. This is activity from Lead’s core — your banking infrastructure — reported to you. Legacy formats. Nacha files are retained for reference only — ACH file integrations have been replaced by the ACH API. [VERIFY zero active Nacha submitters; if some remain, change to “supported for existing file-integrated programs only.”] As workflows move from files to APIs (Platform Evolution), schemas here gain pointers to their API successors; until a successor ships, the schema on this site is authoritative.