# How to add WhatsApp to Deltek Costpoint

> Source: https://netray.co/integrations/deltek-costpoint-whatsapp
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Integrations

## Short answer

Costpoint has no native WhatsApp channel, so the pattern is a small middleware service: read events and records from Costpoint (web services or reporting views), send approved template messages through the WhatsApp Business Platform, and post replies back as reviewed transactions or notes. For contractors, the safest scope is supplier and subcontractor coordination, not timesheets or anything touching controlled data.

## System

Deltek Costpoint

## Capability

whatsapp

## Intro

Costpoint shops that build hardware under government contracts spend a surprising amount of buyer time chasing suppliers: is the PO acknowledged, what is the real ship date, did the material cert go out. Much of that chase already happens on mobile, and in many regions and small supplier shops it happens on WhatsApp whether the buyer likes it or not. The result is promised dates living in personal phones while Costpoint still shows the date from the original PO line.

WhatsApp is also attractive for the internal side: a project manager who is on a customer site wants to approve a requisition or see a commitment status without opening a VPN session. The catch is that Costpoint is an accounting system of record for cost-type contracts, so every message needs to respect who may see which project, and nothing should be written to the ledger just because a phone replied.

This page covers the realistic architecture, what Costpoint exposes for it, the WhatsApp Business rules that shape the design (opt-in, templates, the 24 hour window), and where the approach is a bad fit.

## Use Cases

### Supplier PO acknowledgement chase

**Description:** When a purchase order is released and unacknowledged after a set number of days, send a template message to the supplier contact with the PO number and a Confirm / Change date quick reply. The reply is logged against the PO for the buyer to apply.

### Subcontractor invoice and milestone nudges

**Description:** Remind subcontractors to submit a milestone invoice or progress report that a subcontract schedule expects, with a link to your portal rather than attachments in the chat.

### Mobile approval of requisitions

**Description:** Send an approver a summary of a requisition (project, task, amount, vendor) with Approve and Reject buttons. The approval is relayed to a workflow step only after the sender number is matched to a Costpoint user.

### Shipment and receipt alerts for program managers

**Description:** Notify the project owner when long-lead material is received or a receiving inspection fails, so schedule risk is seen the same day.

### Field staff reminders without exposing hours data

**Description:** Send a generic reminder that timesheets are due. Keep it contentless: no hours, charge codes or contract numbers in the WhatsApp message.

## System Surface

Costpoint web services and APIs: depending on your version and licensing, Deltek exposes web service and REST style interfaces for several business objects. Confirm which objects (purchase orders, vouchers, projects) your release and contract include before designing around them.

Database: Costpoint runs on Microsoft SQL Server (Oracle in older installs). Read-only reporting views or a replica are a common, safer source for polling PO and receipt status than the transactional tables.

Workflow and notifications: Costpoint has its own approval workflow and email notifications. These can be a trigger point, for example by having notifications land in a mailbox that your service reads.

Import tools: Costpoint's standard import mechanisms (flat file and spreadsheet style imports for several screens) are a controlled way to push accepted changes in, with the usual validation applied.

Costpoint Cloud / GovCon cloud: hosted customers usually cannot query the database directly, so everything goes through supported APIs, exports or integration offerings. Ask Deltek or your reseller what is enabled for your tenant.

## How It Works

### Pick the data source per event

**Detail:** Use an API call or a read-only view per event type (PO released, receipt posted, requisition pending). Avoid screen scraping the web UI; it breaks on upgrades and bypasses role checks.

### Register a WhatsApp Business account

**Detail:** Use the WhatsApp Business Platform Cloud API directly or through a Business Solution Provider. You need a verified Meta business, a dedicated number and approved message templates.

### Collect and store opt-in

**Detail:** Record that a supplier contact agreed to receive WhatsApp messages, with date and source. Keep this in a small table in your middleware, not in a free text Costpoint field.

### Build the middleware

**Detail:** A small service that polls or receives events, maps vendor ID to contact number, renders a template, sends it, and stores the message ID and status. Add idempotency so a retried job does not message twice.

### Handle inbound replies

**Detail:** Receive webhooks, match the sender to a vendor and open PO, parse button payloads, and create a pending change record for the buyer. Free text replies go to a review queue.

### Write back through a gate

**Detail:** A date change or acknowledgement is applied only after a buyer accepts it, using the supported API or import path so Costpoint business rules and audit fields stay intact.

## Example Flows

### Unacknowledged PO chase

**Trigger:** A PO released five business days ago has no acknowledgement flag.

**Steps:**

