Azzindani/Tern_Business_Documents

Fabricated business documents

Every document here is fabricated: companies, people, addresses, tax numbers, bank accounts and amounts are invented. Tax numbers have the shape of the real ones but are drawn at random, so one may by chance equal a real number; e-mail addresses end in .example. No real company's document was used. They are made by a seeded generator (fabricate/ in the Tern repository), so the same arguments give the same files.

What is in a chain

One buying-and-selling story per folder, from a request for quotation to the invoice and its match:

rfq → quotation → purchase_order (with its approval levels) → sales_order → proforma_invoice (some) → delivery_note → proof_of_delivery (signed) → goods_receipt → invoice → tax_invoice (Indonesia) → credit_note (some), and the packet the supplier sends: the invoice alone, with a tax invoice, with a proof of delivery, or bundled with the order, the delivery note and an attachment, as one multi-page PDF.

Layout

fabricated/<REGION>/<chain id>/
  chain.json            the whole story: parties, every document, the expected match, notes on what was done to it
  packet.pdf            what the supplier sends, one file
  packet.json           the parts of packet.pdf with their page ranges, and the expected decision (post or hold, with reasons)
  documents/NN-<kind>.pdf   each document on its own
  documents/NN-<kind>.json  its ground truth: every field and every line
  degraded/<scenario>/packet.pdf    the same packet as a bad document: scan, fax, phone photo, blur, scratches, stains, stamps, a struck-through line, an altered total, a missing page...
  degraded/<scenario>/degrade.json  what was done to which page, where each page came from, and the right handling (read_same, best_effort or hold, with reasons)
manifest.jsonl          one line per chain
degraded.jsonl          one line per bad-document packet
real/                   reserved; empty unless real files have been cleared for publication, and then marked as such

Regions and what varies

Indonesia, Singapore, Malaysia, Thailand, Philippines, Vietnam, United States. Five page layouts, long tables over several pages with the sum carried forward, labels in the local language or English, local number formats, tax rules (a separate tax invoice in Indonesia, zero-rated cross-border sales in USD). About a quarter of the invoices have something wrong on purpose: a price above the order, more billed than received, a missing order number, a total that does not add up, a notice changing the bank account, an order missing its last approval. packet.json says what is wrong, so a system's decision can be scored.

Limits

These are drawn documents. The degraded/ packets add drawn damage (blur, stains, strikes, stamps, missing pages), which is not the same as photographs of real paper: real stamps, handwriting and odd layouts are the hard part and are only partly here. This release: 100 chains, 18 of them with something wrong, 40 with an invoice of more than 12 lines, packet types full_bundle, single, invoice_support, invoice_tax.