How Business Central SOAP Web Services Work
A SOAP integration uses a service endpoint through which an external application sends an XML-formatted request. Business Central receives the request, authenticates the caller, evaluates permissions, executes the requested operation, and returns an XML response containing the result or relevant service information.
Published Business Central pages can expose business entities through SOAP, while codeunits can expose specific business logic or operations. This distinction allows an integration to either work with structured business data or invoke defined application functionality.
- SOAP endpoint: Provides the address through which an external system communicates with Business Central.
- WSDL: Describes the available service operations, messages, data types, and endpoint information.
- XML messages: Carry requests and responses between the connected application and Business Central.
- Authentication and permissions: Control which users or applications can access published services and perform supported operations.
SOAP Services and Business Central Finance
SOAP web services can connect Business Central with financial applications, procurement systems, reporting platforms, banking solutions, and other enterprise software. A connected application can retrieve relevant information or submit supported transactions according to the service definition.
For procurement, a purchase order can form part of a connected procure-to-pay process in which requisitions, approvals, purchasing controls, and Business Central records are synchronized. This type of service-oriented integration helps maintain consistent transaction information across applications.
SOAP connectivity can also support accrual-related processes. Accruals Discovery For Services Receieved But Not Invoiced can use reports, timesheets, and confirmations to identify services received without invoices, providing useful information for accurate accrual processing.
Vendor payment workflows can similarly use connected Business Central information. Late Payment Recommendations supports payment scheduling decisions by considering vendor obligations, payment timing, and cash flow priorities. A Flexible Workflow can apply approval rules according to business unit, department, and monetary thresholds.
SOAP, Pages, Codeunits, and Business Logic
One of the important characteristics of Business Central SOAP services is that they can expose published pages and codeunits. A page-based service is useful when an external system needs access to records represented by a Business Central page. A codeunit-based service is useful when the integration needs to invoke defined business operations.
This distinction matters because the service contract determines what external applications can request and how the returned information is structured. The WSDL provides the consuming application with the technical description needed to construct valid SOAP messages.
For finance integrations, this approach can connect Business Central with established enterprise applications while preserving defined Business Central business logic. The integration architecture should therefore be designed around the actual transaction or information requirement rather than simply exposing every available object.
SOAP Integration Architecture
A typical SOAP architecture contains the external application, authentication mechanism, integration layer, Business Central SOAP endpoint, and downstream business process. The integration layer can transform XML data, map fields, route requests, and coordinate information between Business Central and other applications.
When evaluating ERP integration for professional-services organizations, ERP for Professional Services: Best Platforms, AI & ROI provides broader context on ERP capabilities and finance workflows. The relationship between ERP functionality and operational processes is also relevant when considering How ERP and Business Processes Work Together.
Organizations comparing ERP platforms for growing businesses can also use Best ERP for Medium-Sized Business in 2025 – Full Guide as context when assessing integration capabilities, extensibility, and connected financial operations.
SOAP Services in Connected Finance Automation
SOAP services can provide structured access to Business Central information for finance workflows that rely on established enterprise integrations. XML-based requests and responses can carry transaction information between applications, supporting processes such as invoice handling, accruals, vendor management, and financial reporting.
The Hyperbots Platform can incorporate connected ERP information into finance workflows, including document processing, business rules, and tax validation. More broadly, Web Services Finance provides terminology for understanding the role of web services in finance and business workflows.
Banking connectivity is another relevant area. Bank Web Services describes web-based interfaces used to connect banking information with financial applications. At an enterprise level, Central Finance provides context for coordinating financial information and processes through centralized finance capabilities.
Best Practices for Business Central SOAP Services
Effective SOAP integration begins with identifying the exact pages or codeunits required by the external application. The service contract should then be documented so that developers understand available operations, data types, authentication requirements, and expected responses.
- Define service scope: Publish only the Business Central objects and operations required by the integration.
- Protect access: Apply appropriate authentication and permissions for every consuming application.
- Validate XML: Ensure requests follow the expected SOAP structure, namespaces, fields, and data types.
- Monitor transactions: Track service requests, responses, and business processing outcomes.
- Maintain mappings: Document relationships between external-system fields and Business Central fields.
For broader ERP connectivity, integration architecture should also account for how Business Central exchanges data with other enterprise systems. This helps keep financial workflows aligned with the ERP while supporting connected applications and reporting processes.
Summary
Business Central SOAP Web Services provide an XML-based integration mechanism for external applications that need to communicate with Business Central through published pages and codeunits. SOAP endpoints, WSDL definitions, XML messages, authentication, and permissions form the core components of this service model.
SOAP services can support established finance and operational integrations involving procurement, vendor management, accruals, reporting, and other Business Central processes. When service contracts, permissions, mappings, and monitoring are defined clearly, SOAP provides a structured foundation for connecting Business Central with enterprise applications.