accounting scheme

A scheme of accounts to which the results of certain events are posted. The accounting scheme consists of ledger accounts, structured in a parent-child hierarchy.

account matching authorization scheme

A company-specific set of authorization restrictions that can be linked to account matching users.

account matching properties

A company-specific set of properties with matching information linked to a ledger account.

advance payment/receipt

A paid or received amount, which cannot be allocated to an invoice or any other document. After an invoice has been created, the advance payment or receipt can be allocated to it. Unlike an unallocated payment/receipt, you can calculate tax on a advance payment/receipt.

anticipated payment

A payment that is not entirely executed yet, or is on its way to be executed.

These anticipated payments can be created:

  • Automatically, for example when a check is generated by the automatic payment procedure.
  • Manually, for example, when a check is written.

anticipated receipt

A receipt that is not completed yet.

Anticipated receipts can be created:

  • Automatically, for example, in case of direct debit.
  • Manually, for example, when a check is entered.

automatic account matching criteria code

A list of fields that determines the matching criteria, including a priority sequence in order to match on different combinations of fields.

automatic account matching criteria set

A company-specific set of priorities with matching criteria that can be linked to an account matching priority to enable automatic matching.

bank reference

A unique number used by the banks to reference each invoice. The bank reference number can be a string of 20 or more digits, composed in such a way that a number check can be performed to check its validity.

In some countries, the bank reference number is a critical component of payment and receipt transactions, especially if payment slips are used. If bank reference numbers are used, the bank reference number must appear on the invoice document, on the payment slip if applicable, and on the payment document.

cash flow reason

An indication of the kind of cash transaction. Transactions to which you link a reason code of the Cash Flow type are included in the cash flow statement, sorted by cash flow reason.

cash flow reason group

A way to group cash flow reasons on the cash flow statement. On the cash flow statement, LN prints the subtotals for each cash flow reason group.

chart of accounts

A hierarchical structure of ledger accounts and dimensions.

To support dual accounting, the chart of accounts can consist of a structure of statutory accounts for fiscal reporting purposes and complementary accounts used for management reporting.

clearing accounts

A temporary account containing costs or amounts that must be transferred to another account.

complementary account

A ledger account that you can use for the amounts that are complementary to the amounts in the statutory accounts. For example, you can link a statutory account and a complementary account to a parent account. If you print the Management report based on the parent accounts, on the report LN adds the amounts in the complementary account to the amount in the statutory accounts.

dimension

Analysis account for ledger accounts to get a vertical view on ledger accounts. Dimensions are used to specify ledger account information.

dimension type

One of up to twelve available analysis account bases for ledger accounts.

financial company

A company that is used for posting financial data in Financials. You can link one or more enterprise units from multiple logistic companies to one financial company.

group company

A financial company to which a number of other financial companies is linked.

A group company is used to centrally:

  • Process the corporate and administrative accounting
  • Accumulate data for consolidated financial reporting from the group's financial companies
  • Perform central cash management processes such as payments and direct debit

integration mapping scheme

A scheme that defines the ledger accounts and dimensions to which the integration transactions are posted.

integration transaction

A financial transaction that is generated through LN packages other than Financials. For each logistic transaction that must be reflected in Financials, LN generates an integration transaction, for example, Purchase/Receipt, Production/WIP Transfer, and Project/Costs of Goods Sold. LN posts the integration transaction to the ledger accounts and dimensions defined in the integration mapping scheme.

intercompany settlement transaction

The automatic postings in one financial company to intercompany billing and clearing accounts instead of invoices generated for sales/purchase transactions between the entities of two logistic companies.

You must define the logistic companies as affiliated-company business partners and you must indicate that intercompany settlements can be performed for the business partner.

intercompany transactions

The transactions created between financial companies which belong to the same financial group.

interim account

An account between two actions or events containing costs or amounts that must be transferred to another account.

ledger account

A register used to record financial transactions and to accumulate the values of the transactions for reporting and analysis. The ledger accounts classify the transactions into categories such as revenues, expenses, assets, and liabilities.

account

ledger account matching scheme

A set of ledger accounts for which a user can perform account matching.

open invoice

Unpaid invoices.

open entry

outstanding invoice

parent/child relation

Generic term to indicate parent and child elements in any multilevel structure. For example, this relationship is used for companies, financial accounts, dimensions, product families, customers, suppliers.

parent-child structures

A hierarchical structure for dimensions and accounts. Multiple child elements can be linked to a parent element. It is used for subtotaling and reports and inquiries. To determine the level in the hierarchy, dimensions and accounts have a sublevel.

payment slip

Optically readable document attached to an invoice, which can be sent to the bank to make the payments for the invoice. The supplier's bank account number, the invoice amount, and an invoice reference number are preprinted on the payment slip. If a payment slip is attached to an invoice, the payment slip is created and printed together with the invoice.

protocol number

A unique sequence number for each document.

In some countries, for example Italy, it is required to report in a fixed sequence to the local authorities.

Predefined protocol numbers can be automatically assigned to finalized transactions.

rate determiner

The method to decide which date is used to determine the exchange rates.

During the composing process, all amounts in foreign currencies are converted to the home currency, based on the determined exchange rate.

statutory account

A ledger account used for official accounting purposes according to legal requirements.

sublevel

A number that indicates the level of a ledger account or a dimension in the hierarchical structure of accounts and dimensions. A low number corresponds with a low sublevel. Ledger accounts can have sublevels 0 through 99. Dimensions can have levels 0 through 9.

Transactions can only be posted to accounts and dimensions which have a sublevel zero. All amounts and quantities on the sublevels 1 and higher are aggregated from lower sublevels.

suspense account

An account that records operations that cannot be posted definitely to an account.

However, such accounts must not appear on the balance sheet. For example:

  • When bank reconciliations bring the balance of the company's account into line with that of the bank, the unidentified movements listed on the bank statements are posted to a suspense account

Note: Unidentified movements can, for example, be customer receipts.

transaction category

A way to categorize transaction types, for example journal vouchers, recurring/reverse journals, purchase invoices, and sales invoices. The category defines how to process a transaction linked to the selected transaction type.

transaction template

A set of entries created (generated and repeated) to distribute a transaction across a number of ledger accounts and dimensions. For example, you can distribute the recurring purchase invoices for general supplies across a number of departments or work centers. The set of transactions is automatically linked to the document.

posting data schedule

transaction scheme

transaction schedule

transaction type

A user-defined three-position code used to identify documents. The series linked to the transaction type give documents the sequence number.

unallocated payment/receipt

A payment/receipt, appearing on a bank statement, which cannot be allocated to an invoice or other document. This payment can be registered as unallocated. An unallocated payment/receipt can be allocated to invoices later.