Bank Transactions (JSON, 60 records)
The bank transactions as a JSON array — the format twin of the CSV, for import and reconciliation testing.
[
{
"txn_id": "T00051",
"date": "2025-11-01",
"account": "****1043",
"description": "Salary deposit",
"category": "income",
"amount": 1926.98,
"currency": "USD",
"balance": 10851.98
},
{
"txn_id": "T00057",
"date": "2025-11-01",
"account": "****1043",
"description": "Book Nook",
"category": "retail",
"amount": -39.24,
"currency": "USD",
"balance": 10647.94
},
{
"txn_id": "T00024",
"date": "2025-11-02",
"account": "****1043",
"description": "Bright Pharmacy",
"category": "health",
"amount": -12.81,
"currency": "USD",
"balance": 7920.74
},
{
"txn_id": "T00056",
"date": "2025-11-03",
"account": "****4021",
"description": "City Transit",
"category": "transport",
"amount": -153.79,
"currency": "USD",
"balance": 7661.32
},
{
"txn_id": "T00041",
"date": "2025-11-04",
"account": "****4021",
"description": "Fuel Stop 24",
"category": "fuel",
"amount": -153.54,
"currency": "USD",
"balance": 5940.88Specifications
- Records
- 60
- Schema
- txn_id, date, account, description, category, amount, currency, balance
- Domain
- banking
- Note
- synthetic; account numbers masked
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
“Bank Transactions (JSON, 60 records)” is a deterministic Novus Examples fixture for Data import, Conversion testing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.
Documented properties for this file: 60 records · schema: txn_id, date, account, description, category, amount, currency, balance. 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("transactions.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- xmlISO 20022 Credit Transfer — pain.001 (XML)A sample ISO 20022 customer credit-transfer initiation (pain.001.001.09) — a single payment with debtor/creditor parties, IBANs, BICs, amount, and remittance info. IBANs are published documentation examples; a fixture for testing payment-message parsers and bank integrations.
- jsonColumnar Nulls Schema (JSON)JSON description of nullable columns in the null-heavy columnar fixtures.
- gexfDirected Acyclic Pipeline - GEXF 1.3A six-stage software pipeline DAG for testing dependency import, cycle checks and reproducible topological sorting. This GEXF 1.3 member carries the same node IDs, edge IDs, directions and weights as its two format twins.
- graphmlDirected Acyclic Pipeline - GraphMLA six-stage software pipeline DAG for testing dependency import, cycle checks and reproducible topological sorting. This GraphML member carries the same node IDs, edge IDs, directions and weights as its two format twins.
- jsonDirected Acyclic Pipeline - JSON edge listA six-stage software pipeline DAG for testing dependency import, cycle checks and reproducible topological sorting. This JSON edge list member carries the same node IDs, edge IDs, directions and weights as its two format twins.
- gexfDirected Dependency Cycle - GEXF 1.3A four-service directed cycle whose only valid topological result is failure, for dependency-analysis regression tests. This GEXF 1.3 member carries the same node IDs, edge IDs, directions and weights as its two format twins.
Generated by generation/data_domains.py. Free for any use, no attribution required — license.