CSV Integration Schema: Transactions
Last updated: October 5, 2026
This is the format for Transactions coming out of Housing.Cloud — housing and dining charges, credits, refunds, and prorations, all in one file.
| Column | Type | Required | Notes |
|---|---|---|---|
hcUniqueId |
string | Yes | A unique identifier from a Housing.Cloud index |
recipientSisId |
string | Yes | |
recipientEmail |
string | Yes | The student's .edu email if provided |
issuerEmail |
string | No | |
costCode |
string | Yes | The Charge Code's code |
amount |
double | Yes | |
dateCreated |
date | Yes | |
billingDateStart / billingDateEnd
|
date | No | Included when the transaction was pro-rated |
isRefund |
boolean | Yes | Distinguishes a refund/credit from a charge |
isProration |
boolean | Yes | |
description |
string | Yes | |
externalTermId |
string | No | Populated if the Cycle has one configured |
Charges, credits, refunds, and prorations all travel in this one file — isRefund and isProration tell them apart. There are no separate debit/credit files.
Delivery
Egress · filename transactions_yyyy_mm_dd_{uuid}.csv. Ethos equivalent: student-charges (v16).