Why does ml-connector need to poll Stampli via SFTP instead of calling a REST API?

Stampli does not publish a public REST API. File-based integration via SFTP with CSV templates is the only third-party integration path available without a formal Stampli partnership agreement. ml-connector polls the outbound directory on your defined interval, parses the exported files, and posts the records into Infor CloudSuite.

How does ml-connector ensure invoices post to the correct supplier and GL account in CloudSuite?

ml-connector maintains a mapping of Stampli vendor codes to CloudSuite supplier IDs and Stampli GL account codes to CloudSuite GL account strings. When parsing Stampli invoices, it applies these mappings before constructing the CloudSuite AP header and lines. If a vendor or GL account code does not exist in CloudSuite, the posting is flagged for review and not posted.

Does the integration support invoice approval workflows or just AP data synchronization?

The integration syncs approved invoices and payments from Stampli into CloudSuite's AP module. Approval workflows remain in Stampli. ml-connector detects invoices already approved in Stampli and moves them into CloudSuite with the correct GL and supplier coding so your accounting stays in sync with your approval decisions.

Infor CloudSuiteStampli

Infor CloudSuite and Stampli integration

Infor CloudSuite runs procurement and finance across suppliers, purchase orders, invoices, and the general ledger. Stampli runs invoice approval and vendor management. Connecting the two keeps your accounts payable synchronized and your approval workflow end-to-end. Invoices approved in Stampli move into CloudSuite's AP automatically, allocated to the correct GL accounts and suppliers. Payment records from Stampli sync into CloudSuite so your ledger reflects what your AP team has authorized and paid. ml-connector polls Stampli's file export, translates records to CloudSuite's ION API format, and handles the company number and cost allocation details.

How Infor CloudSuite works

Infor CloudSuite (Industrial, Financials, Distribution, M3, LN, SyteLine) exposes suppliers, invoices, purchase orders, GL accounts, and payments through the ION API Gateway. The platform authenticates with OAuth 2.0 using service account credentials registered in an app, and the base URL and token endpoint vary per customer and region and are extracted from the provided .ionapi credentials file. CloudSuite publishes BOD (Business Object Document) push flows for some events if configured via ION Desk, but the primary integration path is polling the REST API for new or modified records by date or status. Every operation requires the CONO (company number) parameter, and rate limits run 100-500 requests per minute per client.

How Stampli works

Stampli automates the procure-to-pay cycle with invoice capture, AI-driven approval workflows, PO matching, and vendor management. Unlike most SaaS platforms, Stampli does not expose a public REST API; third-party integration is file-based only, via SFTP with CSV or XML templates. Stampli exports approved invoices, payments, vendors, and GL accounts to an outbound SFTP directory on an internal refresh cadence of 5-120 minutes depending on entity type. Authentication is SFTP credentials (hostname, port, username, password), and there is no public test environment accessible without a Stampli partnership agreement.

What moves between them

The main flow is Stampli into Infor CloudSuite. ml-connector polls Stampli's SFTP outbound directory on your defined interval, detects new exported invoice and payment files, parses the CSV records, maps Stampli vendors to CloudSuite suppliers by external ID or name match, maps Stampli GL accounts to CloudSuite GL account strings, and posts the invoices into CloudSuite's AP module (APS100MI: AddHead, AddLine) with the correct CONO, supplier, GL account, and cost allocation. Payment records flow the same direction and create payment transactions in CloudSuite. Reference data such as GL accounts and suppliers is aligned so invoice GL coding lands on accounts that exist in CloudSuite.

How ml-connector handles it

ml-connector stores SFTP credentials encrypted and polls the outbound directory on your schedule (typically every 15-30 minutes). On detect of new files, it parses the CSV templates, deduplicates by invoice number and supplier to prevent double-posting, maps Stampli vendors to CloudSuite suppliers by matching external IDs or names, maps GL account codes, and constructs CloudSuite AP invoice headers and lines with the required CONO parameter and cost center allocation. Because Stampli has no webhooks and no public API, all data moves via SFTP file polling. CloudSuite's OAuth token is refreshed proactively before expiry (1-24 hours depending on tenant configuration), and rate-limit 429 responses are respected with exponential backoff. Every record carries a full audit trail so a failed posting can be replayed, and the integration tracks which Stampli exports have been processed to avoid reprocessing on restart.

A real-world example

A mid-sized manufacturing company runs Infor CloudSuite M3 for production and procurement, and uses Stampli for invoice approval and vendor management. Before the integration, the AP team received Stampli approval notifications, exported approved invoices monthly as CSV, and manually entered them into CloudSuite's AP module, then spent days reconciling supplier and GL coding errors. With Stampli and CloudSuite connected, approved invoices flow automatically from Stampli to CloudSuite every 15 minutes with the correct supplier and GL account mapping applied, so the AP team focuses on Stampli approvals while CloudSuite's ledger stays current. Month-end close starts with AP already reconciled and current.

What you can do

Poll Stampli's SFTP outbound directory on a schedule you control, detect new approved invoices and payments, and post them into Infor CloudSuite's AP module.
Map Stampli vendors to CloudSuite suppliers and Stampli GL accounts to CloudSuite GL account strings so invoice coding matches your chart of accounts.
Allocate invoices to the correct company number (CONO) and cost center in CloudSuite so payables land on the right ledger accounts.
Authenticate Stampli via SFTP and Infor CloudSuite via OAuth 2.0 service credentials, refresh tokens before expiry, and respect rate limits with backoff.
Deduplicate invoices by invoice number and supplier, maintain a full audit trail on every record, and replay failed postings without manual re-entry.

Questions

Why does ml-connector need to poll Stampli via SFTP instead of calling a REST API?: Stampli does not publish a public REST API. File-based integration via SFTP with CSV templates is the only third-party integration path available without a formal Stampli partnership agreement. ml-connector polls the outbound directory on your defined interval, parses the exported files, and posts the records into Infor CloudSuite.
How does ml-connector ensure invoices post to the correct supplier and GL account in CloudSuite?: ml-connector maintains a mapping of Stampli vendor codes to CloudSuite supplier IDs and Stampli GL account codes to CloudSuite GL account strings. When parsing Stampli invoices, it applies these mappings before constructing the CloudSuite AP header and lines. If a vendor or GL account code does not exist in CloudSuite, the posting is flagged for review and not posted.
Does the integration support invoice approval workflows or just AP data synchronization?: The integration syncs approved invoices and payments from Stampli into CloudSuite's AP module. Approval workflows remain in Stampli. ml-connector detects invoices already approved in Stampli and moves them into CloudSuite with the correct GL and supplier coding so your accounting stays in sync with your approval decisions.

Connect Infor CloudSuite and Stampli

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started