Importing POs and Actuals via SFTP into Allocadia

Scheduled imports pick up CSV files from an SFTP location on a schedule you define. Here's how the end-to-end flow works.

The flow

1. Your upstream system (ERP, accounting tool, procurement platform) generates a CSV of POs or Actuals.
2. That CSV is dropped at a known SFTP folder provided by Allocadia for your account.
3. At the scheduled run time, Allocadia picks up the file, parses it per the import template configuration, and loads the rows.
4. Imported records attempt to auto-map to Line Items. Those that match land as mapped records; those that don't appear as a red map (N) count on Home.
5. A notification goes out summarizing the run result (success, partial, or failure).

What you need before the first import

• SFTP credentials and target folder path — provided by Allocadia Support during initial setup.
• An import template — Professional Services configures this on your account, mapping each CSV column to its destination field (date columns, amount, PO number, PR number, custom attributes, etc.).
• A schedule — daily, weekly, or on-demand.

Initial setup of SFTP imports is a Professional Services engagement. Once configured, your team drops files; Support adjusts the template for minor changes along the way.

Troubleshooting a failed run

If a run fails, you'll typically see an error pointing to a specific row and column. Common causes:

• A date value outside the accepted range. See Allocadia scheduled import failed: "Invalid date — date outside acceptable range".
• A format mismatch between the file's column format and the import template.
• Missing required columns. If a required field in the template isn't present in the file, parsing fails.

For a specific failure, contact Support with the schedule name, run time, and the error message.

If imports stop running against a new fiscal year

Each new FY hierarchy typically requires the import pipeline to be pointed at it. If POs and Actuals aren't appearing on your newer FY hierarchies, see Why don't my POs and Actuals show up on new fiscal-year hierarchies in Allocadia?

Related articles

• How auto-mapping works for POs and Actuals in Allocadia
• Allocadia scheduled import failed: "Invalid date — date outside acceptable range"
• What date range does Allocadia accept on imports?
• Why don't my POs and Actuals show up on new fiscal-year hierarchies in Allocadia?