MVP limitations

Integrations

Limited provider support initially
OAuth/API integrations only for selected platforms
Some providers may support read-only mode first
No guaranteed parity between providers
Accounting exports/push formats may differ between targets

Reconciliation

Primarily period-based reconciliation
Monthly grouping as the default operational mode
Limited heuristic matching initially
No AI/ML-based matching
No advanced FX reconciliation logic initially
Partial/manual reconciliation flows limited
Reconciliation confidence rules relatively simple
Duplicate detection mostly period/export-reference based

Data ingestion

Historical backfill may be limited
Some providers may expose incomplete historical data
Sync delays depend on provider APIs
Rate limits inherited from external systems
Incremental sync behaviour provider-dependent

Export/push

CSV/XLSX/JSON export only initially
PDF/XML not guaranteed
Push idempotency depends partly on provider capabilities
Some accounting systems may not support robust external references
Export payloads immutable after proposal creation

UI/UX

Functional/minimal UI
Limited dashboards/reporting initially
Limited visual analytics
No advanced workflow automation initially
No extensive localisation initially

File workflows

Uploaded file formats initially limited
Parsing quality depends on source consistency
OCR/document extraction not supported initially
File-based reconciliation less automated initially

Infrastructure

Single-region deployment initially
No HA guarantees initially
Backup/retention policies may evolve
Operational limits may apply to very large datasets

General/platform limitations

Accounting semantics

Different accounting systems model financial data differently
Provider-specific behaviours cannot always be normalized perfectly
Some reconciliation cases require human review
Accounting correctness still depends on source data quality

Ads platforms

Ad platforms are not accounting systems
Late adjustments/refunds may alter historical totals
Spend values may shift after reconciliation windows close
Attribution/reporting changes may affect totals retroactively

Reconciliation limits

Perfect automatic reconciliation is not always possible
Ambiguous matches may require manual review
Cross-currency reconciliation introduces unavoidable complexity
Timezone/provider cutoff differences may affect grouping

APIs/providers

Third-party API changes may temporarily break integrations
OAuth tokens/permissions may expire or be revoked
Providers may rate-limit or throttle requests
Some providers expose incomplete metadata

Data consistency

Totals may shrink or expand retroactively
Historical source records may change
External systems may permit manual edits after export
Concurrent edits outside the platform cannot always be detected immediately

File exports/imports

CSV/XLSX formats vary across accounting systems
Manual spreadsheet editing may introduce inconsistencies
Imported files may contain malformed or locale-specific formats

Legal/compliance

Tax/accounting compliance remains jurisdiction-dependent
Platform output should be reviewed before filing/accounting submission
Local bookkeeping regulations vary substantially between countries

Scope boundaries

Not intended to replace ERP/accounting systems
Not intended to replace BI/marketing analytics platforms
Not intended to provide legal/accounting advice
Primarily focused on reconciliation, normalization, aggregation, and operational export workflows