PongoFin Documentation

Technical and operational guides for the financial platform, PongoSID, and PongoREI. Calculations, categorization, examples, and architecture — all in one place.

Overview

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

  1. Import — Acquisition of bank statements and financial records from CSV, API, or manual entry
  2. Normalization — Standardization of formats, dates, and descriptions
  3. Classification — Assignment of each transaction to an accounting category
  4. Reconciliation — Cross-referencing bank movements with accounting records
  5. Analysis & Reporting — Generation of financial indicators, forecasts, and reports

Core modules

ModuleFunction
Financial platformReconciliation, P&L, cash flow, business plan
PongoSIDReporting to the Financial Accounts Registry (ARF) for obligated entities
PongoREIREI compliance obligations and reports to financial intermediaries

Supported data sources

SourceFormat
Bank statementsCSV, structured exports
API integrationsReal-time or batch sync
Manual entriesUser-defined transactions
Canonical transaction structure:
transaction {
    date
    amount
    description
    counterpart
    category
}
This ensures consistent processing regardless of the original source or format.
Financial logic

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 criterionDescription
AmountExact or near-exact match of the monetary value
Date proximityTransactions within a configurable time tolerance
Description similarityTextual 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
IndicatorDefinition
Operating marginRevenue − Operating costs
EBITDAEarnings before interest, taxes, depreciation, and amortization
Net profitFinal result after all costs, financial charges, and taxes

Balance sheet

SectionComponents
AssetsCash, receivables, inventory, fixed assets
LiabilitiesPayables, loans, deferred revenue
EquityShare 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

OutputDescription
Revenue projectionExpected future revenue by period
Cost projectionExpected cost evolution
Cash flow forecastProjected liquidity position
Sustainability indicatorsFinancial 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
Transaction classification

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

LevelMethodWhen 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

CategoryTypeMain sub-categories
RevenueIncomeProduct sales, Service fees, Interest income, Reimbursements
Operating costsExpenseRent, Utilities, Salaries, Supplies, Marketing, Software
Taxes & contributionsExpenseVAT paid, Income tax, Social contributions, Withholdings
InvestmentsExpenseEquipment, Software development, Participations
FinancingIn/OutMortgages, Leasing, Credit lines, Loan repayments
Internal transfersNeutralInter-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
Note: User feedback on assigned categories is used to improve model accuracy over time. Every manual correction updates the contextual rules for that business profile.
Practical cases

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

DateDescriptionAmountCategoryMethod
2025-01-03Salary credit+€3,200.00Operating costs / SalariesRule
2025-01-05Rent payment−€1,200.00Operating costs / RentRule
2025-01-07Enel utility bill−€180.50Operating costs / UtilitiesRule
2025-01-10Invoice receipt 2025-001+€4,500.00Revenue / Service feesRule
2025-01-15VAT F24 payment−€890.00Taxes / VAT paidRule
2025-01-20Transfer to supplier XYZ−€560.00Operating costs / SuppliesAI
2025-01-25Expense reimbursement+€120.00Revenue / ReimbursementsAI

Output: monthly P&L

Line itemAmount
Total revenue+€4,620.00
Operating costs−€4,940.50
Taxes−€890.00
Net result−€1,210.50

Bank reconciliation — example

Bank movementAccounting entryStatus
Invoice receipt 001 — €4,500Invoice 2025-001 — €4,500Matched
Transfer to supplier XYZ — €560Supplier order XYZ — €560Matched
Unidentified credit — €230Review needed

Export and output formats

Report typeAvailable formats
Classified transactions exportCSV, Excel, JSON
P&L statementPDF, Excel, interactive view
Balance sheetPDF, Excel
Business planPDF, Excel with charts
Reconciliation reportPDF, CSV
Compliance module

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

FeatureDescription
SID flow generationXML/txt file generation in the format required by the Italian Revenue Agency
Pre-submission checksData validation before flow generation to reduce errors
Report archiveOrdered history of generated flows, receipts, and verifications
Multi-entity managementReports for multiple obligated entities in one workspace
TraceabilityFull log of every operation with timestamp and user attribution

Operational workflow

  1. Entry or import of financial account data
  2. Automatic validation of mandatory fields and formats
  3. Pre-submission review with anomaly flagging
  4. SID flow generation in the correct format
  5. Archive of the report with receipt and date
Support

Contact and support

For technical questions, access requests, or platform support, write to:

Support email
[email protected]

Response within 1 business day. For urgent issues, include "URGENT" in the email subject.