.png)
Deltek Costpoint Integration Guide
Deltek Costpoint integrates with enterprise systems through REST web services, selected SOAP services, batch processes, and file-based exchanges.
Deltek Costpoint integration options at a glance
Deltek Costpoint provides RESTful web services for supported business functions, with available resources and operations determined by the release, modules, and deployment. SOAP services may remain available for selected versions or legacy implementations. Costpoint also supports batch-oriented processing and file-based imports or exports in some functional areas, although there is no confirmed universal bulk endpoint or general-purpose webhook framework. Martini can consume Costpoint REST or SOAP services, coordinate scheduled incremental synchronization, transform JSON, XML, or file data, apply validation and business rules, and expose controlled APIs for downstream systems. OAuth 2.0 is documented for supported REST configurations, while Basic Authentication may apply to selected legacy services.
| Integration point | Supported by Deltek Costpoint? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Yes | Read, create, and update supported Costpoint business objects, submit transactions, and coordinate project, labor, purchasing, and billing workflows. | Martini can consume Costpoint REST web services over HTTPS, map responses and requests, apply business rules, and orchestrate calls with other systems. |
| SOAP APIs | Limited | Support existing integrations or Costpoint functions exposed through legacy web services in selected releases or configurations. | Martini can consume SOAP services where the target Costpoint environment exposes them, with XML mapping, authentication configuration, and service-level error handling. |
| Webhooks / outbound callbacks | Not confirmed | A general-purpose webhook framework covering changes to Costpoint business objects was not confirmed. | Martini can receive external webhook events from surrounding systems, but Costpoint changes should use polling, batch processing, or supported exports unless callbacks are confirmed in the environment. |
| Bulk / async / batch processing | Limited | Process high-volume loads through module-specific batch jobs, import processes, web services, or files. | Martini can submit batches or files where supported, poll processing status, preserve row-level errors, and avoid reporting success before Costpoint acceptance is confirmed. |
| File imports and exports | Limited | Exchange labor, accounting, master-data, or other functional-area data where Costpoint import and export processes are available. | Martini can generate, validate, transfer, and process structured files, then monitor supported completion or rejection results. |
| Database / analytics access | Limited | Use authorized on-premises database access for reporting or reconciliation where deployment, licensing, and policy permit it. | Martini can connect to supported databases where authorized, while transactional writes should remain on Costpoint APIs or governed import processes. |
| OAuth 2.0 authentication | Yes | Authenticate supported Costpoint REST integrations using registered client credentials and environment-specific OAuth configuration. | Martini can keep client credentials and tokens in secure configuration and use authenticated API workflows without embedding secrets in logic. |
| HTTP Basic Authentication | Limited | Support selected legacy or configured Costpoint web-service environments subject to local security policy. | Martini can configure Basic Authentication for applicable endpoints, with HTTPS, least privilege, and environment-specific verification. |
How Deltek Costpoint exposes data and business events
Deltek Costpoint REST APIs
Costpoint provides RESTful web services for supported business functions. Resource availability, fields, methods, and endpoint paths depend on the Costpoint release, enabled modules, and deployment configuration.
Martini implementation pattern
Martini implementation pattern: a workflow authenticates to the target Costpoint environment, retrieves or submits a resource, handles pagination and response validation, transforms the data, and writes the result to another system or exposes it through a Martini API.
Implementation sequence
Deltek Costpoint SOAP Services
SOAP services may be available in selected Costpoint versions or configurations, particularly for existing integrations or functions not exposed through REST. Availability should be confirmed before design.
Martini implementation pattern
Martini implementation pattern: a workflow sends an authenticated SOAP request, parses the XML response, maps service-level and business-level errors, and continues orchestration only after the Costpoint operation is accepted.
Implementation sequence
Costpoint Batch Processing
Costpoint supports batch-oriented integration processes, but the exact behavior varies by module and release. Processing may use web services, import jobs, or application-specific batch functions rather than one universal bulk API.
Martini implementation pattern
Martini implementation pattern: a workflow prepares a bounded batch, submits it through the supported Costpoint mechanism, monitors status where available, and records accepted and rejected rows separately.
Implementation sequence
Costpoint File Imports and Exports
Costpoint uses file-oriented imports and exports in some functional areas, including larger accounting or labor-data exchanges and legacy interfaces. Format, staging, naming, and status requirements are deployment-specific.
Martini implementation pattern
Martini implementation pattern: a workflow extracts source data, produces the required file, transfers or stages it according to the environment, and records processing results without treating file delivery alone as business acceptance.
Implementation sequence
Scheduled Incremental Synchronization
A broadly available Costpoint webhook framework was not confirmed. Near-real-time or recurring synchronization therefore commonly relies on scheduled queries using modification timestamps, change filters, batch processes, or supported exports.
Martini implementation pattern
Martini implementation pattern: a scheduled workflow reads a persisted watermark, retrieves changed Costpoint objects, uses an overlap window where necessary, performs idempotent target updates, and advances the watermark only after successful completion.
Implementation sequence
Common Deltek Costpoint integration patterns
Pattern 1: Synchronize employees and projects with workforce or CRM systems
When to use this pattern
Use this pattern when Costpoint is the system of record for project-accounting structures or when workforce and customer-facing systems require current employee and project information. Scheduled incremental reads are appropriate because a general-purpose Costpoint webhook framework was not confirmed.
Integration direction
Example Mapping
| Deltek Costpoint Field | Canonical Field | Target Field |
|---|---|---|
| Employee ID | workerId | Worker identifier |
| Organization | organizationCode | Supervisory organization |
| Project ID | projectCode | Project external ID |
| Project status | projectStatus | Project lifecycle status |
Martini implementation pattern
Martini loads the prior watermark, retrieves changed Employees and Projects with pagination, validates organization and project relationships, maps the objects to the target model, and performs idempotent upserts. It uses overlap windows for timestamp precision, stores cross-references, and routes rejected records without advancing the watermark for unprocessed data.
Martini capabilities used
- scheduled workflows
- API consumption
- pagination handling
- data mapping
- business rules
- idempotent upserts
- error handling
Pattern 2: Synchronize vendors and purchase orders with procurement platforms
When to use this pattern
Use this pattern when Costpoint remains authoritative for government-contract purchasing while another platform manages broader procurement operations or supplier collaboration.
Integration direction
Example Mapping
| Deltek Costpoint Field | Canonical Field | Target Field |
|---|---|---|
| Vendor ID | supplierId | Supplier external ID |
| Purchase Order number | purchaseOrderNumber | Purchase order reference |
| Purchase Order lines | purchaseOrderLines | Order lines |
| Project | projectCode | Project or cost object |
Martini implementation pattern
A Martini workflow retrieves Vendors and Purchase Orders through supported Costpoint APIs or batch processes, enriches them with cross-reference data, validates supplier and project keys, and submits target-system updates. Duplicate detection, bounded retries, and separate business-validation queues protect against repeated purchasing transactions.
Martini capabilities used
- workflow orchestration
- REST or SOAP consumption
- mapping and transformation
- cross-reference storage
- validation
- retry handling
Pattern 3: Process customers and invoices for finance or billing applications
When to use this pattern
Use this pattern when Costpoint billing and receivables data must be synchronized with a finance, customer-facing, or compliance reporting application while preserving invoice state and accounting context.
Integration direction
Example Mapping
| Deltek Costpoint Field | Canonical Field | Target Field |
|---|---|---|
| Customer ID | customerId | Account external ID |
| Invoice number | invoiceNumber | Invoice reference |
| Invoice status | invoiceStatus | Document status |
| Amount and currency | invoiceAmount and currency | Total and currency code |
Martini implementation pattern
Martini retrieves Customers and Invoices, distinguishes creation from status changes, maps project and accounting dimensions, and sends validated payloads to the target. The workflow records Costpoint validation messages, preserves correlation identifiers, and retries only transient transport or availability failures.
Martini capabilities used
- API consumption
- scheduled synchronization
- canonical data mapping
- business rules
- reconciliation
- error classification
Pattern 4: Exchange labor or accounting data through Costpoint files
When to use this pattern
Use this pattern when the required Costpoint function is exposed through an import or export process rather than a REST resource, or when high-volume data is best handled through a governed file interface.
Integration direction
Example Mapping
| Deltek Costpoint Field | Canonical Field | Target Field |
|---|---|---|
| Worker identifier | employeeId | Employee ID |
| Project code | projectCode | Project |
| Labor hours | hours | Reported hours |
| Accounting period | accountingPeriod | Period |
Martini implementation pattern
Martini extracts source data, validates required fields and control totals, transforms it into the Costpoint-required format, and delivers or stages the file according to the deployment. It monitors supported processing status, stores rejected rows and diagnostics, and reports completion only after Costpoint acceptance is confirmed.
Martini capabilities used
- scheduled workflows
- file processing
- data transformation
- validation
- batch orchestration
- monitoring
- error handling
Applications commonly integrated with Deltek Costpoint
Costpoint commonly participates in enterprise architectures that combine project accounting, workforce management, procurement, finance, customer management, and compliance reporting. The following are practical integration targets; exact object coverage and direction should be confirmed for each implementation.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| Salesforce | Synchronize customers, projects, contracts, and billing-related status between customer management and Costpoint project accounting. | Salesforce → Martini → Deltek Costpoint | Martini receives or schedules Salesforce changes, validates customer and project relationships, maps them to Costpoint REST resources, and stores cross-system identifiers with retry and rejection handling. |
| Workday | Exchange employee, organization, and worker-status data for labor, project staffing, and costing processes. | Workday → Martini → Deltek Costpoint | A scheduled Martini workflow retrieves changed Workday workers and organizations, transforms them into Costpoint Employees and organization structures, and routes validation failures for review. |
| ServiceNow | Connect approval, project, procurement, and service workflows with Costpoint financial and project records. | ServiceNow → Martini → Deltek Costpoint | Martini orchestrates ServiceNow requests and Costpoint API calls, applies approval and project rules, and returns Costpoint identifiers and statuses to ServiceNow. |
| Jira | Associate software or engineering work with Costpoint Projects, tasks, and labor reporting. | Jira → Martini → Deltek Costpoint | Martini retrieves approved Jira work or time data, maps it to Costpoint project and labor structures, validates project eligibility, and records rejected rows separately. |
| NetSuite | Exchange Customers, Vendors, Invoices, Purchase Orders, and accounting information where both platforms operate in the enterprise. | Deltek Costpoint → Martini → NetSuite | Martini synchronizes selected Costpoint objects with NetSuite through API calls, canonical mappings, duplicate detection, and reconciliation of source and target identifiers. |
| Microsoft Dynamics 365 | Synchronize customer, vendor, project, purchasing, and financial information across business units. | Microsoft Dynamics 365 → Martini → Deltek Costpoint | Martini schedules incremental reads from both systems, applies company and project mapping rules, and performs idempotent upserts with bounded retries. |
| SAP S/4HANA | Connect corporate finance, procurement, and master-data processes with Costpoint government-contract project accounting. | SAP S/4HANA → Martini → Deltek Costpoint | Martini consumes approved SAP data, transforms accounting and project dimensions for Costpoint, and sends Costpoint transactions or statuses back through controlled workflows. |
| Workiva | Transfer financial, project, and compliance data for reporting, audit, and government-contract compliance processes. | Deltek Costpoint → Martini → Workiva | Martini extracts approved Costpoint data on a schedule, applies reporting-specific transformations, and delivers validated payloads while retaining execution and reconciliation metadata. |
How to build a Deltek Costpoint integration in Martini
Objective
Establish an environment-specific connection to Costpoint using the authentication method and endpoint supported by the target release and deployment.
Instructions in Martini
- Confirm the Costpoint release, modules, deployment model, and enabled web services.
- Configure the HTTPS endpoint and OAuth 2.0 client credentials where supported.
- Use Basic Authentication only where the target service and security policy permit it.
- Store secrets and credentials in secure Martini configuration.
Objective
Select a trigger that reflects Costpoint’s confirmed integration mechanism rather than assuming outbound events are available.
Instructions in Martini
- Use a scheduled trigger for incremental API reads when Costpoint webhooks are not confirmed.
- Use an external event or API trigger when another system initiates the process.
- Use a batch or file workflow when the required Costpoint function is exposed through import or export processing.
Objective
Read the required Costpoint object or receive source data while respecting pagination, filtering, and batch boundaries.
Instructions in Martini
- Retrieve Projects, Employees, Vendors, Customers, Purchase Orders, or Invoices through supported resources.
- Follow Costpoint pagination fields or continuation links.
- Use modification timestamps or supported change filters for incremental synchronization.
- Capture source identifiers, response metadata, and processing context.
Objective
Coordinate Costpoint calls, target-system calls, transformations, validations, and state management in a maintainable Martini workflow.
Instructions in Martini
- Separate extraction, transformation, validation, delivery, and reconciliation stages.
- Use reusable workflow logic for common authentication, pagination, and error handling.
- Persist watermarks and cross-reference identifiers only at appropriate transaction boundaries.
- Route partial failures without obscuring successful records.
Objective
Convert Costpoint structures into the target system’s canonical and application-specific model.
Instructions in Martini
- Map Costpoint identifiers, organizations, projects, accounting dimensions, statuses, amounts, and dates.
- Transform JSON, XML, or file data as required by the target endpoint.
- Handle optional fields and deployment-specific schema differences explicitly.
- Apply controlled defaults only where business ownership has approved them.
Objective
Validate relationships and business conditions before submitting transactions or advancing synchronization state.
Instructions in Martini
- Validate companies, organizations, projects, contracts, vendors, employees, and accounting periods.
- Distinguish transport failures from Costpoint business-validation failures.
- Reject duplicates and use deterministic keys for retry-safe upserts.
- Preserve Costpoint validation messages for remediation.
Common Deltek Costpoint data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Projects | Synchronize project master data, structures, status, and project-accounting attributes. | Salesforce, Jira, Workday, SAP S/4HANA, reporting platforms | Martini retrieves changed Projects, validates companies and organizations, maps project structures, and performs idempotent creates or updates. |
| Employees | Exchange employee master data, labor information, organizations, and employment status. | Workday, Jira, ServiceNow, reporting platforms | Martini maps employee identifiers and organization relationships, protects sensitive fields, and routes invalid or duplicate records for review. |
| Vendors | Synchronize supplier master data for purchasing and accounts payable. | NetSuite, Microsoft Dynamics 365, SAP S/4HANA, procurement platforms | Martini validates supplier keys and payment-related mappings, then upserts Vendors and stores cross-reference identifiers. |
| Customers | Exchange customer or contract-billing party information associated with projects and receivables. | Salesforce, NetSuite, Microsoft Dynamics 365, Workiva | Martini normalizes customer data, applies duplicate and ownership rules, and synchronizes Costpoint Customers with downstream systems. |
| Purchase Orders | Transfer purchasing documents, lines, suppliers, commitments, and receiving-related data. | NetSuite, SAP S/4HANA, Microsoft Dynamics 365, procurement platforms | Martini validates supplier and project references, maps header and line structures, and separates transport retries from business rejections. |
| Invoices | Exchange customer or vendor invoice data for billing and accounts payable processes. | NetSuite, SAP S/4HANA, Microsoft Dynamics 365, Workiva | Martini distinguishes invoice creation from status changes, maps amounts and accounting dimensions, and reconciles target processing results. |
Authentication and security considerations
Environment-specific authentication
Costpoint authentication depends on the release, deployment model, enabled services, and administrator configuration. OAuth 2.0 is documented for supported REST configurations, while Basic Authentication may apply to selected legacy or configured services.
Least privilege and transport security
- Use HTTPS and service accounts with only the Costpoint companies, organizations, projects, and operations required.
- Store OAuth client secrets, passwords, tokens, and endpoint configuration in Martini secure configuration.
- Restrict logs containing employee, labor, invoice, contract, financial, or government-related information.
Deployment verification
Confirm endpoint paths, certificate requirements, client registration, roles, and available resources against the target Costpoint environment before implementation.
Operational considerations for Deltek Costpoint integrations
Synchronization controls
- Handle pagination and use bounded page sizes where supported.
- Use modification timestamps or change filters with overlap windows when timestamp precision may cause boundary gaps.
- Advance synchronization watermarks only after complete successful processing.
Reliability and validation
- Use controlled concurrency, bounded retries, and exponential backoff for transient failures.
- Separate transport errors from Costpoint business validation, duplicate, and partial-batch errors.
- Do not report batch or file success until the relevant Costpoint processing status confirms acceptance.
Change management
Costpoint schemas, resources, required fields, enumerations, and accounting structures may vary by release and module configuration. Test mappings against the target environment and monitor upgrades for breaking changes.
Why use Martini instead of scripts or point-to-point integrations?
Orchestration instead of isolated scripts
Martini provides a governed workflow layer for Costpoint API calls, scheduled synchronization, file processing, target-system delivery, validation, and reconciliation. This avoids duplicating authentication, pagination, mapping, and error logic across unrelated scripts.
Maintainable integration behavior
Workflows can separate extraction, transformation, business rules, delivery, and monitoring while retaining reusable integration logic. Martini can also expose controlled APIs when applications need a stable interface over Costpoint data.
Operational reliability
- Centralize secure configuration and secrets.
- Apply consistent retry, idempotency, watermark, and error-routing policies.
- Monitor executions and preserve diagnostics for reconciliation and support.
Frequently asked questions
Deltek Costpoint can be integrated through RESTful web services, selected SOAP services, batch-oriented processes, and file-based imports or exports. The appropriate mechanism depends on the Costpoint release, enabled modules, deployment model, and required business function. Scheduled incremental synchronization is often required because a general-purpose webhook framework was not confirmed.
Yes. Martini can consume supported Costpoint REST APIs, use SOAP services where enabled, coordinate batch or file exchanges, schedule incremental workflows, map Costpoint objects, and expose controlled APIs for downstream applications. The exact implementation should be validated against the target Costpoint environment.
No. A dedicated Deltek Costpoint connector is not required. Martini can use Costpoint’s confirmed native integration mechanisms, including REST APIs, applicable SOAP services, scheduled retrieval, batch processing, file exchange, and the authentication methods enabled in the target environment.
Lonti does not charge an additional per-connector or per-vendor fee to integrate Deltek Costpoint. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Deltek, cloud infrastructure, or other third-party systems based on subscription, usage, and deployment model.
REST should generally be evaluated first when the required Costpoint resource and operation are available. SOAP may be appropriate for existing interfaces or functions exposed only through legacy services. Batch processes and files may be better for high-volume or module-specific exchanges. The target environment’s documentation should confirm available resources, operations, and authentication.
A broadly available, general-purpose Costpoint webhook framework was not confirmed. Integrations should not assume that changes to Projects, Employees, Vendors, Customers, Purchase Orders, or Invoices generate callbacks. Scheduled incremental reads, batch processes, supported exports, or external middleware may be needed for event-style processing.
Martini can schedule workflows, retrieve changed Costpoint objects using supported timestamps or filters, follow pagination, map data into canonical and target models, and perform idempotent upserts. It can maintain watermarks and cross-references, apply business rules, and reconcile target identifiers and processing results.
Martini workflows can classify authentication, network, throttling, structural, duplicate, and business-validation errors. Transient failures can use bounded retries and backoff, while validation failures can be routed for remediation. Stable Costpoint identifiers, deterministic keys, cross-reference storage, and delayed watermark advancement help make retries safe.
Related Martini documentation
APIs
Workflows
Data
Plan your Deltek Costpoint integration
Use Martini to connect Deltek Costpoint with enterprise applications through governed APIs, scheduled workflows, batch processes, and file exchanges. Validate the target Costpoint environment, select the appropriate integration mechanism, and design reliable synchronization with secure configuration, mapping, business rules, and operational monitoring.