Added value: +{
+  "description": "SALES INVOICES ONLY, and only when the invoice WAS a marketplace order: the channel plus the order's own number, exactly as Taokeh's channel import keys it — 'SHOPEE-<order number>' (e.g. SHOPEE-2608246V81G729), 'TIKTOK-<order ID>' (digits), or 'SHOPIFY-<order ID>' (the numeric id in the Shopify admin address /admin/orders/<id>, NOT the '#1001' order name). It is posted as the sale's order reference and channel, so the invoice counts as a Shopee/TikTok/Shopify sale everywhere and a later live import of the same order is recognised instead of booked twice. A malformed key, a key already on an invoice in the books, or a key another staged document already carries is REFUSED and nothing is staged. A Shopee order number starts with the order's date (YYMMDD); when that is not docDate the document is FLAGGED for the owner (not refused) — check which date is right. Keep `reference` for the invoice's own number.",
+  "type": "string"
+}

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "string"
-  }
-]

Added value: +[
+  "number",
+  "string"
+]

Previous value: -"The line quantity as the old document states it. On a measurement-profile company (see intake_contract's `measureProfile`) OMIT it whenever you give thickness/width/tally, or write the measure detail into the description ('2x2 = 10/10 12/14') — the server derives the authoritative quantity from those, and a quantity sent alongside a parseable tally is NOT used to compute: it is kept as your advisory figure and shown to the owner beside the server's. On the default passthrough company nothing is derived, so this IS the quantity — send it."New value: +"The line quantity as the old document states it. On a measurement-profile company (see intake_contract's `measureProfile`) OMIT it whenever you give thickness/width/tally, or write the measure detail into the description ('2x2 = 10/10 12/14') — the server derives the authoritative quantity from those, and a quantity sent alongside a parseable tally is NOT used to compute: it is kept as your advisory figure and shown to the owner beside the server's. On the default passthrough company nothing is derived, so this IS the quantity — send it. On a timber company, for an item kept in tons, a per-ton quantity MORE than the tons a description's size and total feet give ('2x2 = 400'' is 0.2222 ton) stages the document flagged as not worked out, naming the tons, and it cannot be entered until it is staged again with the tons — send the tons, never the feet."

Previous value: -"The unit PRICE for a sales invoice, or the unit COST for a purchase bill — one field for both; Taokeh maps it. On a sales invoice: two decimals at most (whole sen, or whole cents in another currency), with any discount or tax in its own field; the same on a purchase bill."New value: +"The unit PRICE for a sales invoice, or the unit COST for a purchase bill — one field for both; Taokeh maps it. On a sales invoice: two decimals at most (whole sen, or whole cents in another currency); on a purchase bill: up to four decimals, exactly as invoiced (a per-foot or per-piece price that Taokeh converts to tons: two decimals). Either way, any discount or tax goes in its own field."

Previous value: -"The unit PRICE for a sales invoice, or the unit COST for a purchase bill — one field for both; Taokeh maps it."New value: +"The unit PRICE for a sales invoice, or the unit COST for a purchase bill — one field for both; Taokeh maps it. On a sales invoice: two decimals at most (whole sen, or whole cents in another currency), with any discount or tax in its own field; the same on a purchase bill."

Previous value: -"The piece tally as pieces/length_ft pairs — '10/10 12/14' is 10 pieces of 10 ft and 12 of 14 ft. With thickness and width this is what the quantity is derived FROM."New value: +"The tally as pieces/length_ft pairs — '10/10 12/14' is 10 pieces of 10 ft and 12 of 14 ft — OR the total running feet like 400' when the paper gives no cut list. Never invent a cut list (no '1/400'). With thickness and width this is what the quantity is derived FROM. Every token must be a pieces/length pair — a tally with anything else in it (a grade word, a stray number, '=') is refused; put grade words in the description. A total-feet tally needs thickness and width (or a named size) to work out the tons, and has no pieces, so it cannot carry a per-piece price — both are refused."

Added value: +"The unit the PRICE is quoted in. On a timber company: 'feet' = per running foot, 'pcs' = per piece, 'ton' or omitted = per ton. A per-foot/per-piece price is converted to the per-ton rate from thickness/width/tally, or from a cut list in the description ('2x2 = 10/10 12/14'); a description cut list the server cannot read cleanly is refused — send thickness/width/tally instead."

Added value: +false

Added value: +"The line text as PRINTED on the historical document, when it says more than the product name does — a size, a grade, a job reference. It rides onto the posted line and is what the owner reads beside the original. THIS IS ALSO WHERE A NON-STOCK LINE LIVES: a delivery charge, a transport fee or a labour line has no catalogued product, so put its own wording in `productRef` (it is required and must not be blank) and any extra detail here — the line stages, is flagged as unresolved, and the owner picks or creates the item on the review screen. Do NOT drop the line and do not fold it into another one."

