Executive Summary 

The integration involves mapping data from BytePro's loan file structure to Aidium's REST API, which uses two primary entities: - Transactions - Loan/mortgage data - Contacts - Borrower and party information 

Key considerations include: - BytePro uses enumerated fields with specific category values - Aidium uses nested object structures (e.g., Address objects) - Multiple borrower support (primary, secondary, tertiary) - Team-based data organization in Aidium 

BytePro Enumerated Fields Reference 

The following BytePro fields contain predefined categories that must be mapped to appropriate Aidium values:

1. OccupancyType

BytePro Values

0 - NotAssigned 1 - PrimaryResidence 2 - SecondaryResidence 3 - InvestmentProperty

2. Loan_LoanPurpose

 

BytePro Values

0 - NotAssigned 1 - Purchase 2 - Refinance 3 - Construction 4 - ConstructionPerm 5 - Second 6 - Third 7 - PurchaseMoneySecond 8 - Other 9 - PurchaseMoneyThird 10 - RefiSecond 11 - RefiThird

3. Loan Status

BytePro Values

0 - NotAssigned 1 - Prequal 2 - CreditOnly 3 - InProcessing 4 - Submitted 5 - Approved 6 - Resubmitted 7 - Declined 8 - InClosing 9 - Closed 10 - Canceled 11 - Lead 12 - Suspended 13 - DocsSigned 14 - Funded 15 - Purchased 16 - ClearToClose 17 - DocsSent 18 - CollateralSent 19 - Shipped 51 - CustomStatus1 52 - CustomStatus2 53 - CustomStatus3 54 - CustomStatus4 55 - CustomStatus5 56 - CustomStatus6 57 - CustomStatus7 58 - CustomStatus8 59 - CustomStatus9 60 - CustomStatus10 61 - CustomStatus11 62 - CustomStatus12 63 - CustomStatus13 64 - CustomStatus14 65 - CustomStatus15 66 - CustomStatus16 67 - CustomStatus17 68 - CustomStatus18 69 - CustomStatus19 70 - CustomStatus20 71 - CustomStatus21 72 - CustomStatus22 73 - CustomStatus23 74 - CustomStatus24 75 - CustomStatus25 76 - CustomStatus26 77 - CustomStatus27 78 - CustomStatus28 79 - CustomStatus29 80 - CustomStatus30

4. Borrower 1 & Borrower 2 (Co-Borrower) Marital Status

BytePro Values

0 - NotAssigned 1 - Married 2 - Separated 3 - Unmarried

5. FileData_OccupancyType

BytePro Values

0 - NotAssigned 1 - OwnerOccupied 2 - NotOwnerOccupied 3 - NotApplicable

6. Parties

BytePro Values	0 - NotAssigned 1 - LoanOfficer 2 - LoanProcessor 3 - LoanCloser 4 - Underwriter 10 - Lender 11 - MortgageeForInsurance 12 - FHASponsoringLender 13 - FHAOriginatingLender 20 - RealEstateAgent 21 - ListingAgent 22 - SellingAgent 25 - BuilderOrSeller 26 - Warrantor 31 - HazardInsuranceCompany 32 - MortgageInsuranceCompany 33 - FloodInsuranceCompany 34 - FloodDeterminationCompany 40 - TitleCompany 42 - Appraiser 44 - EscrowCompany 46 - SurveyCompany 48 - CreditBureau 59 - Attorney 60 - BorrowerAttorney 61 - SellerAttorney 62 - LenderAttorney 70 - Inspector 71 - PestInspector 80 - Creditor 81 - Bank 82 - Employer 83 - Landlord 84 - LoanSeller 85 - Investor 86 - Contractor 99 - Borrower 101 - OpenHouseAgent 102 - OtherUser 103 - ReferralSource 104 - HomeOwnersAssoc 105 - SettlementLocation 106 - OtherUser2 107 - OtherUser3 108 - OtherUser4 109 - MortgageeForTitle 110 - Broker 111 - Appraiser2 112 - TaxServiceCompany 113 - HazardInsuranceCompany2 114 - Trustee 115 - FHAAgent 116 - FHAPostClosingMortgageeRep 117 - FHAMortgageeRep 501 - OtherParty1 502 - OtherParty2 503 - OtherParty3 504 - OtherParty4 505 - OtherParty5 600 - Opener 601 - DocDrawer 602 - QualityControl 603 - Compliance 604 - Shipper 605 - LockDesk 606 - Accounting 607 - Servicing 608 - Insuring 609 - Secondary 610 - OtherUser5 611 - OtherUser6 612 - OtherUser7 613 - OtherUser8 614 - OtherUser9 615 - OtherUser10 616 - OtherUser11 617 - OtherUser12 618 - OtherUser13 619 - OtherUser14 620 - OtherUser15 621 - OtherUser16 622 - OtherUser17 623 - OtherUser18 624 - OtherUser19 625 - OtherUser20 626 - OtherUser21 627 - OtherUser22 628 - OtherUser23 629 - OtherUser24

