School-paid platform
EFFA's platform model is school-paid.
EMPLOYER FAQ
EFFA's platform model is school-paid.
Employers remain responsible only for the tuition they agree to fund.
The employer workflow runs in EFFA without a custom implementation project.
HRIS, SSO, and data-feed work are not required to get started.
EFFA is a cloud-based platform where employers manage school relationships, employee eligibility, invoices, and direct tuition payments in one portal. Your team and school partners work with a common process, common language, and unified real-time data. EFFASkills connects the programs employers fund to verified skill outcomes.
Employers pay EFFA nothing and fund only the tuition they choose to fund.
Schools pay a transaction fee on direct-bill settlement. The standard rate is 3.5%, netted from the payout.
Employers can be set up in about 60 minutes: an account, a bank link and confirming terms. No IT, SSO or HRIS integration.
If your environment requires SSO or automated provisioning, raise that requirement during review so the setup path can be assessed.
Disconnected school relationships, eligibility reviews, invoices, and payment updates create extra coordination work for HR, finance, and school partners.
Direct bill changes the workflow: the school submits an invoice, the employer reviews and approves covered tuition, and both organizations work from a shared record. Employees get a simpler path to use covered funding without fronting the covered cost.
Employers are being asked to support faster skill development while keeping education benefits accountable to finance, HR, and operating teams. Schools are also looking for clearer employer relationships and better ways to support working learners.
EFFA focuses on the operating layer: school partnerships, eligibility, invoices, payment status, and connections between funded programs and verified skill outcomes in one shared platform. Tax treatment still depends on the employer's own plan and tax position.
EFFA provides the shared platform for your team and school partners to work together. Your organization keeps its education-benefit policies and approval decisions, while EFFA streamlines the partnership and direct-billing process and keeps funded education activity visible.
EFFA is where schools and employers do business — but the reason it exists is the employee.
Because the workflow is direct-billed, employees do not have to front covered tuition costs. Any school discounts or covered amounts still follow the agreed partnership terms and employer policy.
Schools get a clearer employer partnership workflow. Employers get control and a shared record of what they funded. Employees get a simpler path to use covered education benefits.
Manage school partnerships in one portal, reduce repeated eligibility and payment-status inquiries, and give employees a simpler way to use employer funding without fronting covered tuition costs. EFFASkills connects the programs employers fund to verified skill outcomes.
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.
It can support the same education-assistance benefit while changing the timing and workflow: you're deciding in advance rather than auditing after the fact, and your employee does not carry the covered cost in between. Your tax team still determines the applicable treatment under your own plan.
Reimbursement can create a cash-flow barrier because the employee may have to pay first and wait to be reimbursed. Direct bill helps remove that barrier for covered tuition: the school and employer coordinate the funding through EFFA, and coverage still follows the employer's policy and the agreed school terms.
EFFASkills connects the programs employers fund to verified skill outcomes.
Yes. Bring your participating school partners into one portal, with each partnership's agreed terms connected to eligibility, invoicing, approvals, and payments. Both teams work from unified real-time data, reducing separate spreadsheets and repeated status inquiries.
Invite the school to join EFFA so you can manage the relationship and direct billing together. Once the school is onboarded and your partnership is established, your teams can use the same shared process as your other EFFA school partners.
Yes. Your organization and each school agree on the commercial terms for that partnership. EFFA applies those terms within a common invoicing and payment process, so your team can manage different agreements in one place.
The school submits an invoice through EFFA with the agreed partnership terms applied. Once the employer approves an invoice, our payment processor collects the payment, EFFA's small transaction fee is deducted, and the rest is transferred to the school. School and employer teams can follow the status in real time, while employees avoid fronting covered tuition costs.
Once the employer approves an invoice, our payment processor collects the payment, EFFA's small transaction fee is deducted, and the rest is transferred to the school. The Trust Center explains the payment process and the controls available for finance review.
EFFA does not store full bank account numbers. See the Trust Center for payment-provider and banking-data details.
The school submits the course through EFFA, and the invoice appears in your queue — 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.
Your team can follow payment status throughout the workflow. Processing and receipt depend on the payment method, bank timing, weekends, holidays, and standard payment-rail timing. A payment being approved or processing does not mean the school has received the funds.
EFFA's direct-bill workflow is based on approved invoices, not an employer escrow balance. Your finance team should review the applicable payment setup and any correction, refund, or dispute process with EFFA during onboarding.
Your organization retains those decisions. Your team confirms employee eligibility and the tuition covered by your education-benefit policy. EFFA gives your team and school partners a shared process and visibility into eligibility and approval status.
No. Your team approves the invoice before payment is initiated. The school can submit an invoice for review, but it cannot approve payment on your organization's behalf.
Yes. Your organization can assign responsibilities for employee eligibility and financial approvals to the appropriate authorized users. EFFA records activity so your team can review the decisions associated with a request.
Yes. Your organization sets its education-benefit policy and applicable employee limits. EFFA uses the configured limits in the funding workflow and gives your team visibility into benefit usage.
Approval is the commitment. When you approve an invoice, the payment process 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.
For future funding, your team can update employee eligibility and review outstanding requests with the school. Changing eligibility does not automatically undo an existing payment or resolve obligations already agreed with the school.
Update the employee's eligibility and review any outstanding requests with the school. Changing eligibility for future funding does not automatically undo an existing payment or resolve obligations already agreed with the school. For a payment already in progress, contact EFFA to review the applicable correction, refund, or dispute process.
Detailed financial reports include invoice references, GL codes, employee and school information, course details, amounts, and payment status. Your team can export reporting for review and reconciliation in its existing accounting process.
Yes. Your team can assign a GL code to a school partnership and include that reference in detailed financial reporting, helping finance organize tuition expenses within its accounting process.
Yes. EFFA connects invoice and payment records so your team can trace transactions, review outstanding items, and reconcile activity with school partners. Both teams work from shared, current data, reducing manual spreadsheet tracking and repeated requests for updates.
Track employee eligibility, invoices, approvals, and payment status across your school partnerships using unified real-time data. EFFASkills connects the programs employers fund to verified skill outcomes.
Authorized users can review transaction history in EFFA while the account is active, including the invoice, approval, payment-status, and partnership records needed for normal finance and benefits review. Legal, tax, accounting, compliance, or dispute-resolution obligations may require some records to be retained after live operating access changes.
EFFA can support employer tuition assistance without an HRIS, SSO, or custom IT integration. Employers can be set up in about 60 minutes: an account, a bank link and confirming terms. Your organization still owns its eligibility and funding decisions, while participating schools and employers coordinate invoices and payment status.
Employees access EFFA through their employer's portal. For help with your tuition benefit, email inquiry@effa.io. Employees with access can discover your organization's school partners, express interest in schools, and view their own tuition-benefit information. Your organization retains eligibility and payment approval decisions.
EFFA brings your team and school partners into a common process for eligibility, invoices, approvals, and payments. Shared status and unified real-time data reduce repeated inquiries, spreadsheet tracking, and manual follow-up, giving your team more time for employees and school relationships. Your organization retains its policy and approval decisions.
No. Employees follow the school's admissions and enrollment process. EFFA connects the school and employer around the funding process, helping both teams coordinate the work without replacing the school's existing systems.
Employees can explore your school partners and available tuition discounts, then express interest through EFFA. Your team and the school coordinate eligibility, invoicing, and direct payment in one shared process, so employees don't have to front covered tuition costs.
Adapted from EFFA's Trust Center review materials.
Visit the Trust Center for information about payment controls, data handling, security, and platform agreements. Your reviewers can use it to assess EFFA and request supporting materials for your organization's review.
EFFA does not intentionally collect or store Social Security numbers or full bank account numbers. Banking details are handled by the payment processor; we keep only payment-provider identifiers and the last four digits of an account for audit and display purposes. See the Trust Center for provider details.
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.
EFFA uses service providers for hosting, payments, communications, monitoring, storage, uploads, rate limiting, and selected AI-assisted document processing. The current provider inventory is supplied during security review with each provider's role and applicable access conditions.
Provider-issued trust materials may be available for review where the provider makes them available and where access conditions permit. EFFA distinguishes vendor-issued materials from EFFA-owned security documentation and does not present vendor reports as EFFA's own SOC assessment.
EFFA records indicate a HECVAT questionnaire was completed on June 1, 2026. Qualified security and procurement reviewers can request it through the Trust Center; availability, version, and access conditions are confirmed before sharing.
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 platform terms govern use of the platform. Commercial terms between schools and employers are formalized separately through the partnership workflow. Your organization can request relevant materials for legal, security, or procurement review.
During offboarding, EFFA can work with your team on an export of your transaction records and on deactivating live account access. The exact timing, scope, and retained-record categories are handled through the offboarding and legal review process.
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, payment-provider 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.
Other operating records and account access are handled through the offboarding process, subject to the retained-record categories and any applicable legal, accounting, tax, compliance, or dispute-resolution obligations.
Explore how EFFA brings school relationships, direct tuition payments, and connections between funded programs and verified skill outcomes into one platform—with a common process and unified real-time data.
Employers pay EFFA nothing and fund only the tuition they choose to fund. No IT integration required.