ATOM Promissory Note Feed

1. Overview

Layout/Mapping
• Header Record
• Detail Record
• Trailer Record

II. Overview
In a processing flow, where the lender rather than the guarantor, maintains the promissory notes and the guarantor disburses, it is necessary for the lender to indicate to the guarantor's system that the promissory note has been received. The Promissory Note Verification File allows the lender to send a promissory note indicator to the guarantor. This file format was originally created by GuaranTec for the Missouri Department of Higher Education.

Layout/Mapping
PNV-1 Each Promissory Note Verification File will contain one header record, one or more detail records, and one trailer record, with the data positioned as shown in the following tables.

PNV-2 Each record in the Promissory Note Verification File will be followed by a carriage return character.

Table Column Definitions
Columns in the tables are defined as follows:

Field	The ordinal number of the field.
Name	The name of the field.
Position	The position of the first character in the field.
Size	The size and data type of the field. An X indicates a single alphanumeric character, while a 9 indicates a single numeric character. A number enclosed in parentheses immediately following the symbol X or 9 specifies the number of consecutive occurrences of that symbol. For example, X(005), indicates an alphanumeric field with five characters. A V indicates the location of an assumed decimal point. The V is not counted in the size of the field. The number of 9s that follow the V indicates how many digits follow the assumed decimal point. Thus, 9(005)V99 indicates a numeric field with five digits plus an assumed decimal point followed by two digits.
Enterprise Table	The Enterprise table(s) that corresponds to the data in the file.
Enterprise Column	The Enterprise column(s) that corresponds to the data in the file.
Mapping	Indicates the expected constant value or list of values with their mapping to Enterprise valid values.

Unless otherwise noted, alphanumeric fields are left justified and padded with spaces and numeric fields are right justified and padded with zeros.

Header Record

Field	Name	Position	size	Enterprise Table	Enterprise Column	Expected Value
1	Record Identifier	1	X(001)			H
2	File Identifier	2	X(005)			PNOTE
3	Source ID	7	9(006)	ORG_Organization	OE_code
4	Create Date (MMDDCCYY)	13	9(008)
5	Filler	21	X(060)

Detail Record

Field	Name	Position	size	Enterprise Table	Enterprise Column	Mapping or Expected Value
1	Record Identifier	1	9(002)	N/A	N/A	16
2	Effective Date	3	X(006)	N/A	N/A	N/A
3	State	9	X(002)	N/A	N/A	N/A
4	Lender ID	11	9(006)	ORG_Organization	OE_code	Where organization_cd = LOA_Application. Lender_cd
5	SSN	17	9(009)	PER_Person	SSN	Where person_cd = LOA_Application. Borrower_cd
6	Insurance Number	26	X(010)	N/A	N/A	N/A
7	Lender Branch	36	9(002)	ORG_Organization	BR_code	Where organization_cd = LOA_Application. Lender_cd
8	Loan Type	38	X(001)	LOA_Loan or LOA_SchoolCertRequest	Loan_Type_cd Loan_Group_cd	G or U = Stafford P = PLUS
9	Insurance No. Flag	39	X(001)	N/A	N/A	N/A
10	Filler	40	X(012)	N/A	N/A	N/A
11	Prom Note Verification Flag	52	X(001)	LOA_MasterPromissory or LOA_Application	Paper_Copy_Code App_Copy_Code	Y = A
12	Borrower Authorization Statement Flag	53	X(001)	N/A	N/A	N/A
13	LOAN ID	54	X(016)	LOA_Loan	Loan_cd	(Must match Enterprise system. During normal app processing, the lender would typically receive this in the Guarantor Use Only field of a CL4 Response File record.)
14	Borrower Signature Date (MMDDCCYY)	70	9(008)	LOA_MasterPromissory	Borrower_Signature_Dt
15	Filler	78	X(003)	N/A	N/A	N/A

Trailer Record

Field	Name	Position	size	Enterprise Table	Enterprise Column	Expected Value
1	Record Identifier	1	X(001)			T
2	Detail Record Count	2	9(010)
3	Filler	12	X(069)