TABLE OF CONTENTS
Overview
Grain: One row per state change or event per application | Primary key: id | Foreign key: application_id → loan_applications.id
The audit history is an append-only log of all significant events in the application lifecycle. It is the authoritative record for when things happened and who triggered them.
Delivery folders: las_audit_history-1-day and las_audit_history-30-day
This article covers one table. For delivery options, ingestion guidance, the full table relationship diagram, and the export FAQ, see Data Exports: Clutch Lending LOS (LAS).
Things to Know About This Table
- Rows are never updated: ingest this table append-only, deduplicating by
id. correlation_idgroups all events that originated from a single user action or API call.from_value,to_value, andfield_nameare populated for state-transition and field-update events.metadatais a JSON payload whose schema varies byevent_type.
Important: This is the only table in the export with no
updated_oncolumn, because rows are never modified after they are written.
Data Dictionary
| Field Name | Description | Example | Required? |
|---|---|---|---|
id | UUID: unique history record identifier. | 8b7a6c5d-4e3f-4222-b100-998877665544 | Yes |
application_id | UUID: foreign key to loan_applications. | a1b2c3d4-e5f6-7890-abcd-ef1234567890 | Yes |
partner_id | UUID: your credit union identifier. | 550e8400-e29b-41d4-a716-446655440000 | Yes |
event_type | String: type of event: APPLICATION_CREATED / APPLICATION_STATE_UPDATED / DECISION_CREATED / TASK_COMPLETED / ASSIGNMENT_CREATED / and others | APPLICATION_STATE_UPDATED | Yes |
actor_id | String: user ID of who triggered the event. Null for SYSTEM events. | usr_8f2a91 | No |
actor_type | Enum: who triggered the event: USER or SYSTEM | USER | Yes |
branch_id | UUID: branch context for the event. Null for events not associated with a specific branch. | 0f1e2d3c-4b5a-4677-8899-aabbccddee00 | No |
entity_type | String: type of the specific entity the event pertains to (for example TASK, DECISION, ASSIGNMENT). | TASK | No |
entity_id | UUID: ID of the specific entity the event pertains to. Use with entity_type to join to the relevant table. | 6f5e4d3c-2b1a-4099-8877-665544332211 | No |
correlation_id | UUID: request correlation ID. Use to group all audit events that originated from a single user action or API call. | 9c8d7e6f-5a4b-4333-a211-009988776655 | No |
from_value | String: value before the change. Available for state-transition events. | PENDING_REVIEW | No |
to_value | String: value after the change. Available for state-transition events. | DOC_PREP | No |
field_name | String: the field that changed. Available for field-update events. | state | No |
metadata | JSON: additional event context. Schema varies by event_type. | {"reason": "conditions cleared"} | No |
created_on | Timestamp: when the event was recorded (UTC). | 2026-06-12T15:45:00Z | Yes |
How This Table Joins to the Others
application_id→loan_applications.id.entity_idplusentity_type→ any entity type in the export. Always checkentity_typebefore joining.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article