greek-banking-integration_skill

This skill processes Greek bank statement files (CSV/Excel) from Alpha, NBG, Eurobank and Piraeus, reconciling transactions for accurate accounting.
  • Python

2.5k

GitHub Stars

3

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill greek-banking-integration

  • _meta.json314 B
  • EVALS.json19.0 KB
  • SKILL.md22.3 KB

Overview

This skill parses and reconciles bank statements from all major Greek banks (Alpha, NBG, Eurobank, Piraeus) using file imports (CSV/Excel) and local processing. It provides format detection, Greek-specific encoding fixes, VAT-aware categorization, and automated transaction matching for bookkeeping and exports to accounting systems. No bank API credentials are required — you work with exported statement files placed in import directories.

How this skill works

The skill scans configured import directories, auto-detects bank and file formats, fixes Greek character encodings and date/amount formats, and normalizes transactions into a canonical schema. It applies Greek business rules for expense/income categorization, VAT detection, SEPA and card transaction patterns, then runs confidence-scored reconciliation and duplicate detection. Outputs include reconciliation reports and accounting-ready CSV/JSON for QuickBooks/Xero.

When to use it

  • You receive exported CSV/Excel statements from Greek bank web portals and need automated parsing.
  • You need to reconcile client payments and invoices for Greek companies with VAT rules.
  • You want to batch-process multiple bank accounts across Alpha, NBG, Eurobank, and Piraeus.
  • You must produce accounting exports compatible with QuickBooks or Xero for Greek chart-of-accounts mapping.
  • You require duplicate detection, cashflow analysis, or payment confirmation tracking for Greek operations.

Best practices

  • Place raw exports into per-bank import folders (/data/banking/imports/{bank}).
  • Run format validation first to fix encoding and date/amount inconsistencies before reconciliation.
  • Use auto-detect and test-formats commands on sample files when onboarding a new account.
  • Tune confidence-thresholds for invoice matching to balance automation vs manual review.
  • Keep a processing workspace with raw, validated, categorized, and reconciled folders for clear audit trails.

Example use cases

  • Monthly automated reconciliation for a Greek SME with multiple bank accounts and recurring supplier payments.
  • Matching incoming client transfers to outstanding invoices using reference and fuzzy client-name matching.
  • Preparing accounting exports (CSV/JSON) for QuickBooks or Xero with Greek VAT codes and chart-of-accounts mapping.
  • Detecting duplicate charges and flagging suspicious transactions across accounts (same-day same-amount).
  • Running periodic cashflow analysis and fee optimization reports for bank charges and SEPA fees.

FAQ

No. The skill processes exported files you download from bank portals (CSV/Excel/PDF where supported).

Which banks and formats are supported?

Alpha, National Bank of Greece, Eurobank, Piraeus and several regional banks. Common formats: Excel, CSV, MT940/MT942, OFX, QIF and PDF exports where available.

Can it export to accounting software?

Yes. Exports to CSV, JSON and optional QuickBooks/Xero-compatible formats with Greek VAT and chart-of-accounts mapping.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational