Lunica for NetSuite
Lunica runs beside NetSuite the way your reports do: read from the same data, in the same terms, with nothing posted back without a person.
Oracle’s cloud ERP, run by larger distributors and multi-location dealers.
How Lunica connects to NetSuite.
Lunica reads NetSuite through SuiteQL and the REST API, 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 item record for counts and pricing, quotes and order history for the sales desk. Terms are read as NetSuite has them, so an account on Net 30 ages on that, not on a flat net-30.
Nothing is written to NetSuite by Lunica. Work that belongs in NetSuite goes back as a NetSuite API call or CSV import where one exists, or keyed by your team from what Lunica prepared. Invoice copies and signed tickets come from the File Cabinet, which keeps working exactly as before. Lunica runs on one server inside your network that connects out to your NetSuite account.
51 workflows for NetSuite.
Every workflow in the directory, written in NetSuite’s terms, with a demo in its formats.
Questions
Does it need a server?
Lunica runs on one server inside your network that connects out to your NetSuite account, set up and maintained by Lunica. It reads NetSuite through SuiteQL and the REST API, under a role that can only read. There is no inbound connection from outside your network.
What does Lunica read in NetSuite?
The customer 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 NetSuite?
Nothing lands in NetSuite without a person. What belongs in NetSuite goes back as a NetSuite API call or CSV 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 File Cabinet. Lunica reads them when a workflow needs one and never writes to them.
See it on your NetSuite data.
Thirty minutes. We walk a workflow on NetSuite data, then map it to yours.