EFFA — Employer FAQ

EFFA is the platform where schools and employers do business. Schools use it to formalize employer partnerships and bill them directly for employee tuition. Employers use it to confirm who's eligible, approve invoices, and see what their education spend is producing. One process, one set of records, every school partnership in one place.

Employer tuition benefits mostly still run on reimbursement — the employee pays out of pocket, submits receipts, and waits to be paid back. That's friction sitting between an employee and a decision to upskill, and it lands hardest on the people who'd benefit most.

Direct bill removes it: the school bills the employer, the employer approves, and the employee never carries the cost. What you get back is a benefit people actually use — which is where the return on tuition assistance comes from in the first place, in productivity and in retention.

The pace of required upskilling has accelerated. Roles are changing faster than hiring can keep up with, and the cheapest way to fill a capability gap is usually to build it in someone who already works for you.

Section 127 has allowed employers to provide tax-free educational assistance since 1978; the annual cap has been $5,250 since 1986. Congress has now made the provision permanent, and beginning in 2027 the cap adjusts for inflation for the first time. The benefit is settled and growing. What hasn't kept up is the delivery mechanism — a reimbursement process designed for a slower world, still sitting in front of the fastest-moving thing on an HR agenda.

No, and the difference matters.

A TPA administers your benefit and typically charges a share of what you spend. EFFA doesn't sit between you and the school — the school keeps the relationship, you keep the terms, and EFFA costs you nothing.

You get every partnership in one dashboard, with real-time eligibility, invoices, settlement, and utilization across all of them — not a monthly report from an administrator.

EFFA is where schools and employers do business — but the reason it exists is the employee.

Because EFFA costs schools a fraction of what traditional intermediaries take, schools can pass more of that value through as deeper tuition discounts. Because it's direct-billed, the employee never fronts the cost.

Schools get a real enrollment channel. Employers get control and a clear record of what they funded. The employee gets an education they can afford.

Every school in one dashboard. Real-time eligibility, invoices, settlement, and utilization across every partner — one process instead of a different arrangement with each school, and records that stand up to an audit without anyone assembling them.

Employees who actually use the benefit, because they're not fronting tuition and waiting to be paid back.

A channel, not a reimbursement queue. Your education spend goes to schools you've formalized terms with — so the same dollars buy a partnership, not a stack of receipts.

Reimbursement is retrospective — the employee pays, submits a receipt, and you review a charge that's already happened. Direct bill is prospective: you confirm who's eligible, you set the cap, and you approve each invoice before any money moves.

Same benefit, same tax treatment, same $5,250 — but you're deciding in advance rather than auditing after the fact, and your employee never carries the cost in between.

Because the barrier isn't interest, it's cash flow. An employee who can't front a semester's tuition and wait months to be reimbursed doesn't enroll — regardless of how good the benefit is. Direct bill removes that barrier entirely. The employees most likely to benefit from education funding are usually the ones least able to front it.

Nothing. EFFA runs on a school-paid model — schools pay a transaction fee on direct-bill settlement, 3.5% standard, and employers pay nothing at all. No subscription, no per-seat charge, no implementation cost, no line item on your invoice. You pay the tuition rate you negotiated with the school, and that's the whole of it.

EFFASkills will connect funded programs to the occupations they prepare people for, so employers can see what their tuition spend is building toward.

Most tuition programs can report what was spent. Very few can say what it produced — and that gap is why education benefits get defended as a cost line rather than an investment.

That's the point. Most employers run each school relationship separately: different contacts, different rate sheets, different invoice formats, different spreadsheets. EFFA puts every one of them on the same rail — one dashboard, one approval process, one set of records.

A TPA can also give you one dashboard, but it does so by taking over your school relationships. EFFA gives you the same view while you keep them. Your agreements stay yours; only the process is standardized.

And your employees get one consistent experience regardless of which partner school they attend — same enrollment path, same benefit, no separate process to learn per school.

Invite them — and it's a short conversation.

Tell your contact at the school that you fund tuition through EFFA and you'd like them set up to receive direct-billed payments. Schools have a direct financial reason to say yes: employer-funded enrollment billed through EFFA is revenue they keep, without the 20–50% share a traditional intermediary takes.

