slug: invoiced
provider: Invoiced
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: 4
edges:
- tag: Subscriptions
  spec_file: invoiced-subscriptions-api-openapi.yml
  capability_id: BC-4240
  capability_id_l1: BC-4240
  capability_name: Subscription Lifecycle Management
  confidence: 0.85
  evidence: POST /subscriptions  createSubscription  Create a new subscription; DELETE /subscriptions/{id}  cancelSubscription  Cancel
    a subscription
  reason: Create, preview, update and cancel of recurring subscriptions is squarely Subscription Lifecycle
    Management; the surface spans provisioning, modification and cancellation so no single L2 is named.
- tag: Invoices
  spec_file: invoiced-invoices-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.82
  evidence: POST /invoices/{id}/emails  sendInvoiceEmail  Send an invoice to the customer by email; POST
    /invoices/{id}/pay  Trigger automatic payment collection on an invoice
  reason: Operations create, send, void and collect on customer invoices for an 'accounts-receivable and
    billing automation platform' — this is customer invoicing and collections, i.e. Accounts Receivable
    Management. Some ambiguity with subscription invoicing, but the surface is generic A/R invoicing.
- tag: Credit Notes
  spec_file: invoiced-credit-notes-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.8
  evidence: POST /credit_notes createCreditNote 'Create a new credit note'; schemas CreditNote, LineItem
  reason: Credit notes issued against customer invoices on an explicitly described 'accounts-receivable
    and billing automation platform' are invoice adjustments within Accounts Receivable Management.
- tag: Payments
  spec_file: invoiced-payments-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.78
  evidence: 'POST /payments  createPayment  Record a new payment; schemas: PaymentApplication, Payment'
  reason: Recording payments and applying them (PaymentApplication) against customer balances is cash
    application within Accounts Receivable Management for this A/R platform; could alternatively be read
    as subscription payment collection, hence not maximal confidence.