NetSuite
Subsidiary-aware journals, posted clean.
ERP
ERP · Two-way sync · Live since 2024 · About 25 minutes to connect
Finly writes into Dynamics 365 Finance with the main account and every financial dimension already set, and queues anything the period will not take. A legal entity connects on its own, so a group's books never bleed into each other.
What syncs
Both directions, on every sync.Nothing here is a nightly batch —a record that changes at 14:02 is in the ledger before you look at it.
Connected


Every batch arrives dimensioned the way Dynamics 365 expects —entity, cost centre and project already on the line —so the posting run clears without a correcting journal behind it.
Before you start
You need a Dynamics 365 environment with API access enabled and a user holding rights to post journals, plus a Finly plan on Scale or above.One Dynamics 365 company maps to one Finly entity;a group consolidating several connects each in turn, which is what keeps the eliminations clean and the audit trail per-book.
Two things it deliberately will not do.It will not touch master data —Finly reads your chart, your dimensions and your suppliers and never writes them back, so a mapping change is always yours to make.And it will not post into a closed period —entries queue in Finly until the period reopens, rather than landing in a suspense account for someone to find later.
Related
Get started
Book a 30-minute demo and we'll run your own last month through a sandbox, so you can see the close before you commit to anything.