slug: recvue
provider: RecVue
generated_by: planning/capability-mapping/scripts/classify_capabilities.py
model: claude-opus-5
frame:
- Software & Technology
min_confidence: 0.7
capability_model:
  source: https://github.com/vincentmakes/turbo-ea-capabilities
  license: CC-BY-4.0
  attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities,
    CC BY 4.0
  notice: NOTICE
edge_count: 7
edges:
- tag: Revenue Recognition
  spec_file: recvue-revenue-recognition-api-openapi.yml
  capability_id: BC-4250.50
  capability_id_l1: BC-4250
  capability_name: Subscription Revenue Recognition
  confidence: 0.85
  evidence: 'POST /revenue/contract-amendment-setup  createRevenueContractAmendmentSetup; description:
    ''ASC 606 / IFRS 15 revenue recognition'''
  reason: Revenue contract amendment setup for ASC 606/IFRS 15 is squarely subscription revenue recognition.
- tag: Usage
  spec_file: recvue-usage-api-openapi.yml
  capability_id: BC-4250.10
  capability_id_l1: BC-4250
  capability_name: Usage Metering
  confidence: 0.85
  evidence: 'POST /usage/batches  loadUsageBatch  Load usage records into batch; schemas: Delivery, UsageBatch'
  reason: Ingestion of usage/delivery records feeding usage-based monetization is usage metering.
- tag: Billing
  spec_file: recvue-billing-api-openapi.yml
  capability_id: BC-4250.30
  capability_id_l1: BC-4250
  capability_name: Invoicing & Statement Management
  confidence: 0.75
  evidence: 'POST /billruns createBillRun Create bill run; schemas: BillRun'
  reason: Bill runs are the batch generation of customer invoices in a recurring/usage billing platform
    ('covering order-to-cash, billing, usage-based monetization'), so BC-4250 Subscription Billing & Revenue
    Management is clear. Sub-capability is most likely Invoicing & Statement Management, though a bill
    run also performs rating, hence moderate confidence.
- tag: Billing Schedules
  spec_file: recvue-billing-schedules-api-openapi.yml
  capability_id: BC-4250
  capability_id_l1: BC-4250
  capability_name: Subscription Billing & Revenue Management
  confidence: 0.75
  evidence: 'POST /billingschedules createBillingSchedule Create billing schedule; schemas: BillingSchedule'
  reason: Billing schedules define when and how recurring/milestone charges are billed on a RevOS platform
    for 'recurring, usage, milestone, and hybrid billing models', which sits squarely in subscription
    billing. Evidence is too thin to choose confidently between rating/charging and invoicing sub-capabilities,
    so only the L1 is asserted.
- tag: Invoices
  spec_file: recvue-invoices-api-openapi.yml
  capability_id: BC-4250.30
  capability_id_l1: BC-4250
  capability_name: Invoicing & Statement Management
  confidence: 0.75
  evidence: 'POST /invoices  createInvoice  Create or update invoice; schemas: Invoice — within a platform
    ''covering order-to-cash, billing, usage-based monetization'''
  reason: Invoice creation inside a recurring/usage billing platform is invoicing and statement management
    under subscription billing. Some chance the better home is cross-industry Accounts Receivable, hence
    moderate confidence.
- tag: Customers
  spec_file: recvue-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.7
  evidence: 'POST /customers createCustomerAccount Create customer account; schemas: CustomerAccount'
  reason: CRUD over CustomerAccount records maintains the customer master used by billing and order-to-cash,
    which maps to Customer Data Management. Confidence capped because in a billing platform these accounts
    are primarily billing entities, so a billing-adjacent reading is also defensible.
- tag: Pricing
  spec_file: recvue-pricing-api-openapi.yml
  capability_id: BC-440.20
  capability_id_l1: BC-440
  capability_name: Price List Management
  confidence: 0.7
  evidence: 'GET /pricelists  getPriceLists  Get price lists; schemas: PriceList'
  reason: The single operation retrieves price lists, which is price book/price list maintenance. Could
    alternatively be read as rating tariff setup, so confidence held moderate.