The internal record behind every sales and purchase document. You will rarely write a rule against this directly — route the specific type instead, such as Invoices or Purchase orders.
If you are looking for invoices or quotations, route those modules. This one is the shared table underneath and routing it affects every document type at once.
What you would route on
Any field on the module can be used, including ones you have added yourself. These are the ones businesses reach for:
| Field | Why you would route on it |
|---|---|
| Document type | Though it is cleaner to route the specific module. |
A worked example
Left to the individual document modules in almost every business. It exists so that a rule can be written against documents generally if you genuinely want one rule for all of them.
Caps and overflow
| Setting | Worth it here? |
|---|---|
| A cap per person | Rarely. |
| An overflow owner | Rarely. |
Nothing stops you setting either — they are offered on every module. It is simply that a daily limit answers a question this module rarely asks.
Where to go next
Something missing or wrong here? Tell us. A question that needed asking usually means a page that needed writing.