Fees & Payment Framework
A clean, allocation-safe payment flow. Fees are invoiced with reference requirements to prevent misallocation and delays. Registered Agents coordinate invoice routing and submission sequencing.
Key rule
Payments without correct references may be held for allocation verification and can delay processing.
Who pays
Applicant entities pay fees; Registered Agents can coordinate invoice delivery and confirmations.
Timing
Fees are normally collected at submission and/or at decision, depending on fee type.
Fee types (overview)
Displayed as a framework. Insert exact values later if you publish a schedule.
Collected at submission. Covers intake, completeness checks, and initial review stage costs.
Used where deeper validation is required (technical/security, integrity testing, control walkthroughs).
Collected when an approval decision is made (or prior to publication) as the final issuance step.
Payable for continued status. Links to ongoing supervision, reporting and renewal checks.
Applies to material changes: scope expansion, ownership changes, key system changes, model shifts.
Used for certified copies, register extracts, attestations, or formal correspondence packs.
If you publish an official fee schedule, keep the framework text and inject the actual values inside the “Fee schedule” page.
Invoicing and reference requirements
Payment references exist to reduce reconciliation errors.
| Item | Requirement | Why it matters |
|---|---|---|
| Invoice number | Must be quoted in the transfer reference field. | Enables accurate allocation to the correct file. |
| Applicant name | Must match the applicant entity name used in submission pack. | Reduces mismatches across invoice and evidence pack. |
| Registered Agent ID | Where issued, include the agent ID or code on the payment note. | Routes allocation confirmations to the correct agent. |
| Fee type label | Application / assessment / issuance / renewal. | Prevents fee misclassification and delays. |
Common delay cause: missing references
Transfers without invoice numbers or with mismatched applicant names can be held for allocation verification. Use the invoice details exactly as issued.
Payment methods (framework)
Publish actual methods on your payments support page if needed.
Bank transfer
Primary method for invoiced fees with reference controls.
Card (where offered)
If enabled, still requires invoice reference attachment.
Other rails
Use only if published; avoid off-book payments.
Corrections and misallocations
What happens when payment data is wrong.
Held for review
If references are missing, allocation may pause until verified.
Evidence requested
Proof of transfer + invoice + applicant ID details may be requested.
Reallocation
Where possible, payment can be reassigned to the correct file once validated.
For clarity, keep payments support communications routed through the Registered Agent where applicable.