How to Fill Out and Submit HUD Form 27054E: eLOCCS Access Authorization

HUD Form 27054E is the authorization form that grants an individual user access to the Electronic Line of Credit Control System (eLOCCS), the system HUD uses to disburse grant funds.¹ To complete it, each user needs a HUD Secure Systems ID first, then the user fills in Blocks 1–5, an eligible Approving Official signs Block 6, program areas are listed on attached authorization pages, and the whole package is emailed to your HUD Program Officer — with a notary seal if it’s a new user, reinstatement, or Secure Systems ID change, and within 180 days of the signatures.²

Set Up Secure Systems Access First

The form assumes each person named on it already has a HUD Secure Systems User ID. Block 2a requires one, and the form is rejected without it.² Your organization also needs a designated Secure Systems Coordinator in place, because the coordinator is who retrieves the assigned User ID for new staff after HUD verifies the registration.³

To register, go to the HUD Secure Systems Participant User Registration page and provide your full name, Social Security Number, email, and the organization’s Tax Identification Number. Choose a password that is exactly six characters long using only letters and numbers, and provide your mother’s maiden name for future password resets.⁴

The organization’s Tax ID also has to be registered inside Secure Systems before the 27054E is filed. An unrecognized TIN stops the form from being processed.¹

Pick the Right Function Type in Block 1

Block 1 asks what you’re filing for. The choice controls whether a notary is required, so start here.²

New User — person has never had eLOCCS access. Notary required.
Reinstate User — restores access for someone previously terminated. Notary required.
Change Secure Systems ID — corrects the Secure Systems ID linked to the user in eLOCCS. Notary required.
Terminate User — immediately removes access. No notary.
Add or Remove Program Area(s) — adjusts which grant programs the user can reach. No notary.
Add or Remove Tax-ID Number(s) — updates the organization Tax IDs tied to the user. No notary.
Name/Address Change — updates the user’s name, email, phone, or address. No notary.
Other — for situations that don’t fit the categories above; OCFO Security advises on when to use this option.

Fill In the User Information (Blocks 1–5)

All fields must be typed, not handwritten. Signatures and initials are the only exception.¹ The user completes Blocks 1 through 5; the Approving Official completes Block 6.⁵

Enter the Secure Systems ID in Block 2a. Leave Block 2b blank unless you are correcting a Secure Systems ID that eLOCCS has associated with the user incorrectly. Block 3 collects the user’s full name, office phone, mailing address, and email. Every field in Block 3 must be filled in; a single blank gets the form returned.²

The email address has to contain the applicant’s actual name and match the name registered in Secure Systems. Generic mailboxes like info@organization.org will not be accepted.⁵

Block 4 records the number of authorization pages attached. Block 5 is where the user signs and dates.

Who Can Serve as the Approving Official (Block 6)

The Approving Official vouches for the user’s identity and need for access. They must be the organization’s CEO, a board officer, or someone whose authority sits above the user being authorized. Acting or interim officials are not eligible.¹ The Approving Official cannot approve themselves, and two people holding the same title (co-directors, for example) cannot approve each other.²

Block 6 collects the Approving Official’s name, office phone, title, Secure Systems User ID, office address, and signature with date. Their email must also contain their name, and it cannot be the same as the user’s email.⁵

List the Program Areas (Blocks 9 and 10)

Block 9 specifies which grant programs the user can reach and at what level. For each program area, enter the organization’s Tax ID, the program area code, the program area name, and either Q for query-only or D for drawdown access (drawdown includes query). A link on page 2 of the form itself takes you to the current list of LOCCS program area codes.² If a user needs access across multiple organizations, use Block 10 for the additional ones.

Attach as many authorization pages as needed and put the count in Block 4. Both the Approving Official and the HUD Program Office point of contact should initial each attached page.²

Block 8 Belongs to HUD, Not the Grantee

Block 8 is completed by the HUD Program Officer assigned to your organization, not by anyone on the grantee side. That person must already be registered in LOCCS Web as a user and provides their name, phone, title, User ID, signature, and date.²

Signatures, Notary, and the 180-Day Clock

All signatures must be original, legible, and reflect the signer’s full name.¹ Electronic signatures and DocuSign are now accepted.⁵ The user signs Block 5 and the Approving Official signs Block 6. Blocks 11a, 11b, and 11c collect matching initials and dates from the user, Approving Official, and HUD Program Office.

For a New User, Reinstate User, or Change Secure Systems ID request, a Notary Public has to witness and notarize both signatures and apply a seal. The notary cannot be the user or the Approving Official.² Terminations, program area changes, TIN changes, and address updates do not need a notary.

Watch the timing. The form expires 180 days after the user and Approving Official sign it. If HUD program staff has not submitted it to OCFO Security within that window, the form is invalid and you start over.⁵

How to Submit the Form

Once the form is complete, notarized where required, and signed, email it to the HUD Program Officer assigned to your organization. Both the form’s own instructions and the eLOCCS Registration Guide direct grantees to use secured email.⁵² The Program Officer reviews it and forwards it to OCFO Security.

If you don’t know who your Program Officer is, or your local Program Office cannot resolve an issue, the eLOCCS mailbox is eLOCCS@hud.gov. HUD asks you to try the local Program Office first.¹

Why Forms Come Back

OCFO Security returns a significant share of 27054E submissions. The recurring reasons are worth checking against your draft before you send it:

A blank field anywhere in Block 3.
Generic email addresses like info@safehomes.org; the address has to include the person’s actual name, such as jane.brown@safehomes.org.
The user and Approving Official sharing an email address.
An acting or interim Approving Official, or two same-title people approving each other.
Missing notary seal and signature on a New User, Reinstate User, or Change Secure Systems ID request.
More than 180 days elapsed since the signatures.²

After You’re Approved

Once OCFO Security processes the form, the user is notified at the email address on the form. On first login, the system prompts a password change and setup of security questions. Those questions matter later: if you miss them on a future login, the account is terminated and you have to file a new 27054E to be reinstated.⁵

Staying Active and Recertifying

eLOCCS has a tight inactivity policy. No login within 89 days makes the account inactive; at 90 days it’s suspended. A suspended user can reactivate by answering their security questions correctly at login, but failing them triggers full termination and requires a new 27054E.⁵

Approving Officials recertify their staff inside eLOCCS quarterly.⁵ The 27054E itself is also recertified every six months by the Approving Official as a system-wide security requirement.⁶ Missing recertification can suspend fund access for the whole organization.

Shared logins are prohibited. When someone leaves the organization, file a Terminate User request on Form 27054E right away rather than waiting for the account to lapse on its own.

1
U.S. Department of Housing and Urban Development. eLOCCS Access Guidelines for Business Partners
2
U.S. Department of Housing and Urban Development. HUD Form 27054E eLOCCS Access Form
3
U.S. Department of Housing and Urban Development. Guide to HUD Secure Systems Access
4
U.S. Department of Housing and Urban Development. Participant User Registration
5
U.S. Department of Housing and Urban Development. eLOCCS Registration Guide
6
HUD Exchange. Is Recertification Required Every 6 Months for the Line of Credit Control System