VAT & Company Data Snapshot for Tax Ingestion

Overview

A captured API snapshot of the platform’s company and VAT-registration data used to design and test the VAT-ingestion flow. It documents the real data shape behind multi-business VAT handling, registration dates, filing frequency, cash-receipt basis, tax country and registration status.

Why It Exists

Building reliable VAT ingestion and return-generation requires a faithful model of how businesses, their VAT registrations, and document-processing counters are structured. A representative data export served as the reference fixture for that work.

What We Built

A paginated REST export (4octbackup.json, ~290 company records) capturing each business with its financial-year-end, document counters (uploaded/processed/rejected), Plaid and Stripe linkage fields, and a nested vats array describing every VAT registration, sales_tax_country_code (e.g. IE), registration_date, first_report_date, filing frequency, cash_receipt_basis, and status. This snapshot grounds the VAT-coding and tax-return automation in the platform’s actual schema.

Technologies & Approach

A structured JSON capture of the platform’s company/VAT API, suitable as a fixture for developing and validating ingestion logic, and showing integration points with Plaid (bank connectivity) and Stripe (billing).

Outcome / Impact

Provided a concrete, anonymisable reference for the VAT data model that informed the VAT-code cache and the n8n tax-reconciliation workflows. As a data artefact it de-risked development of the ingestion layer.

Capabilities Demonstrated

• Reverse-engineering and documenting real-world financial data models
• Working with multi-jurisdiction VAT registration and filing concepts
• Producing API fixtures that anchor pipeline development and testing