Automatic account coding — process and rights

Collecting the invoice’s coding input, building the coding proposal, recording the ledger entry and changing the posting type.

Account coding (finance/invoice.makeentry) builds a proposal according to the invoice's typeofcontir type with the contir library and records it as a ledger entry.

Process

  1. Collect the invoice's coding input (getContirInput).
  2. Proposal with the type's adapter (contir->build); the general adapter uses the contir_rule rule store, the type adapters the contir_config parameters.
  3. Recording: finance/entry::saveEntryPayload() (entry header + entry_item lines).
  4. For lease/subscription invoices the validity period is written back (setPassValidity; missing period: error_lease_period).
  5. Warnings are returned, temporary files are cleaned up.

Posting type (savetypeofcontir)

Sets the invoice's typeofcontir field to a value from the shared Company::CONTIR_TYPES list (saveTypeofcontir); an invalid value gives error_contirtype_input.

Data model

Table names carry the installation's own prefix in the database: entry, entry_item, invoice (typeofcontir), contir_rule.

Permissions

EndpointRight
makeentrycore modify + accounting (SUBSCRIPTION) + invoiceInScope; error: error_invoice_id
savetypeofcontircontirtype (legacy permission table only; edit does not replace it) + invoiceInScope

Related topics

Related topics: account coding general ledger permissions
Request consultation Back to home
Topics
permissions (26) outstanding balance (5) account coding (5) invoice (4) general ledger (4) default interest (4) background job (3) financial statement (3) settlement (2) financial document (2) filtering (1) trash (1) invoice image (1) NAV data exchange (1) label (1) analytic breakdown (1) partner repointing (1) invoice import (1) recovery fee (1) account statement (1)