Core Operations

This section documents the day-to-day operational domains of the platform — the modules a PYME uses constantly to sell, buy, hold inventory, manage contacts, and post to the books. Each page is a frontend handoff: code location, key models, the GraphQL surface at a glance, and the cross-cutting integrations to be aware of.

What's covered

Domain	Code	What it does
Sales Cycle	quotes/, orders/, invoices/, receipts/, payments/, credits/	Quote → Order → Invoice → Receipt → Payment, plus customer credit notes
Purchasing Cycle	purchase_requisitions/, purchase_orders/, invoices/ (supplier), expenses/, credits/ (supplier)	PR → PO → Receive → Supplier Invoice → Pay, plus supplier credit notes and one-off expenses
Items & Inventory	items/, inventories/	Catalog, categories, UoMs, alternative unit prices, client-specific discounts, stock tracking and manual adjustments
Contacts	clients/, suppliers/, factories/, salespersons/, addresses/	Customer / supplier / factory / sales rep masters with contacts and addresses
Chart of Accounts & Journals	accounts/, journals/, ledger/	Account tree, manual JEs, the single posting service that writes the GL
Approvals & Sequences	approval_configs/, auto_sequences/	Threshold-based approval routing and per-document-type numbering
Reports & Metrics	reports/, metrics/, home/	Built-in operational reports, landing-page metrics, the home dashboard
RBAC & Users	rbac/, users/, billing/	Path permissions, role/user assignment, billing/subscription
Integrations & Communications	whatsapp/, emails/, chats/, files/, signatures/, pdf/, pdf_templates/, webhooks/, integrations/	WhatsApp + email send, AI chat, file storage, e-signatures, PDF generation, outgoing webhooks

Cross-cutting concepts

• All financial activity converges on LedgerService. Invoices, receipts, payments, expenses, credit notes, payroll, fixed-asset depreciation, recurring journals, and opening balances all post through one service. That service applies the period-close guard and writes a hash-chained row into ledger_audit_logs. See Period Close and Ledger Audit Trail.
• Document numbering is centralised in auto_sequences/. Every numbered document (quote, order, invoice, receipt, payment, PR, PO, JE, credit) draws from a per-tenant sequence so numbers are gapless and concurrency-safe.
• Approvals for high-impact documents (purchase requisitions today, more later) route through approval_configs/.
• DGI/PAC lifts customer invoices and credit notes into Panama's electronic invoicing system — see PAC → Overview.
• AI tabular import lives under each domain's tabular/ package and ingests CSV/XLSX into the corresponding domain.