Sample record

What a reviewer sees before signing

An excerpt from a real assisted pass, run on 31 October 2026 against a fictional Payables brief for a UK business called Northstar Retail UK. The task shown is Oracle Fusion's Manage Payment Terms. Wording is lightly trimmed for the page; the values, sources and risks are as the pass recorded them, and no task has been signed off yet.

Manage Payment Terms

Not reviewed

The brief: set up Payables for a business unit called Northstar Retail UK, on the Northstar UK Ledger, in GBP, with a standard payment term of 30 days, a second approver for invoices over £10,000, and suppliers paid weekly by BACS on Thursdays. This task drew 27 proposals. Each value says where it came from, and a quote from the brief is checked word for word against the brief.

  • From the brief
    AP_TERM_LINE.DueDays: 30Quote verified: “standard payment term of 30 days”. The brief doesn't say whether the 30 days run from the invoice date, so the specialist confirms the date basis.
  • Model inference
    AP_TERM_LINE.DuePercent: 100A single-instalment term needs one line, and percentages must total 100. The brief mentions no split instalments.
  • Model inference
    AP_TERM_LINE.SequenceNum: 1One line for a single-instalment term.
  • Oracle default
    AP_TERM_HEADER.EnabledFlag: Y · Type: STDOracle's defaults on create, named for the specialist to accept or change.
  • Oracle default
    AP_TERM_HEADER.StartDateActive: system dateOracle's default if omitted; the specialist may want a fixed go-live date instead.

Left unanswered, on purpose: the payment-term name. The brief doesn't give one, and the model is not allowed to invent it.

Risks, and what's routed elsewhere

  • High
    The payment-term name is not in the brief. Without it the required identity is missing, and preview is blocked.
  • Medium
    If a 30-day term already exists, creating another could confuse supplier and invoice defaults.
  • Medium
    The weekly Thursday BACS schedule belongs to payment methods and payment process setup, not this task.
  • Medium
    The £10,000 second-approver rule is an invoice approval requirement, not a payment-term setting, and could be lost if no other task picks it up.

The same pass caught a quieter trap on the Manage Bank Charges task: if the currency is left out, Oracle defaults it to USD. The model proposed GBP instead, labelled it an inference, and flagged it as a high risk for the specialist to confirm.

Then a named person decides

A specialist reads the values, their sources and the risks, then approves the task or returns it with a reason. The decision is recorded against their name in the workspace's audit chain, checked again every time the seal is verified, and can be shared with the client as a read-only link that checks the seal when it's opened.

Signed off bynot yet signed
Registry
Oracle Fusion
Run
31 Oct 2026
Tasks in the pass
7
Estimated model cost
about $0.86

Want to see it on your own brief?

We'll walk you through a pass on a sample of your own work.

Book a walkthrough