SYSPRO and SFTP / Flat Files integration

What moves between them

Financial records and master data flow from SYSPRO into SFTP / Flat Files. Invoices, purchase orders, and GL posting batches are read from SYSPRO's OData layer on a monthly or weekly cadence (aligned to your close calendar), formatted as CSV or EDI X12 files, and uploaded to the SFTP / Flat Files server's inbound folder. Supplier and item master records can move in either direction depending on your setup. The connector produces no acknowledgments to SYSPRO; it reads only.

How ml-connector handles it

ml-connector stores the SFTP / Flat Files SSH private key encrypted and presents it on every connection, or uses the password over the SSH channel if key auth is not available. On the SYSPRO side, it obtains a session token by logging into the Utilities/Logon endpoint with the supplied operator credentials, caches that token for the polling interval, and reads OData tables with $filter on timestamp fields to capture only changed records since the last run. GL postings are grouped by cost center and reformatted to match the receiving system's column layout (fixed-width, X12 830, or CSV as configured). Files are written to the SFTP server's inbound folder following your partner's naming convention. Retries use exponential backoff if the SFTP connection is refused or SSH authentication fails, and the connector tracks session token expiry and key passphrase rotation so neither becomes an unexpected outage.

A real-world example

A mid-sized contract manufacturer runs SYSPRO for production and finance, and sends monthly invoices and GL journals to a parent company's legacy ERP that only accepts SFTP file uploads. Before the integration, the finance team exported SYSPRO's GL postings and supplier invoices each month as CSVs, manually mapped them to cost centers, and uploaded them over SFTP. With SYSPRO and SFTP / Flat Files connected, each monthly close cycle automatically exports the GL batch and invoices, formats them to the parent company's spec, and deposits them on the SFTP server, eliminating the manual mapping step and reducing close time by several hours.

What you can do

• •Export SYSPRO invoices, purchase orders, and GL postings as CSV or EDI files on a schedule tied to your monthly or weekly close.
• •Authenticate to SFTP / Flat Files with SSH key or password, and to SYSPRO with OData credentials, transparently bridging both auth models.
• •Map SYSPRO GL posting lines to receiving cost centers and account numbers so downstream imports land on valid dimensions.
• •Poll SYSPRO's OData tables with timestamp filters to capture only new or changed records since the last run.
• •Retry failed SFTP uploads with exponential backoff, track session token expiry, and audit every file sent to the SFTP server.

Questions

Which direction does data move between SYSPRO and SFTP / Flat Files?

Data moves from SYSPRO into SFTP / Flat Files. GL postings, invoices, purchase orders, and master data are exported from SYSPRO as formatted files and uploaded to the SFTP server. The connector does not write back to SYSPRO or request files from it.

Does ml-connector handle both SSH key and password authentication for SFTP?

Yes. ml-connector stores SSH private keys encrypted and presents them on every connection, or sends the username and password over the encrypted SSH channel if key authentication is not available. Host key verification is enforced in production to prevent man-in-the-middle attacks.

How does ml-connector sync SYSPRO's GL postings to the correct cost centers in the receiving system?

ml-connector reads SYSPRO's GL postings from OData and applies a column mapping you configure to reformat each line to the receiving system's cost center and account number format (CSV, X12, or fixed-width). The mapping is stored encrypted and applied on every export.