Skip to content

Latest commit

 

History

History
173 lines (139 loc) · 4.69 KB

File metadata and controls

173 lines (139 loc) · 4.69 KB

Module: Accounting (e-racuni.com)

Datafund accounting integration with e-racuni.com - Slovenia's accounting software.

Overview

This module provides:

  • Financial Overview: Bank balances, receivables, payables at a glance
  • Invoice Tracking: Sales invoices (receivables) and received invoices (payables)
  • Payment Planning: Prioritized payment suggestions based on due dates and cash position
  • Spend Analysis: Retrospective analysis by cost center, category, and project

Quick Reference

Command

Single entry point: /accounting [action]

/accounting sync        # Pull latest data from e-racuni
/accounting overview    # Show financial snapshot
/accounting payables    # List outstanding invoices by vendor
/accounting plan        # Generate payment prioritization
/accounting analyze     # Spend analysis by cost center/category/project
/accounting classify    # Classify paid invoices

Agents

Agent Purpose
accounting-sync Pull data from e-racuni API
accounting-overview Generate financial snapshot
pending-payments List payables grouped by vendor
payment-planner Payment prioritization suggestions
spend-analyzer Spend analysis by cost center/category/project
invoice-classifier Classify paid invoices for analysis

GTD Tags

  • :AI:accounting: - General accounting task
  • :AI:accounting:sync: - Data synchronization
  • :AI:accounting:classify: - Invoice classification

e-racuni.com API

Endpoint

https://e-racuni.com/WebServicesSI/API

Authentication

Every request requires:

  • username: API user account
  • md5pass or secretKey: API password
  • token: Organization token (unique per database)

Rate Limits

  • Standard API: 1 request/second, max 4 burst
  • Reporting API: No limits (for bulk data)

Key API Methods Used

Method Purpose
GeneralLedger.getAccountBalance Account balances
SalesInvoice.getByNumber Retrieve sales invoices
ReceivedInvoice.getList List supplier invoices
Partner.getList Customer/supplier data

Request Format

{
  "username": "api_user",
  "md5pass": "secret_key",
  "token": "org_token",
  "method": "SalesInvoice.getByNumber",
  "parameters": {
    "number": "INV-001"
  }
}

Data Storage

All data stored in 1-datafund/knowledge/accounting/:

knowledge/accounting/
├── balances.json           # Latest account balances
├── invoices/               # Sales invoices (receivables)
├── payables/
│   ├── pending/            # Unpaid supplier invoices
│   └── paid/               # Paid invoices with classification
├── vendors/                # Vendor summary data
├── analysis/               # Generated spend reports
└── sync-log.json           # Sync history

Invoice Classification Schema

Paid invoices include classification metadata:

{
  "invoice_id": "INV-001",
  "vendor": "Vendor Name",
  "amount": 1500.00,
  "currency": "EUR",
  "status": "paid",
  "paid_date": "2025-12-01",
  "classification": {
    "cost_center": "VERITY-2025",
    "category": "infrastructure",
    "project": "Dubai Gold Pilot",
    "tags": ["cloud", "hosting"]
  }
}

Categories

Standard expense categories:

  • infrastructure - Hosting, cloud, servers
  • services - Professional services, contractors
  • software - Licenses, subscriptions
  • marketing - Advertising, events
  • legal - Legal, compliance
  • admin - Office, administration
  • travel - Travel, accommodation
  • other - Uncategorized

Personal Settings Integration

Financial data is sensitive. Daily briefing inclusion is opt-in.

Configure in 0-personal/.datacore/settings.local.yaml:

daily:
  include_accounting:
    enabled: true
    spaces: ["1-datafund"]

Workflow

Daily Sync (via /today)

  1. If personal settings enable accounting for this space
  2. Run /sync-accounting to pull latest data
  3. Include financial summary in briefing:
    • Bank balance
    • Outstanding receivables/payables
    • Overdue items flagged
    • Payments due within 7 days

Payment Planning

  1. Run /pending-payments to see outstanding by vendor
  2. Run /payment-plan to get prioritized suggestions
  3. Review and execute payments manually in e-racuni

Spend Analysis

  1. Ensure paid invoices are classified (manual or via rules)
  2. Run /accounting-analysis with filters:
    • By cost center
    • By category
    • By project
    • By time period

Security Notes

  • API credentials stored in .datacore/env/.env (gitignored)
  • Never commit credentials to repository
  • Module does NOT execute payments - human approval required
  • Financial data stays local, not synced to git