Skip to main content
For standard processing, Funding Machine’s fee is 15% of the client funding fees you actually collect for work completed by the processing team. Your client’s agreement rate determines their funding fee; the 15% processing rate applies to the eligible amount you collect. For example, 18,500ofcardfundingata718,500 of card funding at a 7% client agreement rate produces a 1,295 client fee. Collecting that fee results in a $194.25 processing fee.

​
Which payments qualify?

A payment must belong to the funding engagement the processing team completed. Completing card processing does not make an earlier term-loan payment eligible. Funding you sourced without the processing team does not increase the fee basis. This applies across funding options: term loans qualify when the processing team did the work, and an Operator-sourced card does not qualify just because the team also completed card processing. HELOC funding is excluded and invoiced separately. If your client pays before processing is complete, the payment is checked again after completion using these same eligibility rules. Recovery of a missed payment also uses those rules. Multiple invoices for the same engagement share one limit based on the funding the processing team delivered. Payments that cannot be confidently matched to completed work are held for staff review. A held fee is a proposal; no processing-fee invoice is sent until staff confirm its attribution. Each client invoice can generate only one linked processing-fee invoice. For a payment covering both team and Operator funding, the system checks funding ownership against the current paid CRM invoice. When the funded amounts and invoice lines match, it calculates the team’s collection and allocates invoice-wide discounts proportionally. Operator funding is excluded. For example, a 3,330paymentfor3,330 payment for 48,000 of team funding and 1,000ofOperatorfundingatthesameagreementrateattributes∗∗1,000 of Operator funding at the same agreement rate attributes **3,262.04** to the team, producing a $489.31 fee. If newer Operator funding makes current totals disagree with the invoice’s creation snapshot, the payment stays in review until its collection is verified against the live CRM invoice or by staff. Operator funding in another category also requires a live invoice check, even if that category was absent from the creation snapshot. A verified team-only invoice can proceed automatically; missing or mixed invoice evidence keeps the fee in review. Calculated proposals are checked again against the current invoice and funding when staff confirm. If those details no longer reconcile, the review must be reconciled before confirmation; retries of a confirmed decision use its saved amount. When invoice details cannot establish that allocation, staff must verify and enter the collection for completed team work, accounting for discounts and credits. The charge is capped by the team’s remaining fee entitlement; a cap alone does not establish which part of a mixed payment belongs to the team. The confirmed amount and staff decision are saved for the audit trail. If an existing processing-fee invoice was corrected manually, reconcile it with any held draft for the same team work before confirming another fee. Confirming a held draft creates and sends an invoice. Recovery also reports an older unsent draft that lacks attribution-review controls as requiring reconciliation before a review can be created.

​
Payment and exceptions

Standard processing-fee invoices are due 7 days after issue. If the amount or funding attribution looks incorrect, contact your account manager with the invoice number before approving an additional fee. Accepted Earn While You Learn files follow their separate collection policy: 50% of eligible collected card and term-loan fees while fulfillment is active. See the 7F fulfillment guide for that workflow.