JJijibora
Docs & Product Guide
On this page (5 sections)

Feature Package PK-07 — Procurement & Group Purchasing

Status: Package Specification
Domain: Procurement / Corporate / Multi-Property
Maps to: Playbook H-9 + Process 7 (Cross-Org B2B Joint Procurement)
External integration: ERPNext (fiscal), Record Federation (s184), BBS+ selective disclosure


1. What This Package Does

For hotel groups and corporate accounts, this package aggregates F&B, amenities, and linen demand across properties for volume pricing, with federated escrow release on multi-property delivery verification — replacing individual property orders, inconsistent vendor terms, and manual reconciliation.

2. Features & Functionality

FeatureWhat it doesWho uses itWhat stands behind it
Federated requisitionGroup-level requisition (is_federated: true) bound to peer property scopesGroup procurement lead, property procurement officerscns://federation/procurement; record_federation_binding (s184)
Per-property quota signingEach property signs its allocation quota with its BBS+ key; selective disclosure hides internal marginsProperty GM, finance controllerBBS+ signature; X-Sovereign-DID-Proof header
Authority verdictA named authority must approve the award before any commitmentRegional director, group procurementfn::authority::verify_chain; governance rules (s165)
Federated escrowShared PoCE escrow session; supplier payment released only on multi-property delivery verificationFinance, supplierfn::poce::finalize_session; federated PoCE
Cross-property visibilityGroup-wide spend and vendor performance visible without merging property databasesRegional office, group financerecord_federation_event audit ledger; scope boundaries
ERPNext fiscal syncEach property's PO mirrors to its own ERPNext instance for fiscal complianceProperty accounts payableintegration_entity (system: erpnext) per property

3. Workflow (Group Procurement)

  1. Group aggregates F&B demand across properties → federated requisition claim
  2. Bound to peer property scopes via record_federation_binding
  3. Each property signs its quota with BBS+ key (selective disclosure — no margin leakage)
  4. Authority verdict required before award (verdict = gate; missing verdict blocks)
  5. Shared PoCE escrow session created
  6. Supplier delivers; each property verifies delivery
  7. PoCE escrow released; supplier paid; ERPNext POs mirrored per property

4. Guard Rails

  • Authority verdict required before award; missing verdict blocks award
  • No autonomous escrow release
  • Selective disclosure: no internal margin leakage between properties
  • No synthetic vendor or property IDs

5. Evidence & Audit

  • Federated claim, federation bindings, BBS+ quota signatures, authority verdict, escrow lock/release receipt