Data Exports: Funding

Modified on Tue, Aug 18 at 1:17 PM

TABLE OF CONTENTS

Guidelines
Data Dictionary
Related Articles
Frequently Asked Questions

Guidelines

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. It contains one table in a fixed, predetermined format.

Frequency: daily
Channel: SFTP or File Transfer API
Format: .csv, pipe-delimited, double-quoted

Data included follows a fixed, predetermined format that scales across all Clutch credit unions.

What Is Included in This Data Export?

Two files are included:

Account funding transactions for the past 1 day:
- A list of all concluded account funding transactions in the previous 1 day
- File name (for SFTP): funding-1-day_YYYYMMDDThhmmssZ_part-00000.csv
Account funding transactions for the past 60 days:
- A list of all concluded account funding transactions in the previous 60 days
- File name (for SFTP): funding-60-days_YYYYMMDDThhmmssZ_part-00000.csv

Both files share the same fields (columns), but they differ in use case (when to use each) and total volume of data, since one includes data for the past 60 days.

This export covers funding transactions for both personal and business accounts. Use application_type to tell them apart.

Important: Business applications were previously excluded from this export. Now that they're included, expect your row counts to increase — not just the column count. If your ingestion logic assumes every record represents a personal account, or if you reconcile on row counts, review it before you next process this file.

How to Use the Exports

Data warehouse ingestion:
- Ingest the 60-day file into your warehouse while upserting records (updating existing rows and inserting new ones) based on the primary key. This way, if your ingestion process skips a day, it will catch up on the next run.
- Alternatively, append the 1-day file into your warehouse, taking care to check whether the record already exists — a transaction can appear in more than one daily file if its status changed after it was first written.
Analysis: if you're analyzing the data in a spreadsheet, use the 60-day file so you don't need to append anything.

We recommend ingesting the 60-day file with an upsert operation as your primary method — it's more resilient to missed runs than appending the 1-day file. Use application_id together with account_id as the key.

How Not to Use the Exports

Important: Avoid duplicates. If you need a metric covering a period longer than 60 days, don't append multiple 60-day files without a proper merge/upsert operation — doing so will create duplicate transactions. Instead, iterate through multiple files and keep only the most recent status for each record.

Terminology

An application refers to any user who started the application process, even if they dropped off before opening the account.
An account is the actual account created via an application.
If one application was made for multiple accounts, the export will have multiple rows for the same application — one for each account.
If a user applied multiple times for the same account, multiple applications will appear (one per row).
A business application opens an account for a business entity rather than an individual. Business applications are identified by application_type = business. On these records, applicant_name and member_nr refer to a single resolved authorized signer for the business — the controlling signer where one is designated, otherwise the earliest signer on the application.

Ingesting Exports Into Your Data Warehouse

Update: if a record already exists in your data warehouse as a row in a table, update the entire row; if it doesn't, create a new one.
Append: always add new rows to the existing table.

Data Dictionary

New fields are always appended to the end of the file — existing fields are never renamed, reordered, or removed. If you enforce a strict schema on ingestion, allow for additional trailing columns.

