Zero-upload treasury utility

Private Payment-Run Preflight

Run ISO, EPC SCT 2025, CBPR+ SR2026 readiness, duplicate, identifier, and control-sum checks before release.

Free to use Bank and payment data stays in browser memory and is never uploaded. 0 bytes transmitted — your file never leaves this device

Bank statements and payment files expose account numbers, counterparties, balances, and references. This workspace reads them only in browser memory and creates downloads locally, so none of that bank data is sent to Lucaden or a third party.

Loading tool workspace…

How it works

Complete the job in three clear steps

Choose or paste the bank, payment, invoice, or ledger data required by this workspace.
Run the local parser and resolve every explicit validation or reconciliation failure.
Download the browser-created result, then verify it against the original and the receiving bank’s rules.

Important

Verify every financial result independently

A local validator can prove structural checks, but it cannot confirm a bank's implementation rules, account status, sanctions controls, or settlement. Keep the source file, review every result, and test generated output with the receiving bank before production use.

No warranty — independent verification required

These tools provide local technical checks and transformations, not banking, legal, compliance, or accounting advice. Formats and bank usage rules vary. Always verify output with your bank before submitting, keep the original file, and use a bank test or sandbox channel where available.

Deep explainer

Format, users, failure modes, and a worked example

What the format is

Preflight accepts CSV, one-sheet XLSX, or pain.001 and evaluates required fields, identifiers, exact counts and sums, duplicates, currencies, EPC reference rules, execution dates, and optional CBPR+ address readiness.

Who uses it

Payment factories, AP, payroll, treasury release, ERP export, bank onboarding, and implementation teams checking a batch before bank submission.

Common failure modes

NbOfTxs or CtrlSum differs from extracted payments
An IBAN, BIC, currency, or end-to-end ID is invalid
An EPC identifier starts or ends with slash or contains double slash
A linked supplier-firewall case still holds the beneficiary account

Worked example

A pain.001 declares three transactions and EUR 2,400.00 but contains two duplicated EUR 1,250.00 payments and an unstructured address. The records enter Hold/Fail queues with exact paths; Lucaden never removes or silently repairs them.

Practical details

What this Lucaden tool does

Run ISO, EPC SCT 2025, CBPR+ SR2026 readiness, duplicate, identifier, and control-sum checks before release.

Every byte of input is parsed in this browser tab. Downloads are created with Blob URLs; the suite has no upload endpoint, server action, edge parser, or content-bearing telemetry.

Included capabilities

Client-side File/ArrayBuffer reads
Local validation and generation
Blob URL downloads
Actionable failures instead of partial output

Useful for

Pre-flight payment files
Migrate bank formats
Validate master data
Reconcile finance exports

Questions

About this tool

Does Lucaden upload this bank or payment data?

No. These treasury routes read local files through browser ArrayBuffers, parse them in this tab, and create downloads with local Blob URLs. There is no file upload request.

Can a passing result guarantee bank acceptance?

No. A base-format check cannot cover every bank implementation guide, bilateral agreement, local scheme rule, or compliance control. Always test and confirm the output with the receiving bank.

What should I do when the tool reports malformed input?

Keep the original, use the reported row, tag, line, or path to correct the source system, and run the complete file again. Lucaden does not silently drop malformed financial records.

Open-source foundations

Built transparently

Lucaden documents its standards sources, architectural references, and permissive runtime dependencies while keeping this workspace consistent with the Lucaden interface.

SWIFT structured address milestoneOfficial standards guidance source ISO 20022 message catalogueOfficial standards catalogue source EPC SCT 2025 implementation guidelinesOfficial scheme guidance source Factur-X 1.08 / ZUGFeRD 2.4 announcementOfficial specification announcement source ibantools 4.5.4MIT runtime option source pdf-lib 1.17.1MIT runtime source ExcelJS 4.4.0MIT runtime source Papa Parse 5.5.4MIT runtime source JSZip 3.10.1MIT runtime source Third-party noticesLicenses and attribution