Lunica for Acumatica
Lunica runs beside Acumatica the way your reports do: read from the same data, in the same terms, with nothing posted back without a person.
The cloud ERP with a distribution edition, picked by dealers and distributors who want to own their data.
How Lunica connects to Acumatica.
Lunica reads Acumatica through Acumatica’s OData and REST endpoints, under a role that can only read: the customer record and open items for aging and statements, open purchase orders and receipts for AP matching, the stock item for counts and pricing, quotes and order history for the sales desk. Terms are read as Acumatica has them, so an account on Net 30 ages on that, not on a flat net-30.
Nothing is written to Acumatica by Lunica. Work that belongs in Acumatica goes back as an Acumatica API call or import scenario where one exists, or keyed by your team from what Lunica prepared. Invoice copies and signed tickets come from the files attached to the record, which keeps working exactly as before. Lunica runs on one server inside your network, whether Acumatica is in the cloud or on your own server.
51 workflows for Acumatica.
Every workflow in the directory, written in Acumatica’s terms, with a demo in its formats.
Questions
Does it need a server?
Lunica runs on one server inside your network, whether Acumatica is in the cloud or on your own server, set up and maintained by Lunica. It reads Acumatica through Acumatica’s OData and REST endpoints, under a role that can only read. There is no inbound connection from outside your network.
What does Lunica read in Acumatica?
The customer record, open items and terms, purchase orders and receipts, the stock item, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Acumatica?
Nothing lands in Acumatica without a person. What belongs in Acumatica goes back as an Acumatica API call or import scenario where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in the files attached to the record. Lunica reads them when a workflow needs one and never writes to them.
See it on your Acumatica data.
Thirty minutes. We walk a workflow on Acumatica data, then map it to yours.