LN–Ripple Treasury Integration
How Infor LN, Ripple Treasury (formerly GTreasury) and the banks work together across the whole cash cycle: AP payments going out, customer receipts and remittances coming in, bank statements, forecasting and treasury journals.
LN connects to Ripple Treasury and the banks through three standard pieces: LN Cash Management, which runs payment and direct debit runs, cash application and bank statement (EBS) processing; ION API Gateway, which lets Ripple Treasury read LN data and post journals through LN's OData services; and ION Connect, which moves bank-format files over sFTP and delivers messages such as customer remittance advices into LN.
Payables and receivables at a glance
| Accounts Payable (money out) | Accounts Receivable (money in) | |
|---|---|---|
| What LN sends | Approved AP payment batches (ACH, check, wire) | Direct debit collections, if customers are debited |
| What LN receives | Payment confirmation through the bank statement | Customer receipts on the bank statement and remittance detail for cash application |
| Where it is matched | Bank Statement Workbench: payment against anticipated payment | Bank Statement Workbench and Remittance Advices: receipt against invoices |
| What Ripple Treasury needs | Payments due and payments released | Receivables expected and cash received |
System diagram
Runs on the Infor OS you already have:IDMIDP GenAIIONInfor RPAAPI Gateway
Accounts Payable
Accounts Receivable
Close and improve
Select an item in the diagram, or pick one below, for details.
Velocity Suite compared with an external vendor
| Velocity Suite | External cash-application vendor | |
|---|---|---|
| Where it runs | On the Infor OS you already have: IDM, IDP, ION, RPA and API Gateway | On a separate platform with its own login, data store and uptime |
| How data reaches LN | Standard messages LN already accepts (Process.CustomerRemittanceAdvice, Load.SupplierInvoice) | A custom integration that the project builds and you maintain |
| Documents | Stored in IDM and linked to the LN transaction | Stored in the vendor's system |
| Security | Infor OS roles, one user directory | A second user directory to administer |
| Exceptions | ION notifications with drill back to the document | The vendor's portal |
| Upgrades and support | Infor-delivered catalog, deployed with Infor Services | A separate contract and upgrade cycle |
| Cash matching | LN's EBS Matching Rules, fed by Velocity Suite remittance advices | The vendor's own matching engine, with results passed back to LN |
What it takes
- Velocity Suite is an Infor Cloud add-on to CloudSuite.
- Infor Services deploys and configures each automation.
- Documents are legible and in English, scanned at 300 DPI, one document per PDF under 20 pages.
- Unattended automations run on a Windows server without multi-factor authentication. Email is read from Outlook (classic) or Office 365.
- A proof of value on a sample of your real remittances shows the result with your own data.
Choosing a routing model
| Model A · Ripple Treasury as bank hub | Model B · Hybrid | |
|---|---|---|
| AP payments to the bank | Sent by Ripple Treasury | Sent by LN |
| Direct debit collections | Sent by Ripple Treasury | Sent by LN |
| Customer remittance detail | Banks to Ripple Treasury, then to LN | Banks straight to LN |
| Bank statements for LN | Re-delivered by Ripple Treasury | Straight from each bank |
| Cash application and bank reconciliation | In LN | In LN |
| Bank connections to maintain | Ripple Treasury only | LN (through ION) and Ripple Treasury |
| Payment approval | Ripple Treasury workflow, plus LN batch approval | LN batch approval and payment authorizations |
| If Ripple Treasury is down | AP payments, collections and LN cash application wait | Only treasury payments and forecasting wait |
| Fits when | Bank connectivity and fraud controls already run through Ripple Treasury | AP, AR and bank reconciliation should run natively in LN |
Avoid posting twice
Every treasury transaction eventually appears on a bank statement. If Ripple Treasury also sends a journal for it (interest, fees, a sweep, a funding transfer), the matching statement line in LN must clear against a treasury clearing account through EBS Matching Rules instead of posting to the P&L a second time. Automatic account matching keeps the clearing account at zero. Agree, per transaction type, which system books the entry.
LN integration points
Each LN object Ripple Treasury or the banks touch, the LN session behind it, and how it is reached.
| Data | In LN | Interface | Direction |
|---|---|---|---|
| AP payment batch | Payment Advices (tfcmg1509m000) | GET /odata/tfapi.cmgPayment/Advices and /Lines, or LN payment file over SFTP | LN to Ripple Treasury or bank |
| Direct debit batch | Direct Debit Advices (tfcmg4509m000) | Direct debit file over SFTP | LN to Ripple Treasury or bank |
| Customer remittances | Remittance Advices (tfcmg2150m000) | Process.CustomerRemittanceAdvice BOD in; GET /odata/tfapi.cmgRemittanceAdvice/Remittances and /Lines | Into LN; read |
| Bank statements | Bank Statement Workbench (tfcmg5610m100) | Statement file into the EBS directory over SFTP; GET /odata/tfapi.cmgBankStatement/Statements and /Lines | Into LN; read |
| Treasury journals | Received Journal Workbench (tfgld2616m000) | POST /odata/tfapi.gldReceivedJournal/Journals and /Lines | Ripple Treasury to LN |
| AP open items | AP open entries | GET /odata/tfapi.acpInvoice/OpenEntries | Read |
| AR open items and receipts | AR open entries and receipts | GET /odata/tfapi.acrInvoice/OpenEntries and /Receipts | Read |
| Banks and methods | Bank Relations, Payment/Receipt Methods | GET /odata/tfapi.cmgFinancialsMasterData/BankRelations and /PaymentReceiptMethods | Read |
| GL master data | Chart of Accounts, Dimensions, Periods | GET /odata/tfapi.gldFinancialsMasterData/ChartOfAccounts, /Dimensions, /Periods | Read |
| Supplier and customer bank accounts | Bank accounts by pay-to and pay-by business partner | GET /odata/tcapi.comBusinessPartner/BankAccountsByPaytoBusinessPartner and /BankAccountsByPaybyBusinessPartner | Read |
| Credentials | ION API Gateway authorized app | Backend Service app, OAuth 2.0, .ionapi file | Setup |
LN-side setup checklist
- Infor OS. Create the service-account user. In ION API Gateway, add an authorized app of type Backend Service, download the .ionapi file and share it with Ripple Treasury through a secure channel, not email. Give the user LN authorization for the Cash Management, AP, AR and GL services it calls.
- ION Connect. File connection points (sFTP from cloud, PGP where required) for each file direction. A document flow for the Process.CustomerRemittanceAdvice BOD. Set up the file route into the LN payment, direct debit and EBS directories with Infor Cloud.
- LN payables. CMG Parameters (
tfcmg0100s000) incl. Payment Batch Approval. Bank Branches (tfcmg0511m000). Bank Relations (tfcmg0510m000). Payment methods with file output. Data by Bank/Payment Method (tfcmg0645m000). Payment Authorizations (tfcmg1100m000). Automatic Process Defaults (tfcmg1191m000) for the overnight run. - LN receivables. Direct debits (if used): Invoke Direct Debits Process after Selection, Direct Debit Process Default ID and Direct Debit Batch Approval in CMG Parameters. Cash application: Cash Application Options in CMG Parameters (
tfcmg0500m000), debit and credit note settings in Invoicing Parameters (cisli0100m000), the reversal transaction type on each Bank Relation (tfcmg0110s000), and the Agreed Short Payment transaction type on Financial Business Partner Groups (tfacr0110m000). - LN bank statements. Path for EBS Files and Path For EBS Archive on each bank relation. Transaction Date in Case of Telebanking in CMG Parameters. Record Types (
tfcmg5104m000) and Conversion Data (tfcmg5105m000) for the agreed format. EBS Matching Rules (tfcmg5115m000), including rules that send treasury transaction codes to a clearing account. - LN General Ledger. Transaction type, series and Authorized User for External Journals in Finance Company Parameters (
tfgld0503m000). Treasury clearing and suspense accounts. Automatic account matching (tfgld1250m000) on the clearing accounts. - Ripple Treasury. Connection to the LN endpoints. Payment and collection import (Model A). Remittance export per deposit. Cash ledger and GL extracts for journals, with posting options mapped to LN ledger accounts and dimensions. Bank accounts matching LN bank relations.
- Test end to end. AP: payment batch to bank to statement to match, plus one rejected payment. AR: customer receipt with remittance to applied invoice, a short payment, and a receipt with no remittance. GL: journal to workbench to post. One treasury transaction that shows on both the journal feed and the statement.
- Run it. Add new bank accounts on both sides. Watch ION for failed messages, Ripple Treasury job logs, Received Journal Workbench errors, EBS exceptions and unallocated receipts.
Design decisions
| Decision | What to settle |
|---|---|
| Routing model | Model A, Model B, or a mix by bank. |
| Ripple Treasury connection to LN | Which connection options Ripple Treasury supports for Infor LN (API, file import, or both). This decides how much mapping is built. |
| AP payment files | Which format each bank needs, and whether LN or Ripple Treasury produces it. |
| Direct debits | Whether customers are debited at all. If so, who formats the US ACH debit file. |
| Lockbox and remittance source | Where invoice-level remittance detail comes from (bank lockbox files, ACH addenda, emailed PDFs, EDI), and whether it reaches LN through Ripple Treasury or directly. |
| Statement format into LN | MT940 is distributed natively. BAI2 or CAMT layouts are defined during setup. |
| Short pays and unapplied cash | Tolerances, the short payment account, and whether LN generates debit notes for underpayments. |
| Who books what | For each treasury transaction type (interest, fees, sweeps, FX, intercompany funding), whether Ripple Treasury's journal or LN's EBS posting books it. |
| Positive pay | If checks print from LN, the positive pay file is produced from LN check data (integration build) or by Ripple Treasury. |
| Payroll funding | Payroll totals come from the payroll provider, not LN. |
LN terms for the treasury team
| LN term | Meaning |
|---|---|
| Financial company | The accounting entity. Maps to a Ripple Treasury entity. |
| Group company | The company that groups several financial companies. |
| Bank relation | One of your company's bank accounts, with its bank branch, currency and IBAN (tfcmg0110s000). |
| Bank branch | The bank itself (tfcmg0511m000). |
| Payment / receipt method | How an invoice is paid or collected, and which file or report LN produces (tfcmg0140s000). |
| Pay-to business partner | The supplier being paid (tccom4124s000). |
| Pay-by business partner | The customer who pays (tccom4114s000). |
| Payment batch / payment advice | The invoices selected and composed for one payment run. |
| Direct debit advice | The customer invoices selected for one direct debit run. |
| Anticipated payment / receipt | A payment or receipt in flight, posted to an anticipated account until the bank statement confirms it. |
| Remittance advice | The customer's note of which invoices a payment covers (tfcmg2150m000). |
| Unallocated receipt | Cash received but not yet applied to an invoice. |
| Electronic bank statement (EBS) | A bank statement imported, matched and posted in LN. |
| Ledger account / dimension | GL account and analysis segment. LN supports up to 12 dimension types. |
| Received journal | A journal created outside LN, imported for validation and posting (tfgld2616m000). |
Sources
- Infor LN Financials User Guide for Cash Management, 2026.x. Set up Cash Management and EBS setup (p. 9 to 19), payments and direct debits (p. 20 to 27), Electronic Bank Statements (p. 35 to 37), Cash Application (p. 77 to 79), report groups (p. 101 to 102).
- Infor LN Financials SEPA Master Data Setup, 2026.x. Payment/Receipt Formatted by and the CreditTransferBOD (p. 15).
- Infor LN Financials User Guide for General Ledger, 2026.x. Dimension accounting (p. 12), Journal import and Import Journal Workbench (p. 60 to 61).
- Infor LN CloudSuite content guides for Velocity Suite automations, 2026.x. Customer remittance advice automation (IDP GenAI and RPA, Process.CustomerRemittanceAdvice) and Financial Closing of Unallocated Receipts.
- Infor LN Electronic Commerce User Guide for EDI Business Documents, 2026.x. Remittance Advice (RAD) message.
- Infor API Gateway Administration Guide, 2026.x. Authorized apps, Backend Service type, .ionapi credentials.
- Infor ION Technology Connectors Administration Guide (Cloud). File connection points: FTP, FTPS, sFTP, shared folder, PGP.
- Infor LN OData API catalog. tfapi.cmgPayment, cmgBankStatement, cmgRemittanceAdvice, cmgFinancialsMasterData, gldReceivedJournal, gldFinancialsMasterData, acpInvoice, acrInvoice; tcapi.comBusinessPartner.
Session codes and OData paths refer to Infor LN 2026.x. Items marked as an integration build or a design decision are confirmed during the design phase.