Overview

AUTO-TOW-047, Prioritize Invoice Review, ranks towing invoices for review, correction, or approval by invoice amount, billing discrepancy severity, payer priority, invoice age, documentation gaps, and collection risk.

Decision ID

AUTO-TOW-047

Decision Name

Prioritize Invoice Review

Decision Preparation Model

auto-towing-prioritize-invoice-review-auto-tow-047 version 1.0.0

Default Profile

balanced

Default Scenario

standard

Catalog

DKR-AUTO-RUNTIME-001, active Decision Catalog runtime catalog

5-Minute Quick Path

First working request →

Understanding This Decision

Prioritize Invoice Review helps a towing operation decide which invoices should be reviewed first when billing teams need to resolve discrepancies, approve clean invoices, or intervene before collection risk grows.

Criteria

Criterion IDs are intentionally stable machine identifiers. Display labels are for users; request values should be keyed by canonical criterionId.

Data Preparation Guide

Constraint Processing

This decision includes a catalog-defined hard constraint. Decision Catalog returns the constraint with the decision detail, and Decision Service evaluates it before criteria-based ranking.

Candidates older than three days are intentionally removed from this routine-review ranking. Route them to the configured exception or escalation workflow; exclusion does not mean that the invoice should be ignored.

{
  "constraintSummary": {
    "definedConstraintCount": 1,
    "activeConstraintCount": 1,
    "eligibleOptionCount": 2,
    "excludedOptionCount": 1,
    "eligibleOptions": [
      "option-1",
      "option-2"
    ],
    "excludedOptions": [
      {
        "optionId": "option-3",
        "reasons": [
          "Aging days exceeds the standard review window of 3 days."
        ]
      }
    ]
  }
}

const constraints = decisionDetail.constraints || [];
if (constraints.length > 0) {
  // Decision Service applies catalog constraints before ranking.
  // Excluded candidates appear in response.constraintSummary.excludedOptions.
}

const summary = response.constraintSummary;
const excluded = response.decisionResult?.excludedOptions || [];

Excluded candidates do not participate in ranking because hard constraints are evaluated before scoring. For AUTO-TOW-047, option-3 is excluded from the showcase sample because its invoice age is outside the standard review window.

Decision Preparation Model

The published Decision Preparation Model validates and transforms illustrative Business Data into the canonical criteria required by AUTO-TOW-047 before Decision Service applies ranking.

Profile ID

auto-towing-prioritize-invoice-review-auto-tow-047

Version

1.0.0

Options Path

$.towRequests

Option ID Path

$.optionId

Display Name Path

$.name

{
  "requestContext": {
    "sourceSystem": "automotive-profile-factory",
    "correlationId": "factory-auto-tow-047"
  },
  "towRequests": [
    {
      "optionId": "TOW-047-01",
      "name": "Prioritize Invoice Review Option 1",
      "financial": {
        "invoiceAmount": 42000.0
      },
      "assessment": {
        "billingDiscrepancyScore": 70.0,
        "payerPriorityScore": 37.0,
        "documentationGapScore": 70.0
      },
      "billing": {
        "and": {
          "collections": {
            "agingDays": 2.0
          }
        }
      },
      "risk": {
        "collectionRiskScore": 64.0
      }
    },
    {
      "optionId": "TOW-047-02",
      "name": "Prioritize Invoice Review Option 2",
      "financial": {
        "invoiceAmount": 31000.0
      },
      "assessment": {
        "billingDiscrepancyScore": 30.0,
        "payerPriorityScore": 44.0,
        "documentationGapScore": 46.0
      },
      "billing": {
        "and": {
          "collections": {
            "agingDays": 1.0
          }
        }
      },
      "risk": {
        "collectionRiskScore": 71.0
      }
    }
  ]
}

{
  "optionId": "TOW-047-01",
  "name": "Prioritize Invoice Review Option 1",
  "values": {
    "invoice_amount": 42000.0,
    "billing_discrepancy_score": 70.0,
    "payer_priority_score": 37.0,
    "aging_days": 2.0,
    "documentation_gap_score": 70.0,
    "collection_risk_score": 64.0
  }
}

Profiles and Scenarios

This example selects a Profile for evaluation emphasis and a Scenario for operating context. Discover both from the selected Decision Catalog definition.

Business Data Mode

