Skip to main content
Regulatory reporting in banking is a recurring, high-stakes obligation. Each submission — whether for Basel III capital adequacy, anti-money laundering filings, or consumer lending disclosures — requires pulling data from multiple systems, cross-referencing against regulatory definitions, and formatting the output to exact specifications. Manual compilation is slow, error-prone, and consumes significant analyst time every reporting cycle. Wayak automates this workflow end to end. You connect your transaction database and compliance documentation, define the regulatory metrics in your semantic layer, and schedule a playbook that compiles, validates, and delivers formatted reports on a recurring basis. An agent lets compliance officers query the underlying data conversationally to investigate flagged items or answer ad-hoc questions from regulators.

​
What you need

Data sources

  • Transaction database — completed transactions, posting dates, counterparties, amounts, and currency codes
  • General ledger — account balances, capital ratios, and reserve allocations
  • Core banking system — customer classifications, product mappings, and branch hierarchy

Knowledge spaces

  • Regulatory guidelines — upload Basel III framework documents, Dodd-Frank requirements, and local regulatory filing templates
  • Internal compliance procedures — data validation checklists, exception handling rules, and signoff workflows
Semantic layer: Define these in your ontology before setting up the agent.
ComponentNameDefinition
ObjectTransactionMaps to the transactions table. Represents a single financial transaction with amount, type, and counterparty
ObjectRegulatory FilingMaps to filings in the compliance system. Represents a single report submission with status and period
MetricCapital Adequacy RatioTotal qualifying capital / risk-weighted assets, as defined by Basel III Pillar 1
MetricLarge Exposure RatioAggregate exposure to a single counterparty / total capital, subject to 25% regulatory ceiling
DimensionRegulatory CategoryClassifies transactions by reporting category (credit risk, market risk, operational risk)
DimensionFiling PeriodGroups data by reporting period (monthly, quarterly, annual)
See building a semantic layer for a step-by-step guide.

​
Agent setup

1

Create the agent

Go to Agent Space → New agent.
FieldValue
NameCompliance Reporter
RoleRegulatory Reporting Analyst
GoalCompile regulatory report data, validate figures against defined rules, and answer compliance queries using transaction data and regulatory guidelines
2

Set the description

You are a meticulous regulatory reporting analyst. You compile data for regulatory submissions by cross-referencing transaction records against regulatory definitions and internal validation rules. You flag any data inconsistencies or threshold breaches and cite the specific regulation or policy section that applies. You never finalize a submission — you prepare validated drafts for human review and signoff.
3

Scope data access

Grant access to:
  • Transaction database (all transaction types)
  • General ledger (balances, capital accounts)
  • Core banking system (customer classifications, product mappings)
  • Regulatory guidelines knowledge space
  • Internal compliance procedures knowledge space
  • Transaction and Regulatory Filing objects, Capital Adequacy Ratio and Large Exposure Ratio metrics
4

Add skills

Trigger: User asks the agent to compile data for a specific regulatory report and period.
  1. Identify the reporting template and required fields from the regulatory guidelines knowledge space.
  2. Query the transaction database for all transactions within the specified reporting period.
  3. Classify each transaction by regulatory category using the semantic layer dimension.
  4. Aggregate figures according to the report template structure (e.g., risk-weighted assets by category).
  5. Pull supporting balances from the general ledger to calculate capital ratios.
  6. Return a structured data summary aligned to the report template, with cell-level references to source data.
Trigger: User asks the agent to validate a compiled report.
  1. Load the compiled data for the specified report and period.
  2. Run cross-checks defined in the internal compliance procedures (e.g., assets must equal liabilities plus equity).
  3. Compare calculated ratios against regulatory thresholds (e.g., capital adequacy must exceed 8%).
  4. Flag any validation failures with the specific rule reference and the magnitude of the discrepancy.
  5. Return a validation summary with pass/fail status for each check and a list of items requiring manual review.
Trigger: User asks a question about a specific regulation or reporting requirement.
  1. Search the regulatory guidelines knowledge space for the relevant regulation or section.
  2. Extract the applicable rules, thresholds, and definitions.
  3. If the query involves data, pull the relevant figures from the transaction database or general ledger.
  4. Return the regulatory text with interpretation and any supporting data.

​
Automation

​
Playbook: Quarterly regulatory report

1

Set the trigger

Set the trigger to Schedule — Quarterly on the 5th business day after quarter-end, allowing time for transaction settlement and reconciliation.
2

Build the workflow

The workflow compiles, validates, and packages the quarterly regulatory submission:
  1. Query all transactions from the reporting quarter, joined with customer classifications and product mappings from the core banking system.
  2. Query the general ledger for quarter-end balances, capital accounts, and reserve positions.
  3. Action — classify and aggregate transactions by regulatory category using the semantic layer definitions.
  4. Condition — run validation checks against internal compliance rules. If any check fails, branch to an exception handling step that creates a review task and halts the report.
  5. Action — format the validated data into the regulatory report template, populating each required field.
  6. Delivery — send the draft report to the compliance team for review and signoff.
3

Configure delivery

  • Email — send the formatted draft report to the Chief Compliance Officer and regulatory reporting team
  • Slack — post a summary to #compliance-reporting with report status, key ratios, and any flagged items
4

Test and activate

Click Run now to test with the most recent quarter’s data, then toggle to Active.

​
What’s next

Loan application processing

Automate the intake and routing of loan applications using document review and risk classification.

All Finance & Banking use cases

See the full list.