.png)
GEP SMART Integration Guide
GEP SMART can exchange procurement data with enterprise systems through tenant-specific APIs, callbacks, exports, and file-based integration mechanisms.
GEP SMART integration options at a glance
GEP SMART is designed to integrate source-to-pay data with enterprise applications, but the public product material does not confirm a universal API or authentication model. Customer-specific integration documentation should establish whether REST APIs, outbound callbacks, bulk jobs, scheduled exports, file exchange, or document endpoints are available. It should also define supported objects, pagination, event coverage, credentials, permissions, and request limits. Martini can consume documented GEP SMART APIs, receive tenant-specific callbacks, process scheduled exports or files, expose REST APIs for ERP and finance systems, and orchestrate mappings, validation, reconciliation, retries, and downstream updates in workflows.
| Integration point | Supported by GEP SMART? | Common use cases | How Martini supports it |
|---|---|---|---|
| REST APIs | Not confirmed | If enabled for the tenant, REST APIs could support reading and writing Suppliers, Purchase orders, Invoices, Contracts, and other procurement objects. Confirm endpoint paths, object coverage, pagination, filters, and lifecycle operations with GEP. | Martini can consume documented REST APIs from workflows, map request and response payloads, apply business rules, and expose REST APIs for connected ERP or finance applications. |
| GraphQL APIs | Not confirmed | No official public GEP SMART GraphQL documentation was found, so GraphQL should not be assumed for procurement queries or mutations. | Martini can consume GraphQL APIs generally, but a GEP SMART GraphQL interface must be confirmed before designing against it. |
| SOAP APIs | Not confirmed | No official public GEP SMART SOAP documentation was found. SOAP should not be selected unless the tenant’s integration documentation explicitly provides it. | Martini can consume SOAP services generally, but any GEP SMART SOAP contract, security model, and operations require tenant confirmation. |
| Webhooks / outbound callbacks | Not confirmed | Public materials do not verify general-purpose webhooks or complete event coverage. Confirm whether callbacks exist for Suppliers, Purchase requisitions, Purchase orders, Invoices, Contracts, or other objects. | If GEP SMART provides tenant-specific callbacks, Martini can receive them through an API or webhook-triggered workflow and retrieve or process the related object. |
| Bulk / asynchronous / batch processing | Not confirmed | Large supplier, catalog, purchase-order, invoice, or spend transfers may use vendor-provided jobs, scheduled exports, or batch interfaces, but specific GEP SMART endpoints were not verified. | Martini can orchestrate scheduled retrieval, staged processing, pagination, batching, reconciliation, and controlled retries once the GEP exchange model is confirmed. |
| File / attachment APIs | Not confirmed | Contracts, sourcing documents, supplier files, catalogs, and invoice-related documents may require file or attachment handling. Multipart uploads, document endpoints, SFTP, and export formats must be confirmed. | Martini can process supported files and document metadata in workflows, apply validation and transformation, and route content to downstream systems when the tenant provides an approved exchange mechanism. |
| Database / analytics access | Not confirmed | Direct database access to GEP SMART is not documented. Spend analytics should use supported exports, reporting interfaces, or documented APIs rather than direct database connectivity. | Martini can consume approved export or API data and can write normalized results to an authorized database, but it should not connect directly to an undocumented GEP SMART database. |
| Authentication | Not confirmed | The public material does not verify OAuth 2.0, API keys, JWTs, service accounts, scopes, or tenant-specific network controls. Confirm the required model with GEP. | Martini can store endpoint configuration, credentials, tokens, and client secrets in environment configuration and secrets management, subject to the confirmed GEP security model. |
How GEP SMART exposes data and business events
GEP SMART REST APIs
Public GEP SMART product material confirms enterprise integration as a product capability but does not verify a public REST API catalog. If the customer’s tenant provides REST specifications, those documents should define supported objects, operations, authentication, pagination, filters, and request limits.
Martini implementation pattern
Martini implementation pattern: Martini consumes the tenant-provided REST API from a workflow, retrieves or submits GEP SMART objects, maps the payload to a canonical model, applies validation and ownership rules, and writes to the target system. It records identifiers and checkpoints for reconciliation.
Implementation sequence
GEP SMART callbacks
General-purpose GEP SMART webhooks and outbound callbacks are not confirmed publicly. Callback availability, event coverage, payload structure, and delivery behavior must be verified for each required object and event.
Martini implementation pattern
Martini implementation pattern: if the tenant provides callbacks, Martini exposes a receiving API or webhook-triggered workflow, validates the notification, and retrieves the current GEP SMART object when the event contains only a reference. The workflow then processes the change and handles duplicate or out-of-order notifications.
Implementation sequence
GEP SMART exports and files
GEP SMART documents, procurement files, and large data transfers may use scheduled exports or file exchange, but supported formats and protocols are tenant-specific and not publicly verified. Confirm whether exports, SFTP, multipart uploads, or document endpoints are available.
Martini implementation pattern
Martini implementation pattern: Martini receives or retrieves an approved file through the configured exchange mechanism, validates its format and provenance, parses the content, maps rows or document metadata, and sends valid results to downstream systems while isolating rejected items.
Implementation sequence
Scheduled GEP SMART synchronization
Scheduled processing is a practical option when callbacks are unavailable or when the tenant supplies exports, APIs, or batch jobs. Pagination, modified-date filters, delta markers, and request limits must be confirmed with GEP.
Martini implementation pattern
Martini implementation pattern: a scheduler starts a workflow that reads the durable high-water mark, retrieves changed objects or files, applies an overlap window, reconciles stable GEP SMART identifiers, and advances the checkpoint only after successful downstream processing.
Implementation sequence
Common GEP SMART integration patterns
Pattern 1: Synchronize suppliers with an ERP
When to use this pattern
Use this pattern when GEP SMART and an ERP share responsibility for supplier onboarding, qualification, master data, or supplier status. The exact direction and fields should follow the tenant’s system-of-record agreement.
Integration direction
Example Mapping
| GEP SMART Field | Canonical Field | Target Field |
|---|---|---|
| supplier identifier | supplier.externalId | Business Partner ID |
| supplier name | supplier.name | Business Partner Name |
| qualification status | supplier.qualificationStatus | Supplier Status |
| tax information | supplier.taxDetails | Tax Number |
Martini implementation pattern
A scheduled or tenant-supported event-driven workflow retrieves approved supplier changes, validates required identifiers and classifications, checks the cross-reference for an existing ERP supplier, and creates or updates the target idempotently. Validation failures are separated from transport failures, and periodic reconciliation detects missed changes.
Martini capabilities used
- workflows
- API consumption
- data mapping
- business rules
- error handling
- scheduled execution
Pattern 2: Process purchase requisitions and purchase orders
When to use this pattern
Use this pattern to connect GEP SMART purchasing approvals with ERP fulfillment, accounting, or document-number processes. Correlation identifiers are essential when the same request moves between systems.
Integration direction
Example Mapping
| GEP SMART Field | Canonical Field | Target Field |
|---|---|---|
| requisition identifier | purchaseRequest.externalId | Requisition Number |
| requester | purchaseRequest.requesterId | Requester |
| line items | purchaseRequest.lines | Requisition Lines |
| purchase-order status | purchaseOrder.status | Order Status |
Martini implementation pattern
Martini receives or retrieves approved Purchase requisitions, validates accounting dimensions and line items, submits them to the ERP, and stores the returned document number. A reverse workflow maps ERP Purchase order and approval statuses back to GEP SMART. Before retrying an uncertain create, the workflow queries by external reference when no idempotency key is available.
Martini capabilities used
- workflows
- API consumption
- data mapping
- conditional routing
- business rules
- error handling
Pattern 3: Synchronize invoices and payment status
When to use this pattern
Use this pattern when GEP SMART captures supplier Invoices and an ERP or finance application performs validation, approval, accounting, or payment processing.
Integration direction
Example Mapping
| GEP SMART Field | Canonical Field | Target Field |
|---|---|---|
| invoice identifier | invoice.externalId | Transaction ID |
| supplier identifier | invoice.supplierId | Vendor ID |
| purchase-order number | invoice.purchaseOrderId | Purchase Order Reference |
| invoice status | invoice.status | Approval or Payment Status |
Martini implementation pattern
A Martini workflow receives or retrieves invoice data, normalizes supplier and purchase-order identifiers, maps tax and currency fields, and submits the invoice to the finance system. Returned validation, exception, approval, rejection, and payment states are mapped back to GEP SMART where supported. Duplicate detection and controlled retry logic protect against repeated financial transactions.
Martini capabilities used
- API consumption
- data mapping
- validation
- business rules
- idempotency controls
- error handling
Pattern 4: Distribute sourcing and contract data
When to use this pattern
Use this pattern to publish selected Sourcing events, award results, Contracts, and contract metadata to document, commercial, or analytics applications. File handling must be designed separately from metadata handling.
Integration direction
Example Mapping
| GEP SMART Field | Canonical Field | Target Field |
|---|---|---|
| sourcing event identifier | sourcingEvent.externalId | External Reference |
| award result | sourcingEvent.awardStatus | Award Status |
| contract start date | contract.startDate | Start Date |
| contract renewal status | contract.renewalStatus | Renewal Status |
Martini implementation pattern
Martini retrieves selected sourcing or contract changes, maps metadata to the target repository, and applies filtering rules for approved or publishable content. If GEP SMART exposes a supported document endpoint or file exchange, a separate workflow validates and transfers attachments; otherwise, the workflow stores only approved references and reports unavailable content.
Martini capabilities used
- workflows
- API consumption
- data mapping
- file processing
- business rules
- monitoring
Applications commonly integrated with GEP SMART
GEP SMART can participate in enterprise procurement architectures alongside ERP, finance, workflow, document, and business applications. The specific interface, object coverage, and direction should be confirmed for each tenant and product deployment.
| Application | Scenario | Direction | Martini Pattern |
|---|---|---|---|
| SAP S/4HANA | Synchronize Suppliers, Purchase requisitions, Purchase orders, Invoices, accounting information, and purchasing status between procurement and ERP processes. | GEP SMART → Martini → SAP S/4HANA | Use a scheduled or tenant-supported event-driven workflow to retrieve or receive GEP SMART data, normalize supplier and document identifiers, apply ownership and validation rules, and write idempotently to SAP S/4HANA. Return ERP document numbers and statuses through a reverse workflow. |
| Oracle Fusion Cloud ERP | Exchange supplier, purchasing, invoice, financial, and approval information between GEP SMART and Oracle finance and procurement processes. | GEP SMART → Martini → Oracle Fusion Cloud ERP | Consume documented GEP SMART and Oracle interfaces through a Martini workflow, map procurement fields to Oracle structures, preserve correlation identifiers, and route validation or authorization failures to an operational error path. |
| NetSuite | Transfer supplier, purchasing, order, and invoice information when NetSuite is the organization’s financial system. | GEP SMART → Martini → NetSuite | Use scheduled synchronization or confirmed callbacks, maintain a cross-reference between GEP SMART and NetSuite identifiers, transform currencies and accounting dimensions, and reconcile failed or overlapping updates. |
| Workday | Provide organization, worker, supplier, or finance-related reference data that supports procurement processes and return selected status information. | Workday → Martini → GEP SMART | Retrieve approved reference data from Workday, validate effective dates and identifiers, map it to the GEP SMART tenant model using the supported interface, and record rejected or unmapped values for review. |
| Salesforce | Share supplier, account, sourcing, or relationship information where procurement and commercial teams coordinate supplier activity. | GEP SMART → Martini → Salesforce | Expose or consume APIs as appropriate, transform supplier and relationship fields, apply field-level ownership rules, and use correlation IDs to prevent duplicate account or supplier updates. |
| ServiceNow | Coordinate procurement requests, approvals, supplier issues, and service-related purchasing workflows across enterprise operations. | ServiceNow → Martini → GEP SMART | Receive approved ServiceNow requests through an API or workflow trigger, validate procurement attributes, submit supported data to GEP SMART, and return document references and status updates to ServiceNow. |
| Coupa | Exchange supplier, sourcing, purchasing, or spend information during coexistence, migration, or specialized procurement scenarios. | GEP SMART → Martini → Coupa | Use tenant-supported APIs or exports on each side, stage and reconcile overlapping supplier and purchasing identifiers, apply explicit system-of-record rules, and isolate migration or coexistence exceptions. |
| Microsoft SharePoint | Store or distribute contract and sourcing documents when document collaboration is managed outside GEP SMART. | GEP SMART → Martini → Microsoft SharePoint | Process document metadata and, only where supported, file payloads through a Martini workflow; validate MIME types and permissions, transfer content securely, and retain links or external references rather than assuming attachments are portable. |
How to build a GEP SMART integration in Martini
Objective
Establish the tenant-specific GEP SMART integration contract before building workflows, including endpoint details, authentication, permissions, supported objects, and network requirements.
Instructions in Martini
- Obtain the GEP SMART API or integration documentation for the tenant
- Confirm the authentication method, token behavior, service account, and object permissions
- Store credentials, tokens, endpoint URLs, and environment values in Martini secrets and configuration
- Verify sandbox and production connectivity separately
Objective
Select the trigger that matches the confirmed GEP SMART exchange model and the required latency and volume.
Instructions in Martini
- Use a documented callback or webhook only when the tenant confirms event coverage
- Use a scheduler for polling, exports, reconciliation, and batch processing
- Use an API exposed by Martini when ERP or internal applications initiate procurement submissions
- Define the checkpoint, overlap window, and expected delivery behavior
Objective
Obtain current GEP SMART data while preserving identifiers, request context, and evidence needed for reconciliation.
Instructions in Martini
- Retrieve objects through documented tenant APIs or receive approved files and callbacks
- Implement confirmed pagination, modified-date filters, status filters, or delta markers
- Capture GEP request identifiers and external object identifiers
- Do not assume that a timeout means a non-idempotent operation failed
Objective
Coordinate calls, transformations, validations, downstream writes, and response handling as a maintainable Martini workflow.
Instructions in Martini
- Separate retrieval, validation, mapping, target writes, and status updates into clear workflow stages
- Use conditional routing for validation, authorization, throttling, and business exceptions
- Use reusable services or workflow components for shared identifier and status logic
- Preserve correlation IDs across each system boundary
Objective
Convert GEP SMART procurement objects into the canonical and target models required by ERP, finance, workflow, document, or analytics systems.
Instructions in Martini
- Map actual objects such as Suppliers, Purchase orders, Invoices, Contracts, and Purchase requisitions
- Normalize identifiers, dates, currencies, tax values, statuses, and accounting dimensions
- Handle optional and tenant-configured fields without discarding required business information
- Validate required fields before creating or updating downstream objects
Objective
Enforce ownership, lifecycle, approval, duplicate, and reconciliation rules before committing changes.
Instructions in Martini
- Define the system of record for suppliers, requisitions, orders, invoices, contracts, and statuses
- Use stable identifiers and cross-reference mappings for idempotency
- Reject or quarantine unknown status values and missing required attributes
- Apply approval and publication rules before distributing sourcing or contract data
Common GEP SMART data objects used in integrations
| Object | Typical Use | Common target systems | Martini handling |
|---|---|---|---|
| Suppliers | Synchronize supplier profiles, classifications, contacts, qualification information, tax details, and status. | SAP S/4HANA, Oracle Fusion Cloud ERP, NetSuite, Workday | Martini maps stable supplier identifiers, validates required fields, applies system-of-record rules, detects duplicates, and supports scheduled or event-triggered synchronization where the tenant permits it. |
| Sourcing events | Distribute requests for information, requests for quotation, auctions, bids, awards, and related sourcing activity. | Salesforce, SharePoint, analytics platforms, ERP systems | Martini transforms event and award data, routes selected outcomes, processes document references separately, and records unmapped statuses or fields for review. |
| Contracts | Synchronize negotiated agreements, terms, dates, versions, supplier relationships, and renewal metadata. | Microsoft SharePoint, Salesforce, ERP systems, contract-management applications | Martini maps contract metadata, applies date and status rules, and transfers attachments only when GEP SMART exposes an approved document or file mechanism. |
| Purchase requisitions | Send internal requests for goods or services through approval and purchasing processes. | SAP S/4HANA, Oracle Fusion Cloud ERP, ServiceNow, NetSuite | Martini validates requester, supplier, accounting, currency, and line-item data, applies approval-related rules, and uses correlation identifiers to prevent duplicate submissions. |
| Purchase orders | Exchange approved purchasing documents, supplier references, line items, delivery details, and status information. | SAP S/4HANA, Oracle Fusion Cloud ERP, NetSuite, Coupa | Martini maps document and line-level fields, preserves external references, handles status transitions explicitly, and reconciles uncertain outcomes after transport failures. |
| Invoices | Synchronize supplier invoices, purchase-order references, tax information, exceptions, approvals, and payment-related status. | SAP S/4HANA, Oracle Fusion Cloud ERP, NetSuite, finance applications | Martini transforms supplier IDs, purchase-order numbers, currencies, tax codes, and accounting dimensions while separating validation, authorization, throttling, and downstream business errors. |
Authentication and security considerations
Tenant-specific authentication
Public GEP SMART product information does not confirm a standard customer-facing API authentication model. Confirm whether the tenant uses OAuth 2.0, API keys, client credentials, service accounts, IP allowlisting, or another mechanism before implementation.
Secrets and permissions
Store GEP SMART credentials, tokens, client secrets, endpoint configuration, and environment-specific values in Martini secrets and configuration. Apply least-privilege permissions for the required procurement objects and environments.
Data protection
- Protect supplier, invoice, payment, tax, contract, and sourcing information in transit and at rest.
- Do not place credentials, tokens, financial data, or sensitive contract content in ordinary workflow logs.
- Confirm tenant, regional, network, retention, and document-access requirements with GEP.
Operational considerations for GEP SMART integrations
Limits and pagination
GEP SMART rate limits, concurrency restrictions, pagination style, and delta capabilities were not publicly confirmed. Validate these details and implement controlled requests, overlap windows, durable checkpoints, and exponential backoff for throttling or transient failures.
Idempotency and reconciliation
Use stable object IDs and external references for Suppliers, Purchase orders, Purchase requisitions, Invoices, and Contracts. Query before retrying uncertain non-idempotent operations where no idempotency key is available, and run periodic reconciliation to detect missed events or failed writes.
Schema and lifecycle changes
Tenant configuration may add custom fields, classifications, approval states, and status values. Treat optional fields carefully, explicitly handle unknown statuses, and test changes to required attributes, API versions, and enumerations in a sandbox.
Documents and errors
Do not assume document references can be transferred as file payloads. Confirm size, MIME type, permissions, scanning, and retention requirements. Separate validation, authentication, authorization, throttling, network, and downstream business errors so each can be retried or remediated appropriately.
Why use Martini instead of scripts or point-to-point integrations?
Orchestrate more than an API call
GEP SMART integrations often cross procurement, ERP, finance, document, and workflow boundaries. Martini coordinates these interactions in workflows rather than embedding fragile logic in isolated scripts or point-to-point mappings.
Make mappings maintainable
Martini provides reusable API, transformation, validation, business-rule, and error-handling assets. This supports consistent handling of supplier identifiers, purchasing statuses, invoice values, accounting dimensions, and tenant-specific fields.
Operate with control
- Use scheduled, API-led, file-based, or confirmed event-driven workflows as appropriate.
- Centralize secrets and environment configuration instead of hardcoding credentials.
- Capture correlation identifiers, checkpoints, retries, and reconciliation outcomes.
- Expose controlled APIs for ERP and internal applications when GEP SMART is not the initiating system.
Frequently asked questions
GEP SMART can be integrated through mechanisms enabled by the customer’s tenant, which may include documented APIs, outbound callbacks, scheduled exports, batch jobs, file exchange, or document interfaces. The tenant’s integration documentation must confirm the available endpoints, objects, authentication, event coverage, and limits.
Yes, Martini can integrate with GEP SMART using the native mechanisms confirmed for the tenant. Martini can consume documented GEP SMART APIs, receive confirmed callbacks, process approved files or exports, expose APIs for ERP and finance systems, and orchestrate mapping, validation, retries, and reconciliation.
No. A dedicated GEP SMART connector is not required. Martini can use GEP SMART’s confirmed native APIs, callbacks, files, exports, or other supported integration endpoints. No native Martini GEP SMART connector is documented in the supplied materials.
Lonti does not charge an additional per-connector or per-vendor fee to integrate GEP SMART. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from GEP, cloud infrastructure providers, or other third-party systems based on subscription, usage, and deployment model.
Use the current mechanisms documented for the customer’s GEP SMART tenant. REST APIs may be suitable if provided, while scheduled exports, batch jobs, or file exchange may be appropriate for larger transfers. GraphQL and SOAP should not be assumed because public documentation did not confirm them.
General-purpose webhooks and complete event coverage were not confirmed in the public material reviewed. The tenant may provide callbacks for selected objects or events, but GEP documentation should confirm availability, payloads, delivery behavior, authentication, and retry expectations before an event-driven design is used.
Martini can use scheduled workflows, confirmed event notifications, API pagination, exports, or files to synchronize data. Stable GEP SMART and external identifiers, cross-reference mappings, high-water marks, overlap windows, pre-write lookups, and periodic reconciliation help prevent duplicates and identify missed changes.
Yes. Martini can expose REST APIs for ERP, finance, supplier-facing, or internal applications, then validate and transform submitted data before orchestrating calls to GEP SMART interfaces confirmed by the tenant. It can also return correlation identifiers and downstream status information.
Related Martini documentation
Workflows
Plan your GEP SMART integration
Confirm the GEP SMART tenant’s APIs, callbacks, exports, file mechanisms, authentication model, object permissions, and request limits, then use Martini to implement a secure, observable workflow that connects procurement data with your enterprise systems.