Bienvenue sur FlowZap, l'application pour créer des diagrammes avec Rapidité, Clarté et Contrôle.

Flux de bon de commande

finance

Flux de travail de bon de commande d’approvisionnement avec création de la demande, validation du budget, sélection du fournisseur, appel d’offres concurrentiel et circuit d’approbation à paliers basé sur des seuils de montant.

Code FlowZap complet

Requester { # Requester
n1: circle label:"Start"
n2: rectangle label:"Create purchase requisition"
n3: rectangle label:"Add line items"
n4: rectangle label:"Attach specifications"
n5: rectangle label:"Receive PO number"
n6: circle label:"End"
n1.handle(right) -> n2.handle(left)
n2.handle(right) -> n3.handle(left)
n3.handle(right) -> n4.handle(left)
n4.handle(bottom) -> Procurement.n7.handle(top) [label="Submit"]
n5.handle(right) -> n6.handle(left)
}
Procurement { # Procurement
n7: rectangle label:"Review requisition"
n8: diamond label:"Budget available?"
n9: rectangle label:"Source vendors"
n10: rectangle label:"Request quotes"
n11: rectangle label:"Return for budget approval"
n12: diamond label:"Competitive bids required?"
n13: rectangle label:"Select best vendor"
n14: rectangle label:"Single source justification"
n7.handle(right) -> n8.handle(left)
n8.handle(right) -> n9.handle(left) [label="Yes"]
n8.handle(bottom) -> n11.handle(top) [label="No"]
n9.handle(right) -> n12.handle(left)
n11.handle(top) -> Requester.n2.handle(bottom) [label="Revise"]
n12.handle(right) -> n10.handle(left) [label="Yes"]
n12.handle(bottom) -> n14.handle(top) [label="No"]
n10.handle(right) -> n13.handle(left)
n13.handle(bottom) -> Approval.n15.handle(top) [label="Approve"]
n14.handle(right) -> n13.handle(top)
}
Approval { # Approval Chain
n15: rectangle label:"Route based on amount"
n16: diamond label:"Amount threshold?"
n17: rectangle label:"Manager approval"
n18: rectangle label:"Director approval"
n19: rectangle label:"VP approval"
n20: diamond label:"Approved?"
n21: rectangle label:"Generate PO number"
n22: rectangle label:"Reject with comments"
n15.handle(right) -> n16.handle(left)
n16.handle(right) -> n17.handle(left) [label="< $5K"]
n16.handle(bottom) -> n18.handle(top) [label="$5K-$50K"]
n16.handle(left) -> n19.handle(top) [label="> $50K"]
n17.handle(bottom) -> n20.handle(top)
n18.handle(bottom) -> n20.handle(top)
n19.handle(bottom) -> n20.handle(top)
n20.handle(right) -> n21.handle(left) [label="Yes"]
n20.handle(bottom) -> n22.handle(top) [label="No"]
n21.handle(top) -> Requester.n5.handle(bottom) [label="PO issued"]
n22.handle(top) -> Requester.n2.handle(bottom) [label="Rejected"]
}

Quick Answer

Flux de bon de commande is a workflow template that maverick spending and unapproved purchases waste 10-20% of procurement budgets.

Pourquoi ce workflow ?

Maverick spending and unapproved purchases waste 10-20% of procurement budgets. This workflow enforces procurement policies with requisition creation, budget validation, competitive bidding, and tiered approvals.

Comment ça fonctionne

  1. Step 1: Requisition is created with item details, quantity, and estimated cost.
  2. Step 2: Budget validation checks against department budget and GL coding.
  3. Step 3: Vendor sourcing identifies approved vendors or initiates RFQ process.
  4. Step 4: Competitive bidding is required for purchases above threshold (e.g., $10K).
  5. Step 5: Tiered approval routes based on amount: Manager < $5K, Director < $25K, VP < $100K, CFO > $100K.
  6. Step 6: Approved PO is sent to vendor and tracked through delivery.

Alternatives

Email-based approvals lack audit trails and are easily bypassed. Procurement tools like Coupa or Ariba cost $100K+/year for enterprise. This workflow provides a visual policy that procurement teams can enforce.

Key Facts

Template NameFlux de bon de commande
Categoryfinance
Steps6 workflow steps
FormatFlowZap Code (.fz file)

Modèles associés

Processus d’approbation budgétaire

finance

Processus d’approbation budgétaire d’entreprise avec routage d’approbation par paliers en fonction des seuils de montants (CFO < 100 K$, CEO 100 K$–1 M$, Conseil > 1 M$), comparaison avec l’année précédente et affectation des fonds.

Workflow d’onboarding fournisseur

finance

Workflow d’onboarding fournisseur avec examen de la demande, vérification des formulaires W-9/W-8BEN, validation des certificats d’assurance, vérifications d’antécédents et approbation de conformité avant l’activation du fournisseur.

Processus de rapprochement bancaire

finance

Processus de rapprochement bancaire avec appariement automatisé des transactions, reporting des écarts, analyse des divergences et création d’écritures comptables pour les décalages temporels et les erreurs bancaires.

Retour à tous les modèles