Document template · generic.procurement.non_conformance_report
Supplier Non-Conformance Report (NCR)
- Render-verified
- Commercial
- Version 1.0.0
Non-conformance report (NCR) raised by a buyer against a supplier delivery, capturing the affected PO line, lot/batch, quantity received vs. quantity non-conforming, classification (minor|major|critical), root-cause initial hypothesis, immediate action (accept|reject|return|sort_100pct|concession), supplier response due date, corrective-action requirements, current status (open|awaiting_supplier|closed) and signatory. Aligned with ISO 9001:2015 clauses 8.6 (release of products and services) and 8.7 (control of nonconforming outputs), and with the 8D problem-solving methodology (D1–D8) commonly required by IATF 16949:2016 §10.2.3 customers.
JSON Schema
Fields in this template
Data sent to the API is validated against the template’s JSON Schema before anything is rendered. This template defines 14 fields:
| Field | Required | Type | Description |
|---|---|---|---|
| ncr_id | Required | string | |
| raised_on | Required | date | |
| raised_by | Required | object | |
| supplier | Required | object | |
| po_reference | Required | string | |
| item | Required | object | |
| non_conformance_description | Required | string | |
| classification | Required | enum | |
| root_cause_initial_hypothesis | Required | string | |
| immediate_action | Required | enum | |
| supplier_response_due_by | Required | date | |
| corrective_action_required | Required | string | |
| status | Required | enum | |
| signatory | Required | object |
POST /render
Generate it
One POST /render call: send your JSON, get the finished PDF back. Or skip the JSON entirely and describe the document in plain language on chut.app.
curl -X POST https://api.papii.eu/render \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"template": "generic.procurement.non_conformance_report",
"data": { ... },
"options": {"language": "en"}
}' -o non-conformance-report.pdf Frequently asked questions
What is “Supplier Non-Conformance Report (NCR)”?
Non-conformance report (NCR) raised by a buyer against a supplier delivery, capturing the affected PO line, lot/batch, quantity received vs. quantity non-conforming, classification (minor|major|critical), root-cause initial hypothesis, immediate action (accept|reject|return|sort_100pct|concession), supplier response due date, corrective-action requirements, current status (open|awaiting_supplier|closed) and signatory. Aligned with ISO 9001:2015 clauses 8.6 (release of products and services) and 8.7 (control of nonconforming outputs), and with the 8D problem-solving methodology (D1–D8) commonly required by IATF 16949:2016 §10.2.3 customers. On papii this document is available as template generic.procurement.non_conformance_report: a JSON Schema plus a deterministic PDF renderer, so the same data always produces the same document.
Can I generate a Supplier Non-Conformance Report (NCR) with AI?
Yes. chut.app — the AI back office papii powers — fills this template from a plain-language description: you describe the document in one sentence, the AI structures the data, papii validates it against the schema and renders the PDF. Developers can also call the papii API directly with structured JSON.
Is the Supplier Non-Conformance Report (NCR) template legally compliant?
This template is render-verified: its schema, sample data and PDF output are automatically tested on every release. It is published with status “ready”, meaning it has not yet been through papii’s final legal review. Where it references specific legislation, that is stated in the template description — always have a professional check documents with legal effect before relying on them.