REP027 software connects a payment or electronic money institution's month-end safeguarding position to the monthly return required under SUP 16.14A. It should assemble governed data, validate the draft, expose unresolved exceptions, record approval and preserve the exact version and evidence associated with submission.
The objective is not to automate judgement out of reporting. It is to remove uncontrolled rekeying and make every reported figure traceable to the CASS 15 record that produced it.
Key takeaways
- REP027 is generally due within 15 business days after each calendar month end.
- It is not FSA056 or the Client Money and Assets Return used by certain investment firms.
- The return should use the same data and definitions as the approved safeguarding reconciliations.
- A complete workflow covers data, validation, exceptions, approval, submission evidence and corrections.
- Safeheld connects REP027 with daily CASS 15 control and board reporting.
What REP027 software should do
| Stage | Software control |
|---|---|
| Period opening | Confirm entity, reporting period and deadline |
| Data assembly | Use approved month-end reconciliation and source snapshot |
| Mapping | Populate fields using versioned reporting logic |
| Validation | Apply format, arithmetic, reconciliation and trend checks |
| Exceptions | Display unresolved breaks and required decisions |
| Approval | Record named review of the exact return version |
| Submission | Preserve output, receipt and regulator response |
| Correction | Retain original, reason, approval and resubmission |
Generating a formatted file without this control chain solves only the final mechanical step. For the content of each section, see our section-by-section guide to the monthly safeguarding return.
REP027 and CMAR are different
REP027 is the monthly safeguarding return for payment and e-money safeguarding institutions under SUP 16.14A. FSA056, often called CMAR, is a separate return for CASS medium and large investment firms.
A group may need both, but they should have distinct obligation owners, forms and evidence. Software experience with CMAR does not automatically demonstrate support for REP027.
Safeheld configures the payment and e-money safeguarding workflow around CASS 15 and SUP 16.14A rather than relabelling an investment-firm return.
Direct lineage from reconciliation
Every material REP027 value should trace to an approved source, reconciliation or attestation. The system should preserve the rule version used for the period.
If a user exports a figure, edits it in a spreadsheet and later submits it, the filed value has separated from the controlled value. The firm then needs another reconciliation between its return and its reconciliation system.
Safeheld produces the reporting workflow from the same governed position used for daily safeguarding. Reporting-specific adjustments are recorded separately with an owner and approval.
Month-end data snapshot
The platform should lock the source population used for the return. Later ledger corrections must not silently alter the record of what was prepared and approved.
A snapshot should retain the entity, account, currency, cut-off, input version and any late data. The preparer can then explain whether a later correction requires a revised return or only prospective remediation.
Source-completeness checks should run before field population. A correct formula over a missing account remains wrong.
Validation
REP027 validation should include:
- required-field and permitted-value checks;
- arithmetic and cross-field relationships;
- comparison with the month-end safeguarding record;
- comparison with previous periods;
- consistency with exception and breach populations; and
- explanation of unusual movements.
The platform should distinguish a blocking error from a warning requiring explanation. Every override needs attribution and evidence.
Open exceptions and notifications
The draft return should display open shortfalls, reconciliation failures and unresolved data problems. Users should not be able to complete the workflow without recording their treatment.
REP027 does not replace notification without delay where another rule requires it. Safeheld connects the event record to both workflows so the firm can see whether a matter was corrected, reported monthly and notified separately where required.
This removes the risk of a breach register, return and board pack counting different events.
Approval and submission evidence
Approval should attach to the exact output submitted. Safeheld records the reviewer, time, return version and decision.
The record should include the generated file, validation output, submission attempt, regulator receipt and any rejection. A corrected resubmission remains linked to the original rather than replacing it.
Where electronic filing is supported, confirm the exact live submission method during implementation. Generating a return and submitting it are separate capabilities.
Board packs
The board pack should use the same figures as REP027 but explain them differently. Directors need trends, material exceptions, repeated causes, control failures and remediation, not a copy of the form.
Safeheld produces regulatory and management views from the same controlled data. This keeps the filed position consistent with the position overseen by the governing body.
Corrections
A correction should record what changed, why, which source or mapping was wrong, the impact, approval and resubmission evidence. The workflow should also create remediation for the underlying cause.
Repeated corrections may show that a source, definition or review control is defective. Safeheld makes the correction history available for management information and audit.
Why Safeheld
Safeheld does not treat REP027 as an isolated form. It connects monthly reporting with the daily records, reconciliations, exceptions and approvals on which the return depends.
That creates one evidence chain from source data to submitted value. It reduces manual rekeying, preserves version history and helps firms answer supervisory questions without reconstruction.
Request a REP027 demonstration and ask us to trace a return figure back to the underlying reconciliation and source records in real time.
Frequently asked questions
What is REP027?
It is the monthly safeguarding return required under SUP 16.14A for safeguarding institutions within scope.
When is REP027 due?
It is generally due within 15 business days after each calendar month end.
Is REP027 the same as FSA056 or CMAR?
No. Those are separate reporting arrangements for certain investment firms.
Can REP027 be fully automated?
Data assembly, mapping, validation and workflow can be automated. Accountable review and regulatory decisions should remain controlled by the firm.
Does Safeheld submit REP027 directly?
Submission capability depends on the deployed product and current FCA interface. Confirm the live method during procurement. Safeheld preserves the reporting and submission evidence workflow in either case.