Data Exports: Clutch Lending STP

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?
  • Why are some applications missing from the export?
  • Why are the member number, housing, income, or employment fields blank for an application?
  • 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 STP (Straight-Through Processing) data export: the files it contains, their columns, and how to use them.

This export covers loan applications that were processed through Clutch's straight-through processing (STP) flow, from the application through decision, booking to your core, and funding. It is a relational export: a set of tables that join to each other, rather than a single flat file. It is a focused subset of the Clutch Lending LOS (LAS) export, plus a few fields specific to STP (core account number and funded timestamp).

What Is a Data Export?

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

• Frequency: daily
• Channel: SFTP
• Format: .csv, pipe-delimited, with a header row. Every value is double-quoted, and a missing value is delivered as an empty quoted value ("")
• Data included: a fixed, predetermined format that scales across credit unions

What Is Included in This Data Export?

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

• Past 1 day: records created or updated during the previous calendar day (UTC), delivered under a folder named stp_<table>-1-day
• Past 30 days: records created or updated during the previous 30 calendar days (UTC, ending at midnight today), delivered under a folder named stp_<table>-30-day

Both variants have the same columns; they differ in the time window and total volume. When no record falls in the window, you still receive a file that contains only the header row.

Only applications that were processed through straight-through processing are included, regardless of the outcome (funded, declined, routed to manual handling, failed, or still in progress). Applications that never entered the STP flow do not appear in this export.

The six 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 (for decisions, which does not deliver updated_on, upsert on id).

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 treat the id of a disbursement as permanent: it can change when the application's disbursement list is saved again. See the disbursements article.
• Do not join tables by row order or by timestamps. Always use the documented keys (application_id, participant_id).

Terminology

• An application is a loan application originated in the Clutch Lending LOS for your credit union that was processed through straight-through processing (STP).
• 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.
• The main applicant is the application's primary applicant. The member number and the housing, income and employment fields on loan_applications describe the main applicant.
• Routed off STP means the application was moved off the straight-through-processing path to manual handling (see stp_off_board_stage and stp_off_board_reason on loan_applications).
• The main applicant's information on loan_applications is as reported on the application; it is blank when it could not be linked to the application.

Table Relationship Diagram

All tables join to loan_applications via application_id.

loan_applications (1)
    ├── loan_products (1:many, typically one)
    ├── participants (1:many, primary + co-applicant)
    │       └── decisions (1:many, one per participant)
    ├── closing_information (1:1)
    └── disbursements (1:many, one per disbursement)

Secondary relationships

• decisions.participant_id → participants.id

Join Key Reference

Data Type Conventions

Money fields are decimal USD dollars. Ratio fields are decimals (0.42 = 42%). Timestamps are UTC and include milliseconds. Any double quote (") inside a text value is replaced with a single quote (') so it does not break the file.

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.