EFTPS now requires multifactor authentication for system access, so each staff member who signs in needs a personal login and a second factor. Protecting federal tax payments takes a pair of controls: MFA on every login, and a named supervisor who decides which staff member may send a client payment and checks that it went out. The sections below explain both, how several enrollments change the picture, and how to plan for outages.
Chief takeaways
- EFTPS requires MFA for every system access, so a practical way to meet it is a personal login and an individual second factor rather than a shared credential.
- Two recommended controls for staff access: MFA on each login, as required, and a named supervisor your firm appoints to decide who may send payments and verify afterward that the correct payment went out.
- The EFTPS site raises multiple enrollments as a question to settle, so list each enrollment a staff member needs, the reason, and who approved it before granting access.
- Your tax payment is due regardless of the website's availability, so plan an early internal send date and keep a second authorized payer with tested access.
Why EFTPS now requires MFA
Before you decide who on your team gets access, it helps to understand why the login has changed. The EFTPS home page says its new authentication process supports Executive Order 14028, which requires all federal agency applications to implement multifactor authentication, or MFA.
The EFTPS page says its authentication supports that order, and the order covers federal agency applications. EFTPS states that Fiscal Service requires MFA for system access.
MFA is a login method that asks for more than one kind of proof. A password is one kind. A code from an approved device or app is another. Using both means a stolen password alone does not open a client's payment account.
For a partner or operations lead, the practical effect is that login access and payment authority become separate questions. A firm might once have issued one shared credential and trusted staff to use it carefully. Under MFA, each user needs a login of their own and a second factor that proves who is signing in. Each sign-in can then be tied to one person, which is the only way a firm can later answer the question "who sent that payment?"
What the MFA rule means for staff logins
Fiscal Service requires MFA for system access. That sentence sets the scope. It covers system access in general, which means every sign-in path to EFTPS, not only the first login of the week. Read this way, the rule applies to each person who logs in, not to the firm as a whole.
Start with the device. A factor only works if the staff member can reach it. If the second factor is a phone that is lost, on leave, or shared with the rest of the office, that person cannot log in until the factor is restored. Decide in advance who can reset a factor and how quickly that can happen, so a lost phone does not become a payment problem.
Next, consider shared logins. An office that once let three people use one EFTPS credential now has to split it into separate personal logins, each with its own factor. A shared password with no individual factor does not meet a requirement stated for system access, so the shared credential has to go. Most of the work is deciding who should hold each login, not creating the logins themselves.
Then consider location. Staff who log in from home, from a client site, or from a shared computer all fall under the same system access rule. Your staff policy should state which devices may hold a factor and whether a personal phone is allowed. Many firms find it easier to answer that once, in writing, than to answer it case by case when someone is locked out.
Finally, document each setup. Record who holds each login, which factor they use, and when the login was issued. That record becomes the baseline for the review you run whenever staff change roles. Without it, you will be reconstructing history on the day someone asks what happened.
What supervisor duty looks like
The second control is less technical than the first. A named partner or manager decides which staff member may send a payment, and checks afterward that the right payment went out. Duties like this are easy to describe and easy to skip, so it helps to see how another profession has written them down.
Pennsylvania's rules for lawyers offer a useful parallel, though they bind lawyers, not tax staff, and nothing here is a legal standard for EFTPS. The supervision rule says that a lawyer with direct supervisory authority over another lawyer "shall make reasonable efforts to ensure that the other lawyer conforms to the Rules of Professional Conduct" ( Pennsylvania Code & Bulletin). The accompanying commentary adds that the duty attaches to people with real authority: "Paragraph (a) applies to lawyers who have managerial authority over the professional work of a firm."
Another comment notes that a supervisor can fall short of the duty even when the underlying misconduct was not the supervisor's own. For a tax office, the lesson is the same. The duty sits with the people who hold authority, and it has to be specific enough that someone can check it.
For EFTPS, the translation is direct. Name the supervisor. State what that person must check, such as which client a payment belongs to and whether the amount matches the plan. Record that the check happened. A supervisor who approves in principle but never looks at the log has not done the job.
Logging in with multiple enrollments
The EFTPS site asks: "How do I authenticate if I need to access multiple EFTPS enrollments?" The EFTPS site asks this question, so multiple enrollments are worth settling as their own question before setup. A firm with many clients may hold several enrollments, and a staff member who works across them needs that case settled before setup.
Use the table to match each access case to the requirement behind it and the step to take.
| Access case | What the requirement says | Planning step |
|---|---|---|
| Standard system access | MFA is required for system access | Give each user a personal login and a factor that works |
| Multiple enrollments | The question is raised as a separate case | List every enrollment a staff member needs before granting access |
| Executive order basis | The federal order behind the change | Write the MFA requirement into staff policy as a fixed rule |
Before you grant anyone access to more than one enrollment, write down the enrollments that person needs, the reason each is needed, and who approved it. Keep the list short. A staff member who pays for three clients should not have a login that reaches thirty. The list also gives you a checkpoint: when assignments change, you compare the new need against the written list instead of relying on memory.
Work through the multiple-enrollment case during setup, not on payment day, so the answer is in place before a deadline arrives. If you cannot answer the question for a particular enrollment, do not grant access to it yet. Raise it with the system's operators first.
Comparing one login with several enrollments
This article frames two common cases side by side: a staff member with one enrollment and a staff member with several. MFA for system access applies to both. The second pattern adds the enrollment question covered above. The table compares the two on the measures that matter when you assign access.
| Measure | One enrollment | Several enrollments |
|---|---|---|
| Authentication basis | MFA for system access | MFA for system access, plus the enrollment question covered above |
| Setup work | One personal login and one factor | One personal login, with each enrollment mapped before access |
| Review frequency | When the person's client list changes | Each time an enrollment is added, removed, or reassigned |
| Main exposure | A credential shared or left signed in | Access reaching accounts the person should not touch |
The single-enrollment case is simpler to set up. Its main risk is the one every login carries: a credential shared or left signed in. The multiple-enrollment case is harder to set up and review, and its main exposure is breadth. A payer who can reach many enrollments can send many payments, so the list should be the smallest set the job requires.
When you compare the two patterns, think about the person rather than the account. A bookkeeper who handles one client's deposits faces a narrow decision. A manager who can reach many enrollments faces a wide one, and every additional enrollment should earn its place on the list.
Planning around site outages
Deadlines do not wait for software. The payment rule is stated plainly: "Please note: Your tax payment is due regardless of this Web site's availability." A payment deadline does not move because the website is down. That makes outage planning a deadline question, not a convenience question.
| Situation | Deadline effect | Planning response |
|---|---|---|
| Website unavailable several days before the deadline | Payment still due on its scheduled date | Start the payment early enough to absorb a delay |
| Website unavailable on the due date | Payment still due that day | Send the payment early, retry the site, and record each attempt and the outage |
| Website back up after an outage | Payment still due at the original time | Send the payment as soon as access returns and record the outage |
Outage planning also tells you which staff belong on the access list. If the only person with working MFA is out on a due date that falls during an outage, the firm cannot pay on time. A second authorized person with a tested factor is therefore part of the outage plan, not an extra. Test that person's login before the deadline, when nothing depends on it.
Decide what counts as an outage. A slow site and a site that refuses logins call for different responses, so write down which one triggers the backup.
Set the outage plan before the first payment of each cycle. Write down who checks whether the site is up, who makes the call to pay early or wait, and who sends the payment once access returns. A plan written on the due date tends to be made under pressure, so keep these steps in the same document as the access list, and review both together.
Which one should you pick?
The central choice for most firms is how many people hold EFTPS payment access. The rules of thumb below follow from the MFA requirement and the enrollment question:
- If you are a small firm with one bookkeeper, pick one named payer and one tested backup, because a single factor can otherwise stop every payment and the backup protects the due date.
- If you are a firm with many client enrollments, pick a payer limited to the enrollments that person needs, because a wider login widens what one person can send. Multiple enrollments are their own case.
- If you are an operations lead who handles staff turnover, pick a short written list for each staff member, because it lets you compare each new assignment against what that person already holds.
Choose the smallest set of payers that still covers the deadline. One payer and one backup covers most small offices. Larger firms need more payers, but each added login should have its own factor and its own enrollment list. Too few payers leaves the firm exposed to a single absence. Too many spreads access thin and makes review harder.
Setting up staff access step by step
Setup is where the two controls meet. The MFA requirement decides how each login must work, and the supervisor decides who should hold one. The steps below put both into practice.
- List the people who need access. Write each name beside the reason. Leave off anyone who only needs to see payment confirmations.
- Issue one personal login per person. A shared login makes it hard to show that each sign-in has its own second factor.
- Register a second factor for each login. Confirm that the factor works on the device the person will actually use.
- Test the payment path before a deadline. Have each payer sign in, check what the login can reach, and confirm that the backup can do the same.
| Setup step | What to check before moving on | Basis for the step |
|---|---|---|
| Personal login | Each user signs in with credentials that belong to that user | MFA for system access |
| Second factor | The factor works on the device the person uses | MFA for system access |
| Written policy | Staff policy states MFA as a fixed rule | The federal order behind the change |
Setup is the cheapest moment to fix a gap. A login that is wrong on day one is easy to correct. The same error discovered on a due date is expensive.
Keep a record of when each login was issued and which factor it uses. You will need that record in the later steps, when access changes.
Choosing who holds EFTPS access
The EFTPS source poses the multiple-enrollment question without giving a rule for it. Check your case with the system directly before you grant anyone more than one enrollment.
Choosing holders means naming roles, not only people. The table compares three roles a firm commonly needs.
| Role | Access it needs | Risk if the role is empty |
|---|---|---|
| Primary payer | Personal login, tested factor, enrollments for assigned clients | No one sends payments on a normal cycle |
| Backup payer | Personal login, tested factor, the same enrollments as the primary | A missed due date if the primary is out or locked out |
| Approving partner | Reviews who holds each login; no payment access by default | Access grows without anyone deciding it should |
Keep the payer list short. Each added payer should have a reason on the record, a personal login, and a factor that works. A firm with one bookkeeper may need only a primary and a backup. A firm with several staff who share client work will need to decide how many people can reach each enrollment, and write the answer down.
Tracking who can pay and when
Tracking has to cover two things: who can pay, and the calendar on which they must act. A due date that falls during an outage still needs a named person and an internal send date.
Build one log with these columns: staff name, enrollments held, type of second factor, date the login was issued, the supervisor who approved it, and the date it was last tested. Update the log whenever anything changes. For the calendar, record each due date your firm pays against and set an internal send date earlier than it. The internal date is your own margin. The requirement does not set it for you, but the due date holds even when the site is unavailable, so the margin is what protects you.
Assign a named supervisor to check the log against the payments actually sent. That check is the second control. The MFA requirement shows who signed in, and the supervisor's review shows whether the payment was the one the firm meant to make.
Reviewing access after a staff change
When someone changes roles or leaves, the access list has to change with them. Because access runs through each person's own login and factor, that person's access should end when their role ends. Make the change on the day the role changes, not at the next review. A login left open between jobs is exactly the exposure this guide is meant to close.
Work through these steps in order:
- Remove the person's enrollments from their login.
- Disable or reassign their second factor so it cannot be used.
- Confirm that the backup payer can still sign in and reach the enrollments they need.
- Update the log with the change and the date.
- Have the supervisor sign off on the revised list.
Do not hand a departing person's login to a replacement. The replacement should receive a personal login and a factor of their own. This keeps each sign-in traceable to one person, which is the point of the MFA requirement.
Keeping the payment deadline in view
A site problem does not move the deadline, so a plan for a slow or down site must be ready before the deadline arrives. Put the calendar where the team can see it, and check it at an interval you set.
Set the internal send date early enough that a delay still leaves time to pay. If the site is down near the deadline, the first step is to retry the site and record the attempt with its time. The second call goes to the supervisor, who decides whether to keep trying or to escalate. Write both steps into the plan, and record each attempt with its time.
Review the calendar regularly, and check that each upcoming due date has an internal send date and a named payer. A deadline with no owner tends to slip quietly, and the cost of a missed due date falls on the client, not on the person who forgot to assign it.
Related guides: Client data access controls: 4 tools for a firm WISP · Firm authentication mistakes: 6 staff access errors · 2 Arizona withholding start dates for nonresident staff.
Reader questions
Does each staff member need their own EFTPS login? Yes, in practice. MFA applies to system access, and a shared login makes it hard to tie each sign-in to one person. Give each person a login and a second factor of their own.
Why does EFTPS require MFA now? The change follows the federal order that requires MFA for federal applications. EFTPS states that Fiscal Service requires MFA for system access, so staff logins should follow that requirement.
Can one staff member handle several enrollments? The source does not say whether one staff member may hold several enrollments. List each enrollment and its reason, and confirm the case with EFTPS before granting access. Multiple enrollments are a separate access question, so settle it before setup rather than on a payment day.
Can we delay a payment if the website is down? No. The due date stays where it is. Plan for an early send date.
What if the only authorized person is unavailable on the due date? That is the situation a backup exists for. Test the backup's login before the deadline, when nothing depends on it.
Does a supervisor have to approve each payment? Nothing in the requirements discussed here sets that rule. Approval is a choice your firm makes. One option is a supervisor review of the log instead of approving each payment.
Where can we get help with other tax issues? The Internal Revenue Service says: "Click the Help link on IRS.gov for help with many tax issues."