Title: Pine & Birch — Sample Business Document
Author: Pine & Birch
Document comments: pine-and-birch.com/sample-files

Sample Business Document
Published by Pine & Birch · pine-and-birch.com/sample-files
1. Section 1
This is a sample document published by Pine & Birch, a technology consulting firm in Toronto. It exists so that developers, QA testers, and product teams have a realistic file to use when testing uploads, previews, conversions, and integrations. Everything in it is fictional and free to use for any purpose.
A good test document mixes the structures real users produce: headings at several levels, ordinary paragraphs, bulleted and numbered lists, a data table, an embedded image, and page breaks. Parsers and previewers that handle this file cleanly will handle most documents your customers upload.
Key points
Realistic structure: headings, lists, tables, and images
Deterministic content — identical on every download
Unicode, smart quotes, and currency symbols included
No macros, no scripts, no tracking of any kind
Free for any use, no attribution required
How to use this file
Download the file size that matches your test case.
Upload it to the system under test, or pass its path to your parser.
Compare the extracted text, page count, and metadata with the values shown on the download page.
Keep the file in your repository as a fixture; it will not change.
The table below shows fictional quarterly figures for a small distribution company. Values are deterministic, so the same file downloaded twice is byte-for-byte identical, which makes it safe to use as a fixture in automated tests and checksums.
When testing a document-processing pipeline, check the details that break silently: non-ASCII characters such as café, naïve, and Zürich; smart quotes like “this” and ‘that’; currency symbols (€, £, ¥); and long words that force line wrapping in narrow columns.
Accessibility matters even in test data. This document uses real heading styles rather than bold text, so screen readers and converters can build a proper outline from it. The image includes alternative text, and the table has a header row.
Nothing here should be treated as a template for legal, financial, or medical documents. It is a fixture — a stable, known input that lets you verify that the rest of your system behaves correctly.
Order ID | Date | Customer | Product | Qty | Total
PB-100001 | 2025-07-03 | Birchwood Interiors | Label Printer | 12 | $2,226.00
PB-100002 | 2025-01-27 | Harbourfront Textiles | Warehouse Scanner | 11 | $3,520.00
PB-100003 | 2025-07-14 | Silverline Freight | Data Migration | 4 | $9,600.00
PB-100004 | 2025-04-21 | Lakeshore Medical Supply | Warehouse Scanner | 1 | $320.00
PB-100005 | 2025-02-06 | Harbourfront Textiles | API Add-on | 3 | $297.00
PB-100006 | 2025-01-03 | Cedar & Co. Furniture | Support Plan (Monthly) | 1 | $450.00
PB-100007 | 2025-06-10 | Cedar & Co. Furniture | Support Plan (Monthly) | 5 | $2,250.00
PB-100008 | 2025-06-02 | Northwind Logistics | Warehouse Scanner | 7 | $2,240.00

Figure: embedded sample image.

2. Section 2
This is a sample document published by Pine & Birch, a technology consulting firm in Toronto. It exists so that developers, QA testers, and product teams have a realistic file to use when testing uploads, previews, conversions, and integrations. Everything in it is fictional and free to use for any purpose.
A good test document mixes the structures real users produce: headings at several levels, ordinary paragraphs, bulleted and numbered lists, a data table, an embedded image, and page breaks. Parsers and previewers that handle this file cleanly will handle most documents your customers upload.
Key points
Realistic structure: headings, lists, tables, and images
Deterministic content — identical on every download
Unicode, smart quotes, and currency symbols included
No macros, no scripts, no tracking of any kind
Free for any use, no attribution required
How to use this file
Download the file size that matches your test case.
Upload it to the system under test, or pass its path to your parser.
Compare the extracted text, page count, and metadata with the values shown on the download page.
Keep the file in your repository as a fixture; it will not change.
The table below shows fictional quarterly figures for a small distribution company. Values are deterministic, so the same file downloaded twice is byte-for-byte identical, which makes it safe to use as a fixture in automated tests and checksums.
When testing a document-processing pipeline, check the details that break silently: non-ASCII characters such as café, naïve, and Zürich; smart quotes like “this” and ‘that’; currency symbols (€, £, ¥); and long words that force line wrapping in narrow columns.
Accessibility matters even in test data. This document uses real heading styles rather than bold text, so screen readers and converters can build a proper outline from it. The image includes alternative text, and the table has a header row.
Nothing here should be treated as a template for legal, financial, or medical documents. It is a fixture — a stable, known input that lets you verify that the rest of your system behaves correctly.

Figure: embedded sample image.

3. Section 3
This is a sample document published by Pine & Birch, a technology consulting firm in Toronto. It exists so that developers, QA testers, and product teams have a realistic file to use when testing uploads, previews, conversions, and integrations. Everything in it is fictional and free to use for any purpose.
A good test document mixes the structures real users produce: headings at several levels, ordinary paragraphs, bulleted and numbered lists, a data table, an embedded image, and page breaks. Parsers and previewers that handle this file cleanly will handle most documents your customers upload.
Key points
Realistic structure: headings, lists, tables, and images
Deterministic content — identical on every download
Unicode, smart quotes, and currency symbols included
No macros, no scripts, no tracking of any kind
Free for any use, no attribution required
How to use this file
Download the file size that matches your test case.
Upload it to the system under test, or pass its path to your parser.
Compare the extracted text, page count, and metadata with the values shown on the download page.
Keep the file in your repository as a fixture; it will not change.
The table below shows fictional quarterly figures for a small distribution company. Values are deterministic, so the same file downloaded twice is byte-for-byte identical, which makes it safe to use as a fixture in automated tests and checksums.
When testing a document-processing pipeline, check the details that break silently: non-ASCII characters such as café, naïve, and Zürich; smart quotes like “this” and ‘that’; currency symbols (€, £, ¥); and long words that force line wrapping in narrow columns.
Accessibility matters even in test data. This document uses real heading styles rather than bold text, so screen readers and converters can build a proper outline from it. The image includes alternative text, and the table has a header row.
Nothing here should be treated as a template for legal, financial, or medical documents. It is a fixture — a stable, known input that lets you verify that the rest of your system behaves correctly.

Figure: embedded sample image.