Skip to content
Novus Examples
json1.5 KB

Alder Books Reconciliation — Intentionally invalid semantic test records

Intentionally 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.

Data importError handling
Preview, first 50 linesjson
{
  "schemaVersion": 1,
  "kitId": "business-accounting-reconciliation",
  "purpose": "Intentionally invalid records for local semantic validation; do not import.",
  "cases": [
    {
      "id": "duplicate-primary-key",
      "table": "bank",
      "rows": [
        {
          "transaction_id": "TXN-001",
          "date": "2026-08-01",
          "description": "Client receipt",
          "opening_balance": 5000,
          "amount": 650,
          "closing_balance": 5650.0,
          "currency": "USD"
        },
        {
          "transaction_id": "TXN-001",
          "date": "2026-08-01",
          "description": "Client receipt",
          "opening_balance": 5000,
          "amount": 650,
          "closing_balance": 5650.0,
          "currency": "USD"
        }
      ],
      "expectedError": "duplicate-primary-key"
    },
    {
      "id": "wrong-key-type",
      "table": "bank",
      "rows": [
        {
          "transaction_id": 42,
          "date": "2026-08-01",
          "description": "Client receipt",
          "opening_balance": 5000,
          "amount": 650,
          "closing_balance": 5650.0,
          "currency": "USD"
        }
      ],
      "expectedError": "schema-type"
    },
    {
      "id": "orphan-reference",
      "table": "journal",
      "rows": [
… 63 lines total: download for the full file.

Specifications

Kit
accounting-reconciliation
Industry
finance
Schema Version
1
Synthetic
true
As Of
2026-09-08
Cases
3
Intentionally Invalid
true

Testing contract

Expected to fail
Scenario
Use intentionally invalid semantic test records in the Alder Books Reconciliation bank-import, ledger, reconciliation, budgets, expenses, receivables, management-reporting workflow.
Expected result
Three independent cases report duplicate-primary-key, schema-type and foreign-key errors. JSON syntax remains valid.

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

“Alder Books Reconciliation — Intentionally invalid semantic test records” is a deterministic Novus Examples fixture for Data import, Error handling. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: JSON · 1,536 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("invalid-records.json") as f:
    data = json.load(f)
print(type(data), len(data))

Related files

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