- What changed: Automated COE submission fix and clearer Eligibility API guidance for COE and early underwriting feedback.
- Why it matters: Faster eligibility decisions, less manual data entry, and smoother lender integrations that shorten timelines.
- Related shifts: Loan Review API is now required for FFLR files; LGY Hub replaced VIP and requires two-factor authentication.
- Who benefits: Veterans get quicker responses; lenders gain cleaner pipelines and fewer handoffs between systems and staff.
Does 25.4.2 change how lenders request a COE?
Yes. The fix re-enabled Automated COE submissions, allowing lenders to submit applications directly without workaround steps.
What does the Eligibility API provide now?
It supports COE retrieval plus early underwriting feedback and a projected funding fee, helping lenders spot issues earlier.
Do lenders need anything new to comply?
Use LGY Hub with two-factor authentication and transmit FFLR files via the Loan Review API instead of manual uploads.
Key Takeaways
- LGY 25.4.2 fixed Automated COE submissions, restoring lender ability to submit COE applications quickly and reliably.
- Eligibility API gives lenders COE retrieval and early underwriting feedback, reducing manual entry and duplicate data.
- Loan Review API became mandatory for FFLR documents, replacing manual uploads and tightening post-close compliance workflows.
- VASP program wound down May 2026, ending new submissions and transitioning servicers back to traditional options.
- LGY Hub replaced VIP portal and requires two-factor authentication, standardizing secure access for lenders and partners.
- Data security improved in 25.4.0, restricting SSN searches to exact matches, lowering misdirected eligibility exposures.
Explore VA COE Resources
These articles answer the most common questions Veterans ask about Certificates of Eligibility and VA loans.- VA Certificate of Eligibility (COE): The Complete Guide — Understand eligibility, entitlement, required documents, and lender retrieval steps for your VA Certificate of Eligibility.
- Do You Need a COE Before Getting Pre-Approved for a VA Loan? — Learn if a COE is required before pre-approval and how timing affects underwriting.
- How Long Does It Take to Get a VA COE? — Compare instant electronic retrieval with manual reviews, and see timelines by service type and application method.
- Does a VA COE Expire, and When Should You Reapply? — Clarify COE validity versus pre-approval expirations, and know when reapplying or updating details is necessary.
- VA COE Denials and Delays: Causes and How to Fix Them — Troubleshoot missing records, entitlement conflicts, identity mismatches, and spouse documentation issues that cause processing delays.
VA’s Loan Guaranty Service is moving decisively toward an API-first ecosystem. Release 25.4.2, deployed March 17, 2026, restored the intended Automated COE submission path, removing a blocker that forced workarounds. The VA also refreshed public guidance for its Eligibility API, which enables direct COE retrieval with early underwriting feedback. These changes, combined with mandatory Loan Review API usage and the long-planned transition to LGY Hub with multi-factor authentication, aim to shorten cycle times and raise data integrity across lenders and VA operations.
What did LGY 25.4.2 change for Automated COE?
LGY 25.4.2 ensured lenders can submit Certificate of Eligibility applications from the Automated COE screen, targeting faster intake and fewer failed transmissions. VA described the fix and deployment timing in its March 2026 external release notes (LGY 25.4.2 Release Notes).
- Automated COE submissions now follow the designed path, eliminating redundant entry and reducing queue congestion that previously delayed initial eligibility determinations across high-volume lender pipelines.
- Stability at the first eligibility step reduces downstream rekeying and exception handling, improving throughput to disclosures, appraisal ordering, and pre-underwriting file reviews performed by distributed lender operations teams.
- VA staff benefit from cleaner intake data and fewer duplicate artifacts, which allows technicians to focus on exceptions that legitimately require adjudication rather than repetitive transmission errors or partial records.
What did LGY 25.4.0 improve before that?
The February 2026 release tightened SSN search precision so eligibility searches return only the associated record, improving privacy and accuracy. VA recorded the behavior change in its external notes (LGY 25.4.0 Release Notes).
- Restricting SSN lookups to a single associated record reduces misdirected results, mitigating accidental exposure of unrelated Veteran eligibility data during lender and servicer workflows.
- Cleaner search results minimize file splits and unnecessary manual reviews, which in turn decreases the probability of late-file corrections that complicate funding-fee calculations and post-close verifications.
- By curbing false positives at search, the release reduces data reconciliation steps, improving overall quality for downstream functions such as case assignment, guaranty remittance, and compliance checks.
What does the Eligibility API deliver to lenders?
The Eligibility API enables direct COE retrieval and returns early policy feedback, including a projected funding fee, minimizing rekeying and late surprises. VA’s Transformation Hub explains the capability and intended benefits (VA Transformation Hub – Eligibility API).
- COE retrieval integrates with loan origination systems to populate eligibility data automatically, removing manual entry and improving audit trails for future loan review and quality assurance examinations.
- Early underwriting feedback surfaces potential policy issues and expected funding-fee amounts, enabling proactive cures before disclosures finalize and borrowers lock rate terms or schedule appraisals.
- Standardized payloads align with industry datasets, supporting consistent field mapping and more deterministic error handling across partner integrations and lender technology stacks.
Why is the Loan Review API now required for FFLR?
For loans selected for Full File Loan Review on or after November 4, 2026, lenders must transmit documents via the Loan Review API. VA’s dedicated page and Circular 26-24-13 document the requirement (Loan Review – VA; Circular 26-24-13).
- API submission standardizes stacking order and completeness, reducing manual uploads that fragment files and complicate the chain of custody during post-close auditing and guaranty issuance reviews.
- Automated delivery improves timeliness for VA reviewers, lowering exception rates and clarifying responsibilities among lender compliance, closing, and post-closing teams managing parallel audit workflows.
- Uniform transmission of UCD, ULAD, and supporting documents provides a consistent baseline for analytics, enabling VA to spot systemic defects and communicate targeted corrective actions to lenders.
What changed with the VASP program?
VA ended new Servicing Purchase submissions in spring 2026 and outlined wind-down procedures. The closeout FAQs and Circular 26-25-02 summarize dates and obligations (VASP Closeout FAQs; Circular 26-25-02).
- Servicers discontinued new VASP submissions while certain trial payment plans continued temporarily, with clear deadlines and documentation standards governing final purchases and reconciliations.
- Wind-down guidance directed servicers back to traditional relief options, requiring process adjustments within loss-mitigation teams and updates to internal policy manuals and borrower communications.
- The change rebalanced staff focus toward core guaranty operations, ensuring resources supported stable servicing outcomes beyond the extraordinary conditions that originally justified VASP’s introduction.
What is the status of LGY Hub and two-factor authentication?
LGY Hub is the current entry point for Loan Guaranty applications and requires two-factor authentication through AccessVA/ID.me, replacing the legacy VIP portal (LGY Hub Transition).
- Centralized access with two-factor authentication strengthens identity assurance, aligning with a zero-trust posture and reducing credential risks across lender users and third-party technology providers.
- Role-based permissions and periodic account reviews are necessary housekeeping steps; inactive or unverified accounts are subject to deactivation under published VA guidance and help resources.
- ServiceNow support routes integration and operations issues through a single channel, providing consistent tracking and quicker resolution for production-impacting incidents and onboarding requests.
How do the VA APIs fit across the loan lifecycle?
LGY is assembling complementary APIs for each stage: Eligibility for COE and policy feedback, optional Pre-Close for conformance checks, Guaranty Remittance for funding-fee payments and LGC issuance, and Loan Review for post-close audits (Pre-Close API; Guaranty Remittance API).
- Eligibility initiates decisions with machine-readable responses, helping lenders shape disclosures and identify exceptions before the file advances to underwriting or appraisal ordering milestones.
- Pre-Close can validate conformance and funding-fee amounts before closing documents finalize, cutting last-minute changes that disrupt payments, disclosures, or borrower cash-to-close calculations.
- Guaranty Remittance automates funding-fee remittance and LGC return, improving reconciliation speed and creating a complete digital audit trail from application through guaranty issuance and servicing.
How should lenders prepare LOS integrations?
Lenders should request Partner Test Environment access, align payloads to VA datasets, test end-to-end, and train staff on 2FA, permissions, and exception handling before promoting to production. VA’s Technology Knowledge Center and lender resources outline the process (Technology Knowledge Center).
- Secure sandbox credentials for lender and technology-provider accounts, then configure service users, callback endpoints, and logging so integration failures are observable and quickly actionable.
- Map LOS fields to Eligibility and Loan Review schemas; adopt deterministic error handling to translate VA messages into clear, fixable tasks for disclosure, processing, and underwriting teams.
- Plan a staged rollout with tight change control, defined rollback criteria, and targeted training that reflects real scenarios rather than generic demonstrations or vendor marketing materials.
What does this mean for Veterans and timelines?
Faster, reliable COE submissions accelerate first-step decisions and reduce rescinds. VA’s status page describes typical contact goals for COE requests and cautions against duplicate submissions while under review (COE Status – VA.gov).
- Earlier clarity on eligibility and funding-fee expectations helps buyers write stronger offers with confidence, improving contract coordination among lenders, agents, and appraisal scheduling teams.
- Reduced manual handoffs create steadier communication, so Veterans receive consistent answers despite staffing differences between daytime processors, evening support teams, and distributed underwriting groups.
- Cleaner data and standardized submissions lessen late-file corrections that can trigger closing delays, re-disclosures, or funding-fee adjustments after borrowers have locked their rate terms.
What recent LGY changes should teams track?
| Date | Release / Change | Summary | Who is impacted |
|---|---|---|---|
| Nov 4, 2024 | Loan Review API requirement | FFLR documents must be transmitted via API; manual WebLGY uploads no longer accepted (VA Loan Review). | Lenders; post-close teams |
| Feb 2026 | LGY 25.4.0 | SSN search returns only the associated eligibility record (25.4.0 Notes). | Lenders; VA staff |
| Mar 2026 | LGY 25.4.2 | Automated COE submission fix restores intended workflow (25.4.2 Notes). | Lenders; Veterans |
| May 2026 | Eligibility API page refresh | COE retrieval and early feedback emphasized (Transformation Hub). | Lenders; providers |
| May 2026 | VASP wind-down | Program closeout and key dates published (VASP FAQs). | Servicers |
| Ongoing | LGY Hub transition | VIP decommissioned; AccessVA/ID.me two-factor required (LGY Hub Transition). | All LGY users |
How should teams implement the Eligibility API and Automated COE quickly?
- Audit LGY Hub access and enforce two-factor authentication across all roles, removing inactive accounts and validating least-privilege permissions for processors, underwriters, closers, and administrators.
- Secure sandbox credentials, configure service users, and stand up reliable callback endpoints with structured logging so integration exceptions surface immediately, not days later during production incidents.
- Map LOS fields to Eligibility responses and Loan Review schemas; document error codes and create playbooks so operations staff resolve issues without escalating routine, predictable cases.
- Test Automated COE end-to-end, confirming stability after 25.4.2, then scale pilots to multiple branches to capture environment differences before broad production enablement across regions.
- Cut over FFLR to the Loan Review API per Circular 26-24-13, validating UCD, ULAD, and LR file delivery, reconciliation, and downstream reporting for audit readiness.
- Promote with change control and monitor results, scheduling targeted training that mirrors real loan files, including edge cases that previously triggered rescinds or post-close findings.
The Bottom Line
LGY 25.4.2 restores speed and reliability at the very start of VA lending by fixing Automated COE submissions. The refreshed Eligibility API guidance, mandatory Loan Review API, and LGY Hub’s two-factor authentication point in the same direction: standardized data, fewer manual uploads, and earlier, clearer feedback. Veterans benefit through faster decisions and fewer last-minute changes. Lenders benefit through predictable pipelines and better auditability. The work ahead is disciplined integration, proactive staff training, and vigilant monitoring as VA continues modernizing critical loan processes.
Citations Used
- VA LGY 25.4.2 External Release Notes
- VA LGY 25.4.0 External Release Notes
- Loan Review API Requirement (FFLR)
- Circular 26-24-13 (FFLR API Mandate)
- VASP Program Closeout FAQs
- Circular 26-25-02 (VASP Wind-down)
- LGY Hub Transition and Two-Factor Authentication
- Transformation Hub – Eligibility API Overview
- Pre-Close API Overview
- Guaranty Remittance API Overview
- COE Status and Contact Expectations
Frequently Asked Questions
Does LGY 25.4.2 change what documents lenders need for COE?
No. It fixes the submission path, not documentation requirements. Lenders still collect evidence consistent with policy; the change restores the intended automated transmission route for faster intake.
Is the Eligibility API required to originate VA loans?
No. It is strongly encouraged for efficiency and early feedback. The mandatory requirement applies to Loan Review API for FFLR selections, which replaced manual uploads beginning November 2026.
What’s the benefit of the Pre-Close API if it’s optional?
It surfaces conformance and funding-fee issues before closing, reducing last-minute changes. Teams often see smoother signings and fewer redisclosures when they validate earlier in the process.
How do we access LGY systems after VIP?
Use LGY Hub with two-factor authentication through AccessVA/ID.me. Ensure accounts are current, roles are scoped correctly, and inactive credentials are removed under published guidance.
Did VA end the VASP program for good?
Yes. New submissions stopped in 2026 according to VA’s closeout guidance. Certain active trials continued briefly, then servicers returned to standard options defined in the Servicer Handbook.
What happens if we don’t use the Loan Review API?
For selected loans, non-compliance can jeopardize program participation. The API ensures uniform submission of UCD, ULAD, and LR files with better auditability and timeliness.
How quickly does VA process a COE request?
Timelines vary by case. VA’s status page outlines typical contact goals and discourages duplicate submissions while a request is under review to prevent delays and confusion.
Do these updates replace human underwriters?
No. APIs provide earlier data and policy feedback, but underwriters still make final decisions. The intent is fewer surprises, clearer files, and quicker, higher-quality approvals.
The VA Loan Network Editorial Team is comprised of dedicated mortgage specialists and financial writers committed to providing veterans and service members with accurate, up-to-date information on VA loan benefits, eligibility, and the home-buying process.
