PongoFin Documentation
Technical and operational guides for the financial platform, PongoSID, and PongoREI. Calculations, categorization, examples, and architecture — all in one place.
Platform architecture
PongoFin transforms raw banking data into structured financial intelligence through a layered processing pipeline. Every transaction is validated, normalized, and classified before entering any calculation or report.
Processing pipeline
- Import — Acquisition of bank statements and financial records from CSV, API, or manual entry
- Normalization — Standardization of formats, dates, and descriptions
- Classification — Assignment of each transaction to an accounting category
- Reconciliation — Cross-referencing bank movements with accounting records
- Analysis & Reporting — Generation of financial indicators, forecasts, and reports
Core modules
| Module | Function |
|---|---|
| Financial platform | Reconciliation, P&L, cash flow, business plan |
| PongoSID | Reporting to the Financial Accounts Registry (ARF) for obligated entities |
| PongoREI | REI compliance obligations and reports to financial intermediaries |
Supported data sources
| Source | Format |
|---|---|
| Bank statements | CSV, structured exports |
| API integrations | Real-time or batch sync |
| Manual entries | User-defined transactions |
transaction {
date
amount
description
counterpart
category
}
This ensures consistent processing regardless of the original source or format.
Calculation methods
All financial calculations follow standard accounting principles, with additional analytical layers for projections and insights. Rules are deterministic and every change, classification, and reconciliation is tracked with a timestamp and user attribution.
Data normalization
During import, every record goes through:
- File parsing — Structure detection and field extraction
- Date conversion — Unified ISO format across all sources
- Currency handling — Conversion and normalization to base currency
- Description cleanup — Noise removal, abbreviation expansion
- Operation type identification — Credit / debit classification
Bank reconciliation
Reconciliation verifies consistency between bank movements and accounting records. The reconciliation engine applies multi-attribute matching:
| Matching criterion | Description |
|---|---|
| Amount | Exact or near-exact match of the monetary value |
| Date proximity | Transactions within a configurable time tolerance |
| Description similarity | Textual comparison of transaction descriptors |
Unmatched items are flagged for manual review, ensuring complete auditability.
Chart of accounts
Every transaction is assigned to an accounting category based on a configurable chart of accounts. Standard categories include:
- Revenue — Sales, service fees, interest income
- Operating costs — Rent, salaries, supplies, utilities
- Taxes — VAT, income tax, social contributions
- Investments — Capex, asset acquisitions
- Internal transfers — Inter-account movements
P&L statement
The profit and loss statement is calculated by aggregating classified transactions over a period:
Revenue
− Operating costs
− Financial charges
− Taxes
─────────────────
= Net profit | Indicator | Definition |
|---|---|
| Operating margin | Revenue − Operating costs |
| EBITDA | Earnings before interest, taxes, depreciation, and amortization |
| Net profit | Final result after all costs, financial charges, and taxes |
Balance sheet
| Section | Components |
|---|---|
| Assets | Cash, receivables, inventory, fixed assets |
| Liabilities | Payables, loans, deferred revenue |
| Equity | Share capital, retained earnings, net profit |
Financial forecasting
The platform generates forward-looking projections based on:
- Historical cash flow analysis — Past revenue and cost patterns
- Time trends — Growth rates, decay curves, momentum
- Projection models — Statistical techniques applied to historical data
Automated business plan
| Output | Description |
|---|---|
| Revenue projection | Expected future revenue by period |
| Cost projection | Expected cost evolution |
| Cash flow forecast | Projected liquidity position |
| Sustainability indicators | Financial viability and runway metrics |
Data integrity
- Data validation — Schema and format checks on every imported record
- Balance verification — Ensures debits and credits remain balanced
- Duplicate detection — Identifies and flags potential duplicate transactions
- Cross-report consistency — Validates totals match across different report views
- Audit trail — Every change recorded with timestamp and user attribution
Categorization system
The system uses a 3-level hybrid approach to categorize transactions: deterministic rules, an AI-assisted model, and user review. Categories follow a hierarchical schema with parent categories and sub-categories.
The 3 classification levels
| Level | Method | When applied |
|---|---|---|
| 1 — Deterministic rules | Patterns on amount, counterpart, description | First application, highest precision |
| 2 — AI model | Classification based on historical data | When rules don't give a confident match |
| 3 — User review | Manual override and feedback | Ambiguous cases or new patterns |
Hierarchical category structure
| Category | Type | Main sub-categories |
|---|---|---|
| Revenue | Income | Product sales, Service fees, Interest income, Reimbursements |
| Operating costs | Expense | Rent, Utilities, Salaries, Supplies, Marketing, Software |
| Taxes & contributions | Expense | VAT paid, Income tax, Social contributions, Withholdings |
| Investments | Expense | Equipment, Software development, Participations |
| Financing | In/Out | Mortgages, Leasing, Credit lines, Loan repayments |
| Internal transfers | Neutral | Inter-account transfers, Cash withdrawals, Deposits |
Matching rules
Deterministic rules evaluate:
- Counterpart — Entity/company name in the payment reference
- Description pattern — Keywords and regex on the bank transaction note
- Amount range — Typical amounts by category (e.g. recurring payroll)
- Frequency and periodicity — Recurring transactions at a fixed amount
- SWIFT/BIC code — Counterpart bank identification
Input and output examples
This section shows concrete examples of how the platform processes bank data, from the import phase through to final reports.
Bank statement CSV format
The expected input format for bank statements:
Date;Description;Amount;Currency;Balance
2025-01-03;SALARY CREDIT;+3200.00;EUR;5400.00
2025-01-05;RENT PAYMENT;-1200.00;EUR;4200.00
2025-01-07;ENEL UTILITY BILL;-180.50;EUR;4019.50
2025-01-10;INVOICE RECEIPT 2025-001;+4500.00;EUR;8519.50
2025-01-15;VAT F24 PAYMENT;-890.00;EUR;7629.50
2025-01-20;TRANSFER TO SUPPLIER XYZ;-560.00;EUR;7069.50
2025-01-25;EXPENSE REIMBURSEMENT;+120.00;EUR;7189.50 Output: classified transactions
| Date | Description | Amount | Category | Method |
|---|---|---|---|---|
| 2025-01-03 | Salary credit | +€3,200.00 | Operating costs / Salaries | Rule |
| 2025-01-05 | Rent payment | −€1,200.00 | Operating costs / Rent | Rule |
| 2025-01-07 | Enel utility bill | −€180.50 | Operating costs / Utilities | Rule |
| 2025-01-10 | Invoice receipt 2025-001 | +€4,500.00 | Revenue / Service fees | Rule |
| 2025-01-15 | VAT F24 payment | −€890.00 | Taxes / VAT paid | Rule |
| 2025-01-20 | Transfer to supplier XYZ | −€560.00 | Operating costs / Supplies | AI |
| 2025-01-25 | Expense reimbursement | +€120.00 | Revenue / Reimbursements | AI |
Output: monthly P&L
| Line item | Amount |
|---|---|
| Total revenue | +€4,620.00 |
| Operating costs | −€4,940.50 |
| Taxes | −€890.00 |
| Net result | −€1,210.50 |
Bank reconciliation — example
| Bank movement | Accounting entry | Status |
|---|---|---|
| Invoice receipt 001 — €4,500 | Invoice 2025-001 — €4,500 | Matched |
| Transfer to supplier XYZ — €560 | Supplier order XYZ — €560 | Matched |
| Unidentified credit — €230 | — | Review needed |
Export and output formats
| Report type | Available formats |
|---|---|
| Classified transactions export | CSV, Excel, JSON |
| P&L statement | PDF, Excel, interactive view |
| Balance sheet | PDF, Excel |
| Business plan | PDF, Excel with charts |
| Reconciliation report | PDF, CSV |
PongoSID — Financial Accounts Registry
PongoSID is the module dedicated to preparing and submitting reports to the Financial Accounts Registry (Anagrafe dei Rapporti Finanziari) for obligated entities, professional firms, and financial intermediaries.
Who it's for
- Banks and financial intermediaries
- Fiduciaries and trust companies
- Professional firms (accountants, labor consultants)
- Obligated parties under D.P.R. 605/1973 and related regulations
- Operators managing ARF reporting on behalf of clients
Core features
| Feature | Description |
|---|---|
| SID flow generation | XML/txt file generation in the format required by the Italian Revenue Agency |
| Pre-submission checks | Data validation before flow generation to reduce errors |
| Report archive | Ordered history of generated flows, receipts, and verifications |
| Multi-entity management | Reports for multiple obligated entities in one workspace |
| Traceability | Full log of every operation with timestamp and user attribution |
Operational workflow
- Entry or import of financial account data
- Automatic validation of mandatory fields and formats
- Pre-submission review with anomaly flagging
- SID flow generation in the correct format
- Archive of the report with receipt and date
Contact and support
For technical questions, access requests, or platform support, write to:
Response within 1 business day. For urgent issues, include "URGENT" in the email subject.