# PocketLog Importer

PocketLog Importer is a Docker container companion for PocketLog that automatically turns bank comma-separated value (CSV) exports into PocketLog transactions. It is open source and self-hosted, installable on Docker Hub and Unraid.

Canonical page: https://ourlocalhost.com/app/2428/pocketlog-importer

## Description

PocketLog Importer is a Docker container companion for PocketLog that automatically turns bank comma-separated value (CSV) exports into PocketLog transactions. It runs as a background service: a scheduled job reads new CSV files, applies a regex whitelist, and pushes only matched, enriched bookings to PocketLog's CSV import endpoint. It is useful for self-hosters who want rule-based, repeatable bank-statement import without a web interface.

## Platform availability

Available on 1 of 10 platforms: Unraid.

## Health score

47/100 (Fair), based on 3 of 4 factors.
- Maintained: 83 (last commit 81 days ago)
- Popular: 0 (0 GitHub stars)
- Easy to install: 35 (1 install platform, install notes, Docker image)

## Links

- Docker Hub: https://hub.docker.com/r/anym001/pocketlog-importer
- Unraid: https://ca.unraid.net/apps/pocketlog-importer-1l5tg0q07r7d2m?q=pocketlog-importer
- GitHub: https://github.com/anym001/pocketlog-importer

## Common questions

### How do I connect pocketlog-importer to my PocketLog instance?

Create an API key in PocketLog with the import scope, pass it to the container as POCKETLOG_API_KEY, and set pocketlog.base_url in config/config.yaml.

### How do I control which bank bookings are imported?

Edit config/rules.yaml with regex rules, which are matched case-insensitively and first match wins. Bookings that match no rule are dropped and written to a .unmatched.csv file for review.

### How often does it process new CSV files, and can I trigger it manually?

It uses an internal cron scheduler, with hourly processing by default. You can also trigger a one-off run with docker exec pocketlog-importer pocketlog-import --once.

### Can I test the rules before anything is imported into PocketLog?

Yes, run the importer with --dry-run to write the output CSVs without importing anything.

### Where are processed, failed, and unmatched files stored, and is rerunning safe?

Processed originals move to /data/processed, failed files go to /data/failed, and unmatched bookings are written to .unmatched.csv. PocketLog deduplicates, so re-runs are safe.

---
Source: Our Local Host (https://ourlocalhost.com/app/2428/pocketlog-importer), the self-hosted and open-source app directory.
