Codify — Article

Federal Loan Systems Modernization Act of 2026 creates Lending.gov shared platform

Authorizes GSA-led shared services platform to centralize federal loan processing, set government-wide loan management standards, and fund operations through interagency agreements and a capped remittance fee.

The Brief

The bill authorizes the creation of a centralized shared-services platform, branded Lending.gov, to consolidate loan application intake and loan management functions across Federal loan programs and to adopt commercially available loan processing software. It directs the General Services Administration to propose an operational plan and designates a lead agency to serve as the initial Provider and operational host.

Why it matters: the measure replaces a patchwork of legacy systems with a single government-managed service layer, creates government-wide standards for loan management, and establishes a financing approach for ongoing operations. For agencies and compliance officers this means new interagency agreements, service-level commitments, and a structured migration process that will change where and how loan data and servicing functions are executed.

At a Glance

What It Does

The bill requires GSA to deliver a plan to OMB and Congress to stand up Lending.gov using commercial loan-management software and to designate an initial Provider that will operate and continuously improve the platform. It sets agency migration deadlines, establishes performance reporting and satisfaction surveys, and authorizes a marketplace of additional Providers if efficiencies warrant.

Who It Affects

Affected parties include the General Services Administration, the Office of Management and Budget, agencies that administer federal loan or loan guarantee programs (especially those originating or servicing more than 50 loans per year or $10 million aggregate), commercial loan-technology vendors, and borrowers who will use a single portal. Program managers and financial officers will have new oversight and reporting responsibilities tied to platform performance.

Why It Matters

The bill creates government-wide technical and governance standards for federal loan management and codifies data ownership and portability expectations, which vendors and agencies must meet. It also introduces a funding model—interagency reimbursements plus a remittance fee capped at 0.25%—that ties the platform’s sustainability to transaction volume and agency buy-in.

More articles like this one.

A weekly email with all the latest developments on this topic.

Unsubscribe anytime.

What This Bill Actually Does

Within six months of enactment GSA must deliver a detailed plan describing how to build Lending.gov, including which agency will act as the initial operational Provider, what commercial loan-management products will be considered, cost estimates, and a timeline. That plan is the blueprint for consolidation: it must identify common failures caused by legacy systems, recommend procurement approaches under existing acquisition law, and describe how to maintain agency authorities while centralizing administrative functions.

The operational model places day-to-day responsibility on the designated Provider. The Provider must run the portal and underlying systems, onboard agencies, provide technical support, host servicing and portfolio-management tools, maintain auditable financial subledgers, and meet federal cybersecurity, privacy, and cloud requirements.

The statute requires program-manager satisfaction as a key performance standard, mandates annual standardized surveys, public reporting of results consistent with law, and remediation plans if metrics fall short.Migration is structured and time-bound. OMB, working with GSA and the Provider, begins migrations within two years of the plan and generally requires agencies to complete migration within three years of enactment, subject to narrowly defined exceptions.

Migration criteria focus on scale: programs originating or servicing more than 50 loans annually or with aggregate loan amounts above $10 million are presumptively within scope. Exceptions may be granted for up to three years, must be notified to Congress, and trigger a required migration plan from the agency.Oversight and future market design sit with GSA and OMB.

GSA must set government-wide loan-management standards in coordination with OMB and the Federal Credit Policy Council, report annually to Congress on migration status and cost-effectiveness, and may recommend adding up to three additional Providers to create a shared-services marketplace. Any additional Providers must use the public-facing capabilities of the initial Provider to ensure a consistent applicant experience.The bill finances ongoing operations through interagency agreements and an optional remittance fee applied to loans serviced on the Platform.

The Provider may set a remittance fee up to 0.25% of loan face value, subject to consultation with GSA and restrictions on assessing fees on direct loans to individual borrowers unless an agency head certifies there will be no material harm to affordability or program objectives. Collected fees flow into a dedicated fund restricted to platform operations and migration support.

The Five Things You Need to Know

1

GSA must submit a plan to OMB and Congress within six months that designates a lead Provider, proposes commercial loan technology, and estimates costs.

2

Agencies must complete migration of loan-management systems to Lending.gov within three years of enactment, unless OMB grants an exception of up to three years.

3

Programs that originate or service more than 50 loans annually or have aggregate loans above $10 million are presumptively required to migrate to the Platform.

4

The Provider may collect a remittance fee up to 0.25% of the loan face value to fund operations, but fees on direct loans to individual borrowers require a certification showing no material harm to affordability or access.

5

The Provider must ensure customer agencies retain ownership and full access to program data and must support exporting records in standardized, non‑proprietary formats.

Section-by-Section Breakdown

Every bill we cover gets an analysis of its key sections. Expand all ↓

Section 1

Short title

States the Act’s name as the Federal Loan Systems Modernization Act of 2026. This is the reference used in subsequent legal and administrative materials.

Section 2

Definitions

Provides working definitions for key terms used throughout the bill—Administrator (GSA), Director (OMB), Platform (Lending.gov), Provider, loan management, and loan management technology—which set the scope for what functions can be centralized and what tools qualify as commercial solutions.

Section 4

Establishment plan and required elements

