Financial File Normalizer avatar

Financial File Normalizer

Under maintenance

Pricing

from $250.00 / 1,000 successful file normalizations

Go to Apify Store
Financial File Normalizer

Financial File Normalizer

Under maintenance

Exact transaction JSON from customer-owned OFX/QFX/QBO, mapped CSV and transaction-only QIF exports.

Pricing

from $250.00 / 1,000 successful file normalizations

Rating

0.0

(0)

Developer

Andrew

Andrew

Maintained by Community

Actor stats

0

Bookmarked

1

Total users

0

Monthly active users

5 days ago

Last modified

Share

Convert your own exported banking transactions into exact, validated JSON. Supported: banking/credit-card OFX 1/2, OFX-formatted QFX/QBO, explicitly mapped CSV and transaction-only QIF Bank/Cash/CCard.

  • Exact decimal-string amounts; no floats, rounding or LLM inference. At most 38 significant and 12 fractional digits; excessive precision/scientific notation is rejected.
  • Explicit date/currency conventions, account numbers suppressed, source-ID deduplication with conflict rejection.
  • Safe errors instead of silently returning partial success.
  • Hard limits: 2 MB content, 10,000 raw transactions; caller limits may be lower.

What it does not do

No bank connections, financial/accounting/tax advice, PDF/OCR, investment/loan statements, QIF account/split sections, QuickBooks import-file generation or balance reconciliation. This is transaction extraction, not full-fidelity archival conversion. Do not upload credentials or information you are not entitled to process.

Input and output

Paste export text into content. CSV additionally needs csv_mapping and csv_currency; QIF needs csv_currency and an explicit csv_date_format. One normalized result appears in the default dataset, with a transactions array and summary counts/net totals. All examples in the source project are synthetic.

Privacy

Apify stores input and dataset output under its platform/account retention settings. This is not a zero-retention actor. Review run-storage access/deletion and your data-processing requirements before sending real financial data. Local-library/HTTP alternatives do not intentionally persist request data.

Pricing and availability

Unpublished draft. Suggested validation price: $0.25 per successfully normalized file; not configured, enabled or charged by this build. API availability and payment entitlement must be verified on the exact approved deployment before launch.

Support

After publication, use the Apify Messaging button for the publisher. No public support or listing is created by this local build.