AesirX ComplianceOne | Circular 41 Payment-System Supervision

A sourced due date for reports the Circular clocks. Each submission check records the report, the reporting period and its last day. Where Circular 41 states the clock for that period, ComplianceOne computes the due date from that deadline record. Article 15(2)(e) permits a move only for an official public holiday, Tết or a weekend. The reporting calendar uses a separately reviewed official schedule with its source, coverage, workweek and timezone. Company holidays do not extend the legal deadline. A sourced applicable official make-up working day counts as working. Missing or insufficiently covered calendar evidence leaves the adjusted date unconfirmed; it does not extend the filing duty. The check names the record the date came from. The date is fixed when the check is approved, and an unsent report past it reads Overdue in words. Where no installed record states a clock, you record the provision the deadline comes from, and ComplianceOne adds no date of its own.

The submission, recorded after approval. A check keeps who prepared the report, the signatory, the channel used, the date and time your organisation submitted, the signed-file and receipt references and the filled forms it covers. Circular 41's records make the signatory and the channel required to record a submission, and the preparer required to approve, and the register holds you to that. You record the submission after the check is approved without reopening the approval.

Separate company and statutory calendars. Settings keeps operational company closures separate from the sourced calendar these reporting clocks select. An authorised maintainer records the applicable official sources, weekend/workweek, public holidays, Tết and official make-up working days, with an explicit coverage and completeness decision. ComplianceOne checks the record and uses that declared basis; it does not supply or authenticate government schedules. A reviewed interval with no exceptions differs from an unconfigured empty calendar. Company holiday edits cannot extend these statutory dates. Approved checks keep their historical date and calendar evidence; current changes are shown separately, without rewriting the approval. Earlier approvals without calendar provenance say so. There is no reopen or replacement workflow for a historical approved check in this change.

Requests from the Supervision Unit. The Requests and corrections tab records each request: its kind, its reference, what it asks for, its owner and the deadline the request itself states. ComplianceOne computes no deadline for a request. Where the request states none, the record says so and never reads overdue. A request to explain and resend data also records the section, the defect type, the root cause and the correction, and an answer sent after the stated deadline shows as late.

Interruptions measured from the incident record. You record the interruption window once, on the incident: when the service stopped, when it came back and when remediation was completed. An immediate notice is owed once the interruption lasts longer than the 30-minute threshold in the installed record. The incident's own card says so to anyone who can read the register, and links to the notice. The register lists every such interruption with no notice recorded, and its overview counts them. The Form No. 03 incident report is due 3 working days after remediation is completed, counted from that record, not from detection or from closing the ticket. You record when the notice was sent, what it said and when the report went, and you link the filled Form No. 03, labelled official. A report past its due date reads Overdue.

Change and contract notices on their working-day clocks. On the Change and contract notices tab, an operator's process, risk-policy or membership-rule change is due 15 working days after the change. An e-wallet provider's cooperating-bank contract is due 3 working days after it takes effect. Both due dates are counted from the installed deadline records, and each notice keeps the date you sent it and its evidence.

Evidence files, bound to what they prove. You upload the signed report file, the receipt, the notice email or the report on a recommendation to the record it proves. That is a check, a notice, a request, a recommendation or an inspection. A file a record names cannot be deleted, and a file that is no longer held says so. A text reference still records material held elsewhere.

Recommendations that close on your report. The Recommendations tab lists every recommendation in one place: those from inspection minutes and those from a supervision letter, which needs no inspection record. Each keeps its source, reference, owner, deadline, the date your report was sent and the date you closed it internally. A recommendation from a supervision letter also keeps the measures taken and its evidence files; one from an inspection is recorded on the inspection, with the inspection's files. A recommendation with a deadline cannot be closed internally before its report is sent. An inspection cannot be closed while one of its recommendations with a deadline has no report date, and the register names the one still open.

Inspections with their decision and minutes. Each inspection records the reference of the inspection decision and the date it was received, and the reference of the minutes. Every change is kept in the audit trail.

Evidence packs an inspector can read. You can export one evidence pack per reporting period and one per inspection, as CSV, Excel, PDF or Word. The period pack lists the calendar rows with their state and due-date source, and the checks with who prepared, signed and sent them. It adds the requests, the recommendations, the linked incidents, the corrections and which holiday calendar the due dates used. The inspection pack adds the decision and the minutes. Files appear by name and SHA-256 fingerprint, never by content. Every record is labelled official or internal, and the file contains no calculated supervisory figure.

Forseti drafts, a person decides. In the Form Filler, Forseti AI can draft the narrative of a Form No. 01 or Form No. 02 for a person to accept or reject field by field. It does not read the register's records.

ComplianceOne records and evidences your reporting. It does not calculate your indicators, submit or transmit a report, connect to a State Bank system, supervise a payment system or certify that a report is complete, correct or received; you send the reports through the State Bank's systems.