Previous value: -"The line quantity as the old document states it. On a measurement-profile workspace (see intake_contract's `measureProfile`) OMIT it whenever you give thickness/width/tally, or write the measure detail into the description ('2x2 = 10/10 12/14') — the server derives the authoritative quantity from those, and a quantity sent alongside a parseable tally is NOT used to compute: it is kept as your advisory figure and shown to the owner beside the server's. On the default passthrough workspace nothing is derived, so this IS the quantity — send it."New value: +"The line quantity as the old document states it. On a measurement-profile company (see intake_contract's `measureProfile`) OMIT it whenever you give thickness/width/tally, or write the measure detail into the description ('2x2 = 10/10 12/14') — the server derives the authoritative quantity from those, and a quantity sent alongside a parseable tally is NOT used to compute: it is kept as your advisory figure and shown to the owner beside the server's. On the default passthrough company nothing is derived, so this IS the quantity — send it."

Previous value: -"Thickness in inches on a dimensional line — measurement-profile workspaces only (intake_contract shows this workspace's `measureProfile`). Give thickness + width + tally INSTEAD of a quantity and the server computes the authoritative quantity from them."New value: +"Thickness in inches on a dimensional line — measurement-profile companies only (intake_contract shows this company's `measureProfile`). Give thickness + width + tally INSTEAD of a quantity and the server computes the authoritative quantity from them."

Added value: +"The line quantity as the old document states it. On a measurement-profile workspace (see intake_contract's `measureProfile`) OMIT it whenever you give thickness/width/tally, or write the measure detail into the description ('2x2 = 10/10 12/14') — the server derives the authoritative quantity from those, and a quantity sent alongside a parseable tally is NOT used to compute: it is kept as your advisory figure and shown to the owner beside the server's. On the default passthrough workspace nothing is derived, so this IS the quantity — send it."

Added value: +"The piece tally as pieces/length_ft pairs — '10/10 12/14' is 10 pieces of 10 ft and 12 of 14 ft. With thickness and width this is what the quantity is derived FROM."

Added value: +"Thickness in inches on a dimensional line — measurement-profile workspaces only (intake_contract shows this workspace's `measureProfile`). Give thickness + width + tally INSTEAD of a quantity and the server computes the authoritative quantity from them."

Added value: +"Width in inches on a dimensional line. Goes with thickness and tally."

Previous value: -"'sales_invoice' = an invoice this workspace ISSUED to a customer. 'purchase_bill' = a bill a supplier issued TO this workspace (inventory lines only, same rule as create_bill_draft). Other kinds are not supported yet."New value: +"'sales_invoice' = an invoice this company ISSUED to a customer. 'purchase_bill' = a bill a supplier issued TO this company (inventory lines only, same rule as create_bill_draft). Other kinds are not supported yet."

Previous value: -"The document number exactly as printed in the old system (e.g. INV1603). Taokeh keeps it, so the customer's copy and yours still match. It must be unique in this workspace: a number already on the books is refused by name. Leave it out only if the document genuinely has no number. Before the first such invoice is entered, the owner must confirm where the real invoice series continues; Taokeh never silently starts migrated books at INV1."New value: +"The document number exactly as printed in the old system (e.g. INV1603). Taokeh keeps it, so the customer's copy and yours still match. It must be unique in this company: a number already on the books is refused by name. Leave it out only if the document genuinely has no number. Before the first such invoice is entered, the owner must confirm where the real invoice series continues; Taokeh never silently starts migrated books at INV1."

Previous value: -"The document number exactly as printed in the old system (e.g. INV1603). Taokeh keeps it, so the customer's copy and yours still match. It must be unique in this workspace: a number already on the books is refused by name. Leave it out only if the document genuinely has no number, and Taokeh will mint one."New value: +"The document number exactly as printed in the old system (e.g. INV1603). Taokeh keeps it, so the customer's copy and yours still match. It must be unique in this workspace: a number already on the books is refused by name. Leave it out only if the document genuinely has no number. Before the first such invoice is entered, the owner must confirm where the real invoice series continues; Taokeh never silently starts migrated books at INV1."

Added value: +{
+  "description": "The ORIGINAL this document was read off — the photo of the handwritten cash-sale slip, the scanned invoice page. Call request_attachment_upload FIRST, PUT the raw bytes to its uploadUrl, then pass the token here (there is no inline base64 on this door: a backlog export would blow the context). The file rides the staged row, the owner sees it BESIDE your figures on the document's own review screen, and it lands on the posted invoice or bill automatically when they approve. Re-staging the same sourceDocId WITH a token replaces the file; re-staging without one leaves the file already there untouched, so a bare filing is repairable.",
+  "type": "string"
+}

Added value: +{
+  "description": "TRUE if this line is a balancing / catch-all figure rather than a real item — rounding, an adjustment, 'misc'. Say so honestly: Taokeh flags a residual line that carries a material share of the document, because that is where a misread hides. Never use a residual line to force a total to tie — report the gap instead.",
+  "type": "boolean"
+}

Previous value: -"Your own arithmetic, kept for the owner to read. Never used to compute."New value: +"Your own arithmetic, kept for the owner to read. Never used to compute. On a handwritten slip this is what the owner checks you against — show the tally, the multiplication, the subtotal, in the order you did them."