Playbooks

Playbooks are standard operating procedures (SOPs) for PCM. Use calls.md for payload shape and required fields.

Surface availability (explicit)

• API Gateway: Available.
• Direct Lambda: Not offered.
• CLI: Available (g3n pcm ..., API Gateway).
• MCP: Available.

Playbook: Purchase order lifecycle

Goal: Create, approve, issue, and receive a purchase order.

Why this sequence:

• Orders must be approved and issued before receipt.
• Receipts anchor invoice matching and vendor performance.

Preconditions

• Suppliers exist in PVM.
• Facilities are configured in OFM.

SOP (happy path)

1. Create PO (POST /po/create).
   • Reason: records requested items and terms.
2. Approve PO (POST /po/approve).
   • Reason: enforces internal controls before issuance.
3. Issue PO (POST /po/issue).
   • Reason: communicates commitment to the vendor.
4. Record receipt (POST /receipt/record).
   • Reason: captures inbound quantities and timestamps.
5. Get/list PO (POST /po/get, /po/list) for audit.
   • Reason: confirm status and line-level outcomes.

Outputs

• Approved/issued PO with receipts recorded.

Failure modes / remediation

• invalid-state: ensure approvals precede issuance.
• Receipt mismatches: adjust via follow-up receipts or vendor credits.

Cross-service relationships

• ICS: receipt and stock movement linkage (as applicable).
• PVM: supplier and item definitions.

Playbook: Invoice match + dispute resolution

Goal: Match invoices to receipts and resolve disputes cleanly.

Why this sequence:

• Invoice matching ties financial liability to received goods.

Preconditions

• PO and receipts exist.

SOP (happy path)

1. Get invoice (POST /invoice/get) or list (POST /invoice/list).
   • Reason: locate the invoice to match.
2. Match invoice (POST /invoice/match).
   • Reason: reconciles invoice lines to receipts and PO.
3. Dispute (POST /invoice/dispute) when mismatches are detected.
   • Reason: captures the reason and pauses settlement.
4. Resolve dispute (POST /invoice/resolve) after vendor agreement.
   • Reason: updates financial posture and clears the dispute.
5. Apply credits (POST /credit/apply) if required.
   • Reason: corrects net payable after adjustments.

Outputs

• Matched invoice, optional dispute and resolution trail.

Failure modes / remediation

• conflict or invalid-state: re-check invoice status before match/resolve.

Cross-service relationships

• Accounting: financial events and exports may consume PCM invoices.