1. Regulatory Reporting
  2. Features
  3. Regulatory Returns
Feature · Regulatory Returns

Regulatory Returns

Prepare return packages linked to assessments and record review decisions.

OverviewReturns awaiting decision
Regulatory Reporting · Regulatory Returns

Returns awaiting decision

Approval conditions

New
ParentOrganizationAuthorityPeriod endReported amount USDSubmission receipt
ASS-12832ORG-1452ATH-76810 Oct410SR-165
ASS-19348ORG-8641ATH-17810 Oct740SR-728
ASS-98987ORG-2977ATH-99511 Oct680SR-557
ASS-85336ORG-5457ATH-23617 Oct230SR-541
ASS-73343ORG-6989ATH-21022 Oct290SR-238
6 of 6 records
ATH-768Regulatory returns · RR-70213
Submitted
ParentASS-12832
OrganizationORG-1452
Period end10 Oct
Reported amount USD410
Submission receiptSR-165
Example screen with sample data

What you can do

Build a return from an assessed period

A regulatory return belongs to an organization and a parent assessment. The Reporting Analyst records the authority, period end, reported amount in US dollars and submission receipt. The Control Owner submits the prepared package for independent review. The package carries a revision and status so the reviewer can identify the version being considered. The review decision links to the parent assessment and its source revision. The assessment link lets the team follow the package back to its scope, tests, findings and evidence.

Suppose a reporting team prepares a quarterly return. The analyst checks that the assessment covers the period and entity named on the package. A return drafted against another organization’s assessment would be a poor handoff, even if its amount appears plausible. The reviewer should inspect the linked assessment and the package details before approving the submitted version.

How the work is organized

  • Package identity. Organization and parent assessment tie the return to the entity and assurance work.
  • Reporting details. Authority, period end, amount and submission receipt describe the package under review.
  • Decision state. Revision, decision date and status show which submitted version received the decision.

What to agree during setup

Agree who prepares the amount and where the source calculation is maintained. Decide how the reporting team captures a receipt and how it relates to the package. If a separate filing system submits the return, define that connection and how its accepted reference is brought back to this record. The app’s return record is the reviewable package and receipt trail for the team.

Assign an Independent Assurance Reviewer who is separate from the person preparing the package. Agree what the reviewer checks before approval: the entity, period, assessment outcome, supporting evidence, amount and receipt. Determine how a rejected package is corrected and resubmitted under a new revision, preserving the earlier decision’s context.

Check the handoff on an actual case

Prepare a draft return for a named organization and completed assessment period. Fill in the authority, period end, amount and submission receipt from the team’s actual supporting material. Have the Control Owner submit it for review. Have the reviewer compare the package with the parent assessment, its decision and unresolved findings. Record either an approval or rejection, including the decision date.

Then change a package detail and verify the team can identify which revision was reviewed. A completed return should be explainable from the package to its assessment and from that assessment to the tests and any retests. The receipt should be a reference the reporting team can use in its filing reconciliation.

What your team sees

  • Returns awaiting decision — Open submitted packages with authority, period and revision for review.
  • Regulatory return status board — Track packages from draft through decision and completion.
  • Assessments in review — Check the parent assessment before accepting a return.

Follow the work through

Use the return review process for the approval handoff. Completion review covers receipt and exception checks.

What it keeps track of

Data model
Regulatory returns
Regulatory return packages prepared for review and approval.
Assessments
Control assessment engagements with period, scope and lifecycle.
Organizations
Reporting entities and their reporting configuration.
Review decisions
Independent review decisions recorded against an assessment revision.
Findings
Control testing findings with severity and remediation status.
Operation receipts
Durable receipts for guarded operations with stable operation keys.

Who uses it

Permissions
Reporting Analyst
, Independent Assurance Reviewer, Control Owner

Set up Regulatory Reporting your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started