Finance Reference Data (FIN)
The fin submodule of com owns the cross-cutting financial reference data used by sales, purchasing, and accounting flows: cost components, credit ratings, terms of payment, and terms of invoice. It exposes only one cross-module lookup — findTermsOfPaymentByCodeMandatory — and otherwise provides standard CRUD pages for administrators to maintain the entries.
Concepts
Cost ComponentA named bucket of cost (for example "material", "labour", "freight"). Used by costing/pricing logic to attribute amounts to a category.
Credit RatingA named risk classification attached to partners. Each rating may carry a UI warning style so high-risk customers stand out in the UI.
Terms of PaymentA named payment-due policy: how many days after invoice the payment is due, and whether advance payment is required.
Terms of InvoiceA named invoicing policy: whether invoices are combined per period and how often invoices are emitted.
Entities
Cost Component (CostComponent)
A named cost bucket.
| Field | Description |
|---|---|
| Business key (up to 8 characters). |
| Human-readable name. |
Credit Rating (CreditRating)
A named credit-risk classification.
| Field | Description |
|---|---|
| Business key (up to 3 characters). |
| Human-readable name. |
| Optional |
Terms of Payment (TermsOfPayment)
A named payment-due policy.
| Field | Description |
|---|---|
| Business key (up to 3 characters). |
| Human-readable name. |
| Optional number of days after invoice when payment is due. |
| Whether the policy requires payment in advance. Default |
Terms of Invoice (TermsOfInvoice)
A named invoicing policy.
| Field | Description |
|---|---|
| Business key (up to 3 characters). |
| Human-readable name. |
| Whether multiple deliveries are combined onto a single invoice for the period. |
| How often invoices are emitted — see Invoice Frequencies below. |
Invoice Frequencies (InvoiceFrequency)
| Code | Name | Meaning |
|---|---|---|
| Direct | Each delivery is invoiced immediately. |
| Weekly | Deliveries in a week are invoiced together. |
| Monthly | Deliveries in a month are invoiced together. |
Functionality
Mandatory terms-of-payment lookup
TermsOfPaymentReaderService exposes both an optional and a mandatory lookup of TermsOfPayment by code. The mandatory variant raises a business exception when the code does not exist; this is the seam other modules use when a missing terms-of-payment value should fail loudly. All other entities are read directly through their generated readers.
Public API
COM_FIN_QueryApi
Read-side facade.
| Method | Description |
|---|---|
| Terms of payment by code; raises a business exception if not found. |
COM_FIN_CommandApi
This submodule does not provide a command API class. Cost components, credit ratings, and the two terms entities are maintained through their default CRUD pages.
ViewModel actions
The submodule defines view models for the four entities but does not declare any custom UI actions.