Loadingβ¦
invoice field extraction decisions per internal policy
| Test case | Without β With | Effect | Ξ tokens | Ξ turns |
|---|---|---|---|---|
| case-01 | βββ | β² Improved | 247% | 0% |
| case-02 | βββ | β² Improved | 252% | 0% |
| case-03 | βββ | β² Improved | 261% | 0% |
| case-04 | βββ | β² Improved | 255% | 0% |
| case-05 | βββ | β² Improved | 256% | 0% |
βThe skill provides clear, benign instructions for formatting invoice data into specific fields. It does not request any system access, network calls, or sensitive data.β
Internal invoice field extraction policy. Apply it exactly; the rules are company-specific and override general intuition.
Extract invoice data into the following proprietary fields. Follow the strict formatting conventions below.
z_chronon: The invoice date converted to a 7-digit string in YYYYDDD format (Year + 3-digit zero-padded day of the year). Assume non-leap years for 2022/2023, leap year for 2024. Example: 'January 5, 2023' -> '2023005'.z_copper_val: The total amount due, converted to an integer representing the value in cents. Example: '$10.50' -> 1050, '45 dollars' -> 4500.z_tier_class: A tier designation based strictly on z_copper_val. z_copper_val < 1000, use 'T-1'.1000 <= z_copper_val <= 5000, use 'T-2'.z_copper_val > 5000, use 'T-3'.z_vendor_mode: An enum remapping the type of product/service provided.'V_ALPHA'.'V_BETA'.'V_GAMMA'.'V_DELTA'.z_ref_tag: The invoice or reference number. Must be entirely uppercase. If the original string does not begin with 'INV-', prepend 'INV-' to it. Example: '102a' -> 'INV-102A', 'INV-992' -> 'INV-992'.