Which transaction types should a treasury engine natively support to cover corpo

A fit-for-purpose treasury engine should natively support the full lifecycle for: (1) Payments and collections across rails (SWIFT MT/ISO 20022, ACH/NACHA, SEPA, RTP/FedNow), including file formats, pain/pacs/camt messages, and bank APIs; (2) FX cash and derivatives (spot, forwards, swaps), with confirmations, settlement netting, and CLS/PvP where available; (3) Interest rate instruments (loans, deposits, IRS), with accruals and hedge effectiveness; (4) Investments (MMFs, time deposits, commercial paper), including cutoffs and reporting; (5) Debt and intercompany positions, including in-house bank and netting. Native reconciliation, intraday positions, and exception handling are essential to attain straight-through processing. ISO 20022 schemas provide the extensible structures for payments, statements, and billing (camt.086), while SWIFT’s network and standards facilitate global bank connectivity. For U.S. domestic rails, NACHA rules govern ACH transaction formats and return handling. Ensuring these transaction types are supported with robust controls (dual approvals, sanctions screening integration) reduces operational risk and accelerates settlement. Key Takeaway: Cover payments, FX/IR, investments, debt, and intercompany—with ISO 20022-native data and multi-rail connectivity—to meet enterprise treasury needs.