Table 686 "Payment Practice Data"
PaymentPractices · Microsoft.Finance.Analysis
Across versions
- BC23-28not present
- BC29-30present
Neighbourhood 3 connected objects and pages
PaymentPractices · Microsoft.Finance.Analysis · BC29-30 · source at ea08af5e · facts from BC29
Learn documents this table through its pages: Page 686 “Payment Practice Data List” (1 Learn page).
Properties
| Property | Value |
|---|---|
| DataClassification | CustomerContent |
Fields
Explanation: the field’s ToolTip in the code; without one, the ToolTip of a page control bound to the field (marked via the page); without that, its Caption (marked caption) when that differs from the name.
| No. | Name | Type | Explanation | Notes |
|---|---|---|---|---|
| 1 | Header No. | Integer | — | |
| 2 | Invoice Entry No. | Integer | Specifies the invoice entry number that is the source for this entry. via Page 686 “Payment Practice Data List” | |
| 3 | Source Type | Enum “Paym. Prac. Header Type” | — | enum Enum 686 “Paym. Prac. Header Type” |
| 4 | Pmt. Entry No. | Integer | Specifies the closing payment entry number that is associated with the source invoice entry, if any was applied. via Page 686 “Payment Practice Data List” | |
| 5 | Invoice Posting Date | Date | Specifies the posting date of the invoice entry that is the source for this entry. via Page 686 “Payment Practice Data List” | |
| 6 | Invoice Received Date | Date | Specifies the date the invoice was received that is the source for this buffer entry. If empty, the posting date is used. via Page 686 “Payment Practice Data List” | |
| 7 | Due Date | Date | Specifies the due date of the invoice entry that is the source for this entry. via Page 686 “Payment Practice Data List” | |
| 8 | Pmt. Posting Date | Date | Specifies the posting date of the payment entry that is associated with the source invoice entry, if any was applied. via Page 686 “Payment Practice Data List” | |
| 9 | Invoice Is Open | Boolean | Specifies whether the invoice entry that is the source for this entry is open. via Page 686 “Payment Practice Data List” | |
| 10 | Invoice Doc. No. | Code[20] | — | |
| 11 | CV No. | Code[20] | — | |
| 12 | Inv. External Document No. | Code[35] | — | |
| 13 | Company Size Code | Code[20] | Specifies the company size code of the vendor that is the source for this entry. via Page 686 “Payment Practice Data List” | |
| 14 | Agreed Payment Days | Integer | Specifies the number of days that was the agreed period for payment for the invoice. via Page 686 “Payment Practice Data List” | |
| 15 | Actual Payment Days | Integer | Specifies the number of days that was the actual period for payment for the invoice. via Page 686 “Payment Practice Data List” | |
| 16 | Invoice Amount | Decimal | Specifies the amount of the invoice entry that is the source for this entry. via Page 686 “Payment Practice Data List” | |
| 20 | Dispute Status | Code[10] | Specifies whether the invoice is flagged as disputed. Copied from the vendor ledger entry during data generation. | TableRelation Table 142 “Dispute Status” (Dispute Status) |
| 21 | Overdue Due to Dispute | Boolean | Specifies whether the invoice is overdue due to a dispute. This field is automatically calculated based on whether the invoice is overdue and has a dispute status. | not editable |
| 22 | SCF Payment Date | Date | Specifies when the supplier received payment under a supply chain finance arrangement. When filled in, replaces the payment posting date for calculating actual payment days. |
Keys
- Key1: Header No., Invoice Entry No., Source Type (clustered)
- Key2: Pmt. Posting Date
Procedures
CopyFromInvoiceVendLedgEntry(VendorLedgerEntry: Record "Vendor Ledger Entry")CopyFromInvoiceCustLedgEntry(CustLedgerEntry: Record "Cust. Ledger Entry")SetFilterForLine(PaymentPracticeLine: Record "Payment Practice Line")
Relations
- Dispute Status: TableRelation Table 142 “Dispute Status”
Pages and codeunits on this table
- Page 686 “Payment Practice Data List” (source table)
Ask your agent
Procedure bodies are not stored here (D10). For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "table", object_name: "Payment Practice Data"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.