Skip to content

Lunica for Dynamics 365 Business Central

Lunica runs beside Business Central the way your reports do: read from the same data, in the same terms, with nothing posted back without a person.

Microsoft’s mid-market ERP, common at dealers who left a legacy LBM system for general accounting.

How Lunica connects to Business Central.

Lunica reads Dynamics 365 Business Central through Business Central’s API, under a user that can only read: the customer card and open items for aging and statements, open purchase orders and receipts for AP matching, the item card for counts and pricing, quotes and order history for the sales desk. Terms are read as Business Central has them, so an account on 30 EOM ages on that, not on a flat net-30.

Nothing is written to Business Central by Lunica. Work that belongs in Business Central goes back as a Business Central API call or import where one exists, or keyed by your team from what Lunica prepared. Invoice copies and signed tickets come from the attachments on the record, which keeps working exactly as before. Lunica runs on one server inside your network, whether Business Central is in Microsoft’s cloud or on your own server.

51 workflows for Dynamics 365 Business Central.

Every workflow in the directory, written in Business Central’s terms, with a demo in its formats.

Questions

Does it need a server?

Lunica runs on one server inside your network, whether Business Central is in Microsoft’s cloud or on your own server, set up and maintained by Lunica. It reads Dynamics 365 Business Central through Business Central’s API, under a user that can only read. There is no inbound connection from outside your network.

What does Lunica read in Business Central?

The customer card, open items and terms, purchase orders and receipts, the item card, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.

Can it post to Business Central?

Nothing lands in Business Central without a person. What belongs in Business Central goes back as a Business Central API call or import where one exists, or keyed by your team from what Lunica prepared.

What about our documents?

Invoice copies and scans keep living in the attachments on the record. Lunica reads them when a workflow needs one and never writes to them.

See it on your Business Central data.

Thirty minutes. We walk a workflow on Business Central data, then map it to yours.