> ## Documentation Index > Fetch the complete documentation index at: https://docs.myfundingmachine.com/llms.txt > Use this file to discover all available pages before exploring further. # 7F Fulfillment > Work HELOC assistance and Earn While You Learn files from one fulfillment workspace. Nate and Max use **Admin → Internal → 7F Fulfillment**. Choose **All files**, **HELOC**, or **Earn While You Learn**. Processor work continues in the existing processing queue. EWYL remains controlled by the hidden per-Location Labs switch. Use the [fulfillment queue guide](/sops/fulfillment-queue) to find files, prioritize follow-ups, and recover from loading errors. ## Contact layout When the Location's EWYL Labs switch is enabled, the full **Earn While You Learn** panel appears in **Overview** for Applicants and **Funding** for Clients. There is no separate contact tab. Handoff, scheduling, fulfillment fees, shared history, and withdrawal controls all stay in that panel. Staff opening a file from the fulfillment queue and saved EWYL links land on the appropriate tab automatically. The panel is shown only for qualifying files or files already enrolled in EWYL. Files that do not qualify and have never enrolled do not see an EWYL banner or offer. Existing files keep their status and history visible after qualification changes, a withdrawal request, or release. ## Separate responsibilities **HELOC:** help the Operator and Applicant submit the application. The Operator owns follow-up through closing and collection of their fee. HELOC carries no 7F processing or fulfillment fee. **Earn While You Learn:** the Operator closes the sale and gets the client agreement and processing application signed. A qualifying file transfers to the fulfillment team as soon as the Operator accepts **Use 7F Fulfillment**. No team approval is needed. Arrange processing, follow up on pending cards and term loans, update final approvals and amounts, and collect the Operator's client invoice. Operators can continue editing; the file's shared history records changes. ## Qualification settings Initially, combined card and term-loan low-end preapproval of **\$40,000** qualifies on its own. HELOC estimates do not count. **EWYL settings** supports alternative scenarios: any scenario may qualify, but all conditions within it must pass. Conditions include minimum preapproval, minimum credit score, maximum DTI, and minimum annual income. Missing required data does not qualify. A file can transfer during processing, until a completed card or term-loan result has been returned. Existing transfers remain active after processing completes or eligibility settings change. Adjust criteria for future files rather than rejecting accepted ones. ## Calls and follow-up Choose separate active CRM calendars in **HELOC settings** and **EWYL settings**. Calendar changes apply to new handoffs or booking requests; existing files keep their assigned calendar. A calendar previously used for HELOC cannot also become an EWYL calendar. The Applicant is the primary attendee and the Operator can join as a guest. For EWYL, the Operator can book, copy the scheduling link, or send it to the Applicant. Appointment updates appear on the file and in shared history. Use **Refresh appointment status** to read the current CRM appointment. Duplicate contact identities require review before an appointment can be linked safely. Canceling a call does not withdraw the file. Use the calendar confirmation to reschedule or cancel a booking. Nothing confirms a booking automatically. A HELOC call that arrives as **New** is suggested as **Confirm call** in the queue until a team member sets it to **Confirmed** on the file. A HELOC file enters the queue when its plan is confirmed, when the Operator opens the booking calendar, when a call lands on the fulfillment calendar, or when staff match a booking by hand. Each has its own undo: clear the plan, **Remove from queue** on a booking-request row that has no plan and no appointment, cancel the call in the CRM, or **Unmatch**. A test or ineligible file leaves the queue the same way it came in. The **HELOC prescreen report** next to the queue is read-only: it counts prescreen outcomes and opens no files. Work every file from 7F Fulfillment. Keep the file's owner, status, next action, and follow-up due date current. Processing, lender follow-up, and collection are separate stages. ## Collections and the fulfillment fee Keep card and term-loan funding fees on separate client invoices from HELOC and other funding. Payments are credited only within their funding category. 7F's fulfillment fee is **50% of actual collected card and term-loan funding fees**, replacing the 15% processing fee. Each client invoice has one linked 7F invoice. Partial payments accrue without issuing another invoice for each payment. The 7F invoice is issued when the client invoice is fully paid or when staff use **Close collections and invoice collected amount** to finish collection short of the original balance. A failed issuance remains visible for retry. Collections can be reopened before the linked fee invoice is finalized. Refunds, payment corrections, and receipts changed after finalization are held for reconciliation without adding restored payments to the fee a second time. An exact restoration before finalization clears the correction hold only when all receipts belong to the same fee rate and the restoration is in that rate period. Corrections across release, mixed fee rates, and finalized invoices remain held for review. Review the linked fee invoice before proceeding; do not create a second fee invoice for the same client invoice. ## Withdrawal The Operator uses **Request withdrawal** and sees confirmation that the request was submitted. The file and fee arrangement remain active until staff select **Release file**. Operators may cancel their request while it is pending. Collections received before release retain the 50% rate. Subsequent collections follow normal processing-fee eligibility and attribution rules. Keep the history and invoices when releasing a file. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.