Internal Verification
FSP Registration — Internal Training
Stage D: Capture + Submit on FSCA + Follow-up (Steps 22–49) • Capture forms, upload, validate, submit, track, close via automation
Outcome: application submitted + proof logged + follow-up tracked until completion
Stage D is where the case is “won or lost”
Stage D is the execution stage: you capture the FSCA forms (FSP1–FSP9 where relevant), upload supporting documents, run validation checks, submit, and then manage follow-ups until FSCA reflects progress/approval. This is also where internal automation protects you: once evidence and statuses are logged correctly, the workflow can auto-track and auto-close.
Steps covered: 22–49
Main risks: validation errors, wrong attachments, weak logging
Win strategy: capture clean → validate → submit → log proof → follow up consistently
Non-negotiables in Stage D
- Capture on the correct FSCA service and correct application
- Attachments must be correct, readable, and complete
- Use Validate + Fee Calculator before submitting
- Submit only when there are no validation errors
- Every action must be logged in Zoho (audit + SLA + automation)
Reminder: No PoE is required for learners. This training is about capability and quality standards.
Stage D “Process Rails” (do not deviate)
Rail 1 — Portal Accuracy: Always confirm you are inside the correct new application record before capturing anything. Wrong record = wrong reference = chaos.
Rail 2 — Validation Discipline: Validate early and often. Don’t wait until the end. Fix errors immediately.
Rail 3 — Evidence & Logging: Anything not logged in Zoho is treated as “not done”. Automation depends on accurate logging.
Rail 4 — Follow-up Cadence: Follow-ups must be consistent and recorded. If follow-ups are inconsistent, the case stalls and client trust drops.
Stage D — Steps 22 to 49 (grouped by what you are doing)
These steps are often long in real life. We group them so staff understand the flow: Capture → Upload → Validate/Fee → Submit → Proof/Log → Follow-up → Close via automation.
Steps 22–26 — Open the correct FSCA application record and prepare for capturing forms
›
What you must be able to do
Find the correct application record
- Navigate back into the FSCA portal and locate the application you created (the one linked to the correct reference).
- Confirm applicant identity on-screen matches your verified Stage C data.
- Do not proceed if the applicant identity doesn’t match (stop and escalate internally).
Quality check: You must be able to say: “I am in the correct application for the correct applicant.”
Common errors to avoid
Portal mistakes that waste hours
- Capturing in the wrong application record because multiple attempts exist.
- Starting capture before the Stage C pack is truly ready (missing attachments/information).
- Not saving as you go (timeouts can cause lost data).
Rule: Save frequently. FSCA sessions can expire unexpectedly.
Steps 27–34 — Capture FSP1–FSP9 (form capture discipline + data accuracy)
›
Your SOP refers to capturing FSP forms (FSP1–FSP9). The exact sequence may depend on the portal screens. Your responsibility is: capture accurately, keep data consistent with Stage C, and save each section properly.
What you must be able to do
Capture with “single source of truth” discipline
- Use Stage C standardised data as the reference (names, IDs, registration numbers, addresses, contact details).
- Capture each form section fully and save before moving on.
- Ensure information about KI(s), business details and product categories aligns with what was verified.
Quality check: If you copy/paste, re-check formatting (extra spaces, punctuation, or incorrect casing can create validation issues).
How to prevent validation errors
Common capture mistakes
- Using abbreviations or informal names that don’t match legal documents.
- Mixing “postal” and “physical” addresses incorrectly.
- Wrong legal type selection (natural vs juristic) compared to applicant reality.
- Leaving mandatory fields blank because “we’ll come back later”.
Rule: If a field is mandatory, complete it now or you will face validation block later.
Steps 35–38 — Upload attachments (what “correct upload” means)
›
What you must be able to do
Upload the correct documents to the correct slots
- Attach documents exactly as required by FSCA (correct category/slot where applicable).
- Confirm each upload completes successfully (do not assume).
- Check readability: documents must be clear and complete (not cut off, not rotated, not unreadable).
Quality check: After upload, verify the file name/preview matches what you intended to upload.
Attachment failures to prevent
What usually goes wrong
- Uploading the wrong person’s ID / wrong company docs (mix-ups happen when multiple cases are open).
- Uploading an outdated proof of address (if your SOP requires a currency limit).
- Uploading corrupted files or screenshots where official documents are required.
Rule: One wrong attachment can lead to FSCA queries and long delays. Slow down and confirm.
Steps 39–41 — Fee Calculator + Validate (must be clean before submit)
›
Your SOP includes critical pre-submit checks: Check fee calculator to confirm fee paid is correct, and Validate to ensure no errors remain. Submission is allowed only when the portal indicates it can be submitted.
Fee Calculator (what you must do)
Confirm fee correctness
- Open the fee calculator in the portal for the current application context.
- Confirm the fee expected for this application type and compare to what the client paid / will pay.
- If mismatch exists, stop and correct the issue before moving to submission.
Quality check: Fee mismatches cause avoidable delays and can force rework or re-submission.
Validate (what you must do)
Clear all validation errors
- Select Validate and read the error output carefully.
- Fix errors one by one. Re-run validation until the system confirms you can submit.
- Do not “submit anyway” if errors exist (it will block submission or create failed submissions).
Rule: You may only submit when there are no validation errors and the portal indicates submission is possible.
Steps 42–44 — Submit the application (final checks + submission discipline)
›
What you must be able to do
Submit cleanly (no guessing)
- Confirm validation is clean and fee checks are correct.
- Submit once. Do not click multiple times.
- Capture the submission confirmation outcome (reference, confirmation message, or portal status).
Quality check: After submission, confirm the portal reflects a submitted status (or equivalent).
Submission risks
What causes “we submitted but…” problems
- Submitting without confirming the correct application record.
- Submitting while there are hidden validation errors.
- Not recording submission confirmation, making it impossible to prove later.
Rule: “No proof logged” = “not submitted” in operational terms.
Steps 45–47 — Log proof and update Zoho (so automation can track and close correctly)
›
What you must be able to do
Log the right things in Zoho immediately
- Update the case/record with submission status (as configured in your module).
- Attach or reference the submission proof/confirmation (whatever your SOP requires internally).
- Record key details: submission date/time, FSCA reference, and current status.
Why it matters: Automation and reporting rely on these fields. If you skip them, follow-ups and closure won’t work properly.
Field discipline
How to log so the whole team understands
- Use short factual notes: “Submitted on FSCA portal — confirmation received.”
- Do not write emotional notes like “client is difficult.” Keep notes professional.
- Make sure the record stage advances correctly (Stage D → Follow-up/Monitoring, depending on your blueprint).
Common mistake: keeping proof on desktop or email only, not on the Zoho record. That breaks team visibility.
Steps 48–49 — Follow-ups until completion + close case (automation-assisted)
›
What you must be able to do
Follow-up management (consistent + logged)
- Follow up on FSCA progress according to your SOP cadence (e.g., biweekly where applicable).
- Record each follow-up attempt in Zoho (date, channel used, response/outcome).
- Update the status field so the dashboard reflects “awaiting FSCA” vs “client action required”.
Quality check: Anyone must be able to open the record and immediately see: what was done, when, and what is next.
Closing via automation (concept)
How automation should support you
- When FSCA reflects a final outcome and you update the record accordingly, the workflow can trigger automatic closure steps.
- Automation can also trigger client notifications, internal tasks, and survey steps (depending on your setup).
- Your role is to update the correct “closing fields” so automation fires reliably.
Common mistake: closing manually without updating closing fields → automation doesn’t trigger and the record is left incomplete.
Follow-up best practice (internal standard)
Be consistent: same cadence across all cases. Random follow-ups lead to stalled work and poor client experience.
Be traceable: log each follow-up. If it’s not logged, it didn’t happen.
Be outcome-based: every follow-up must end with “what’s next?” (waiting FSCA / waiting client / internal task).
Escalate smart: if no response/progress over multiple cycles, escalate to Team Lead with evidence of follow-ups.
Mini Quiz — Stage D mastery check
Answer and click “Check answers” for instant feedback.
1) When can you submit the FSCA application?
2) Why must submission proof/status be logged in Zoho?
3) What is the correct follow-up approach after submission?