Start here when your application has operational data. DecisioQ applies the published Decision Preparation Model to produce the required criteria.

{
  "decisionId": "AUTO-TOW-047",
  "businessData": {
    "requestContext": {
      "sourceSystem": "automotive-profile-factory",
      "correlationId": "factory-auto-tow-047"
    },
    "towRequests": [
      {
        "optionId": "TOW-047-01",
        "name": "Prioritize Invoice Review Option 1",
        "financial": {
          "invoiceAmount": 42000.0
        },
        "assessment": {
          "billingDiscrepancyScore": 70.0,
          "payerPriorityScore": 37.0,
          "documentationGapScore": 70.0
        },
        "billing": {
          "and": {
            "collections": {
              "agingDays": 2.0
            }
          }
        },
        "risk": {
          "collectionRiskScore": 64.0
        }
      },
      {
        "optionId": "TOW-047-02",
        "name": "Prioritize Invoice Review Option 2",
        "financial": {
          "invoiceAmount": 31000.0
        },
        "assessment": {
          "billingDiscrepancyScore": 30.0,
          "payerPriorityScore": 44.0,
          "documentationGapScore": 46.0
        },
        "billing": {
          "and": {
            "collections": {
              "agingDays": 1.0
            }
          }
        },
        "risk": {
          "collectionRiskScore": 71.0
        }
      }
    ]
  }
}

Download Business Data request

Prepared Criteria Mode

Use this mode when your application already calculates decision-ready values keyed by authoritative criterion IDs. Prepared Criteria go directly to the decision.

Download Prepared Criteria request

For Prepared Criteria Mode, send decisionId, selected profile/scenario IDs, and option values keyed by canonical criterion ID. The optional mappingProfileId and mappingProfileVersion fields preserve preparation-model lineage; they are not required when submitting already prepared criteria unless the active API contract requires that lineage. The showcase request includes two eligible invoice reviews and one excluded invoice so constraint handling is visible.

{
  "decisionId": "AUTO-TOW-047",
  "mappingProfileId": "auto-towing-prioritize-invoice-review-auto-tow-047",
  "mappingProfileVersion": "1.0.0",
  "profileId": "balanced",
  "scenarioId": "standard",
  "algorithm": "TOPSIS",
  "weightStrategy": "Expert",
  "runSensitivity": false,
  "requestContext": {
    "correlationId": "auto-tow-047-demo-001"
  },
  "options": [
    {
      "optionId": "option-1",
      "name": "High-Value Insurance Invoice",
      "values": {
        "invoice_amount": 125,
        "billing_discrepancy_score": 88,
        "payer_priority_score": 88,
        "aging_days": 1,
        "documentation_gap_score": 88,
        "collection_risk_score": 88
      }
    },
    {
      "optionId": "option-2",
      "name": "Disputed Commercial Invoice",
      "values": {
        "invoice_amount": 250,
        "billing_discrepancy_score": 81,
        "payer_priority_score": 81,
        "aging_days": 2,
        "documentation_gap_score": 81,
        "collection_risk_score": 81
      }
    },
    {
      "optionId": "option-3",
      "name": "Aged Storage Invoice",
      "values": {
        "invoice_amount": 500,
        "billing_discrepancy_score": 74,
        "payer_priority_score": 74,
        "aging_days": 4,
        "documentation_gap_score": 74,
        "collection_risk_score": 74
      }
    }
  ]
}

Execute

curl -X POST "https://dde.vinquery.com/api/v1/decide" \
  -H "Authorization: Bearer ${DECISIOQ_TOKEN}" \
  -H "Content-Type: application/json" \
  -H "X-Correlation-Id: auto-tow-047-demo-001" \
  --data @auto-tow-047-execute.json

Decision Service retrieves authoritative criteria, constraints, and validation metadata from Decision Catalog, executes the deterministic ranking, and returns the decision result plus execution metadata.

Understanding the Result

The successful response includes both the deterministic decisionResult and a top-level explanation object. The explanation adds context but does not select, rerank, recalculate, or override the ranking.

