Finance & ERP
Microsoft Dynamics 365 Business Central and Finance, SAP, Odoo
Invoices, outstanding balances, budgets, costs, purchase orders and serialised receiving records.
See the related question →Example Data Sources
These named systems make the scenarios concrete. They are example sources, subject to assessment, and do not establish a supported connector or partner relationship.
Invoices, outstanding balances, budgets, costs, purchase orders and serialised receiving records.
See the related question →Schedules, progress, labour entries, site instructions and commercial variations.
See the related question →Requests, incidents, assignment histories, approvals, service targets and delivery issues.
See the related question →Business relationships, actual permissions, role activation and access approvals. CyberArk is an optional source where already used.
See the related question →Alerts, findings and exploitation context. External context is assessed for availability, permission and deployment restrictions.
See the related question →Asset identity, service dependencies, observed network location and management records. Observations come from agreed sources.
See the related question →Contracts, acceptance records, variation approvals, access extensions and contractor, lease, BYOD or virtual-resource approvals.
See the related question →Available interfaces, permissions, licensing, record identifiers, matching quality, historical coverage, refresh schedules and deployment restrictions. Some sources may require custom integration or approved exports. A named system is not a promise of native, certified or universal connectivity.