Once they're connected, that school joins the same dashboard as the rest — same process, same records, no separate workflow.

Every partnership carries its own negotiated terms — covered programs, rates, billing basis — and EFFA holds them as live configuration rather than a PDF in someone's inbox. When an invoice arrives, it's already priced at the terms you agreed, and the invoice names the agreement that governed it.

You see utilization by school, spend by school, and enrollment by school in one place, in real time. Adding your fourth school partner is the same amount of work as adding your first.

Terms almost always differ — each school sets its own discounts and billing structure, and you negotiate directly with them. EFFA doesn't standardize your deals; it standardizes the process around them.

Every agreement is visible, current, and comparable in one view, so you can see what each partner actually offers instead of reconstructing it from email.

You connect a bank account once, during setup. From then on, nothing moves until you approve a specific invoice. When you approve, an ACH bank debit is initiated for that exact amount. Every debit is scoped to something you authorized, and it's traceable to the invoice, the employee, and the course that produced it.

EFFA does not operate a bank account that receives employer funds. Stripe processes the payment and settles to the school's own Stripe account. The employer approves each invoice before any payment moves.

EFFA does not store full bank account numbers — we keep only the references needed to run the transaction, and Stripe handles all sensitive banking details.

The school submits the course through EFFA, and the invoice appears in your queue immediately — itemized by employee, course, and amount, with the discount basis shown and the governing agreement named. You're notified when one arrives. Nothing is buried in an email thread, and nothing needs chasing.

After your approval, ACH settlement typically completes within 4–6 business days. You see the status throughout — approved, processing, paid.

No. There's no escrow, no deposit, no balance to maintain. You pay each approved invoice when you approve it, and that's the only money that ever moves.

Two decisions, and both are yours.

First, eligibility. When an employee enrolls at a partner school, the school submits a request to confirm they're covered. You confirm once and set that employee's annual cap. That's it for that person.

Then, invoices. As each course is billed, an invoice arrives in your queue showing the employee, the course, the amount, and the agreement it was priced under. You approve it, and payment moves. If you don't approve it, nothing happens.

Two touches — not a program to administer.

No. Every dollar that leaves your account is attached to an invoice you approved.

Your bank authorization is scoped to exactly that — it cannot be drawn against anything you haven't approved, there is no auto-pay, and no school can initiate a charge against you. You can revoke the authorization at any time.

Yes. Eligibility confirmation and payment approval are separate permissions, so the person who verifies employment doesn't have to be the person who releases funds. That matters in regulated environments and in any organization with real segregation-of-duties requirements. Every action is recorded with who did it and when.

Yes, and you set it — up to the $5,250 §127 limit or whatever your policy allows. The cap is enforced by the platform: once an employee's funded courses reach it, further charges are blocked automatically rather than depending on someone noticing.

It protects your employee as much as your budget. Nobody enrolls in a course only to discover the benefit ran out — the limit is visible and enforced before anything is billed.

Approval is the commitment. When you approve an invoice, the ACH debit is initiated at that point — there is no cancellation step afterward. That's deliberate: it's what makes the record trustworthy on both sides, and it's why the approval screen shows you the employee, the course, the amount, and the governing agreement before you click.

After approval, corrections run through refund, credit, or dispute — the same as any other payment your organization makes.

What you can do at any time: revoke your bank authorization for future debits, and revoke an employee's eligibility. Both stop anything new immediately. Neither unwinds a payment already in motion.

Revoke their eligibility and no further invoices can be raised against them — that channel closes immediately. Anything already approved and settled stays settled; that's between you and the school, and most partnership agreements address it directly. What matters is that a departure never leaves an open line to your account.

A complete, exportable record of every transaction: employee, school, course, dates, gross tuition, discount applied, net amount, the agreement that governed the price, approval date, and payment date. Not a monthly summary from an administrator — the underlying detail, live, whenever you want it.

Yes. You can map payments to the general ledger accounts you actually use, so tuition spend posts where your finance team expects it rather than arriving as an unclassified line to be sorted out later.