{
  "success": true,
  "decisionType": "AUTO-TOW-047",
  "decisionResult": {
    "winner": "option-1",
    "ranking": [
      {
        "optionId": "option-1",
        "name": "High-Value Insurance Invoice",
        "score": 0.91
      },
      {
        "optionId": "option-2",
        "name": "Disputed Commercial Invoice",
        "score": 0.84
      }
    ],
    "excludedOptions": [
      {
        "optionId": "option-3",
        "reasons": [
          "Aging days exceeds the standard review window of 3 days."
        ]
      }
    ]
  },
  "explanation": {
      "summary": "The selected invoice review provided the strongest billing review priority.",
      "whyRecommended": "It combined invoice value, billing discrepancy severity, payer priority, and acceptable invoice age.",
      "keyDrivers": [],
      "tradeoffs": [],
      "competitors": [],
      "sensitivitySummary": "Sensitivity analysis was not included in this response.",
      "scenarioSummary": "The standard scenario was selected.",
      "risks": [],
      "nextSteps": [],
      "assumptions": []
  },
  "constraintSummary": {
    "definedConstraintCount": 1,
    "activeConstraintCount": 1,
    "eligibleOptionCount": 2,
    "excludedOptionCount": 1
  },
  "requestContext": {
    "correlationId": "auto-tow-047-demo-001"
  }
}

Sensitivity Analysis

runSensitivity is an optional execution flag supported by both Business Data Mode and Prepared Criteria Mode. Set it to true when the client wants recommendation-stability information in the same response. The sensitivity engine analyzes the prepared criteria produced by either input path, perturbs criterion weights by controlled factors, and reports whether the winner remains stable.

{
  "sensitivityResult": {
    "stableWinner": true,
    "winner": "option-1",
    "mostSensitiveCriterion": "invoice_amount",
    "confidence": 95,
    "criterionImpacts": {
      "invoice_amount": 0.1842
    },
    "winnerChangeCounts": {
      "invoice_amount": 0
    }
  }
}

Use sensitivity output to decide whether a recommendation is robust enough for automation or should be reviewed by a person.

Scenario Analysis

Use a published scenario only when it matches the operating context: standard, urgent_customer, cost_control, compliance_review. Compare the winner, ranking gap, and key trade-offs with the baseline run.

Explanation of Decision Result

Every successful response includes a provider-neutral top-level explanation object. It explains the already-finalized deterministic result and does not change the ranking.

{
  "explanation": {
      "summary": "The selected invoice review provided the strongest billing review priority.",
      "whyRecommended": "It combined invoice value, billing discrepancy severity, payer priority, and acceptable invoice age.",
      "keyDrivers": [],
      "tradeoffs": [],
      "competitors": [],
      "sensitivitySummary": "Sensitivity analysis was not included in this response.",
      "scenarioSummary": "The standard scenario was selected.",
      "risks": [],
      "nextSteps": [],
      "assumptions": []
  }
}

Tracing and Logs

Use request identifiers to connect client, catalog, and execution activity during support or integration testing.

X-Request-Id

Optional client-supplied request ID. If omitted, the server generates one.

X-Correlation-Id

Optional client correlation value propagated from Decision Service to Decision Catalog.

requestContext.correlationId

Optional payload value echoed in the response and used for tracing.

configurationUsed

The authoritative effective weight strategy, ranking algorithm, profile, scenario, sensitivity setting, and source for each value.

diagnostics

Safe execution counts returned only when responseOptions.includeDiagnostics is true.

Integration Examples

These examples demonstrate the current DecisioQ flow:

1. Request jwtToken from https://identity.vinquery.com/connect/token.
2. Load AUTO-TOW-047 metadata from https://dks.vinquery.com/decisioncatalog/decisions/AUTO-TOW-047.
3. Execute a Prepared Criteria Mode at https://dde.vinquery.com/api/v1/decide.

Set these environment variables before running any companion example:

DECISIOQ_CLIENT_ID
DECISIOQ_CLIENT_SECRET
DECISIOQ_AUDIENCE=vinquery:api:decisioq

Optional:
DECISIOQ_IDENTITY_URL=https://identity.vinquery.com/connect/token
DECISIOQ_DKS_URL=https://dks.vinquery.com
DECISIOQ_DDE_URL=https://dde.vinquery.com

Download the source files directly:

Troubleshooting

Production Checklist

Next Steps

Review Decision Concepts for criteria, weights, profiles, scenarios, confidence, and sensitivity; use the API Guide for transport details; and return to the examples library to compare related workflows.