🏭 Business process wiki

Which processes the system models from the point of view of an analyst and a process owner. This is "what happens in the business"; the metadata of the objects themselves is in docs/reference/business-layer/.

← Wiki root

Contents#

Getting started#

• 📊 Register report views
• ⚙️ Document commands and subtypes
• 🗺️ Overview and the map of modules
• 🛡️ Sign-in protection
• Process map
• Product direction: Global Core + Localization

Sales#

• 📊 ABC/XYZ
• 🎁 Loyalty
• 📱 Mobile client
• 🔄 Sales and purchasing (the process)
• 🧾 Sales order
• 🚫 Sales order rejection
• 🧾 Sales realization
• 🚚 Delivery trips
• 📍 Field visits and orders

Purchasing#

• 📥 Auto-receipt on purchase order — business rule
• 🧾 Supplier invoice — booking only what the supplier billed differently
• 📑 Supplier contracts

Warehouse#

• 🏬 Stores and stock (the process)
• 🏷️ Item characteristics and item groups

Production & costing#

• 🧮 Cost of stock and of sales
• 🔩 Production routing — settings and capacity rules

Finance & tax#

• 📒 Obligations, payments and the general ledger (the process)
• 💵 Cash desks, bank accounts and money movements
• 💱 Exchange differences
• ⏰ Payment due date
• 🏦 Accounting settings — what the posting profile controls
• 🧾 Tax return and payment
• 🧾 E-invoice envelope

HR#

• 🕒 Timesheet
• 🛡️ Social insurance

Localizations#

• 🌍 Localizations
• 🧾 ZATCA e-invoice
• ⚖️ Saudi Arabian localization
• 🪪 Diia — what is not there, and why it is separate
• 🧾 Unified Register of Tax Invoices (ЄРПН) tax invoice
• 🔌 M.E.Doc at a customer
• 🏦 PrivatBank Autoclient at a customer
• ⚖️ The Ukrainian localization

The principle#

A business process in ZuloOne is documents that move registers (balances, accounting) by the rules of scripts, on top of dictionaries (master data). One engine serves any domain — the only difference is the metadata.

The user does not choose the subtype on the card once the record is saved. The state transition, and the postings it runs, are a document command — a Post, Confirm or Pay button. The catalogue of buttons is Document commands and subtypes.

What to look for where#

There are two reference sources, and neither is "the details of" the other.

This wiki describes processes, invariants and the reasons behind decisions. Why a contour is built the way it is, what cannot be done and why, which trap cost what. It reads front to back.

docs/reference/business-layer/ is the object level. It contains a module's object map, fields, EDTs, number sequences, model.json and menu. Read it when you need an exact name.

The names in both places are checked by tools/check-doc-names.mjs on every CI run.

• Mobile client and field sales — visits, routes, the GPS track, offline sync.

• Product direction — where the business layer is heading.

• Setting up a new customer