Core Field Mappings

Aidium 

Type

Transaction Level Mappings

BytePro Field	Aidium Field	Notes
Select	loanNumber	string	Please select the applicable loanNumber field you use within BytePro
OccupancyType	occupancyType	string	See enum  mapping above
DateCreated	applicationDate	string
DateModified	lastModifiedBy	string	Track  modification
DownPaymentAmount1	downPayment	number	Down payment
status_PreapprovalApplicationDate	applicationDate	date
Status_AppraisalOrdered	appraisalOrderedDate	date
Status_AppraisalReceived	appraisalReceivedDate	date
SubProp_AppraisedValue	appraisedValue	number
Status_ClosedDate	closingDateActual	date
ExtendedFields_CreditRangeBor1	creditScoreBorrower	number
extendedFields_CreditRangeBor2	creditScoreBorrowerSecondary	number
DownPaymentAmount1	downPayment	number
Status_FundingDate	fundedDate	date
_TotalAllIncomes	income	number
LoanAmountInThousands	loanAmount	number
Loan_LoanProgramName	loanProgram	string
Loan_LoanPurpose	loanPurpose	string	See 2. Loan_LoanPurpose
Loan_LTV	loanToValue	number
loan_MortgageType	loanType	string
Loan_LockExpirationDate	lockExpirationDate	date
Loan_LockStartDate	lockDate	date
FileData_OccupancyType	occupancyType	String
Loan_IntRate	rate	Number
Loan_PurPrice	salesPrice	Number
Loan_Term	term	number
Statu_LoanStatus	TransactionInputStatus	string

 

Property Address Mappings (Transaction)

BytePro Field	Aidium Field	Notes
PropertyStreet1	string	propertyAddress.addressLine1	string	Primary address
PropertyStreet2	string	propertyAddress.addressLine2	string	Secondary  address
PropertyCity	string	propertyAddress.city	string	City name
PropertyState	string	propertyAddress.state	StateCode	Must be valid  state code
PropertyZip	string	propertyAddress.zipCode	string	ZIP code

Contact/Borrower Mappings (Contact/Transaction)

BytePro Field	Data Type	Aidium Field	Aidium Type	Notes
Bor1_FirstName	string	firstName	string	Primary borrower
Bor1_LastName	string	lastName	string	Primary borrower
Bor1_MailingStreet	string	address.addressLine1 address.addressLine2	string	Mailing address
Bor1_MailingCity	string	address.city	string	Mailing city
Bor1_MailingState	string	address.state	StateCode	Mailing state
Bor1_MailingZip	string	address.zipCode	string	Mailing ZIP
Bor1_Email	string	Email	string	Primary email
Bor1_Phone	string	phoneNumber	string	Primary phone
Bor1_Employer	string	employerName	string	Employer name
Bor1_JobTitle	string	jobTitle	string	Job title

Party Information Mappings

BytePro Field	Data Type	Aidium Field	Aidium  Type	Notes
Name	string(150)	Contact (type:  LENDER)	string	Create party  contact
Street1	string(50)	address.addressLine1	string	Party address
Street2	string(50)	address.addressLine2	string	Party address
City	string(50)	address.city	string	Party city
State	string(2)	address.state	StateCode	Party state
Zip	string(9)	address.zipCode	string	Party ZIP
Phone	string(20)	workPhoneNumber	string	Party phone
Fax	string(20)	faxNumber	string	Party fax

Parties in BytePro are managed through categories as are listed above in 

Implementation Guidelines 

Data Transformation Rules 

1. Date Conversion: Convert BytePro DateTime fields to ISO 8601 format (YYYY-MM DD) 
2. Currency Fields: Convert NullableCurrency to numeric values, handle null appropriately 
3. Enum Values: Use mapping tables to convert BytePro enum integers to Aidium string values 
4. Address Standardization: Ensure state codes are valid two-letter abbreviations 5. Phone Number Formatting: Standardize phone number formats for consistency 

Custom Field Strategy 

For BytePro fields without direct Aidium equivalents: 

Notify your Implementation Specialist of which custom fields need to be added. 

Error Handling 

1. Required Field Validation: Ensure all required Aidium fields are populated 
2. Data Type Validation: Validate numeric fields, date formats, state codes 
3. Null Value Handling: Define behavior for null/empty BytePro fields 

Multi-Borrower Support 

Handle multiple borrowers by: 

1. Creating separate Contact records for each borrower 
2. Linking contacts to transactions via borrowerId, borrowerSecondaryId, borrowerTertiaryId 
3. Maintaining borrower hierarchy and relationships 
4. Preserving co-borrower and guarantor distinctions 

Testing and Validation

Post-Integration Validation 

1. Compare source and target data for accuracy
2. Validate calculated fields (e.g., loan-to-value ratios) 
3. Verify contact relationships and hierarchies 
4. Test search and retrieval functionality 

Data Quality Checks 

1. Monitor for unmapped enum values 
2. Track conversion errors and data loss 
3. Validate required field population rates 
4. Monitor API response times and error rates