tfacp domains

The printed balance is based on the document date, the date on which the invoice is created.

The printed balance is based on the fiscal period.

The document date of the invoice.

The due date of the invoice.

The initial status if the commission invoice line is created by the Release Commissions/Rebates to Invoicing (tdcms2201m000) session.

The status when the Print Commission Invoices session (see 2.3.3) prints the invoice for the first time.

this is the status when the Print Commission Invoices session (see 2.3.3) prints the invoice again after the original was already printed.

Every receipt results in a separate debit memo.

LN aggregates the receipts on one debit memo as much as possible.

To compress receipts on one debit memo, the receipts must have the same values for the following compression criteria:

• The logistic company.
• The order type.
• The order currency.
• The rate determiner.
• The tax country. The lines of the self-billed debit memo can have different tax codes but the tax country must be the same.
• The business partner of the debit memo.
• The purchase type. The business partner and the purchase type are mandatory compression criteria because together they determine the control account.

These compression criteria are mandatory and you cannot change them.

LN aggregates the receipts on one debit memo as much as possible, based on the same compression criteria as used for Compress (standard). In addition, the order lines for which the receipts are made must all have the same order number.

You can use this option to generate self-billed debit memos per order.

LN aggregates the receipts on one debit memo as much as possible, based on the same compression criteria as used for Compress (standard). In addition, the order lines for which the receipts are made must all belong to the same packing slip.

You can use this option to generate self-billed debit memos per packing slip.

The purchase invoice has no link with purchase orders and is posted to the general ledger without being matched to order/receipts. You can enter transaction lines for the invoice in the Transaction Type session.

The purchase invoice is related to one or more purchase orders that are present in LN. The invoice must go through the purchase invoice matching procedure.

The purchase invoice is related to one or more landed cost lines that are present in LN. The invoice must go through the purchase invoice matching procedure.

The purchase invoice is related to one or more loads or shipments present in Freight . The invoice must go through the purchase invoice matching procedure.

The purchase invoice is related to one or more services procurement orders in Procurement.The invoice must go through the purchase invoice matching procedure.

The procurement card payment is for a requisition entered in Financials or in E-procurement.

The procurement card payment is for disputed payments from previous statements.

The procurement card payment is for any other type of payments.

The invoice lines are related to orders. These lines can be matched to order lines, receipts, consumptions, and landed costs.

The invoice line is related to a cost invoice.

The invoice line is related to landed costs.

LN matches purchase invoices entered in the Purchase Invoice Entry (tfacp2600m000) session with the purchase orders from Procurement .

LN matches purchase invoices entered in the Purchase Invoice Entry (tfacp2600m000) session with the receipts from Warehousing .

LN matches purchase invoices entered in the Purchase Invoice Entry (tfacp2600m000) session with the consumptions.

The purchase invoice can only be matched to orders from purchase offices linked to the financial company in which the invoice is registered and matched.

The invoice can be matched to orders from all the financial companies that share the purchase order data and the warehouse receipt data required for the invoice matching.

Purchase invoice matching is not allowed in the financial company. If you select this option, multicompany purchase invoice matching must be selected for another financial company of the multicompany structure. LN checks for this option during invoice entry. If this option is selected, no purchase order related invoices can be entered. Invoices that were entered before you selected the Not Applicable option can still be matched.

The received purchase invoice is generated manually.

The received purchase invoice is generated using an external device, such as scanning software.

Normal self-billed purchase orders and purchase order schedules.

Triangular invoicing between a warehouse and a sales office or between a purchase office and a sales office.

Bilateral invoicing between two warehouses for automatically generated warehouse transfers.

Bilateral invoicing between two warehouses for manually created warehouse transfers.

Bilateral invoicing between two work centers.

Bilateral invoicing between two warehouses for warehouse transfers that result from Project requirements.

Bilateral invoicing between two warehouses for warehouse transfers that result from Project requirements.

Bilateral invoicing between two warehouses for warehouse transfers that result from Enterprise Planning requirements.

Bilateral invoicing between two warehouses for warehouse transfers that result from Assembly Control requirements in Manufacturing .

The requisition has been registered. If no receipts for the requisition exist, you can still cancel the requisition.

You have canceled the requisition. The requisition cannot be used anymore. For example, you can cancel a requisition if the related purchase was canceled.

The requisition was completely matched with the corresponding procurement card statement lines. The requisition cannot be changed anymore. To make changes, you must first unmatch the requisition.

The requisition has been invoiced.

The invoice is created manually.

The invoice is imported using an external device such as, invoice scanner. The imported invoice is automatically validated.

The received invoice is not validated correctly. The validation errors or unexpected warnings exist for the invoice in the error log.

The received invoice is modified manually. These manual changes are logged and displayed in the received invoice history data.

The invoice is not registered correctly and the open entry is not created for the invoice.

The received invoice is transferred to open entries and cannot be modified.

The received invoice is canceled.

All invoices are printed.

Only the registered invoices are printed.

Only the approved invoices are printed.

Only the matched invoices are printed.

No invoices are printed.

purchase invoice

unallocated payment

standing order

trade note

sales invoice

credit note

currency differences

payment difference

anticipated payments

advance payment

In case of manual entry, you can user may select this relation scenario for supplier invoice which is created as a cost invoice.

In case of manual entry, you can select this relation scenario for supplier invoice which is created as a cost invoice.

In case import reference is specified on the invoice header, this link is created automatically for this scenario. Alternatively, this link is created if the import reference on the invoice header is blank, and the invoice is matched to receipt for which with import reference is specified.

In case import reference is not specified on the invoice header for a cost invoice, you can select this scenario manually.