{
  "format": "boermans-digital.planning-worksheet",
  "version": 1,
  "kind": "process-canvas",
  "locale": "en",
  "process": "Fictional example: checking purchase invoices",
  "items": [
    {
      "id": "purpose",
      "status": "discuss",
      "note": "Fictional exploration: known suppliers with existing purchase orders. Objective: less rekeying and visibility of checks and open invoices. Extraction, approval, posting and payment are separate steps. Not a reviewed financial control framework.",
      "action": "Process owner and finance: confirm objective and required quality; keep payment approval outside the trial."
    },
    {
      "id": "boundaries",
      "status": "discuss",
      "note": "Start: fictional invoice through one test channel, in one currency. Steps: register, propose fields, compare with order/receipt, required authorised approval, test posting, verify final status. Finish: confirmed test posting or explained waiting/rejection status. No payments or changes to supplier master data.",
      "action": "Finance: confirm scope and separate decisions for checking, approval and posting."
    },
    {
      "id": "systems",
      "status": "discuss",
      "note": "Example systems: test intake channel, fictional order/receipt data and test ledger without payment functionality. Fields: supplier, invoice reference, order reference, amounts and currency. Sources and access still require confirmation; fictional documents only.",
      "action": "Finance and administrator: confirm approved test data, minimum access and a test environment without payment functionality."
    },
    {
      "id": "measurement",
      "status": "unknown",
      "note": "No volume, accuracy or time savings measured. Compare the entire current and proposed route. Measure corrections, incorrectly accepted discrepancies, active handling and waiting. Field recognition alone does not demonstrate successful invoice processing.",
      "action": "Finance: measure the same process boundaries and record recovery work and waiting separately."
    },
    {
      "id": "exceptions",
      "status": "discuss",
      "note": "F-01: normal case. F-02: partial receipt. F-03: different payment details. F-04: repeated document. F-05: missing confirmation. Assign an owner to discrepancies; no automatic approval, master-data changes or reposting. Expected outcomes are in the invoice trial log.",
      "action": "Finance, purchasing and administrator: assess the five test cases and record recovery and stopping criteria."
    },
    {
      "id": "ownership",
      "status": "discuss",
      "note": "Example roles: finance sets checks and assesses outcomes; purchasing/receiving explains differences; an authorised role approves under policy; administrator investigates unclear destination status. Roles and backup still require confirmation. Open question: where does most review or waiting work occur today?",
      "action": "Process owner: confirm authority, backup and the open trial question in the pilot checklist."
    }
  ]
}