Source profileQuality 94/100

VincentChuWaiChow/vanguard-frontier-agentic/skills/cross-functional/field-service-to-cash-protocol/SKILL.md

field-service-to-cash-protocol

Use this skill to orchestrate the field service to cash process (service to deliver) across Dynamics 365 Field Service and Dynamics 365 Finance, covering work order creation through service delivery, parts and inventory consumption, invoicing, and accounts receivable settlement. The skill defines stage gates, agent handoff rules, and escalation triggers so that service work is verified before invoicing, inventory is accurately consumed, and revenue is recognized correctly. It does not create or

Source repository stars
21
Declared platforms
0
Static risk flags
0
Last source update
2026-08-24
Source checked
2026-08-25

Decision brief

What it does: where it fits

Use this skill to orchestrate the field service to cash process (service to deliver) across Dynamics 365 Field Service and Dynamics 365 Finance, covering work order creation through service delivery, parts and inventory consumption, invoicing, and accounts receivable settlement. The skill defines stage gates, agent handoff rules, and escalation triggers so…

Best for

  • A field service work order must progress from creation through scheduling, delivery, parts consumption, invoicing, and payment.
  • Inventory consumed during field service must be reconciled with accounts in Dynamics 365 Finance.
  • A service agreement with recurring invoicing requires coordination between Field Service and Finance.

Not for

  • The matter is confined entirely to work order scheduling with no financial impact — route to the Field Service specialist.
  • The matter involves project-based billing from Dynamics 365 Project Operations — use the appropriate project-to-profit process.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic --skill "skills/cross-functional/field-service-to-cash-protocol"
Safe inspection promptEditorial

