Finly — Infivex

The product

Built by accountants, for accountants

Business Central covers the general ledger extremely well. What it does not always cover is the day-to-day detail an accountant needs in a specific country — the daybooks, the journal layouts, the payment formats and the reporting conventions that make a period close feel routine instead of manual.

Finly fills that gap. It sits inside Business Central as a published extension, so there is no second system to log into and no export-import loop. Your team works on the pages they already know, with the finance functionality added where they expect to find it.

Objects and pages carry a consistent SF suffix, so it is always clear which functionality comes from Finly and which comes from the base product — useful during audits and during upgrades.

The Finly VAT daybook running inside Microsoft Dynamics 365 Business Central — The Finly VAT daybook inside Business Central — a chronological sales and purchase VAT journal, on the same pages your finance team already uses.

Inside the core

What the Core app brings

The country-neutral Core carries the functionality every finance team needs, regardless of where the company is registered.

📈

Reporting

Finance reporting built for the people who sign off the numbers, including the VAT daybook — a chronological sales and purchase VAT journal.

📝

Journals

Journal pages and posting behaviour shaped around accounting practice rather than around generic data entry.

💳

Payments

Payment handling and bank-statement work, so incoming and outgoing money reconciles against the ledger instead of beside it.

🔌

API

API pages that expose Finly's finance data to reporting tools, portals and the rest of your Microsoft estate.

Multi-app architecture

One core, five countries

Customers install Core plus their country app. The core stays identical everywhere; only the thin country layer changes.

🇧🇪 Belgium 🇳🇱 Netherlands 🇫🇷 France 🇸🇬 Singapore 🇵🇭 Philippines

1

Core does the general work

A single country-neutral build carries every shared capability and publishes integration events at the points where local practice differs.

2

The country app subscribes

Each country app compiles against its own country base app, so it can reference local fields directly and supply the local behaviour.

3

Adding a country is additive

A new market means a new thin app and its own subscribers — not a rewrite of the shared code every existing customer runs.

Ask about your country About Business Central

At a glance

Platform: Business Central
Architecture: Core + country app
Countries available: 5
Object range: Registered
Publisher: Infivex Global

Why the split matters

An architecture that survives its second country

Finly originally handled localization with conditional compilation — one codebase with country switches baked into it. That works for one market and just about survives two. It does not scale, and every new country makes the shared code riskier to change.

So we rebuilt it. Localization now happens through integration events: the Core raises an event wherever behaviour is country-specific, and the country app answers it. Country code lives in a country app instead of being conditionally compiled into everyone else's build.

The practical result for you: an upgrade to a market you do not operate in cannot break the app you are running.

How we implement it

What you get

Why finance teams run Finly

No second system. Finly is an extension, not a satellite application. There is no interface to maintain, no nightly sync and no reconciliation between two sets of numbers.
Local practice, not a local translation. Country apps supply real local behaviour, because each one is built against its own country base app rather than approximating it.
Clear provenance. The SF naming on Finly objects makes it obvious what is standard Microsoft and what is ours — which matters when an auditor asks.

Upgrade-safe by construction. Finly extends Business Central through supported extension points, so Microsoft's regular releases stay routine rather than becoming projects.
Registered object range. The suite runs on a Microsoft-assigned registered object range, which is what AppSource requires and what avoids collisions with other extensions you install.
One partner for the whole stack. The people who wrote Finly are the people who implement and support your Business Central — see SLinkHub for the e-invoicing side.

Questions

Finly FAQ

Yes. Finly is an extension for Microsoft Dynamics 365 Business Central, not a standalone accounting package. If you are not on Business Central yet, that has to come first — and since we do not do greenfield ERP rollouts, we would point you to an implementation partner for that step and pick things up once the platform is in place. See how we work with Business Central.

Belgium, the Netherlands, France, Singapore and the Philippines. You install the country-neutral Core plus the app for your country. If your market is not on the list, talk to us — the architecture is designed so that adding a country is a new thin app rather than a change to everyone else's code.

The country apps are separate, thin extensions that all depend on the same Core, which is exactly what makes multi-country setups tractable. The right arrangement depends on how your companies and environments are structured, so it is one of the first things we map during the business process analysis.

The same thing that happens with any well-built extension: we test the release in a sandbox and verify Finly's compatibility before it reaches your production environment. Because Finly uses supported extension points rather than modified base objects, there is nothing to re-merge.

We do. Finly is published by Infivex Global PTE Ltd, and support runs through the same SLA-backed service as the rest of your Business Central environment. See ERP Support.

Finly — accounting depth for Business Central