Yes. Every settlement carries a reference you can match against the corresponding debit, and approved and paid invoices export as a file your AP team can reconcile directly. Reconciliation should take minutes, not an afternoon of matching amounts by eye.

Spend and utilization by school, by employee, and by period. Cap consumption against each employee's remaining balance. Enrollment activity across every partnership. Everything exports.

Your transaction history stays available for as long as your account is active — you're not working from a rolling window. Records are designed to satisfy audit and §127 substantiation requirements without anyone reassembling them after the fact.

Under an hour. Your school partner invites you, you complete your account, connect a bank account for payment, and confirm the terms the school proposed. That's the whole of it — no implementation project, no phased rollout, no professional services engagement.

No integration is required to launch. EFFA is cloud-based with no HRIS feed and no data build.

That's a security posture as much as a speed one: EFFA holds no directory access and no federation trust with your systems. There is nothing connected to your identity provider to review, and nothing to disconnect if you leave.

SSO and automated provisioning aren't built today. If your environment requires them, we want to know early.

No. An employee never needs an EFFA account to receive the benefit. The school owns the student record, the school invoices, and the employer approves — none of it requires the employee to log in anywhere.

Employers may optionally invite employees to a read-only view of their own tuition benefit and their employer's partner schools. That view cannot approve anything, pay anything, or change anything, and it shows an employee only their own record.

Employees cannot sign themselves up. Every EFFA account inside an employer is created by that employer's administrator.

Approving invoices as they arrive. That's the ongoing job.

There are no reimbursement claims to process, no receipts to verify, no checks to cut, and no spreadsheet reconciling what was promised against what was paid. Whether you have five employees using the benefit or fifty, the work is the same shape — the platform batches, prices, and documents; you approve.

The school does it. When your employee enrolls, the school creates their record and asks you to confirm eligibility. You're not uploading rosters, maintaining a list, or telling schools who works for you. The school carries the administrative load — which is the right place for it, since they're the ones enrolling the student.

Enroll. That's it. They don't front any money, don't submit receipts, and don't wait to be paid back. From their side the benefit simply works — which is precisely why people use it.

EFFA does not intentionally collect or store Social Security numbers or full bank account numbers. Banking details are handled entirely by Stripe; we keep only Stripe identifiers and the last four digits of an account for audit and display purposes.

We're deliberate with the word "intentionally": some product fields are free text and reviewers can upload documents, so we can't claim it's technically impossible for a user to type or attach sensitive data. But we don't request it, design for it, or store it in structured fields.

EFFA is designed to support schools that use service providers for employer-sponsored billing. Schools decide how they satisfy their FERPA obligations, including whether EFFA fits within their "school official" framework for a given engagement. EFFA does not make that determination on a school's behalf, but we can walk your school, legal, or compliance team through the data we receive, how it is used, and how the workflow is structured.

We also use the U.S. Department of Education's College Scorecard as a public data source for school lookup; no personal data is sent to it.

Yes. EFFA is hosted on established cloud infrastructure whose security and compliance programs include SOC reporting. We can provide relevant vendor trust documentation, including SOC reports where available, to reviewers who need them.

Yes. EFFA completed a HECVAT questionnaire on June 1, 2026. We're glad to share it with qualified security and procurement reviewers under NDA.

EFFA supports employer education-assistance workflows, but we do not determine tax treatment. Whether a payment qualifies under IRC §127 depends on the employer's own education-assistance plan and tax position. We do not represent that any payment is automatically tax-free or provide tax advice. We can provide the transaction records your finance, benefits, or tax team needs to make that determination.

EFFA's Terms of Service cover employer, school, and user workflows and are accepted online when an account is created. There is usually no separate signing step. If your team has specific legal, security, or procurement requirements, we're glad to provide the right materials for review.

On written request, EFFA exports your transaction records and removes or deactivates your data within 30 days.

Some records are retained because they have to be — the immutable payment and audit ledger that explains what happened. That includes settled and attempted invoices and their line items, settlement and refund records, Stripe payment identifiers, cap and liability history, the commercial terms used to price historical invoices, audit trails showing who authorized what and when, and anything subject to legal, accounting, tax, compliance, or dispute-resolution obligations.

Everything else — live operating data, display records, account access — is removed.