Role Guide: Funding Processor and File Analyst
For Funding Processors and File Analysts. After this page you will know how to turn a complete document set into a scrubbed, verified, funder-ready package, how to manage stips, and where your authority stops.
Track: Strategic Funding · Role: Processor · Time to complete: 35 min
What you own
You are the last check before a file leaves the company. Underwriters judge the whole desk by the files you send. You own:
- The scrub. Every file gets the 20 point bank statement review and a 3-line summary before it is submitted.
- Integrity. You run the fraud and integrity checks and you stop any file you believe is altered.
- The package. One standard order, one naming standard, one summary format, every time.
- The match recommendation. You suggest which funders in the funder matrix fit the file. The desk lead approves the final list.
- Submission and logging. You submit only through approved portals or channels and log every submission.
- Stips. Every funder request becomes a task with a due time and is chased the same day.
You do not own pricing, offer presentation, funder negotiation or approval decisions.
Daily rhythm
| Part of shift | Focus |
|---|---|
| Start of shift | Check in. Open "Stips Pending" first: funders are waiting on these. Then "Ready to Scrub". |
| First block | Clear stips: request missing items, upload received items, update the CRM. |
| Middle blocks | Scrub new complete files (oldest first, unless the desk lead flags a priority). Run fraud checks. Build packages. |
| Before US end of day | Submit approved packages so they reach funders inside business hours. Log every submission. |
| End of shift | Every file has a status and a next action. End-of-shift report: scrubbed, submitted, stips cleared, files stopped and why. Check out. |
KPIs that matter
| KPI | Narqix standard |
|---|---|
| Complete file to submission time | Same day for files received early in shift |
| Same-day submission rate | Campaign target |
| Kickback rate (files a funder returns for missing or wrong items) | As close to zero as possible |
| Stip turnaround | Requested within the hour, chased the same day |
| Scrub accuracy (QA review of your sheets) | No critical errors |
| Fraud catches | Every suspected file stopped and escalated |
| Files submitted without a scrub sheet | Zero |
The package standard
Every submission package is built the same way:
- Scrub summary (the 3-line summary from the scrub sheet, plus open questions)
- Signed application
- Bank statements merged into one PDF, newest month first, month-to-date on top
- ID for each signer
- Voided check or bank letter
- Product-specific documents in checklist order
- Position list if the merchant has existing advances
File names follow the standard: legal name, document type, period. Example: (LEGAL NAME) Statements (MONTH RANGE).pdf
The submission subject line follows the standard: New Submission, legal name, amount requested, months of statements, product, and the company name. Example: New Submission · (LEGAL NAME) · (AMOUNT REQUESTED) · 4 months plus MTD · MCA · (COMPANY NAME)
Pre-flight checklist (before any submission)
- Signed application with authorization to share the file with funders
- Complete document set for the product
- Scrub sheet complete, 3-line summary written
- Fraud and integrity check passed, or cleared in writing by the desk lead
- Self-reported facts compared to statement facts, and every gap noted (for example, merchant said 1 advance, statements show 2)
- Funder list approved by the desk lead (no mass sending to every funder, called shotgunning)
- Submission channel is an approved portal or secure channel, never personal email
Coach's note: when the merchant's answers and the statements disagree, the statements are not automatically right and the merchant is not automatically lying. Statements lag: a new advance funded last week will not show yet. Ask, record the answer word for word, and put the gap in the summary. Underwriters trust files that show their own gaps.
Handoffs
You receive work from: the Application Assistant and Document Chaser (complete files) and the Renewal and Follow-Up Rep (renewal files).
You pass work to: the desk lead (funder match approval), funders (approved submissions), and the closer or founder (offers). You send stip requests back to the Document Chaser or directly to the merchant, per campaign.
After a decision: funded files go to the Renewal and Follow-Up Rep for check-ins. Declined files get a reason code and a re-check date and go to the Renewal and Follow-Up Rep.
Offers: what you do and do not do
When a funder sends an offer, you record it in the CRM exactly: amount, payback or total repayment, term, payment amount and frequency, and any conditions. You then pass it to the closer or founder. You do not present the offer, explain it, compare it or comment on whether it is good. The funder delivers any required state disclosure; you log that it was delivered and signed.
Common mistakes
- Using gross deposits as revenue. Funders size files on true revenue.
- Missing a position because the debit has a vague description.
- Merging statements oldest first, or leaving out the month-to-date.
- Submitting to every funder "to see who bites". This spreads the merchant's data and creates duplicate inquiries.
- Letting a stip sit overnight because the merchant "will send it tomorrow". Set the task, send the reminder, log it.
- Writing opinions in the summary ("great merchant!"). Write facts.
Never do this: never submit a file you believe is altered. Never change a merchant's document. Never leave a known position out of the summary. Never send merchant documents to any funder the desk lead has not approved. Never share pricing with a merchant.
Escalation rules
Escalate to the desk lead the same shift when:
- Any fraud signal appears (see Fraud and Integrity Checks)
- Statements show a funder payment returned, a stop payment on a funder, or signs of default
- You find an auto-stop flag: open bankruptcy, active tax lien, recent judgment
- The merchant's answers and statements disagree on positions and the merchant will not clarify
- A funder asks for something unusual (for example, a document you have never seen requested)
- A merchant contacts you about an offer or pricing
Check yourself
- In what order do bank statements go in the merged PDF?
- Name four items on the pre-flight checklist.
- A funder emails a stip at the end of your shift. What happens before you check out?
- What does "shotgunning" mean and why is it banned?
- A merchant calls you to ask if the offer is good. What do you say and do?
© Narqix Academy