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.
| 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 |
Select a flow in the diagram, or pick one below, to see what happens in LN, ION and Ripple Treasury.
| 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 | The client already runs bank connectivity and fraud controls through Ripple Treasury | The client wants AP, AR and bank reconciliation to run natively in LN |
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.
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 |
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.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).tfcmg5104m000) and Conversion Data (tfcmg5105m000) for the agreed format. EBS Matching Rules (tfcmg5115m000), including rules that send treasury transaction codes to a clearing account.tfgld0503m000). Treasury clearing and suspense accounts. Automatic account matching (tfgld1250m000) on the clearing accounts.| 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 needs a conversion to be confirmed. |
| 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 | The LN manuals do not describe a positive pay file. If checks print from LN, positive pay is a build from LN check data, or Ripple Treasury produces it. |
| Payroll funding | Payroll totals come from the payroll provider, not LN. |
| 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). |
Session codes, OData paths and behaviors come from the Infor LN 2026.x manuals and the LN OData API catalog. Anything they do not describe is marked as a build or an open decision.