Dynamics NAV (also known as Navision) is Microsoft's on-premises ERP for small and mid-market companies covering financials, sales, purchasing, inventory, and manufacturing. It is the predecessor to Business Central and remains in active use at thousands of companies that have not yet migrated to the cloud.
Pull open, released, and shipped sales orders with customer details, line items, and delivery dates. Create new orders and update quantities or pricing from your product.
Read customer master data including payment terms, credit limit, currency, and assigned salesperson. Write back updated contact or shipping address information from your CRM or onboarding product.
Read item master records with unit of measure, unit price, and inventory levels by location. Askel handles NAV's multi-location inventory structure so your product sees quantities by warehouse.
Pull approved purchase orders and outstanding receipts. Create new purchase orders from your product's replenishment or procurement workflow.
Read the chart of accounts and GL entries by posting date and account number. Useful for accounting and financial-reporting products that need to pull transactions from NAV into their own ledger view.
Pull vendor master data including payment terms, bank account details, and purchase currency. Write back updated addresses or contact details from your supplier-management product.
Thornbrook Office Supplies has run their financials and inventory on Dynamics NAV for a decade and recently added your AR automation product to reduce manual collections work. Their finance team needs open invoices from NAV to appear in the AR platform daily so collectors can prioritize outreach without exporting spreadsheets.
Thornbrook's NAV administrator opens the Web Services page in NAV (typically at /DynamicsNAV/WebClient/default.aspx, then searching for Web Services). They publish the Customer, Sales Invoice, and Sales Order pages as SOAP or OData services. Askel's setup guide provides the exact page names to publish.
Thornbrook's admin enters the NAV host URL (including port 7048), the NAV instance name (e.g. DynamicsNAV110), the company name, and the NAV username and password into the Askel setup screen. Askel composes the Basic auth header and constructs the Web Services URL, then confirms connectivity by fetching the customer list.
Askel reads the SOAP or OData service definitions for the published NAV pages and identifies the Customer, Sales Invoice, and Sales Order fields. Any custom fields Thornbrook has added to these pages appear alongside the standard fields in the mapping draft.
Thornbrook uses a custom field on the Sales Invoice page to track their internal collection category. A CS rep maps this to the AR platform's bucket attribute and runs a dry-run against 300 open invoices to confirm the data imports correctly.
The nightly AR sync is enabled. Askel pulls all open invoices from Thornbrook's NAV company, loads them into the AR platform, and flags overdue items for the collections queue. When a payment is posted in NAV, the invoice status updates in the platform on the next sync.
The customer's NAV administrator publishes the required Pages and Codeunits as Web Services in the NAV admin console, then provides the NAV host, port 7048, instance name, optional company name, username, and password. Askel composes Basic auth and builds the Web Services URL from these components. Windows Authentication is not supported; NAV user accounts with NavUserPassword or AAD credentials are required.
© 2025 Askel.ai. All rights reserved.