Set up SFTP ingestion
Create an SFTP connection so Complyance can pick up invoice files. You need Developer portal access and files that match the connection’s mapping.
Name the connection
Open Developer portal → SFTP, then choose Add SFTP connection. In Name and metadata, enter a unique Connection name, such as “Acme Trading — invoices”. Choose the Country and Environment for these documents. Check the displayed Mapping template, then choose Next.
Start in Sandbox. Your spreadsheet columns must match the mapping used by the connection.
Choose who hosts the server
Select Complyance-hosted server to receive an endpoint that your team uploads to. Select Your own server if Complyance should collect files from an SFTP server you already operate.
You cannot change the connection type later. Changing hosts requires a new connection.
Set up authentication
For a Complyance-hosted server, choose Username & password or SSH public key. With password authentication, save the generated credentials when shown. With SSH authentication, register your uploader’s public key and keep its private key in your own system.
For Your own server, choose Username & password or Username & private key. Enter Host, Port, Username and Remote path, followed by the password or private key for that server. Include the key’s passphrase if it has one.
Use a dedicated SFTP account with access to the intended upload directory. Keep passwords and private keys out of invoice files.
Choose file handling and notifications
In Customization, review the lookup interval for your own server, file handling and email notifications. Decide how successfully imported, failed and duplicate files should be handled before activating the connection.
Use the folder paths shown by the connection. Its remote root contains inbound/, invalid/ and validated/; upload new files to inbound/.
Create, test and activate
Review the connection and choose Create connection. Creation leaves it in Draft. Save any one-time password before closing its dialog.
Choose Test connection. When it succeeds, the connection is Validated. Choose Activate to start ingestion; the connection should show Active. Updating connection details requires another successful test before activation.
Check the first file
Upload one small sample file in the supported spreadsheet format (.xlsx, .xls or .csv) using the connection’s mapping. Open Fetch history to check its result, then review the resulting document in the Invoice Portal.
A successful upload to SFTP does not by itself prove that an invoice passed validation. Check the file result and the document result separately.
If something goes wrong
Connection test fails: check the hostname, port, authentication and remote directory permissions. Retest before activating.
No file appears: confirm the connection is Active, the environment is correct and the file is in the expected inbound directory. For your own server, allow for its lookup interval.
A file fails or is skipped as a duplicate: inspect Fetch history before uploading it again. Re-uploading the same file can be skipped. Keep the file and failure details when asking support to recover a failed import.
Next, set up purchase invoice webhooks if your application also needs notifications about received purchases.
Last updated
