Questions, answered

Click Get started, then use Proto to configure Regulatory Reporting for your business. Start with one organization, one business unit, a reporting period and a control assessment. Rehearse a test, independent decision and return package before expanding the scope.

An assessment records the organization, business unit, period, scope statement, owner and planned tests. Its linked tests and decisions describe the work completed for that scope.

The tester links a test to an assessment and control, then records the tested date, sample size, exception count, result and evidence reference. Supporting files can be attached to the assessment.

A failed test can become a finding with severity, description and links to the same assessment and control. A named owner receives a corrective action, and an independent reviewer records a retest.

The Independent Assurance Reviewer records a decision and reason against the assessment revision. The team can identify the version that was reviewed if the scope later changes.

A return links to an organization and parent assessment. It carries authority, period end, reported amount in US dollars, submission receipt, revision, decision date and status.

Yes. The reporting team can correct the package, and the Control Owner can submit its new revision for another independent decision. Keep the earlier decision and its reason understandable.

Record attachments belong to an assessment. Each has a title, evidence type, uploader, upload date and internal or shared visibility.

Use the operation receipt’s key, expected revision, result state, failure reason and effect references. Compare them with the records actually present before deciding the next action.

Operations Overview shows pending decisions, findings and failed operations. The working views also include Assessments in review, Actions submitted for verification and Returns awaiting decision.