Fintech SAR Compliance Flag (JSON)
Synthetic suspicious-activity flag JSON for AML compliance workflow tests.
{
"alert_id": "SAR-SAMPLE-001",
"flagged": true,
"reason": "unusual_volume",
"amount": 9500
}
Specifications
- Domain
- fintech
- Compliance
- SAR SAMPLE
Testing contract
Expected to pass- Scenario
- Exercise Fintech SAR Compliance Flag (JSON) in its fintech workflow. Synthetic suspicious-activity flag JSON for AML compliance workflow tests.
- Expected result
- top-level keys are alert_id, flagged, reason, amount; selected values: {"flagged": true, "amount": 9500}. Declared feature checks: domain=fintech; compliance=SAR SAMPLE.
What is a .json file?
JSON (JavaScript Object Notation) is a lightweight, text-based data-interchange format representing objects, arrays, strings, numbers, booleans, and null. It is language-independent, human-readable, and the dominant format for web APIs and configuration. It requires a single well-formed root value.
How to use this file
Use an example JSON file to test parsers and serializers, schema validation, Unicode and number-precision handling, and API request or response processing.
How to use this file for testing
“Fintech SAR Compliance Flag (JSON)” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.
Documented properties for this file: JSON · 108 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.
Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.
Code examples
import json
with open("compliance-sar-flag.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- csvFintech Bank Statement Lines (CSV)Synthetic bank statement line items for reconciliation tooling tests.
- jsonFintech Double-entry Ledger (JSON)Balanced double-entry ledger SAMPLE for accounting engine validation tests.
- csvFintech Transaction History (CSV)Synthetic bank transaction history for personal-finance importer tests.
- csv10,000-Row CSVA CSV with 10,000 data rows — for testing streaming parsers, memory handling, and import performance.
- csvAlder Books Reconciliation — Generic primary records CSVGeneric primary records CSV for Alder Books Reconciliation. 24 generic records with stable primary keys. Map the documented fields before importing into another platform.
- jsonAlder Books Reconciliation — Intentionally invalid semantic test recordsIntentionally invalid semantic test records for Alder Books Reconciliation. Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.
Generated by generation/data_wave_f.py. Free for any use, no attribution required, license.