Lunica for QuickBooks Enterprise
Lunica runs beside QuickBooks the way your reports do: read from the same data, in the same terms, with nothing posted back without a person.
Intuit’s desktop accounting for smaller yards and shops, often beside a separate point of sale.
How Lunica connects to QuickBooks.
Lunica reads QuickBooks Enterprise through the QuickBooks SDK on the machine that hosts the company file, under a read-only connection: the customer record and open items for aging and statements, open purchase orders and receipts for AP matching, the item list for counts and pricing, quotes and order history for the sales desk. Terms are read as QuickBooks has them, so an account on Net 30 ages on that, not on a flat net-30.
Nothing is written to QuickBooks by Lunica. Work that belongs in QuickBooks goes back as the QuickBooks SDK where it allows, or keyed by your team from what Lunica prepared. Invoice copies and signed tickets come from the attachments on the transaction, which keeps working exactly as before. Lunica runs on one Windows server inside your network, beside the company file.
51 workflows for QuickBooks Enterprise.
Every workflow in the directory, written in QuickBooks’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 company file, set up and maintained by Lunica. It reads QuickBooks Enterprise through the QuickBooks SDK on the machine that hosts the company file, under a read-only connection. There is no inbound connection from outside your network.
What does Lunica read in QuickBooks?
The customer record, open items and terms, purchase orders and receipts, the item list, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.
Can it post to QuickBooks?
Nothing lands in QuickBooks without a person. What belongs in QuickBooks goes back as the QuickBooks SDK where it allows, or keyed by your team from what Lunica prepared.
What about our documents?
Invoice copies and scans keep living in the attachments on the transaction. Lunica reads them when a workflow needs one and never writes to them.
See it on your QuickBooks data.
Thirty minutes. We walk a workflow on QuickBooks data, then map it to yours.