Recued
Menu
← Back to recipes

Records runtime compatibility canary

by recued-core v1 111 views

Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.

Complete workflow

Bank statement import 3 pinned recipes

Use “Bank statement import” in Recued to bring a statement you exported yourself — CSV from any bank — into your own warehouse, with no aggregator in the middle. Aggregators gate real account data behind an approved business account; a file needs no credentials and no third party sees your transactions. You name your bank's columns once, so nothing is guessed. Re-importing an overlapping export skips lines you already have instead of double-counting them. Feeds ledger-book and expense-ledger.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

Use “Import a bank statement (CSV)” in Recued. Reads a statement CSV you exported from your bank, lets you match its columns from the file’s own header, and records every line in your own warehouse. Re-importing an overlapping export adds only what is new.

pack:statement-importbankingcsvimport
by recued-core pinned v7

Use “List statement lines” in Recued. Shows imported statement lines, most recently imported first, for one account or across all of them, with the net for the page.

pack:statement-importbankingrecordsread
by recued-core pinned v1
View pack details, dependencies, and permissions →
How it works 1 step

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (1 steps)
◆ require_runtime core.records.require-runtime
Require runtime records

Uses (1 operation)

Pack operation Require runtime records core.records.require-runtime

About

Details

1 steps recipe_id: statement-import-require-records-runtime