Sage 300
Sage 300 is a mid-market ERP covering accounting, inventory, order entry, payroll, and project management for small and medium businesses primarily in North America. It runs on-premises or hosted through a Sage 300 partner and exposes data through Sage 300 Web Services using Basic auth.
What you can do
Read and write AR invoices
Pull open and posted Accounts Receivable invoices with customer details, line items, tax amounts, and payment terms. Post new AR invoices from your product's billing or contract-management workflow.
Sync customer records
Read customer master data including account group, credit limit, payment terms, and currency. Write back updated address or contact information from your CRM or onboarding product.
Access GL accounts and journal entries
Read the chart of accounts, fiscal period definitions, and posted journal entries. Useful for financial-reporting tools that need to pull transactions from Sage 300 into a consolidation or analytics view.
Read and write purchase orders
Pull open POs from the Sage 300 Purchase Orders module, including vendor details, line items, and expected receipt dates. Create new POs from your product's procurement or replenishment workflow.
Sync inventory items and stock levels
Read item master records, unit-of-measure definitions, and inventory quantities by location from the Inventory Control module. Askel handles Sage 300's multi-location inventory model.
Read vendor master and AP data
Pull vendor records, open AP invoices, and payment history. Useful for AP-automation products that need to match vendor invoices against POs or manage payment runs.
Pulling Sage 300 financials into a management-reporting platform
Wentworth Building Products is a regional distributor that runs accounting, inventory, and order entry on Sage 300. Their CFO has deployed your management-reporting platform to consolidate Sage 300 financials with data from other systems and produce monthly board reports. They need GL balances and journal entries from Sage 300 to land in the platform within an hour of month-end close.
- 1
Enable Sage 300 Web Services
Wentworth's IT administrator confirms that the Sage 300 Web Services component is installed and running on their Sage 300 server. They note the server hostname, port (typically 443 for HTTPS or 8080 for HTTP), and the Sage 300 company database identifier (e.g. SAMLTD).
- 2
Create a dedicated Sage 300 user
Wentworth's Sage admin creates a dedicated integration user in Sage 300 with read access to the GL, AR, AP, and Inventory modules. They note the username and password.
- 3
Enter credentials in Askel
Wentworth's CFO enters the Sage 300 host URL, company database ID, username, and password into the Askel setup screen inside your reporting platform. Askel composes the Basic auth header, constructs the web services URL, and confirms connectivity by fetching the chart of accounts.
- 4
Map and validate
Wentworth uses optional fields on GL accounts to tag cost-center segments. A CS rep maps these optional fields to the reporting platform's cost-center dimension and runs a dry-run against the prior quarter's journal entries to confirm the data loads and aggregates correctly.
- 5
Go live
The hourly GL sync is enabled for the days around month-end, and a nightly sync for the rest of the month. Askel pulls new journal entries from Wentworth's Sage 300 company and loads them into the reporting platform. The CFO's board reports are populated automatically within the hour after close.
Basic auth
The customer's Sage 300 administrator provides the web services host URL, the Sage 300 company database identifier, a dedicated user account username, and password. Askel composes Basic auth credentials and constructs the web services endpoint URL from the host and company ID. The Sage 300 Web Services component must be installed and accessible from Askel's infrastructure.
How Askel sits between your product and the customer's system
FAQ for Sage 300
Which Sage 300 versions are supported?+
Does this work with Sage 300cloud (Sage 300 hosted by a partner)?+
What module access does the Sage 300 user need?+
How are Sage 300 optional fields handled?+
catching drift before it breaks, and hitting go-live dates.
© 2025 Askel.ai. All rights reserved.