NetSuite Integration for NDT Inspection Companies
For inspection groups that run NetSuite as the corporate ERP but need NDT-specific operations: method-specific reports, technician certification tracking, equipment calibration and crew dispatch, connected to NetSuite through REST APIs on both sides.
Who this is for
Larger NDT and inspection groups, and inspection divisions inside engineering or fabrication companies, where finance, procurement and consolidation already run on NetSuite. NetSuite is a strong general ERP, but it does not know what a written practice, a vision test, a calibration block or an IQI is. Atlantis ERP handles the inspection operation, and NetSuite keeps the financial and corporate records.
What data flows, and in which direction
| Record | Direction | Notes |
|---|---|---|
| Customer and sales order / PO | NetSuite → Atlantis | Creates or updates the customer and the job with PO number and contract references. |
| Project / job | Either direction | Where NetSuite projects are used for job costing, the Atlantis job and the NetSuite project share a key. |
| Approved timesheets | Atlantis → NetSuite | Billable hours by job, work type and technician, if NetSuite does the billing. |
| Invoice | Atlantis → NetSuite, or built in NetSuite | Either Atlantis builds the invoice and posts it, or NetSuite bills from the timesheets it receives. |
| Vendor bills for calibration and consumables | Atlantis → NetSuite (optional) | Purchases linked to an equipment serial in Atlantis can be passed to NetSuite for payables. |
Typical architecture
NetSuite's SuiteTalk REST Web Services provide an OpenAPI-described record API for standard and custom records, and NetSuite recommends OAuth 2.0 for new REST integrations, with token-based authentication also supported; RESTlets are available where a custom endpoint is cleaner. Your NetSuite administrator creates an integration record and a role limited to the records in scope.
The dividing line is usually simple: NetSuite owns the customer, the ledger and consolidation; Atlantis owns how the work was done and who was qualified to do it. The integration moves the records that cross that line, and nothing else.
What the Atlantis side offers
Atlantis ERP has an open REST API. The same API the offline field app uses to fetch assigned jobs and issued equipment and to submit reports is available for integration, and the records an NDT company cares about are reachable through it: jobs and team assignments, NDT reports and their status, technician certifications with their computed status (active, expiring soon, expired, revoked), equipment with calibration status and due dates, timesheets, quotations and invoices. Which objects are exposed, in which direction and to which system is agreed during implementation, because every integration is scoped to the customer's landscape rather than shipped as a fixed connector.
- No prebuilt, certified connector is claimed. The integration is built against your system's published API and Atlantis's REST API during implementation.
- Your system stays the system of record for whatever it owns today, whether that is the asset register, the general ledger or the customer master.
- Mapping is agreed in writing before anything is built: object, field, direction, trigger, and what happens when a record fails validation.
What gets configured during implementation
- Scope workshop. Which records move, in which direction, and who owns each field. Anything not agreed here is not built.
- Access on both sides. A dedicated integration user or app registration on your system with the minimum permissions for the agreed objects, and API credentials on the Atlantis side.
- Key mapping. How a record in one system is found in the other: work-order number, equipment or functional-location ID, customer number, invoice number.
- Field mapping and code lists. Status values, units, methods and result codes translated between the two systems.
- Triggers and timing. Event-driven (on approval, on posting) or scheduled, depending on what your system supports and what the business needs.
- Errors and retries. Where a failed record is logged, who is told, and how it is re-sent once fixed.
- Test in a sandbox, then a controlled go-live on a small set of records before the full flow is switched on.
Why not build NDT inside NetSuite
It can be done with enough customisation, and some groups try. The cost shows up later: custom records for certifications, vision tests, OJT hours, calibration certificates and method-specific report data, plus the field app for offline capture, all maintained against NetSuite release cycles. For a direct comparison of the trade-offs, see NDT ERP vs generic ERP.
Why integrate instead of re-keying
Every NDT company that works for large asset owners ends up typing the same facts twice: the work order number from the client's system onto the job, and the result from the report back into the client's system or into accounts. Re-keying is where report numbers get transposed, where a rejected weld is closed as accepted in someone else's system, and where invoices wait because nobody has matched the timesheet to the purchase order. An integration removes the second keystroke for the records that matter, and leaves an audit trail showing what was sent, when, and what the other system replied.
If NetSuite is your corporate system, book an integration scoping call with your finance lead and operations lead on the same call. See also the integrations overview and Atlantis ERP.
Frequently asked questions
Which NetSuite API is used?
Usually SuiteTalk REST Web Services with OAuth 2.0, which NetSuite recommends for new REST integrations. RESTlets or SOAP web services are used where the scope needs them.
Does NetSuite or Atlantis issue the invoice?
Either works. Some groups bill in NetSuite from the approved timesheets Atlantis sends; others let Atlantis build the invoice and post it. It is decided in the scope workshop.
Can NetSuite projects stay the cost-tracking tool?
Yes. The Atlantis job and the NetSuite project share a key, and hours or costs flow to the project as agreed.
Do we need a NetSuite partner involved?
Not necessarily. Your NetSuite administrator sets up the integration record and role; if you already work with a NetSuite partner, they can join the scoping call.
Is this a certified connector?
No. Atlantis does not claim a certified or marketplace connector. The integration is built during implementation against your system's published API and the Atlantis REST API, scoped to the records you need.
Who owns the integration once it is live?
That is agreed in the scope: typically Atlantis maintains the Atlantis side and the mapping, and your IT team owns credentials and permissions on your system. Changes to the mapping are handled as change requests.
Sources
- SAP Business Accelerator Hub (S/4HANA APIs)
- IBM Maximo Manage REST APIs
- NetSuite OAuth 2.0 for REST web services
- QuickBooks Online API (Intuit developer help)
- Business Central API v2.0 endpoints
Speak to an ASNT NDT Level III
Atlantis NDT provides ASNT Level III consulting, NDT training to ASNT SNT-TC-1A, inspection management software and independent report validation. Request a free consultation and we will return a tailored quote — affordable, accessible and fully customizable to your programme.