News Alert!
Per Circular 26-24-13, use of the Loan Review API to transmit Full File Loan Review (FFLR) documents to VA is required for all loans selected for a FFLR on or after November 4, 2024. As of this date, LGY will no longer accept files received via manual upload to WebLGY Correspondence in response to an FFLR request. Failure to comply could result in a lender’s inability to make VA loans.
Lenders who use a third-party Loan Origination System (LOS) should engage their technology provider in discussions regarding implementation of a Loan Review integration and encourage them to collaborate with LGY. Lenders with a proprietary LOS or a desire to build their own integration should request a discussion with the Loan Origination Transformation (LOT) API Implementation Team by visiting the LGY Help Center and selecting ‘API Support’ as the product for which you are seeking support.
Visit the Loan Review page to learn more!
Use the navigation buttons below to see more details on recent Transformation activites.
VA is transforming the VA home loan lifecycle to eliminate manual data entry, improve data integrity, and streamline the process. This large-scale undertaking is a years-long effort that includes an end-to-end Application Programming Interface (API) ecosystem to introduce LGY technology dataset standards such as (Uniform Loan Application Dataset (ULAD), Uniform Appraisal Dataset (UAD), Uniform Closing Dataset (UCD), and Uniform Loan Delivery Dataset (ULDD) that align with the lending community and other Federal agencies.
A transformed LGY means an increased focus on our customers, Veterans. It also means providing transparency and real-time visibility to relevant loan information throughout the loan lifecycle.
VA will take a phased approach in deploying the various APIs to realize its full transformation strategy. The Loan Review API was released to production in January 2023, followed by Pre-Close API beta version testing availability as of September 2023, with subsequent releases of the Pre-Close API to cover multiple borrower purchase loans, Interest Rate Reduction Refinancing Loans (IRRRLs), and Cash-out Refinance loans. Other APIs will be released over the next couple of years.
The Loan Review API will allow loan files, along with the Uniform Loan Application and Closing datasets, to be submitted directly from a lender’s system to VA with the click of a button – a streamlined, simplified method with increased data accuracy that allows lenders to spend less time logging into VA systems and uploading documents, and more time providing Veterans with better, more personalized service.
The Pre-Close API is an optional tool allowing lenders to submit loan data and obtain feedback on the funding fee amount and loan conformance to important aspects of VA policy. The Pre-Close API can result in fewer late-breaking funding fee or other closing cost changes for the Veteran and lender, and allowing them to close with increased confidence.
The Guaranty Remittance API enables lenders to submit a closed loan for guaranty, allowing VA to evaluate the final closing disclosure and baseline loan information and provide feedback on VA policy conformance, calculate the appropriate funding fee amount, and return the Loan Guaranty Certificate (LGC) through the lender’s Loan Origination System (LOS). The API performs a series of checks which compare the data being submitted against data that was previously submitted when the appraisal was ordered. The funding fee will be calculated, payment remittance process through pay.gov initiated, and the LGC generated.
The Eligibility API provides the ability to obtain a Veteran’s Certificate of Eligibility (COE) and early feedback on the loan. Implementing the Eligibility API can result in dramatically reducing manual data entry, while providing a preview of underwriting advice and the projected funding fee.
The Appraisal API provides the ability for a lender to order and manage their appraisals, enabling automated updates on appraisal status. Implementing the Appraisal API can result in lower costs, more automation and earlier establishment of the case and loan parameters within LGY.
The Automated Underwriting System API provides the ability for a lender to receive practical, action-orientated underwriting recommendations. Implementing the Automated Underwriting System API can result in a faster automated underwriting process.
The Partner Test Environment (PINT) is an essential component of our Transformation Strategy that will be used by partners to validate API request, XML files, understand business rules, and complete end- to -end testing.
1. Familiarize yourself with the API documentation
2. Request your API test credentials
3. Begin testing
Loan Review testing is available as of December 5, 2022.
Pre-Close beta testing is available as of September 19, 2023.
Hours of availability: Daily, between the hours of 8:00AM and 8:00 PM EST
Monthly Maintenance will occur per the schedule below and availability will be reduced to 8:00AM – 6:00PM EST on these days:
All questions concerning VA transformation efforts, including Partner Test Enviroment, should be submitted to the LGY Help Center
Section navigation: Loan Review, Pre-Close ,and Guaranty Remittance
The Loan Review API is a part of the Department of Veterans Affairs (VA) Loan Guaranty Service (LGY) technology transformation strategy to eliminate manual data entry, improve data integrity, and streamline VA home loan processes. It will provide lenders an automated way to submit to VA for review Full File Loan Review (FFLR) documents, the Uniform Closing Dataset (UCD), and the Uniform Loan Application Dataset (ULAD).
Yes, loans selected for FFLR on or after November 4, 2024, must have FFLR documents submitted using the Loan Review API.
Per Circular 26-24-13, use of the Loan Review API to transmit Full File Loan Review (FFLR) documents to VA is required for all loans selected for a FFLR on or after November 4, 2024. As of this date, LGY will no longer accept files received via manual upload to WebLGY Correspondence in response to an FFLR request. Failure to comply could result in a lender’s inability to make VA loans.
The steps required to manually upload UCD and ULAD files, for loans that have been selected for full file loan review (FFLR) are explained in detail in the following document and can be followed until November 4, 2024, (UCD/ULAD Upload Quick Steps)
Yes, there is a 100 MB file limit for files uploaded via LGY APIs.
The use of the Loan Review API will allow a lender to stay in their LOS, reducing the time it takes a lender to gather and submit the loan review documents.
No, the Loan Review API does not reduce or change the required documents to be submitted to VA for review.
LGY is requesting the latest version of the Uniform Closing Disclosure (UCD), including any post-close adjustments or re-disclosures. For instance, if there is an update to fees and the UCD changes from the one at closing, LGY would like the updated UCD representing the updated fees.
The Loan Review API will accept MISMO version 3.3 of the UCD. As the closing dataset evolves, the API will evolve to ensure it remains compatible with updates to the UCD.
LGY is requesting the latest version of the Uniform Loan Application Dataset (ULAD), including any post-close adjustments or re-disclosures.
The Loan Review API will accept version 3.4 of the ULAD. As the loan application dataset evolves, the API will evolve to ensure it remains compatible with updates to the ULAD.
LGY APIs can process UCD and ULAD datasets with embedded PDF documents. However, the embedded PDF documents will be ignored by LGY APIs, LGY will review the PDF documents in the merged FFLR stacking order.
LGY APIs can process UCD and ULAD datasets that include the base MISMO schema and, in some cases, extensions. In that case, the base MISMO schema will be processed, and extensions will be ignored. LGY cannot accept the Freddie Mac/LPA version of the ULAD as it results in schema validation errors.
LGY asks that you follow the GSE UCD Phase 3 Critical Edits and use a valid MISMO Fee Type wherever applicable.
The data from the submission of the UCD and ULAD will be extracted to improve data integrity and streamline the FFLR process for VA Loan Specialists.
Loan Review API is available for use now and will be required for FFLR requests on or after November 4, 2024. Lenders can submit FFLR documents, the UCD, and ULAD to VA via the Loan Review API as soon as the technology has been implemented within their Loan Origination System (LOS) or a corresponding proprietary integration.
Begin discussions with your LOS provider/vendor and regularly visit the Technology Knowledge Center to review API specifications and to remain up to date with announcements.
Begin discussions with your IT department and regularly visit the Technology Knowledge Center to review API specifications and to remain up to date with announcements.
Specifications for the Loan Review API and other VA API information are posted on the VA’s Technology Knowledge Center website to assist lenders and their development teams prepare to use each VA API.
Other information including training, technical developments, and announcements are published on VA’s Technology Knowledge Center website. Please frequently visit VA’s Technology Knowledge Center website to stay up to date on VA’s technology transformation.
All questions concerning VA transformation efforts, including Loan Review API, should be submitted to the LGY Help Center
The Pre-Close API will enable lenders to obtain feedback on the funding fee amount and loan conformance to important aspects of VA policy prior to closing the loan. The API will leverage data in the Uniform Closing Dataset (UCD) and Uniform Loan Application Dataset (ULAD), along with some additional loan information to accomplish this.
No, lenders are not required to use the Pre-Close API. This is an optional tool that will provide lenders with the ability to obtain feedback and make appropriate adjustments prior to closing a loan
The Pre-Close API introduces the opportunity to obtain feedback on the funding fee and VA policy conformance prior to loan closing, allowing lenders to respond to the feedback and close loans with increased confidence. The Pre-Close API can reduce the number of late-breaking changes.
It is important for lenders to understand that using the Pre-Close API is not a guaranty. Although this tool will provide lenders with feedback on the loan, it cannot review a loan for compliance with 100% of VA statutory and regulatory requirements. Lenders are ultimately responsible for ensuring the compliance with relevant statutes and regulations.
Lenders should provide the latest version of the Uniform Closing Disclosure (UCD). If there is an update to fees and the UCD changes prior to closing, the lender should submit the updated UCD representing the updated fees.
The Pre-Close API will accept MISMO version 3.3 of the UCD. As the closing dataset evolves, the API will evolve to ensure it remains compatible with updates to the UCD.
Lenders should provide the latest version of the Uniform Loan Application Dataset (ULAD). If there is an update to application data and the ULAD changes prior to closing, the lender should submit the updated ULAD representing the changes.
The Pre-Close API will accept version 3.4 of the ULAD. As the loan application dataset evolves, the API will evolve to ensure it remains compatible with updates to the ULAD.
LGY APIs can process UCD and ULAD datasets with embedded PDF documents. However, the embedded PDF documents will be ignored by LGY APIs.
LGY APIs can process UCD and ULAD datasets that include the base MISMO schema and, in some cases, extensions. In that case, the base MISMO schema will be processed, and extensions will be ignored. LGY cannot accept the Freddie Mac/LPA version of the ULAD as it results in schema validation errors.
LGY asks that you follow the GSE UCD Phase 3 Critical Edits and use a valid MISMO Fee Type wherever applicable.
A beta version of the Pre-Close API is available for testing in the partner testing environment now. This version covers pre-close feedback on single and two borrower purchase loans. Updated versions are expected to cover multiple borrower purchase loans, Interest Rate Reduction Refinancing Loans (IRRRLs), and Cash-out Refinance loans.
Lenders can execute Pre-Close API testing as soon as the technology has been implemented within their Loan Origination System (LOS) in a test instance.
Begin discussions with your LOS provider/vendor and regularly visit the Technology Knowledge Center to review API specifications and to remain up to date with announcements.
Begin discussions with your IT department and regularly visit the Technology Knowledge Center to review API specifications and to remain up to date with announcements.
Specifications for the Pre-Close API and other VA API information are posted on the VA’s Technology Knowledge Center website to assist lenders and their development teams prepare to use each VA API.
Other information including training, technical developments, and announcements are published on VA’s Technology Knowledge Center website. Please frequently visit VA’s Technology Knowledge Center website to stay up to date on VA’s technology transformation.
All questions concerning VA transformation efforts, including the Pre-Close API, should be submitted to the LGY Help Center.
Help Center
The Guaranty Remittance API will enable lenders to automate the processes of remitting the funding fee and obtaining the loan guaranty certificate for a VA loan. The API will leverage data in the Uniform Closing Dataset (UCD) and Uniform Loan Application Dataset (ULAD) to accomplish this.
Guaranty Remittance will leverage the Uniform Closing Dataset (UCD) and Uniform Loan Application Dataset (ULAD) to reduce manual entry required to remit the funding fee and obtain the loan guaranty certificate. Manually reporting a loan for guaranty can take between 5-15 minutes today. Using the Guaranty Remittance API, lenders will do this in as little as 30 seconds, leveraging the scale and speed of automation. Loan feedback will be made available to help lenders resolve common issues and errors.
Please continue to leverage the bulk process for remittance of the funding fee. Once the Guaranty Remittance API is live, the process of remitting the funding fee and obtaining the loan guaranty certificate will be migrated to the API and the bulk CPU process will be decommissioned.
Lenders will be required to provide the following data sets: ULAD, UCD; and information from VA Forms 26-1820 and 26-6393.
Yes. The new solution will leverage the Uniform Closing Dataset (UCD) and the Uniform Loan Application Dataset (ULAD) to bring efficiencies to the process of remitting the funding fee and obtaining the loan guaranty certificate.
The Guaranty API will accept version 3.3 of the Uniform Closing Dataset (UCD). As the closing dataset evolves, the API will evolve to ensure it remains compatible with updates to the UCD.
The Guaranty API will accept version 3.4 of the Uniform Loan Application Dataset (ULAD). As the loan application dataset evolves, the API will evolve to ensure it remains compatible with updates to the ULAD.
LGY APIs can process UCD and ULAD datasets with embedded PDF documents. However, the embedded PDF documents will be ignored by LGY APIs.
LGY APIs can process UCD and ULAD datasets that include the base MISMO schema and, in some cases, extensions. In that case, the base MISMO schema will be processed, and extensions will be ignored. LGY cannot accept the Freddie Mac/LPA version of the ULAD as it results in schema validation errors.
LGY asks that you follow the GSE UCD Phase 3 Critical Edits and use a valid MISMO Fee Type wherever applicable.
Begin discussions with your loan origination system provider/vendor and regularly visit the Technology Knowledge Center to review API specifications and to remain up to date with announcements
Begin discussions with your IT department and regularly visit the Technology Knowledge Center to review API specifications and to remain up to date with announcements.
Currently, VA will not require lenders to use the Guaranty Remittance API to remit the funding fee, report a guaranteed loan, and request a Loan Guaranty Certificate. However, VA is exploring whether to propose regulatory changes that would mandate lenders to use APIs when providing certain required information. Any proposed rulemaking would be published in the Federal Register and open to comment from the public.
All questions concerning VA transformation efforts, including Guaranty Remittance API, should be submitted to the LGY Help Center
