Skip to content
Novus Examples
csv371 B

Harbour Kitchen Group: GST/HST return lines

GST/HST return lines for Harbour Kitchen Group. The six return lines as a three-column CSV keyed by the line number the form uses, so a reader can address a value by its line rather than by its position. Line 109 and line 115 both carry 3152.57 CAD because there are no instalments to deduct.

csv

text/csv

371 B
Document Set
tax
Industry
retail
Source Kit
retail-commerce
Entity
Harbour Kitchen Group
Synthetic
true
As Of
2026-09-08

Binary csv: no in-browser preview. Download it above to open in a compatible application.

Specifications

Document Set
tax
Industry
retail
Source Kit
retail-commerce
Entity
Harbour Kitchen Group
Synthetic
true
As Of
2026-09-08
Rows
6
Currency
CAD
Net Tax
3152.57

Testing contract

Expected to pass
Scenario
Look up lines 105, 108 and 109 by line number and check the subtraction.
Expected result
Line 105 minus line 108 is 3407.82 minus 255.25, which is 3152.57, the value on line 109. A reader that addresses rows by index rather than by line number lands one row out on line 110, which is a real zero and not an absent value.

What is a .csv file?

CSV (Comma-Separated Values) is a plain-text tabular format where rows are lines and fields are separated by commas, with quoting rules for values that contain delimiters, quotes, or newlines. It has no formal type system and depends on encoding and dialect conventions. It is the most portable format for tabular data exchange.

How to use this file

Use an example CSV to test parsers against quoting and embedded-delimiter edge cases, header handling, encoding detection, and import pipelines into databases or spreadsheets.

How to use this file for testing

“Harbour Kitchen Group: GST/HST return lines” is a deterministic Novus Examples fixture for Data import, CSV parsing. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 6 rows. 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 pandas as pd

df = pd.read_csv("gst-hst-return.csv")
print(df.head())
print(df.dtypes)

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