Skip to main content

Importing Payments

K
Written by Kelly Walsh

πŸ“₯ Importing Payments in Trovata TMS

---

πŸ—οΈ Overview

Payment imports allow you to bulk load payments from external sources (ERP systems, spreadsheets, TMS exports) rather than entering them one by one.

Source File β†’ Validation β†’ Mapping β†’ Import β†’ Workflow Routing β†’ Bank Transmission

---

πŸ“‹ Supported Import Formats

Format

Description

Best For

CSV

Comma-separated values

Excel exports, simple payrolls

XLSX

Excel spreadsheet

Manual payment batches

XML

Structured markup

ERP system exports (SAP, Oracle)

ISO 20022

pain.001 XML standard

SWIFT/bank-grade payments

NACHA

ACH file format

US domestic ACH batches

MT101

SWIFT message format

International wire batches

BAI2

Bank statement format

Reconciliation-based payments

---

πŸ”§ Step-by-Step Import Process

---

Step 1: Prepare Your Import File

Ensure your file contains the required fields:

Field

Required?

Description

Payment Date

βœ… Yes

Value/settlement date

Amount

βœ… Yes

Payment amount

Currency

βœ… Yes

ISO currency code (USD, EUR)

Beneficiary Name

βœ… Yes

Payee name

Beneficiary Account

βœ… Yes

Bank account number

Routing/SWIFT Code

βœ… Yes

ABA routing or SWIFT BIC

Payment Type

βœ… Yes

Wire, ACH, Check

Debit Account

βœ… Yes

Your bank account to debit

Reference/Description

βšͺ Optional

Payment memo/reference

Line Code

βšͺ Optional

ATOM internal line code

Entity/Cost Center

βšͺ Optional

For allocation purposes

---

Step 2: Download the Template

Trovata TMS Menu β†’ Cash Management β†’ Payments β†’ Import β†’ Download Template

  • Choose your preferred format (CSV, XLSX, XML)

  • Template includes all required columns with validation rules

  • Sample data included for reference

---

Step 3: Navigate to Payment Import

Trovata TMS Menu β†’ Cash Management β†’ Payments β†’ Import Payments

---

Step 4: Upload Your File

Option

Description

Manual Upload

Browse and select file from your computer

SFTP Drop

Automated file drop from ERP/system

API Push

Real-time import via REST API

Scheduled Import

Auto-import on a schedule (daily, hourly)

---

Step 5: Field Mapping

If your file columns don't match Trovata TMS's standard names:

Import Wizard β†’ Field Mapping Step: β”œβ”€β”€ Map "Vendor Name" β†’ Beneficiary Name β”œβ”€β”€ Map "Pay Amount" β†’ Amount β”œβ”€β”€ Map "Pay Date" β†’ Payment Date └── Save mapping as template for future imports

> πŸ’‘ Tip: Save your field mapping as a named template so you don't have to re-map every time!

---

Step 6: Validation & Error Review

ATOM automatically validates each record:

Validation Check

Error Example

Required fields

Missing beneficiary account

Amount format

Non-numeric value in amount field

Date format

Invalid date "13/45/2024"

Currency code

Unknown currency "XXX"

Routing number

Invalid ABA routing number

Duplicate detection

Same payment already exists

Limit check

Exceeds daily payment limit

Sanctions screen

Beneficiary on OFAC list

Handling Errors:

Validation Results: β”œβ”€β”€ βœ… 47 records passed β€” ready to import β”œβ”€β”€ ⚠️  3 records have warnings β€” review recommended   └── ❌ 2 records failed β€” must fix before import

  • Fix & Re-upload β€” correct errors in source file

  • Import Valid, Skip Errors β€” import passing records only

  • Export Error Report β€” download list of failed records

---

Step 7: Review & Confirm Import

Before finalizing, review the import summary:

Summary Item

Details

Total records

52 payments

Total amount

$2,450,000.00

Currency breakdown

USD: $2.1M, EUR: €350K

Payment types

Wire: 12, ACH: 38, Check: 2

Value dates

Today: 20, Tomorrow: 32

---

Step 8: Submit for Workflow Approval

Once imported, payments automatically enter the approval workflow:

Import Complete β†’ Payments Created β†’ Routed to Approval Tiers β†’ Bank Transmission

  • Each payment follows your configured workflow rules

  • Approvers notified automatically

  • High-value payments escalated per threshold rules

---

πŸ”„ Automated/Scheduled Imports

For recurring imports (e.g., weekly payroll):

Trovata TMS Menu β†’ Administration β†’ Scheduled Imports β†’ New Schedule

Setting

Example

Source

SFTP server / shared drive

Frequency

Daily at 7:00 AM

File Pattern

payroll_*.csv

On Success

Auto-submit for approval

On Error

Email alert to treasury team

Archive

Move processed files to /archive

---

πŸ”— ERP Integration Imports

ERP System

Integration Method

SAP

IDoc / BAPI direct integration

Oracle ERP

REST API / file-based

NetSuite

CSV export β†’ SFTP

Workday

API connector

Microsoft Dynamics

XML file export

---

πŸ“Š Post-Import Monitoring

After import, track your payments:

Trovata TMS Menu β†’ Cash Management β†’ Payments β†’ Payment Monitor

Status

Meaning

IMPORTED

Successfully loaded, pending workflow

PENDING

In approval queue

APPROVED

Approved, queued for bank

SENT

Transmitted to bank

CONFIRMED

Bank acknowledged receipt

REJECTED

Bank rejected β€” needs investigation

FAILED

System error β€” contact support

---

πŸ†˜ Common Import Issues & Fixes

Issue

Fix

File format not recognized

Check file extension and encoding (UTF-8)

Date format errors

Use MM/DD/YYYY or YYYY-MM-DD consistently

Amount with currency symbols

Remove $, €, Β£ β€” numbers only

Routing number invalid

Verify 9-digit ABA or 8/11-digit SWIFT BIC

Duplicate payment flagged

Check if payment already exists in system

Import template outdated

Re-download latest template from ATOM

Large file timeout

Split into batches of 500 records max

---

πŸ” Security & Audit

Control

Description

Import log

Every import logged with user, timestamp, record count

File hash

Checksum validation prevents tampering

Approver notification

Imported payments trigger approval alerts

Rollback capability

Can void entire import batch if needed

Audit trail

Full history of who imported what and when

---

Did this answer your question?