Tern Client Services: Invoice register JSON
Invoice register JSON for Tern Client Services. The same 3 invoices as invoice-register.csv with the settlement rule stated: the retainer is drawn while a balance remains and the remainder is billed. totals.outstanding is 3200.00.
json
application/json
- Document Set
- professional-services
- Industry
- professional-services
- Source Kit
- crm-services
- Synthetic
- true
- As Of
- 2026-09-08
- Rows
- 3
Binary json: no in-browser preview. Download it above to open in a compatible application.
Specifications
- Document Set
- professional-services
- Industry
- professional-services
- Source Kit
- crm-services
- Synthetic
- true
- As Of
- 2026-09-08
- Rows
- 3
- Encoding
- UTF-8
Testing contract
Expected to pass- Scenario
- Apply the stated settlement rule to the invoices in issue order and compare with the retainer ledger.
- Expected result
- Applying the rule to 4000.00 of retainer settles SVCINV-1 and SVCINV-2 in full and leaves SVCINV-3 wholly unsettled, giving exactly the retainer_applied and outstanding columns in the file and the 0.00 closing balance on retainer-ledger.csv.
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
“Tern Client Services: Invoice register JSON” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.
Documented properties for this file: 3 rows · UTF-8. 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("invoice-register.json") as f:
data = json.load(f)
print(type(data), len(data))Related files
- csvTern Client Services: Contact export in the semicolon dialectContact export in the semicolon dialect for Tern Client Services. The same 8 contacts written with a semicolon delimiter. The billing_address field is still quoted because it contains newlines, but the tags field is now bare: "billing,renewals" needs no quotes when the delimiter is a semicolon, so the same value is quoted in contacts-export.csv and unquoted here. The file has 33 physical lines.
- csvTern Client Services: Contact export with quoted fieldsContact export with quoted fields for Tern Client Services. 8 contacts in 33 physical lines, because every billing_address is a four-line address held in one quoted field. The addresses also contain commas, the notes contain doubled double-quote characters where a quotation appears, and the tags field holds the comma-separated value "billing,renewals" inside quotes. Every one of those is correctly escaped RFC 4180.
- csvTern Client Services: Expense claim whose mileage was paid at a superseded rateExpense claim whose mileage was paid at a superseded rate for Tern Client Services. The same 6 lines as expense-claim.csv, but the three mileage amounts were computed at the superseded 0.58 per kilometre while the rate column still reads 0.62. The mileage subtotal is 136.88 where 236 km at the stated rate is 146.32, so the claim is 9.44 light and totals 212.13 instead of 221.57.
- csvTern Client Services: Expense claim with mileageExpense claim with mileage for Tern Client Services. 6 claim lines for August: 3 mileage lines worth 146.32 and 3 receipted lines worth 75.25, 221.57 in total. amount equals quantity times rate on every line, including the mileage lines where quantity is kilometres. Each line carries the project it belongs to and a receipt reference.
- csvTern Client Services: Mileage logMileage log for Tern Client Services. 3 client trips totalling 236 km. amount equals distance_km times rate_per_km on every row at the 0.62 per kilometre MIL rate from fee-schedule.csv, and the column sums to 146.32. Each trip names the project it was made for, so the mileage allocates cleanly to the three projects.
- csvTern Client Services: Professional fee scheduleProfessional fee schedule for Tern Client Services. Five rate codes. STD at 100.00 per hour is the only billing rate any time entry uses, which is why every row of timesheet-export.csv carries 100.00; OOH and TRV are defined but unused in this period and carry used_this_period false. MIL at 0.62 per kilometre is the mileage rate mileage-log.csv applies and COST at 58.00 per hour is the internal rate project-profitability.csv uses.
Generated by generation/industry_documents.py. Free for any use, no attribution required, license.