Apex on Dynamics 365
From quote to general journal, inside Dynamics 365.
Apex quotes from the items and prices in Dynamics 365, turns signed deals into sales orders, bills them as sales invoices, and posts revenue to the general journal. Business Central and Finance and Operations each keep their own documents; Apex writes to them the way your team would.
- Customers
- Items
- Sales prices
- Posted sales invoices
- Customer ledger entries
- Sales orders
- Sales invoices
- Sales credit memos
- General journal
- Customers
- Claimed
- Read before write
- Written
- Confirmed
Two products
Business Central and Finance and Operations, mapped separately.
Dynamics 365 is two different ERPs under one name. Apex maps each on its own terms rather than pretending they are the same.
| Business Central | Finance and Operations | |
|---|---|---|
| Customers | Customer card, with price group and payment terms | Customer accounts per legal entity |
| Prices | Items, sales prices and price lists | Released products and trade agreements |
| Orders | Sales orders | Sales orders per legal entity |
| Invoices | Sales invoices, posted or unposted | Free text or order invoices |
| Corrections | Sales credit memos | Credit notes against the invoice |
| Revenue | General journal lines | General journal, to your main accounts and dimensions |
Dimensions
Your dimensions travel with every line.
Dynamics reporting depends on dimensions. Apex carries them from the contract to the invoice line to the journal, so nothing lands untagged.
Set on the contract
Department, region, product line or project chosen once per contract line, from the values defined in Dynamics.
Kept on the invoice
Each sales invoice line is written with the same dimension values, so revenue reports split as they do today.
Kept on the journal
Recognized revenue posts to the main accounts and dimensions your controller already reports on.
Write-back
Written once, read back, then trusted.
- 01
Claimed
One worker takes each write from the outbox.
- 02
Checked
Apex looks in Dynamics for a document with its reference before writing, so a retry never posts a duplicate.
- 03
Written
Through a dedicated application user with only the permissions you grant.
- 04
Confirmed
Read back and compared. Any difference waits for a person.
Agents propose, people approve
The agent drafts. A person decides.
Agents draft renewal quotes from the contract and Dynamics price changes, and flag invoices whose lines are missing a dimension. They propose; a person approves.
Every agent stops at an approval gate until it has earned its way out of one. Nothing releases cash, commits spend or touches a customer without a person saying so.
Your dataModels that read your data run inside your environment, behind your firewall. No client data reaches a frontier lab.
Start here, keep the foundation
Start with one function. Add the rest without starting over.
Connect Dynamics 365 once. Apex brings customers, items, prices, open invoices and payments into your Ferrata foundation, and every function you add works from that same data. Many teams start with subscription billing in one legal entity and widen from there.
FAQ
Questions, answered plainly.
Which Dynamics 365 products does Apex work with?
Apex is built to connect with Dynamics 365 Business Central and Dynamics 365 Finance and Operations, each through its own APIs. Apex is an independent product and is not certified by or affiliated with Microsoft.
Does Apex post invoices in Business Central?
It writes sales invoices, and you choose whether they stay unposted for review or are posted. Keeping them unposted for the first few billing cycles is a sensible start.
Can Apex handle several legal entities?
Yes. Each customer and contract belongs to a legal entity or company, and Apex writes documents to that entity in its currency and with its accounts.
Are Dynamics dimensions supported?
Yes. Dimension values are set on the contract line and carried to every invoice line and journal entry Apex writes, using the values defined in Dynamics.
What happens if Dynamics is unavailable?
Writes wait in the outbox and nothing is assumed to have landed. When Dynamics is back, each write checks for an existing document first, then posts.
Who sets up the connection?
Ferrata's engineers, working with your IT team, against your own environment. You create the application user and decide its permissions.
Related in Apex
- Subscription billingBilling schedules with phases, amendments, proration and co-terming.View
- InvoicingInvoices calculated in Apex, checked against the PO, posted to your ERP first.View
- CPQConfigure, price and quote from the items and price lists already in your ERP.View
- SAPQuotes, orders, invoices and journals on SAP Business One or S/4HANA.View
- Revenue recognitionRevenue schedules computed from your policy, journals posted to the ERP after review.View
From Ferrata Labs
- The platformThe Brain: retrieval, models and audit inside your own environment.
- Swift, the order agentTurns customer purchase orders into clean sales orders.
- The embedded teamTwo forward-deployed engineers, working with your IT team.
- Book a discovery callThirty minutes on one workflow, and an honest answer on where to start.
Start with Apex, or talk it through first.
Thirty minutes with Ferrata Labs on one workflow. You leave with a view of where Apex fits, and an honest answer if the sequencing is wrong and you should fix something else first.
Your pricing, approval and billing rules are your advantage, and they stay yours. Apex is configured to the way you sell and bill. You are not handing over a playbook or fitting into a template.