Skip to content
Banking & finance

Close the day before the day closes.

Core banking hosts, card switches, credit bureaus and regulators all hold part of the same picture. SpanFlow joins them on your own servers — where banking data has to stay.

1

End-of-day reconciliation

Today

An operations officer exports from the core system, downloads the switch file and matches them in a spreadsheet every evening.

With SpanFlow

The officer arrives to an exception list. Matched transactions are already filed; every break is in their inbox.

  1. 1Core ledger
  2. 2Settlement file (SFTP)
  3. 3Match & compare
  4. 4File the matched set
  5. 5Email each break

See it working: End-of-day reconciliation (ledger vs settlement file)

2

Customer onboarding as one decision call

Today

An officer opens three tabs — ID service, credit bureau, watch list — and keys the same customer into each.

With SpanFlow

Branch, mobile app and call centre all call one endpoint. The checks run in parallel and return one decision.

  1. 1POST /onboarding
  2. 2ID check
  3. 3Credit check
  4. 4Watch-list screen
  5. 5One decision

See it working: Onboarding checks as one decision call

3

Monthly regulatory return

Today

Someone assembles the submission from four systems over three days at month end.

With SpanFlow

The return is assembled the same way every month, totals grouped and checked, waiting for sign-off.

  1. 1Scheduled monthly
  2. 2Gather from each system
  3. 3Group & total
  4. 4Check rules
  5. 5Sign-off email

See it working: Monthly regulatory return, assembled and signed off

Templates for banking & finance

Runnable today — create them in your workspace and press run.

Database → SFTP file

Database → CSV on SFTP

Writes a CSV onto the SFTP server — including one deliberately broken row. It exists to give the validate-and-route demo something to find, which…

PostgreSQLSFTP
File in, validation, two destinations

SFTP CSV → validate → database, rejects emailed

Reads the CSV back off SFTP and takes it a row at a time: good rows are loaded into a table, a bad one is emailed to somebody instead of being…

SFTPPostgreSQLEmail
Excel export

Database → Excel workbook in object storage

The same rows again, this time as a real .xlsx workbook dropped into MinIO. Nothing about the pipeline changes except the format — that is the…

PostgreSQLAmazon S3
A finance app with a multi-page front end on a file database

Personal finance app (app + front end)

A small money tracker on a local SQLite file, with a front end: accounts, transactions, a category summary and an add form. See the totals, log a…

SQLitePublished appFront end5 pipelines
Two sources joined, breaks routed and emailed

End-of-day reconciliation (ledger vs settlement file)

The bank operations job, end to end: the core ledger on one side, the settlement file the switch dropped on SFTP on the other, joined on…

PostgreSQLSFTPEmail
Parallel checks joined into one published decision

Onboarding checks as one decision call

The tabs an onboarding officer opens by hand — the identity service on one, the credit bureau and its watchlist flag on another — as one published…

PostgreSQL
Scheduled assembly, grouped totals, state and sign-off

Monthly regulatory return, assembled and signed off

The month-end return as a scheduled pipeline instead of three days of assembly. Exposures are read, grouped and totalled by category, each total…

PostgreSQLEmail
Rendered documents

Donation receipts, one per gift (PDF)

Every donation row becomes its own receipt: the node repeats over the rows with forEach and writes each PDF straight to a file store, so the run…

SQLiteLocal filesRendered documents

Stop moving data by hand.

Start free with three projects, or talk to us about running it across your organisation.