Field Name	Description	Example
`applicant_name`	String: applicant's first and last name. Null if the user dropped off before identifying themselves. On business records, the resolved authorized signer.	Jane Doe
`member_nr`	Number: the user's member number in core. Null if the user wasn't an existing member and didn't finish the application.	400012345
`application_id`	String: a UUID that represents a unique account opening application. Together with `account_id`, this forms the primary key for the table.	0030dbe4-ead5-4543-afa1-61d24688b4ef
`account_id`	String: a UUID that represents a unique account. Together with `application_id`, this forms the primary key for the table.	0030dbe4-ead5-4543-afa1-61d24688b4ef
`transaction_funding_date`	Timestamp: date and time when the account was funded.	2024-03-07 18:08:32.765
`account_type`	String: account type the user is applying for. Null if the user dropped off before selecting one.	savings ; certificate ; checking
`funding_type`	String: the funding method the applicant chose: • CREDIT_CARD: credit card • INTERNAL_ACCOUNT: transfer from an existing account at the credit union • ACH: transfer from an existing account at another institution • CASH: cash • LFAO: funding performed by the credit union via internal transfer • NULL: user dropped off before choosing a funding method	CASH
`funding_amnt`	Number: amount the user chose to fund the account with.	$1000.00
`provider_name`	String: name of the funding provider that processed the transaction.	stripe ; plaid
`payment_transaction_id`	String: identifier used by the provider for the transaction.	0030dbe4-ead5-4543-afa1-61d24688b4ef
`account_number`	String: account number from core.	2121234567
`branch_name`	String: the name of the branch where the application is sitting.	The Best Branch
`application_numeric_id`	String: the human-readable application identifier.	12345
`application_type`	String: whether the underlying application is for a personal or a business account. Possible values: personal, business. Null on records created before this field was introduced.	business
`business_id`	String: a UUID that represents the business entity on a business application. Null on personal records.	3f9a2c71-8d04-4e2b-9a17-b5c8e0f4a921
`business_name`	String: legal or operating name of the business. Sourced from the entity's legal name, falling back to company name, then DBA name, then the authorized signer's name. Null on personal records.	Northgate Landscaping LLC

Data Exports: Account Opening — application-level detail for the accounts these transactions fund, including funding status and timestamps.
Data Exports: NACHA — transaction-level detail for the NACHA files we send you.
Data Exports: API vs SFTP Delivery — how exports are delivered, and how to choose between the API and SFTP.

Frequently Asked Questions

How Can I Get Started With Data Exports?

Ask your Clutch Customer Success Manager to turn it on for you. We recommend querying files through our File Transfer API — it makes it easy to build automations, set retries, or pull retroactive files. As an alternative, you can use SFTP, which requires setting up a connection (you may need to involve your IT team) and hosting your own server. See Data Exports: API vs SFTP Delivery for a side-by-side comparison.

Why Should I Use Clutch's Data Exports?

Data exports keep your team informed without needing to request ad hoc reports. They work for both operations and IT — you can open the .csv file directly in Excel or Google Sheets, or have your IT team ingest it into your data warehouse. It's an extract you can build reports on top of.

What's the Cost?

Clutch does not charge any additional fees. If you use SFTP, you'll need to host your own SFTP server. Alternatively, you can use our File Transfer API with minimal setup on your end.

How Long Are the Exports Available for Download?

For SFTP, it's up to you — since you host the server, you control how long files are retained once we push them. If you need retroactive files, contact our support team. For the File Transfer API, new exports are generated daily at 11:00 AM UTC and remain available for one week; you can query them at any time during that window.

What Should I Do if I Didn't Receive My Daily File?

Contact our support team at support@withclutch.com for assistance.

I Lost Access to a File and Need to Recover a Copy. How Can I Get It?

If you're using the File Transfer API, you can query it using the referenceDate parameter to retrieve past files — see the File Transfer API documentation for details. If you're using SFTP, contact your Customer Success Manager to arrange a recovery.

I Need a Data Export for Sandbox Data. How Do I Get It?

Sandbox only contains test users and can be misleading when interpreting data, so we don't support sandbox data exports.

How Can I Request a New Data Export to Answer New Business Questions?

Tell us what you're trying to achieve. Your implementation contact can help determine whether an existing export already supports your use case — if not, they'll pass your request along to our product team.

What Should I Do if I Want to Request Additional Fields in My Data Export?

We don't currently support custom fields per credit union, and we typically add new fields on roughly a 90-day cadence. Contact your Customer Success Manager to let them know which fields you need.

What Should I Do if I Want to Report Inconsistencies in the Data?

Let your Customer Success Manager know or submit a ticket to our Support team, and we'll assign an engineer to investigate right away.