Home › NetSuite Financials ⇄ Bank · Splunk SIEM · Treasury + Compliance
Turion Space · 7 integration points · 6 connector technologies
NetSuite
ERP · system of record for: GL · FX · vendor payments · A/R · A/P · period close · audit log origin
NetSuite
Bank (Wells Fargo) · daily FX feed · transactions · ACH/wire · Splunk Cloud SIEM · cross-system audit aggregation
Total integration points
7
3 categories
Bank → NS flows
3
FX · transactions · reconciliation
NS → Bank flows
1
ACH payment runs
→ SIEM flows
3
audit aggregation + alerting
Connectors
6
NS Banking + NACHA + Splunk + UF + PagerDuty + Slack
📋 All Integrations
💱 Bank · FX + Transactions (3)
💸 Treasury · ACH + Payments (1)
🔐 Compliance · Audit Aggregation (3)
🔌 Connector Stack
📜 Sync Run History
ConnectorVendorUsed forLicenseNotes

🔧 Architecture rationale

Why 6 connectors? Bank operations and SIEM aggregation need different transports:
  • NS Banking native · FX rates + transaction download + auto-match · OAuth 2.0 to Wells Fargo.
  • NACHA + SFTP · ACH payment runs · same-day wires · per-tx fees from bank.
  • Splunk Cloud SIEM · cross-system audit aggregation · CMMC L2 + DFARS 252.204-7012 mandated · same connector as SF↔NS audit flow (INT-043).
  • Splunk Universal Forwarder · one per system (NS · SF · Arena · MES · Vendor portal) · TLS 1.3 + cert auth.
  • PagerDuty · critical alert paging · on-call rotation for security incidents.
  • Slack · non-critical alert channel · daily digest · still audit-logged.

Last 24 hours of sync runs across all connector flows. Click any row to drill into the integration detail.

TimestampFlowStatusDurationRecordsErrorsNotes