Moneo.lv + Go Fig
Connect Moneo ERP to Go Fig for dimensional accounting, multi-company consolidation, and Baltic-market financial intelligence.
Moneo is the Latvian-market ERP of choice for small and mid-market companies operating in Latvia, Lithuania, and Estonia, spanning accounting, inventory, manufacturing, and payroll under one Baltic-compliant ledger. Its native reporting is oriented toward statutory filing and SAF-T export rather than management segmentation, so dimensional analysis across cost centers, projects, and custom-code combinations usually ends up rebuilt in Excel. Go Fig connects to Moneo via its REST API (or direct read-only SQL against the Moneo database for on-premise deployments), lands every journal entry, invoice line, bill, and inventory movement in the Financial Intelligence Graph at line-item grain, and preserves cost-center, project, and custom-dimension codes on every posting. Multi-company Moneo installations sync through one connection so holding-entity and operating-entity books consolidate against a single canonical chart of accounts, with EUR as the base and original transaction currency preserved. The data lands next to CRM, banking, and payroll sources so Celeste can answer segment-margin, project-profitability, and working-capital questions that statutory Moneo reports cannot assemble alone.
Key facts
- Deployments
- Cloud and on-premise SQL
- Grain
- Journal-line with cost center and project
- Multi-company
- All Moneo entities under one connection
- Currencies
- EUR base plus transaction currency preserved
- Sync cadence
- Hourly incremental, nightly full reindex
What you can do with Moneo.lv data in Go Fig
Dimensional P&L for Baltic operations
Slice revenue, COGS, and OpEx by cost center, project, and custom code combinations without rebuilding reports in Moneo's statutory report writer. Management P&L by branch, practice area, or product line becomes queryable rather than spreadsheet-assembled.
Multi-entity consolidation across Latvia, Lithuania, Estonia
Roll up multiple Moneo companies (and cross-border Baltic entities) with mapped chart of accounts and consistent dimension codes. Intercompany eliminations and FX revaluation express as Go Fig flows rather than month-end spreadsheet work.
Inventory and working-capital visibility
Join Moneo inventory movements, POs, and sales orders to the accounting ledger so inventory on hand, days of stock, and aging by SKU are visible to finance alongside the consolidated P&L, not trapped inside the operations module.
Data available from Moneo.lv
Go Fig extracts and normalizes the following data from your Moneo.lv account:
How to connect Moneo.lv
Provision API or SQL read-only credentials
For Moneo cloud, generate a read-only API key scoped to the companies Go Fig should sync. For on-premise Moneo, create a dedicated database login with SELECT on the Moneo schema and install the Go Fig read-only agent on a Windows host that can reach the database, or configure a VPN tunnel. Use a service identity rather than a named user so key rotation does not affect anyone's login.
Select companies and historical window
Moneo installations typically contain multiple companies per legal entity or brand. Pick which companies Go Fig should sync. Each posting keeps its source company ID so consolidation queries can segment by entity. Default backfill is 3 to 5 years, which covers trend analysis and statutory restatement review.
Map cost centers, projects, and custom dimensions
Moneo uses configurable cost-center and dimension codes on every journal line. Go Fig auto-discovers the dimension structure and exposes each code as a queryable column. Celeste suggests a mapping into management reporting cuts (department, product line, customer segment) if your Moneo codes follow an internal convention. Project grain is preserved so project-level profitability is one query away.
Lock periods and schedule sync cadence
Moneo supports period-lockdown once statutory filings are accepted. Go Fig captures lock status per period and versions records by last_modified timestamps, so edits to a closed period are tagged as change events rather than silently overwriting history. Hourly incremental sync is the default, with nightly full reindex to catch backdated adjustments. On-demand refresh is available for close week.
Authentication: REST API key authentication for Moneo cloud deployments, scoped per company with read-only permissions. On-premise installations are connected via a read-only SQL Server or PostgreSQL login with SELECT on the Moneo database, typically through the Go Fig read-only agent or an IP-allowlisted VPN tunnel so the database is not exposed publicly. Credentials are stored encrypted and rotate independently of operator logins.
Common Questions About Moneo.lv Integration
Does Go Fig handle Moneo's multi-company setups and Baltic cross-border consolidation?
Yes. Moneo installations commonly span multiple companies per tenant, and cross-border groups run separate Moneo instances in Latvia, Lithuania, and Estonia. Go Fig syncs all companies under one connection, preserves source company ID on every record, and supports connecting multiple Moneo instances in one Go Fig tenant for cross-border rollup. Intercompany eliminations and FX revaluation express as Go Fig flows on top of the consolidated ledger.
How are cost centers, projects, and custom dimension codes handled?
Moneo's cost-center and dimension-code model is preserved as first-class columns on every journal line, invoice, and bill. Projects are exposed at posting grain so project P&L (revenue minus direct cost minus allocated overhead) can be assembled directly. Custom codes defined by your team in Moneo show up as typed columns without a separate mapping step, which means segment-margin queries work against the codes your accountants already use.
How does Go Fig handle multi-currency and EUR-base FX revaluation?
Moneo stores transactions in the currency of issue and posts to EUR as the statutory base for Baltic-domiciled entities. Go Fig preserves both the transaction currency and the posted rate, materializes an EUR reporting column, and tags period-end unrealized FX entries separately so consolidated P&L can isolate FX impact from operating variance. Cross-border groups reporting in a non-EUR currency can define a custom reporting currency on top.
What about statutory period locks, SAF-T filings, and restatements?
Moneo supports period lockdown tied to statutory filings (VAT, CIT, SAF-T), and Go Fig respects those locks on every sync. When a period is reopened for a restatement or a late adjustment, Go Fig captures the change, retains prior versions, and tags the record so audit can trace which number was reported on which close date. SAF-T-relevant fields are preserved at the line level so reconstructing a submitted file from Go Fig is straightforward.
What's the sync strategy for on-premise Moneo installations?
Go Fig prefers change-data-capture against the Moneo database where the underlying engine supports it (SQL Server CDC or logical replication in PostgreSQL). Where CDC is not available, hourly snapshot sync with change-detection on last_modified columns is the default. Backfills run during off-hours to avoid contention with accounting users. The Go Fig read-only agent commonly runs on the same Windows host as the Moneo database so there is no network egress, which is helpful for shops that restrict outbound traffic from the finance VLAN.
Ready to connect Moneo.lv?
See how your Moneo.lv data looks in Go Fig with a personalized demo.
Book a Demo