Encyclopedia

What the objects actually mean

Not “how to create a sales invoice in ERPNext” — that dates the moment the UI changes. What an invoice is: the obligation it creates, the rules that must hold, what goes wrong in real businesses, and only then how ERPNext models it.

These are business architecture questions, not product questions. ERPNext is one implementation of the answer. Machine-readable index for anyone building on top of this.

More coming, one chain at a time

The order-to-cash chain first — lead, opportunity, quotation, sales order, delivery note, invoice, payment, credit note — then procure-to-pay, master data, inventory and the entity/compliance chain. Published in chains rather than alphabetically, because a half-built graph teaches nobody: an invoice only means something next to the order before it and the payment after it.