Inspect the Agent Skill "field-service-to-cash-protocol" from https://github.com/VincentChuWaiChow/vanguard-frontier-agentic/blob/5e32c1f3b9ba9e9bacae9687f55bed35b5def90f/skills/cross-functional/field-service-to-cash-protocol/SKILL.md at commit 5e32c1f3b9ba9e9bacae9687f55bed35b5def90f. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Workflow

    1. Receive work order creation trigger; validate that customer account, service scope, and billing method are defined. 2. Confirm that required parts are available in the assigned inventory location (warehouse or technician's truck stock). 3. Schedule and dispatch field technici…

    Receive work order creation trigger; validate that customer account, service scope, and billing method are defined.Confirm that required parts are available in the assigned inventory location (warehouse or technician's truck stock).Schedule and dispatch field technician via Dynamics 365 Field Service scheduling board; record assignment.
  2. 02

    Purpose

    This skill orchestrates the field service to cash process (referred to as "service to deliver" in the Microsoft Dynamics 365 business process catalog) in Dynamics 365 environments. It coordinates Dynamics 365 Field Service (work order management, scheduling, service delivery, an…

    This skill orchestrates the field service to cash process (referred to as "service to deliver" in the Microsoft Dynamics 365 business process catalog) in Dynamics 365 environments. It coordinates Dynamics 365 Field Serv…
  3. 03

    When to use

    A field service work order must progress from creation through scheduling, delivery, parts consumption, invoicing, and payment.

    A field service work order must progress from creation through scheduling, delivery, parts consumption, invoicing, and payment.Inventory consumed during field service must be reconciled with accounts in Dynamics 365 Finance.A service agreement with recurring invoicing requires coordination between Field Service and Finance.
  4. 04

    When NOT to use

    The matter is confined entirely to work order scheduling with no financial impact — route to the Field Service specialist.

    The matter is confined entirely to work order scheduling with no financial impact — route to the Field Service specialist.The matter involves project-based billing from Dynamics 365 Project Operations — use the appropriate project-to-profit process.The matter is a warranty claim or service contract renewal without an active work order — escalate to the Field Service and finance owners.
  5. 05

    Participating agents

    d365-field-service-to-cash-agent — owns work order creation, scheduling, service delivery confirmation, and inventory consumption in Dynamics 365 Field Service

    d365-field-service-to-cash-agent — owns work order creation, scheduling, service delivery confirmation, and inventory consumption in Dynamics 365 Field Serviced365-finance-close-to-report-agent — owns invoicing, accounts receivable, revenue recognition, and cash application in Dynamics 365 Finance- d365-field-service-to-cash-agent — owns work order creation, scheduling, service delivery confirmation, and inventory consumption in Dynamics 365 Field Service - d365-finance-close-to-report-agent — owns invoicing, ac…

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score94/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars21SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
VincentChuWaiChow/vanguard-frontier-agentic
Skill path
skills/cross-functional/field-service-to-cash-protocol/SKILL.md
Commit
5e32c1f3b9ba9e9bacae9687f55bed35b5def90f
License
Apache-2.0
Collected
2026-08-25
Default branch
master
View the original SKILL.md

Field Service to Cash Protocol

Purpose

This skill orchestrates the field service to cash process (referred to as "service to deliver" in the Microsoft Dynamics 365 business process catalog) in Dynamics 365 environments. It coordinates Dynamics 365 Field Service (work order management, scheduling, service delivery, and inventory consumption) with Dynamics 365 Finance (invoicing, accounts receivable, and cash application). The protocol ensures that service is verified as delivered before invoicing, that parts consumed are accurately recorded against inventory, and that revenue is recognized in the correct period. It does not give field service configuration or financial accounting advice; all recommendations are subject to human owner confirmation.

When to use

  • A field service work order must progress from creation through scheduling, delivery, parts consumption, invoicing, and payment.
  • Inventory consumed during field service must be reconciled with accounts in Dynamics 365 Finance.
  • A service agreement with recurring invoicing requires coordination between Field Service and Finance.
  • A work order completion must be verified before an invoice is generated or posted.
  • A cross-module discrepancy between field service actuals and financial postings needs investigation.

When NOT to use

  • The matter is confined entirely to work order scheduling with no financial impact — route to the Field Service specialist.
  • The matter involves project-based billing from Dynamics 365 Project Operations — use the appropriate project-to-profit process.
  • The matter is a warranty claim or service contract renewal without an active work order — escalate to the Field Service and finance owners.
  • Direct Field Service or Finance configuration is required — route to the relevant specialist agent.

Participating agents

  • d365-field-service-to-cash-agent — owns work order creation, scheduling, service delivery confirmation, and inventory consumption in Dynamics 365 Field Service
  • d365-finance-close-to-report-agent — owns invoicing, accounts receivable, revenue recognition, and cash application in Dynamics 365 Finance

Inputs required

  • Work order number and customer account
  • Service type and scope of work
  • Assigned field technician and scheduled date
  • Parts and inventory items required for the work order
  • Applicable service agreement or contract reference
  • Billing method (time and materials, fixed price, or agreement invoice)

Evidence required

  • Work order completion confirmation from the field technician in Dynamics 365 Field Service
  • Parts consumed and labor time recorded on the work order
  • Customer sign-off or work order closure approval (if required by contract)
  • Inventory adjustment confirmation for parts consumed
  • Invoice draft validated against work order actuals before posting

Workflow

  1. Receive work order creation trigger; validate that customer account, service scope, and billing method are defined.
  2. Confirm that required parts are available in the assigned inventory location (warehouse or technician's truck stock).
  3. Schedule and dispatch field technician via Dynamics 365 Field Service scheduling board; record assignment.
  4. Monitor work order progress; flag overdue work orders to the field service owner.
  5. Upon service completion, verify that the technician has recorded all labor time and parts consumed on the work order.
  6. Work order verification gate: confirm the work order is marked as "Complete" in Dynamics 365 Field Service; if customer sign-off is required, confirm it is recorded.
  7. Trigger inventory adjustment for consumed parts; confirm inventory levels are updated in the system.
  8. Hand work order actuals (labor, parts, travel) to d365-finance-close-to-report-agent for invoice creation.
  9. Create invoice draft in Dynamics 365 Finance; validate against work order actuals and applicable service contract pricing.
  10. Invoice accuracy gate: surface discrepancies between invoice draft and work order actuals for human resolution before posting.
  11. Post the invoice; open an accounts receivable entry with the correct payment terms.
  12. Monitor payment due date; surface collection activities to the finance owner as needed.
  13. Apply cash receipt to the open invoice; close accounts receivable entry.

Decision gates

GateConditionAction if not met
Parts availabilityRequired parts in stock at assigned locationNotify d365-field-service-to-cash-agent; arrange parts transfer or order
Work order completionWork order marked complete in Dynamics 365 Field ServiceDo not proceed to invoicing; return to field service agent
Customer sign-offSign-off recorded if required by contractHold invoice; await confirmation
Inventory adjustmentConsumed parts reflected in inventory systemHold invoice; resolve inventory discrepancy first
Invoice accuracyInvoice matches work order actuals and contract pricingHold posting; flag for human resolution
Cash applicationPayment matched to invoiceDo not auto-close AR entry on partial payment without finance owner approval

Refusal triggers

  • Invoice is requested for a work order that is not yet marked as "Complete" — refuse.
  • Inventory adjustment is requested without a corresponding work order consumption record — refuse.
  • Customer PII, field technician credentials, or service agreement financial terms are included in any input — stop; redact and escalate.
  • A live invoice or AR entry modification is requested without human authorization — refuse.
  • A backdated work order completion or invoice date is requested — refuse; escalate to the field service and finance owners.

Handoff rules

  • d365-field-service-to-cash-agent provides a work order actuals summary (labor, parts, travel) to d365-finance-close-to-report-agent before any invoice is created.
  • Every handoff carries a capsule: matter_id, work_order_id, current_stage, gate_outcomes, open_questions, do_not_do_list.
  • No invoice is posted without a verified work order completion record.
  • All escalations are logged with trigger, timestamp, and receiving owner.

KPIs

  • Work order to invoice cycle time
  • First-time fix rate (work orders completed without return visits)
  • Invoice accuracy rate (first-pass match to work order actuals)
  • Days sales outstanding for field service invoices
  • Inventory accuracy rate for field service consumption

References

Frequently asked questions

What to verify before installation and use

What does the field-service-to-cash-protocol source document cover?

Use this skill to orchestrate the field service to cash process (service to deliver) across Dynamics 365 Field Service and Dynamics 365 Finance, covering work order creation through service delivery, parts and inventory consumption, invoicing, and accounts receivable settlement. The skill defines stage gates, agent handoff rules, and escalation triggers so…

How do I install field-service-to-cash-protocol?

The source record exposes this install command: npx skills add https://github.com/VincentChuWaiChow/vanguard-frontier-agentic --skill "skills/cross-functional/field-service-to-cash-protocol". Inspect the command and pinned source before running it.

Alternatives

Compare before choosing

Computed 10029,034

garrytan/gbrain

bulk-ingestion

End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.

Computed 10024,921

alirezarezvani/claude-skills

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

Computed 10015,122

wanshuiyin/Auto-claude-code-research-in-sleep

citation-audit

Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.

Computed 10014,671

prowler-cloud/prowler

postgresql-indexing

PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing index usage statistics, reindexing, dropping indexes, or working with partitioned table indexes. Also trigger when discussing index strategies, partial indexes, or index maintenance