slug: navision provider: Microsoft Dynamics NAV 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: 13 edges: - tag: Accounts spec_file: navision-accounts-api-openapi.yml capability_id: BC-200.10 capability_id_l1: BC-200 capability_name: General Ledger Management confidence: 0.92 evidence: List Accounts / Get an Account / List General Ledger Entries, schemas Account, GeneralLedgerEntry reason: Reads the chart of accounts and general ledger entries of a company — squarely General Ledger Management. - tag: Journals spec_file: navision-journals-api-openapi.yml capability_id: BC-200.10 capability_id_l1: BC-200 capability_name: General Ledger Management confidence: 0.9 evidence: 'createJournal Create a Journal; listJournalLines List Journal Lines; schemas: Journal, JournalLine' reason: General journals and journal lines in an ERP are the core general ledger posting mechanism. - tag: Purchase Invoices spec_file: navision-purchase-invoices-api-openapi.yml capability_id: BC-200.20 capability_id_l1: BC-200 capability_name: Accounts Payable Management confidence: 0.9 evidence: 'createPurchaseInvoice Create a Purchase Invoice; schemas: PurchaseInvoice, PurchaseInvoiceCreate' reason: Creating and listing purchase (vendor) invoices is invoice processing within Accounts Payable Management. - tag: Purchase Orders spec_file: navision-purchase-orders-api-openapi.yml capability_id: BC-500.30 capability_id_l1: BC-500 capability_name: Purchase Order Management confidence: 0.9 evidence: POST /companies({company_id})/purchaseOrders createPurchaseOrder Create a Purchase Order; List Purchase Order Lines reason: ERP purchase order CRUD — PO creation and lines is Purchase Order Management. - tag: Permission Sets spec_file: navision-permission-sets-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.85 evidence: POST /companies({company_id})/users({user_id})/userPermissions createUserPermission Assign a Permission Set to a User reason: Assigning permission sets to users and listing user permissions is identity and access management. - tag: Sales Invoices spec_file: navision-sales-invoices-api-openapi.yml capability_id: BC-200.30 capability_id_l1: BC-200 capability_name: Accounts Receivable Management confidence: 0.85 evidence: POST /companies({company_id})/salesInvoices createSalesInvoice Create a Sales Invoice reason: Customer invoicing in an ERP is Accounts Receivable Management. - tag: Vendor Payments spec_file: navision-vendor-payments-api-openapi.yml capability_id: BC-200.20 capability_id_l1: BC-200 capability_name: Accounts Payable Management confidence: 0.8 evidence: GET /companies({company_id})/vendorPaymentJournals listVendorPaymentJournals reason: Vendor payment journals are accounts payable payment processing. - tag: Customer Payments spec_file: navision-customer-payments-api-openapi.yml capability_id: BC-200.30 capability_id_l1: BC-200 capability_name: Accounts Receivable Management confidence: 0.75 evidence: GET /companies({company_id})/customerPaymentJournals List Customer Payment Journals reason: Customer payment journals in an ERP are the cash-application/receivables posting mechanism, squarely Accounts Receivable Management, though the surface is a single read operation. - tag: Customers spec_file: navision-customers-api-openapi.yml capability_id: BC-420.10 capability_id_l1: BC-420 capability_name: Customer Data Management confidence: 0.75 evidence: 'POST /companies({company_id})/customers Create a Customer; schemas: CustomerCreate, Customer, CustomerUpdate' reason: Full CRUD over the ERP customer master record — customer master data maintenance. Could also be read as AR sub-ledger master, but customer data management is the most defensible reading. - tag: Extensions spec_file: navision-extensions-api-openapi.yml capability_id: BC-600.60 capability_id_l1: BC-600 capability_name: IT Application Management confidence: 0.75 evidence: installExtension Install an Extension; uninstallExtension Uninstall an Extension; unpublishExtension Unpublish an Extension reason: Lifecycle management of installed apps/extensions in the ERP tenant — application lifecycle administration rather than a functional business capability. - tag: Environment Operations spec_file: navision-environment-operations-api-openapi.yml capability_id: BC-600.40 capability_id_l1: BC-600 capability_name: IT Operations Management confidence: 0.7 evidence: GET /environments/{environmentName}/operations List Environment Operations; schema EnvironmentOperation reason: Tracking of long-running administrative operations on Business Central environments — IT operations/administration tooling for a hosted application estate. - tag: Extension Upload spec_file: navision-extension-upload-api-openapi.yml capability_id: BC-600.60 capability_id_l1: BC-600 capability_name: IT Application Management confidence: 0.7 evidence: POST /companies({company_id})/extensionUpload createExtensionUpload; installUploadedExtension Install Uploaded Extension reason: Uploading and installing ERP extension (app) packages into the Business Central environment is application lifecycle/deployment administration, i.e. IT Application Management. Not a business-domain capability despite the ERP context. - tag: Item Categories spec_file: navision-item-categories-api-openapi.yml capability_id: BC-610.20 capability_id_l1: BC-610 capability_name: Master Data Management confidence: 0.7 evidence: 'GET /companies({company_id})/itemCategories listItemCategories List Item Categories; schemas: ItemCategory' reason: Item category reference data is product master data classification, supporting master data management. Thin evidence (read-only list), so moderate confidence.