slug: ordway provider: Ordway 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: 14 edges: - tag: Revenue Schedules spec_file: ordway-revenue-schedules-api-openapi.yml capability_id: BC-4250.50 capability_id_l1: BC-4250 capability_name: Subscription Revenue Recognition confidence: 0.9 evidence: GET /revenue_schedules listRevenueSchedules; 'revenue recognition schedules' reason: Revenue schedules are precisely the artefacts of subscription revenue recognition management under ASC 606. - tag: Invoices spec_file: ordway-invoices-api-openapi.yml capability_id: BC-4250.30 capability_id_l1: BC-4250 capability_name: Invoicing & Statement Management confidence: 0.88 evidence: POST /invoices createInvoice Create an invoice; PUT /invoices/{id} updateInvoice Update an invoice reason: Creation and amendment of invoices on a subscription billing platform is squarely Invoicing & Statement Management. - tag: Subscriptions spec_file: ordway-subscriptions-api-openapi.yml capability_id: BC-4240 capability_id_l1: BC-4240 capability_name: Subscription Lifecycle Management confidence: 0.88 evidence: POST /subscriptions createSubscription Create a subscription; PUT /subscriptions/{id} updateSubscription reason: Create/read/update of subscription records is Subscription Lifecycle Management; operations span provisioning and modification so no single L2 is named. - tag: Usages spec_file: ordway-usages-api-openapi.yml capability_id: BC-4250.10 capability_id_l1: BC-4250 capability_name: Usage Metering confidence: 0.88 evidence: POST /usages createUsage Create a usage record; 'Supports usage-based billing' reason: Ingestion of usage records feeding usage-based billing is Usage Metering. - tag: Payments spec_file: ordway-payments-api-openapi.yml capability_id: BC-4250.40 capability_id_l1: BC-4250 capability_name: Payment Collection & Dunning confidence: 0.85 evidence: POST /payments createPayment Create a payment; GET /customers/{id}/payment_methods List payment methods for a customer reason: Payment capture plus stored payment methods for customers is payment-method management and collection within subscription billing. - tag: Chart Of Accounts spec_file: ordway-chart-of-accounts-api-openapi.yml capability_id: BC-200.10 capability_id_l1: BC-200 capability_name: General Ledger Management confidence: 0.82 evidence: GET /chart_of_accounts listChartOfAccounts List chart of accounts; schema ChartOfAccount reason: Chart of accounts is the accounting structure underpinning the general ledger; read-only exposure of GL account master data maps to General Ledger Management. - tag: Revenue Rules spec_file: ordway-revenue-rules-api-openapi.yml capability_id: BC-4250.50 capability_id_l1: BC-4250 capability_name: Subscription Revenue Recognition confidence: 0.82 evidence: GET /revenue_rules listRevenueRules; vendor 'Supports ... ASC 606 compliant revenue recognition' reason: Revenue rules configure recognition treatment, matching Subscription Revenue Recognition (ASC 606 / IFRS 15). - tag: Billing Runs spec_file: ordway-billing-runs-api-openapi.yml capability_id: BC-4250.30 capability_id_l1: BC-4250 capability_name: Invoicing & Statement Management confidence: 0.8 evidence: POST /billing_runs "Create a billing run"; platform "for managing subscriptions, invoicing, payments, revenue recognition" reason: Billing runs on a SaaS subscription-billing platform execute the periodic invoice generation cycle, placing this in Subscription Billing & Revenue Management; invoicing is the most likely sub-capability though rating is adjacent. - tag: Journal Entries spec_file: ordway-journal-entries-api-openapi.yml capability_id: BC-200.10 capability_id_l1: BC-200 capability_name: General Ledger Management confidence: 0.8 evidence: GET /journal_entries listJournalEntries List journal entries; schema JournalEntry reason: Journal entries generated from billing/revenue events are general ledger postings, mapping to General Ledger Management. - tag: Customers spec_file: ordway-customers-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.78 evidence: POST /customers createCustomer Create a customer; GET /customers/{id}/contacts List contacts for a customer; schemas Customer, Contact, CustomerNote reason: Full CRUD over customer master records plus contacts and notes is customer data management, even though the vendor is a billing platform. - tag: Billing Schedules spec_file: ordway-billing-schedules-api-openapi.yml capability_id: BC-4250 capability_id_l1: BC-4250 capability_name: Subscription Billing & Revenue Management confidence: 0.75 evidence: GET /billing_schedules "List billing schedules"; schema BillingSchedule reason: Read-only access to subscription billing schedules on a billing and revenue automation platform — clearly subscription billing, but the two list/get operations do not distinguish rating, invoicing or revenue-schedule sub-capabilities, so L1 only. - tag: Refunds spec_file: ordway-refunds-api-openapi.yml capability_id: BC-4250 capability_id_l1: BC-4250 capability_name: Subscription Billing & Revenue Management confidence: 0.75 evidence: 'POST /refunds createRefund Create a refund; schemas: Refund, RefundInput' reason: Refund issuance against billing/payments in a subscription billing platform sits in Subscription Billing & Revenue Management; the evidence does not clearly name whether this is invoice adjustment or payment-side handling, so no L2. - tag: Statements spec_file: ordway-statements-api-openapi.yml capability_id: BC-4250.30 capability_id_l1: BC-4250 capability_name: Invoicing & Statement Management confidence: 0.75 evidence: GET /statements listStatements List statements; schema Statement reason: Customer billing statements in a billing platform map to Invoicing & Statement Management; thin context but the schema name is explicit. - tag: Payment Runs spec_file: ordway-payment-runs-api-openapi.yml capability_id: BC-4250.40 capability_id_l1: BC-4250 capability_name: Payment Collection & Dunning confidence: 0.72 evidence: POST /payment_runs createPaymentRun Create a payment run; schema PaymentRunInput reason: A payment run executes batched collection of amounts due from customers, matching Payment Collection & Dunning rather than generic batch plumbing.