Machine-readable contracts

Canonical Schemas

Each modeled Business Object has a human-maintained YAML definition and a normative JSON Schema 2020-12 contract. The links below intentionally expose the raw artifacts so adopters can inspect, copy or download them directly.

Representation rule: YAML is the maintained authoring representation; JSON Schema is normative validation. JSON publication must remain semantically identical to the YAML model.
Business ObjectYAML definitionJSON Schema
procurement.purchase-requisitionYAMLSchema
procurement.supplierYAMLSchema
procurement.purchase-orderYAMLSchema
procurement.receiptYAMLSchema
finance.invoiceYAMLSchema
finance.paymentYAMLSchema
finance.journal-entryYAMLSchema
finance.payment-runYAMLSchema
sales.customerYAMLSchema
sales.quoteYAMLSchema
sales.sales-orderYAMLSchema
sales.returnYAMLSchema
hr.workerYAMLSchema
hr.positionYAMLSchema
hr.leave-requestYAMLSchema
hr.payroll-runYAMLSchema
service.customer-caseYAMLSchema
service.service-requestYAMLSchema
logistics.shipmentYAMLSchema
logistics.deliveryYAMLSchema
logistics.inventory-transferYAMLSchema
manufacturing.work-orderYAMLSchema
manufacturing.production-orderYAMLSchema
manufacturing.material-issueYAMLSchema
projects.projectYAMLSchema
projects.project-taskYAMLSchema
projects.project-timeYAMLSchema
projects.project-costYAMLSchema

Reusable common schemas

Try them

The separate Autonomous Business Reference project provides a non-normative playground for representative capabilities while linking back to these canonical contracts.