Two real sample deliveries
Both source documents are public-domain U.S. federal government publications (freely reproducible, no private data). They were run through the exact same pipeline a paid order uses, to show what you actually get — including the case where the source data itself is genuinely messy.
Example 1 — clean case READY · 0 flags
Source: IRS Form W-9 instructions (6 pages) — four small classification tables (entity type → box to check; payment type → exemption; account type → whose name/TIN).
Result: 4 tables extracted, one sheet per table, headers kept, multi-line cell text preserved verbatim, every source row and column accounted for. Nothing flagged because nothing was ambiguous.
Download delivery package (.zip)
Contains: the .xlsx, the delivery note, and a checksummed file manifest — exactly what a buyer receives.
Example 2 — messy case REVIEW_REQUIRED · 62 flags
Source: Federal Reserve H.15 "Selected Interest Rates" (3 pages) — a dense statistical release with category header rows and a stacked date header.
Result: the full 53×9 grid extracted, every genuinely blank cell in the source kept exactly where it was — and all 62 blank positions listed by row and column in the delivery note, instead of a guessed number or shifted cells.
Download delivery package (.zip)
This is the case that matters most: the service hands you the mess with exact coordinates, not a falsely-tidy file.
Why both
Example 1 shows the normal case: exact, silent, done. Example 2 shows the hard case: the service does not hide the mess, it hands you the mess with coordinates. A buyer choosing a converter should care more about Example 2 than Example 1 — it's the case where a plain converter would either drop data or quietly fabricate it.