slug: fortnox
provider: Fortnox
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: 6
edges:
- tag: Accounts
  spec_file: fortnox-accounts-api-openapi.yml
  capability_id: BC-200.10
  capability_id_l1: BC-200
  capability_name: General Ledger Management
  confidence: 0.9
  evidence: '"List accounts", "Create an account", GET /accounts/{Number}, schema Account; vendor manages
    "vouchers, accounts, suppliers, supplier invoices... financial years"'
  reason: In this Swedish cloud accounting/ERP platform, Accounts are ledger accounts keyed by account
    Number and sit alongside vouchers and financial years, i.e. chart-of-accounts maintenance within general
    ledger management, not customer or user accounts.
- tag: Supplier Invoices
  spec_file: fortnox-supplier-invoices-api-openapi.yml
  capability_id: BC-200.20
  capability_id_l1: BC-200
  capability_name: Accounts Payable Management
  confidence: 0.9
  evidence: GET /supplierinvoices listSupplierInvoices; POST /supplierinvoices createSupplierInvoice;
    schema "SupplierInvoice"
  reason: Creation and retrieval of incoming supplier invoices in an accounting platform is plainly accounts
    payable invoice processing.
- tag: Vouchers
  spec_file: fortnox-vouchers-api-openapi.yml
  capability_id: BC-200.10
  capability_id_l1: BC-200
  capability_name: General Ledger Management
  confidence: 0.88
  evidence: POST /vouchers createVoucher; GET /vouchers/{VoucherSeries}/{VoucherNumber}; schemas "Voucher",
    "VoucherRow"
  reason: Vouchers with voucher series and debit/credit rows are accounting journal entries posted to
    the general ledger — general ledger management.
- tag: Invoices
  spec_file: fortnox-invoices-api-openapi.yml
  capability_id: BC-200.30
  capability_id_l1: BC-200
  capability_name: Accounts Receivable Management
  confidence: 0.85
  evidence: POST /invoices createInvoice Create an invoice; schemas "Invoice", "InvoiceRow"
  reason: Customer-facing sales invoices with invoice rows in an accounting platform — accounts receivable
    (customer invoicing). Distinct from the separate Supplier Invoices tag, confirming the receivable
    reading.
- tag: Customers
  spec_file: fortnox-customers-api-openapi.yml
  capability_id: BC-420.10
  capability_id_l1: BC-420
  capability_name: Customer Data Management
  confidence: 0.8
  evidence: GET /customers listCustomers; POST /customers createCustomer; schema "Customer"
  reason: CRUD over customer master records keyed by CustomerNumber in an accounting/ERP platform — customer
    data management (customer master). No segmentation, loyalty or service operations present.
- tag: Financial Years
  spec_file: fortnox-financial-years-api-openapi.yml
  capability_id: BC-200.10
  capability_id_l1: BC-200
  capability_name: General Ledger Management
  confidence: 0.7
  evidence: GET /financialyears listFinancialYears; POST /financialyears createFinancialYear; schema "FinancialYear"
  reason: Financial years define the accounting period structure of the ledger in this accounting platform,
    which sits under general ledger management (period structure/close). Thin surface, hence moderate
    confidence.