Skip to content
Testaroo
json13.4 KB

Bank Transactions (JSON, 60 records)

The bank transactions as a JSON array: the format twin of the CSV, for import and reconciliation testing.

Data importConversion testing
Preview, first 50 linesjson
[
  {
    "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.88
… 603 lines total: download for the full file.

Specifications

Records
60
Schema
txn_id, date, account, description, category, amount, currency, balance
Domain
banking
Note
synthetic; account numbers masked

Testing contract

Expected to recover
Scenario
Load the JSON twin of the legacy bank statement and reconcile each masked account chronologically.
Expected result
All 60 objects parse, but balances do not reconcile in published date order because accumulation preceded sorting. This twin preserves the historical defect; the P9 accounting kit supplies a corrected scenario.

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 Testaroo 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))

Generated by generation/data_domains.py. Free for any use, no attribution required, license.

Related files