Loadingβ¦
invoice field extraction decisions per internal policy
| Test case | Without β With | Effect | Ξ tokens | Ξ turns |
|---|---|---|---|---|
| case-01 | βββ | β² Improved | 239% | 0% |
| case-02 | βββ | β² Improved | 249% | 0% |
| case-03 | βββ | β² Improved | 237% | 0% |
| case-04 | βββ | β² Improved | 160% | 0% |
| case-05 | βββ | β² Improved | 260% | 0% |
βThe skill provides clear, benign instructions for extracting and formatting specific fields from invoice text. It does not require any external tools, network access, or sensitive data handling.β
Internal invoice field extraction policy. Apply it exactly; the rules are company-specific and override general intuition.
All incoming vendor invoices must be mapped to the ZetaGlow-V4 schema. Do not use standard naming conventions. Extract exactly 5 fields according to the following strict conventions:
z_chronon: The invoice date converted to a 7-digit Julian/Ordinal date format (YYYYDDD). For example, January 1, 2023 becomes 2023001, and December 31, 2023 becomes 2023365.glow_bux: The total invoice amount converted to an integer representing cents. Ignore currency symbols. For example, $150.00 becomes 15000. $45.99 becomes 4599.t_level: The vendor tier code determined by the vendor's name prefix:T-1T-2T-3T-U (Unknown)nexus_tag: The department/category enum remap. N-CYBERN-PHYSN-MINDN-NULLis_rush: A boolean. Output true if the text contains any of the following keywords (case-insensitive): "urgent", "asap", "rush", "expedite". Otherwise, output false.