Data Exports: Clutch Lending LOS (LAS)

TABLE OF CONTENTS

• Overview
• What Is a Data Export?
• What Is Included in This Data Export?
• How to Use the Exports
• How Not to Use the Exports
• Terminology
• Table Relationship Diagram
• Join Key Reference
• Data Type Conventions
• Frequently Asked Questions
  • How can I get started with data exports?
  • Why should I use Clutch's data exports?
  • What's the cost?
  • How long are the exports available for download?
  • What should I do if I didn't receive my daily file?
  • I lost access to a file and I need to recover a copy. How can I get it?
  • I need a data export for sandbox data. How do I get it?
  • How can I request a new data export to answer new business questions?
  • Can I ask for additional fields in my data export?
  • What should I do if I want to report an inconsistency in the data?
• Getting Help

Overview

This article helps users at partner credit unions understand the Clutch Lending LOS data export: the files it contains, their columns, and how to use them.

This export covers loan applications originated in the Clutch Lending LOS, from origination through decision, closing, and funding. It is a relational export: a set of tables that join to each other, rather than a single flat file.

What Is a Data Export?

A data export is a daily batch of data, sent in .csv format via SFTP or the File Transfer API. Each file contains one table in a fixed, predetermined format.

• Frequency: daily
• Channel: SFTP or File Transfer API
• Format: .csv, pipe-delimited, double-quoted
• Data included: a fixed, predetermined format that scales across 100+ credit unions

For a comparison of the two delivery methods and the details of each, see Data Exports: API vs. SFTP Delivery.

What Is Included in This Data Export?

Eleven tables, each delivered as its own file. For each table there are two variants:

• Past 1 day: records created or updated in the previous 1 day, delivered under a folder named las_<table>-1-day
• Past 30 days: records created or updated in the previous 30 days, delivered under a folder named las_<table>-30-day

Both variants have the same columns; they differ in the time window and total volume. For the File Transfer API, the .csv files are delivered inside a zip.

The eleven tables, each with its own article containing the full data dictionary:

How to Use the Exports

Data warehouse ingestion

• Recommended: ingest the 30-day file of each table into your warehouse while upserting records (updating existing rows and inserting new ones) based on the primary key id. This way, if your ingestion process skips a day, it will catch up on the next run.
• Or append the 1-day file into your warehouse, taking care to check whether the record already exists there. Use the updated_on column to keep only the latest version of each record.

Analysis

• If you are going to analyze the data in a spreadsheet, use the 30-day files so you do not need to append anything.

Joining tables

• All tables join to loan_applications via application_id. See the Join Key Reference below.

How Not to Use the Exports

Important: If you need a metric spanning more than 30 days, do not append multiple 30-day files without a proper merge or upsert operation — you will get duplicates of the same records. Iterate through the files keeping the most recent version of each record (by id, using updated_on).

• Do not join tables by row order or by timestamps. Always use the documented keys (application_id, participant_id, entity_id plus entity_type).

Terminology

• An application is a loan application originated in the Clutch Lending LOS for your credit union.
• A participant is an applicant on an application. An application always has a PRIMARY participant and may have a CO_APPLICANT. Filter on role to separate them.
• audit_history is append-only: rows are never updated, so it is the authoritative record of when things happened and who triggered them.
• Participant personal information is point-in-time: it reflects the applicant's information as of the application, not later profile updates.

Table Relationship Diagram

All tables join to loan_applications via application_id.

loan_applications (1)
    ├── loan_products (1:1)
    ├── participants (1:many, primary + co-applicant)
    │       └── decisions (1:many, one per participant)
    ├── closing_information (1:1)
    │       └── disbursements (1:many, one per disbursement method)
    ├── staff_assignments (1:many, one per assignment event)
    ├── tasks (1:many)
    ├── comments (1:many)
    ├── audit_history (1:many)
    └── underwriting_metrics (1:1, decision-time snapshot)

Secondary relationships

• decisions.participant_id → participants.id
• tasks.participant_id → participants.id (nullable)
• comments.entity_id → resolves to a task or other entity (see entity_type)
• audit_history.entity_id → resolves to any entity type (see entity_type)

Join Key Reference

Data Type Conventions

Money fields are decimal USD dollars. Ratio fields are decimals (0.42 = 42%). Timestamps are UTC.

Frequently Asked Questions

Getting Help

For questions about enabling this export, adding a table, or anything specific to your credit union's setup, start with your Customer Success Manager. If you need help from Clutch Support, you can:

• Submit a ticket in the Clutch Support Portal at support.withclutch.com/support/tickets/new (the "Submit a Ticket" link in the top navigation).
• Email support@withclutch.com.