invoice-outlisted

# Invoice Out Build Standard **Spec:** AIP-BS-INVOICE-OUT · **Version:** 2026-09-26 · **Canonical:** https://aipathway.com.au/explore-ai/invoice-out-build-standard Open specification: the invoice exists in the ledger the day the job finishes. The job system's completion event as the only trigger; every line traced to the job and priced only from the price book read at draft time, with a line the book does not hold parking the invoice; a variation billed only with a signed acceptance attached; a stage invoice for jobs under a building contract, never a progress claim; one invoice per job written once into Xero, MYOB or the job system with its own id back; a release gate held by a person or a threshold rule; parked invoices as a queue with a reason and an owner. Free to implement, with a conformance checklist. ## Read the standard first The full specification is in `reference/invoice-out.md` in this skill. Read it before writing code. It is about 3,000 words and it is the whole job: the checks in order, the objects with their fields, what must never be automated, and a pass test. For the current version, fetch https://aipathway.com.au/explore-ai/invoice-out-build-standard.md. This copy is 2026-09-26. The checks are also structured data, so you do not have to infer a test plan from the prose: https://aipathway.com.au/explore-ai/invoice-out-build-standard/checks.json gives each check a stable id, the ports it observes, what to inject and what to assert. `npx @aipathway/conf