Pine Assembly Workshop: Carrier invoice whose fuel surcharge uses the wrong basis on one line
Carrier invoice whose fuel surcharge uses the wrong basis on one line for Pine Assembly Workshop. The 13 billable shipments with a TOTAL row. Every line is correct except SHIP-07, whose fuel_surcharge was computed on the weight charge alone: 53.68 times 0.065 gives 3.49 instead of 5.05 on the base plus weight charge. The line is 1.56 light and the TOTAL row reads 859.63 against the correct 861.19.
csv
text/csv
- Document Set
- logistics
- Industry
- logistics
- Source Kit
- inventory-manufacturing
- Synthetic
- true
- As Of
- 2026-09-08
- Rows
- 14
Binary csv: no in-browser preview. Download it above to open in a compatible application.
Specifications
- Document Set
- logistics
- Industry
- logistics
- Source Kit
- inventory-manufacturing
- Synthetic
- true
- As Of
- 2026-09-08
- Rows
- 14
- Offending Shipment
- SHIP-07
- Stated Total
- 859.63
- Correct Total
- 861.19
- Difference
- 1.56
- Intentionally Invalid
- true
Testing contract
Expected to fail- Scenario
- Check the footer total against the line sum, then re-rate every line from rate-sheet.json and compare.
- Expected result
- The footer check passes: the 13 lines really do sum to 859.63. Re-rating from the rate sheet fails on SHIP-07 only, which is 1.56 short because the surcharge omitted the 24.00 base charge. An invoice audit that only checks that the lines add up accepts the whole document.
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
“Pine Assembly Workshop: Carrier invoice whose fuel surcharge uses the wrong basis on one line” 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: 14 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("carrier-invoice-fuel-surcharge-basis.csv")
print(df.head())
print(df.dtypes)Related files
- csvPine Assembly Workshop: Packing list whose carton count is short of the bill of ladingPacking list whose carton count is short of the bill of lading for Pine Assembly Workshop. The same packing list as packing-list.csv with the 12 lines of the fourth carton on each BOL-2026-0003 consignment removed. It now describes 52 cartons where the register declares 56. BOL-2026-0003 accounts for 12 pieces against a declared 16.
- xmlAlder Books Reconciliation: camt.053 whose entry count does not match its entriescamt.053 whose entry count does not match its entries for Alder Books Reconciliation. Well-formed XML with the same header, balances and TxsSummry as bank-statement-camt053.xml, but the final Ntry, TXN-024 for 206.00 on 2026-08-24, has been dropped. NbOfNtries still declares 24 while only 23 Ntry elements are present, and the entries now sum to 10442.00 against a CLBD balance of 10236.00.
- txtAlder Books Reconciliation: Fixed-width GL feed with one record a byte shortFixed-width GL feed with one record a byte short for Alder Books Reconciliation. The same 66 records as gl-feed-fixed-width.txt except that record 5 is 119 characters instead of 120: the final character of the 4-character currency field has been lost. Every other record is correct, so a reader that splits on newlines and slices by position reads USD as US on that one record and carries on silently.
- jsonAlder Books Reconciliation: Intentionally invalid semantic test recordsIntentionally 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.
- csvAlder Books Reconciliation: Journal batch with one entry out by 45.00Journal batch with one entry out by 45.00 for Alder Books Reconciliation. The same 3 journals as journal-batch.csv except that line 2 of JB-2026-08-02 credits 19.50 where its debit line is 64.50. That one journal is out by 45.00; the other two balance exactly, which is what makes this the realistic case: a batch-level check catches it only because nothing else offsets it.
- txtAlder Books Reconciliation: MT940 whose :62F: closing balance is out by 100.00MT940 whose :62F: closing balance is out by 100.00 for Alder Books Reconciliation. Identical to bank-statement-mt940.txt in every tag except :62F: and :64:, which state C260824USD10336,00 where the 24 :61: movements applied to the :60F: opening balance give C260824USD10236,00. The file is out by exactly 100.00 and nothing inside the statement explains the difference.
Generated by generation/industry_documents.py. Free for any use, no attribution required, license.