Access
ERPNext uses an API key and secret, at no extra cost. You create a dedicated user, give it a role with Read and Report only on the documents Ziira needs, and generate its keys. You can disable the user or regenerate the keys at any time to withdraw access.
What is read
- Warehouses, customers, suppliers, items and users.
- POS Invoices and Sales Invoices (with items and payments), Purchase Invoices, Payment Entries.
- Stock Ledger Entries, Expense Claims and manual Journal Entries.
Only submitted or cancelled documents are read; drafts never are. Cancelled documents are marked so Intelligence can see them. System-generated ledger postings are not read.
What Ziira checks with it
Everything in the standalone check list: sales against payments, cashier habits, overdue customers, supplier price rises, stock adjustments and manual journals, for as much as your data carries.
Limits
- Read daily by default. A first read of a large site makes many requests, since invoices are read one by one for their child tables.
- Set the time zone to match ERPNext's, because ERPNext sends times without a zone.
- Deleted documents are not seen unless cancelled first, which ERPNext requires.
Frequently asked questions
Can the key write to ERPNext?
Ziira only sends read requests. And if you use the custom read-only role described above, ERPNext itself would refuse writes too.