Student Resource Element

Required Element? No

Can Repeat? Yes

Best Practices: After a Title IV fund is disbursed through SFP, the disbursement details must be sent back via student resources to ensure the disbursement date in SFP matches the record in the student accounting application. If this isn't done downstream processes in SFP will be impacted. These student resources must be retained in the Student Academic and Financial Information (SAFI) for the entire program.

Field: External Transaction ID

Description: Value that represents the student resource

Impact on Financial Aid Processing: Use this ID from an external accounting application.

Example	Data Type	Required	XML Schema Validation	Accessible via Configuration?	Display Locations
12345	String	Yes	No	Yes getExternalTransactionId()	Packaging

Field: Payment ID

Description: Payment ID as defined by SFP during the disbursement of a fund

Impact on Financial Aid Processing: For all disbursements that we send across, we expect that at some point, the disbursement would be sent back to SFP with the date for which the payment was posted to the student ledger and the unapplied amount.

SFP expects that all payments are retained within the student resource section as soon as they appear the first time (used for the credit balance calculation).

If this value is blank, then we'll treat the sent fund as a student resource and try to add it to the student's package based on the academic year that contains the ledger posting date or for which the course is in (if the student resource is within the course).

Example	Data Type	Required	XML Schema Validation	Accessible via Configuration?	Display Locations
0191208-MBA021-PELL-1-1-1-1	String	No	No	Yes getPaymentId()	Disbursing Credit Balance

Field: Source

Description: A description of the source of the sent student resource

Impact on Financial Aid Processing:None

Example	Data Type	Required	XML Schema Validation	Accessible via Configuration?	Display Locations
Oracle Financial	String	Yes	No	Yes getSource()	Packaging

Field: Fund Code

Description: Fund code that represents the sent student resource

Impact on Financial Aid Processing: The fund code sent must match a configured fund code within SFP, else the message will be rejected. This is because if the fund is managed outside of SFP, we need to know how to handle the fund (whether it reduces need, and so on.)

Example	Data Type	Required	XML Schema Validation	Accessible via Configuration?	Display Locations
MNSTATEGRANT	String	No, if Payment ID is populated Yes, if Payment ID isn't populated	Must match Fund Code listed on Fund Configuration Engine	Yes getFundCode()	Packaging

Field: Description

Description: Description of the sent student resource

Impact on Financial Aid Processing: This will be used in the UI when sending across a fund that isn't managed within SFP (For example: Walmart scholarship, grandma's contribution, and so on.). When a fund is managed outside of SFP and sent in to be added to the student's package, we don't use the description as defined when configuring the fund in SFP, instead we use this one. That way institutions can consolidate fund codes if all the funds act the same way, but send a separate description.

Example	Data Type	Required	XML Schema Validation	Accessible via Configuration?	Display Locations
Minnesota State Grant	String	No	No	Yes getDescription()	Packaging

Field: Amount

Description: Amount for which the student resource refers to (whether a payment or a fund managed outside of SFP)

Impact on Financial Aid Processing: This field is used in packaging non Title IV funds.

Example	Data Type	Required	XML Schema Validation	Accessible via Configuration?	Display Locations
3000.32	Decimal	Yes	No	Yes getAmount()	Packaging

Field: Credit Balance Indicator

Description: Indicator representing if the fund can be used in the credit balance calculation

Impact on Financial Aid Processing: The credit balance calculation will only include payments in the student resource section if the credit balance is true.

If you don't want to use SFP to calculate credit balance stipends, you should include this as false for all payments.

Example	Data Type	Required	XML Schema Validation	Accessible via Configuration?	Display Locations
True	Boolean	No	True False	Yes getCreditBalanceIndicator()	Not viewable from the UI

Field: Resource Fee Discount

Description: Indicator representing if the discount is being used to pay for a resource fee

Impact on Financial Aid Processing: The credit balance calculation will include resource fee discounts if configured for Authorization to Hold (ATH) for resource fees and student or parents has sent ATH resource fee.

Example	Data Type	Required	XML Schema Validation	Accessible via Configuration?	Display Locations
True	Boolean	No	True False	No	Not viewable from the UI

Field: Ledger Posting Date

Description: Date for which the payment was made on the student's ledger

Impact on Financial Aid Processing: For disbursed Title IV Payments, this date is reconciled with the date communicated with Common Origination and Disbursement (COD), and it's required to be sent before Return to Title IV (R2T4) calculation.

If the student resource isn't associated to an existing Title IV fund, or to a course in the SAFI, packaging logic will identify which payment period or term to package the student resource to.

Example	Data Type	Required	XML Schema Validation	Accessible via Configuration?	Display Locations
2025-01-01	Date	Yes	No	Yes getLedgerPostingDate()	Disbursing

Field: Unapplied Amount

Description: Amount of the payment that hasn't been applied to a particular charge. This value is used in the credit balance calculation.

Impact on Financial Aid Processing: This field is used in right to cancel calculation and in credit balance calculation.

Unapplied amount must be present for Title IV funding.

Example	Data Type	Required	XML Schema Validation	Accessible via Configuration?	Display Locations
2775.00	Decimal	No	No	Yes getUnappliedAmount()	Credit Balance Disbursing

Field: Amount Applied to Prior

Description: Amount of the payment that was applied to previous academic year charges.

Impact on Financial Aid Processing: Used in the credit balance calculation to allow for $200 to go to prior year charges. Also, calculated when sending informational applied to charge amounts in late disbursement and post withdrawal disbursement messages.

Example	Data Type	Required	XML Schema Validation	Accessible via Configuration?	Display Locations
50.00	Decimal	No	No	No	Credit Balance

Field: Status

Description: Status of the student resource

Impact on Financial Aid Processing: This field is used in packaging non Title IV funds. If set to actual the fund will be Awarded.

Example	Data Type	Required	XML Schema Validation	Accessible via Configuration?	Display Locations
Actual	Enumeration (Enum)	Yes	Actual Estimated	Yes getStatus()	Packaging Credit Balance