Directs GSA to produce a six‑month plan that identifies the initial Provider, catalogs programs for integration in coordination with the Federal Credit Policy Council, documents inefficiencies in existing systems, outlines the operational framework, proposes commercial technology integrations under procurement law, and provides timelines and cost estimates. The plan frames the subsequent migration and procurement actions and is the basis for OMB’s implementation decisions.

4 more sections
Section 5

Provider responsibilities and performance regime

Assigns comprehensive operational duties to the Provider: run and enhance the platform, onboard agencies, provide servicing and portfolio-management tools, maintain auditable financial subledgers, meet cybersecurity and privacy standards, and ensure data portability and agency access. It also makes program-manager satisfaction a primary performance metric, requires annual standardized surveys, public reporting consistent with law, and formal remediation plans for persistent performance shortfalls.

Section 6

Migration schedule, criteria, and exceptions

Sets the migration clock—OMB begins migrations within two years of GSA’s plan; agencies have three years after enactment to move systems unless OMB grants an exception. Migration criteria rely on volume and scale thresholds (more than 50 loans annually or over $10 million aggregate). Exceptions require findings that migration is impracticable, must be reported to Congress, can last no more than three years, and obligate the agency to submit a near‑term migration plan.

Section 7

Oversight and optional marketplace

GSA is charged with government-wide oversight, standard-setting in coordination with OMB and the Federal Credit Policy Council, and annual reporting to Congress on migration status and platform cost-effectiveness. After the initial Provider is established, GSA must assess whether adding up to three additional Providers to create a marketplace would improve services; any additional Providers must use the initial Provider’s public-facing interface to preserve a consistent applicant experience.

Section 8

Financing model and remittance fee

Requires customer agencies to reimburse Provider costs via interagency or service-level agreements and permits the Provider to levy a remittance fee to fund operations—capped at 0.25% of the loan face value unless otherwise authorized. The bill bars routine assessment of this fee on direct loans to individuals unless the agency head certifies there will be no material negative impact on borrower affordability, and it requires collected fees to be held in a dedicated fund restricted to platform operations and migration support.

At scale

This bill is one of many.

Codify tracks hundreds of bills on Government across all five countries.

Explore Government in Codify Search →

Who Benefits and Who Bears the Cost

Every bill creates winners and losers. Here's who stands to gain and who bears the cost.

Who Benefits

  • Borrowers using Federal loan programs — gain a single, government‑operated portal for applications and a standardized customer experience and access to more automated processing tools.
  • Customer agencies and program managers — receive shared operational tools, auditable subledger capabilities, and standardized performance metrics that simplify oversight and reduce the need to maintain bespoke legacy systems.
  • General Services Administration and designated Provider agencies — obtain a central role in federal loan operations and control of a shared services offering that can deliver economies of scale and inform cross‑agency policy.
  • Commercial loan-management vendors — stand to win implementation, integration, and maintenance contracts as agencies procure commercially available platforms adapted for federal use.
  • Congressional appropriations and oversight committees — gain clearer, consolidated reporting on federal loan program operations and cost-effectiveness to inform budgeting and legislative oversight.

Who Bears the Cost

  • Agencies migrating to the Platform — must absorb migration planning, integration work, and potentially change business processes; they also must enter interagency agreements and may pay remittance fees.
  • The Provider and operational host agency — bear operational responsibilities, procurement complexity, and reputational risk tied to platform performance and security compliance.
  • Borrowers of certain loan products — could indirectly bear a portion of ongoing costs if agencies pass on remittance fees where permitted, subject to the statutory certification limit for direct individual loans.
  • Small or specialized loan programs — face compliance and standardization burdens if program-specific requirements conflict with the Platform’s commercial templates.
  • OMB and GSA — assume ongoing oversight, enforcement, and reporting duties that will demand staff time and potentially additional appropriations or reallocation of resources.

Key Issues

The Core Tension

The central dilemma is efficiency through centralization versus fidelity to program‑specific mission and borrower protections: consolidating platforms and adopting commercial software reduces duplication and can lower costs, but it risks imposing one‑size‑fits‑all workflows on legally distinct loan programs and shifting costs in ways that could affect access or affordability.

The bill centralizes administrative loan functions while explicitly preserving agency statutory authorities over program eligibility and policy, but that division creates operational strain: harmonizing commercial loan-management products with unique program rules will require substantial configuration and ongoing exception handling. The statute’s insistence on data ownership and portability mitigates vendor lock‑in risk, yet ensuring seamless export in standardized, non‑proprietary formats may be difficult if commercial vendors resist or if legacy data lack consistent structures.

Funding the platform through remittance fees ties sustainability to loan volume, which aligns incentives but also risks creating pressure to levy charges that could affect borrower affordability or program access. The bill limits fees on direct individual loans without agency certification, but agencies could still choose to assess fees on other products; the net effect on program economics will depend on agency decisions, OMB guidance, and how cost recovery blends with appropriated support.

Finally, the performance regime emphasizes program-manager satisfaction and public reporting, which promotes transparency but may not fully capture borrower outcomes or long-term credit risk implications.

Try it yourself.

Ask a question in plain English, or pick a topic below. Results in seconds.