Skip to main content

A Practical, Low-Code Way to Integrate External Systems with Acumatica Using Import Scenarios

  • December 13, 2025
  • 0 replies
  • 5 views

Hi everyone,

I’d like to share a practical integration pattern we recently implemented using Acumatica’s native tools, without hardcoding or external middleware.

Instead of building custom APIs inside Acumatica, this approach combines:

  • Automated data preparation on the source side

  • Import by Scenario (SM206036)

  • File Synchronization (SM202530)

  • Automation Schedules (SM205020)

It has proven to be simple, stable, and very easy to maintain.

High-level architecture

The overall flow looks like this:

External System (API)
→ Python script prepares and normalizes data
→ Excel file is generated
→ Windows Task Scheduler runs the script daily
→ File is saved into a shared folder
→ Acumatica File Synchronization picks it up
→ Automation Schedule executes Import Scenario
→ Business documents are created in Acumatica
→ (Optional) Business Event sends a notification

We used this pattern to integrate Loyverse POS with Acumatica for a client, bringing daily sales data into ERP automatically.

1. Extracting and preparing external data

A Python script connects to the Loyverse POS API and retrieves daily transactions.
The script handles all data preparation before Acumatica ever sees the file.

Typical logic includes:

  • Calling the API using secure tokens

  • Extracting sales, items, prices, taxes, revenue breakdown

  • SKU mapping and warehouse logic

  • Date and format normalization

  • Sorting data to ensure predictable Import Scenario behavior

  • Exporting to Excel (xlsx format works best)

The goal is to make the file 100% compatible with the Import Scenario, so Acumatica only focuses on importing – not fixing data.

2. Automating data preparation

The Python script is scheduled to run automatically, usually once per day.

Common tools:

  • Windows Task Scheduler

  • Cron (Linux)

Each run:

  • Fetches new data

  • Generates the import file

  • Creates backups for audit

  • Saves the file into a monitored folder

This ensures Acumatica always receives fresh, ready-to-import data.

3. Using File Synchronization in Acumatica

Acumatica’s File Maintenance and File Synchronization screens are used to:

  • Monitor a shared folder

  • Detect new or updated files

  • Import them into Acumatica’s file repository

  • Keep version history for traceability

No manual upload is required, and file handling stays fully inside Acumatica.

4. Running Import Scenarios automatically

Two Automation Schedules are typically configured:

  1. Run File Synchronization

  2. Execute the Import Scenario

These schedules can run sequentially, so data flows into Acumatica without user intervention.

The Import Scenario then creates business documents such as:

  • Sales transactions

  • Revenue records

  • Kit Assembly documents

  • Or other custom entities, depending on the use case

5. Optional: Business Events for notifications

To improve visibility, a Business Event can send:

  • Execution status

  • Record counts

  • Error details

  • Completion time

This is especially useful for finance teams or system owners who want daily confirmation.

Real project example

In a recent F&B project:

  • Sales data was extracted daily from Loyverse POS

  • Python transformed raw transactions into Acumatica-ready structure

  • Files were generated automatically every night

  • Acumatica imported them via File Synchronization + Import Scenario

  • A Business Event emailed a daily summary to the owner

The result was a fully automated, zero-manual integration with high reliability.

Why this approach works well

From implementation experience, this method is:

  • Low-code and easy to maintain

  • Scalable to many external systems

  • Transparent and auditable

  • Fully based on Acumatica native tools

It’s often a better choice than custom-coded integrations, especially for POS, eCommerce, or operational systems.

We documented the full architecture and step-by-step setup (with diagrams and screenshots) here:
👉 https://s4.com.vn/en/a-practical-method-for-integrating-external-systems-with-acumatica-using-import-by-scenarios/

Would love to hear from others:

  • Are you using Import Scenarios for integrations today?

  • Have you combined them with Automation Schedules or File Sync?

  • What external systems are you integrating with Acumatica?

Looking forward to learning from the community.