Use cases

Triage invoice exceptions without approving payment

Proposed design Editorial draft

An invoice workflow can use semantic judgment to identify unclear descriptions or missing supporting explanations.

Accounts payable Synthetic demo Proposed design
Queue · synthetic items
    RulesPolicy in code
    JevChoice · Score · Noul
    Frontier LLMDraft only
    HumanAccountable action
    Inputs

    Select an item.

    Jev + rules

    Judgments appear here.

    Outputs

    Tickets, drafts, queues.

    Exact totals, supplier identity and approval authority remain deterministic controls. Our proposed first release creates an exception recommendation rather than initiating payment.

    Finance can then compare recommendations with established handling. Track false exceptions as well as missed issues, because unnecessary holds consume time and can damage supplier relationships even when no money moves incorrectly.

    Keep arithmetic out of semantic judgments. Separate outputs so an operator can see whether the exception arose from a numerical mismatch or an interpretation.

    Start with retrospective invoices and known review outcomes before any live hold is automated.

    Next step

    Start with retrospective invoices and known review outcomes.

    Pilot card

    What a first pilot of this decision needs. Proposed design, not a measured result.

    DecisionDoes this invoice exception need a buyer to explain it before payment is considered?
    State Jev seesInvoice line text, PO line text, match status from the ERP.
    Questions
    • Noul Is the invoice description too unclear to match to the PO line?
    • Noul Does the invoice appear to bill for something outside the PO?
    First action code may takeSend a query to the buyer with the flagged lines.
    Stays with a personApproval and payment.
    Measure firstExceptions cleared per week; days invoices spend on hold.
    Microsoft surfaceDynamics 365 Finance or SAP export; adapter; Teams task to buyer.
    Out of scopeApproving payment.