- Middleware reads the PO and vendor contact from a reporting view.
- It sends the po_ack template with PO number and the first promised date.
- Supplier taps Confirm or Change date and types a new date.
- Reply is stored as a proposed change with the original message ID.
- Buyer sees it in a queue and accepts, which updates the PO line through the API.

**Result:** Promised dates in Costpoint reflect what the supplier said, with a trail of who accepted the change.

### Requisition approval on mobile

**Trigger:** A requisition reaches the approver's step in Costpoint workflow.

**Steps:**

- Event picked up from the workflow notification mailbox or an API poll.
- Approver number matched to a Costpoint user; if no match, send nothing.
- Template shows vendor, amount and project name only, plus a secure link for detail.
- Approve button posts the decision to a service that calls the workflow action.

**Result:** Approvals that used to wait for a laptop clear the same day, still under the user's own Costpoint identity.

## On Prem

WhatsApp itself is always a cloud service, so the on-prem question is what you let cross that boundary. Keep Costpoint, the middleware and any language model inside your network, and send only minimal template variables outbound: a PO number and a date, not part descriptions tied to a controlled program. If an open-weight model is used to classify free text replies, run it on your own GPUs with vLLM or Ollama and pass it only the reply text and a PO number. For contractors handling CUI or ITAR data, treat WhatsApp as an external channel and decide per field what is allowed; many will limit it to logistics data only.

## Security

- Never put hours, rates, indirect cost data or contract numbers for restricted programs into WhatsApp messages; use a link to an authenticated portal instead.
- Match every inbound number to a known vendor or Costpoint user before acting; unknown senders get a polite fixed reply and no data.
- Verify webhook signatures from Meta and store access tokens in a secrets manager, not in config files.
- Log each message, template, sender and resulting action for audit; contractors under DCAA scrutiny need to explain how a date or approval changed.
- Use a service account with read-only access for polling and a separate, narrowly scoped one for write-back.

## Options

### Marketplace or BSP workflow tool

**Fit:** Simple notifications from exported data, with no two-way write-back to Costpoint.

**Effort:** Days to a couple of weeks plus message fees.

### In-house middleware

**Fit:** Teams with a developer who knows Costpoint's APIs and wants full control over data and approval rules.

**Effort:** Roughly 4 to 8 weeks for a first supplier flow, then ongoing template upkeep.

### Partner build such as Netray with a Costpoint integrator

**Fit:** Two-way flows with AI parsing of replies, human approval and an on-prem model.

**Effort:** Scoped per flow; a pilot is typically weeks, not months.

## Pitfalls

- Messaging outside the 24 hour customer service window without an approved template fails; plan templates for every proactive message.
- Vendor contact data in Costpoint is often an office line or shared mailbox, not a mobile number; budget time to collect real WhatsApp numbers and opt-in.
- Direct database writes to PO tables skip Costpoint business rules and can corrupt audit trails; use supported interfaces.
- Cloud-hosted Costpoint may not allow direct SQL, which invalidates a design built on views.
- Treating a chat reply as authoritative: a supplier saying 'next week' is not a date, so route ambiguous text to a person.

## Faq

### Does Deltek Costpoint have a built-in WhatsApp integration?

**Answer:** Not to our knowledge. Costpoint offers email notifications, workflow and APIs, and some resellers offer add-ons, but WhatsApp is typically connected through a separate middleware that reads from Costpoint and calls the WhatsApp Business Platform. Check with Deltek for your release.

### Can approvals be done over WhatsApp safely?

**Answer:** Yes for low-risk approvals if the sender number is mapped to a Costpoint user, the message is a template with minimal detail, and the decision is applied through the normal workflow. For high-value or controlled-program approvals, use a link to an authenticated page instead.

### Is WhatsApp acceptable for a defense contractor?

**Answer:** It depends on what you send. Logistics data such as a PO number and a date is generally low risk; CUI, ITAR technical data and cost data are not appropriate for a consumer messaging channel. Your compliance owner should set the field-level rules before launch.

### Do we need Costpoint web services to do this?

**Answer:** Not strictly. Read-only reporting views or scheduled exports can drive outbound alerts. Writing replies back safely is where supported APIs or import tools matter, so confirm what your version and hosting model allow.

### What does it cost to run?

**Answer:** Meta charges per conversation or per message depending on category and country, and a BSP may add a platform fee. For a few hundred supplier messages a month the message cost is usually small compared with the build and maintenance effort.

## Search terms

deltek costpoint whatsapp integration, whatsapp for deltek costpoint, costpoint whatsapp api, costpoint purchase order notifications whatsapp, costpoint supplier communication, costpoint approvals mobile, whatsapp business api erp government contractor, costpoint subcontractor reminders, costpoint workflow notifications, connect whatsapp to costpoint

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json