LoginSign Up
← Back to all sparks
T

Treasury Prime

FINANCE
Velocity5.0

BaaS infrastructure platform in steady operational-polish mode — ACH reliability, Prime Data fields, Console workflow upgrades.

banking-as-a-serviceachfednowprime-dataconsole-workflowsreliability
◆Current state
Treasury Prime is a banking-as-a-service infrastructure platform serving banks and fintechs. The visible window is dominated by operational polish — flexible ACH return filing, transaction-table filters and sorting, ACH trace numbers exposed in both API and the Snowflake-based Prime Data mart, and a beta payment-limit notifications surface in the Console.
◆Where it's heading
The throughline is closing edge-case operational gaps for bankers and reconciliation teams. Each release fixes a specific manual workaround (duplicate ACH returns, missing account.status, missing FedNow reject reasons) or surfaces an existing field where it was previously unavailable (trace_number, closed_date, DW_UPDATED_TS). Snowflake migration of Prime Data continues underneath. No directional pivots — pure platform hardening.
◆Prediction
Expect more Beta-tier surfaces (notifications, changelog inbox) graduating to GA as customer feedback firms up. Continued ACH and FedNow workflow refinement, and Prime Data field-by-field expansion to reach API parity. The Snowflake-only future after V1 deprecation shapes upcoming data work.

◆Recent moves

  1. 1mo ago

    Flexible ACH return filing option

    Bankers can now mark an incoming ACH as returned without auto-generating a duplicate file entry — fixing the same-day-double-return case that the team flags as a top support request. Plus a deduplication fix in the int_ledger_transaction_stream model.

    View source ↗
  2. 2mo ago

    ACH window configuration times displayed consistently

    ACH processing window times now render in a consistent wall-clock format with timezone, matching other time-based config fields. Small change but reduces ambiguity for non-Eastern-timezone banks reviewing or editing schedules.

    View source ↗
  3. 2mo ago

    ACH trace number now in Prime Data

    ACH trace_number, previously API-only, is now queryable directly from Prime Data. Plus DW_UPDATED_TS arrives on assoc_txn_backing_book for incremental recon, and account.status gets a backfill across previously-null records. All three changes target the Prime-Data-should-mirror-the-API goal.

    View source ↗
  4. 2mo ago

    Payment limit notifications - available to Beta users ONLY

    Beta surface for org-level velocity-limit notifications across ACH, wire, check, and FedNow, plus a queueing system that improves webhook delivery reliability under load. Webhook queueing is the more material change — it directly reduces the dropped-event class of incidents.

    View source ↗
  5. 2mo ago

    ACH trace numbers now available in the API

    ACH trace numbers reach the API ahead of landing in Prime Data twelve days later — letting fintechs surface them to end customers without contacting the bank. Plus a beta changelog-notification bell in the Console and closed_date display on account details.

    View source ↗
  6. 2mo ago

    Transaction-table sorting and filters; ACH overlap reliability fix

    Console transaction table gains amount sorting and filters by transaction type and payment source, replacing CSV-export workflows for narrow lookups. Underneath, ACH ledger processing handles overlapping runs without serialization errors.

    View source ↗