Lunica for Sage 100
Lunica runs beside Sage 100 the way your reports do: read from the same data, in the same terms, with nothing posted back without a person.
Sage’s mid-market accounting and distribution system, common at single-location dealers and manufacturers.
How Lunica connects to Sage 100.
Lunica reads Sage 100 through Sage 100’s ODBC driver, under a user that can only read: the customer maintenance record and open items for aging and statements, open purchase orders and receipts for AP matching, the item record for counts and pricing, quotes and order history for the sales desk. Terms are read as Sage 100 has them, so an account on Net 30 ages on that, not on a flat net-30.
Nothing is written to Sage 100 by Lunica. Work that belongs in Sage 100 goes back as a Sage 100 import or Visual Integrator job where one exists, or keyed by your team from what Lunica prepared. Invoice copies and signed tickets come from Paperless Office, which keeps working exactly as before. Lunica runs on one Windows server inside your network, beside the Sage 100 server.
51 workflows for Sage 100.
Every workflow in the directory, written in Sage 100’s terms, with a demo in its formats.
Questions
Does it need a server?
Lunica runs on one Windows server inside your network, beside the Sage 100 server, set up and maintained by Lunica. It reads Sage 100 through Sage 100’s ODBC driver, under a user that can only read. There is no inbound connection from outside your network.
What does Lunica read in Sage 100?
The customer maintenance record, open items and terms, purchase orders and receipts, the item record, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to Sage 100?
Nothing lands in Sage 100 without a person. What belongs in Sage 100 goes back as a Sage 100 import or Visual Integrator job where one exists, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in Paperless Office. Lunica reads them when a workflow needs one and never writes to them.
See it on your Sage 100 data.
Thirty minutes. We walk a workflow on Sage 100 data, then map it to yours.