Table 3 "Payment Terms"

Base Application · Microsoft.Foundation.PaymentTerms · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 30023 “APIV2 - Payment Terms” (5 Learn pages), Page 4 “Payment Terms” (1).

Properties

Property	Value
Caption	Payment Terms
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	Code Δ BC29	Code[10]	Specifies a code to identify this set of payment terms.	NotBlank
2	Due Date Calculation Δ BC29	DateFormula	Specifies a formula that determines how to calculate the due date, for example, when you create an invoice.
3	Discount Date Calculation Δ BC29	DateFormula	Specifies the date formula if the payment terms include a possible payment discount.
4	Discount % Δ BC28 Δ BC29	Decimal	Specifies the percentage of the invoice amount (amount including VAT is the default setting) that will constitute a possible payment discount.
5	Description Δ BC29	Text[100]	Specifies an explanation of the payment terms.
6	Calc. Pmt. Disc. on Cr. Memos Δ BC29	Boolean	Specifies that a payment discount, cash discount, cash discount date, and due date are calculated on credit memos with these payment terms.
8	Last Modified Date Time	DateTime	—	not editable
720	Coupled to CRM Δ BC26	Boolean	Coupled to Dataverse caption	obsolete Removed 26.0; #if not CLEANSCHEMA26; not editable

Keys

Key1: Code (clustered)

Events published

OnAfterTranslateDescription(var PaymentTerms: Record "Payment Terms"; Language: Code[10]) (integration)

Procedures

TranslateDescription(var PaymentTerms: Record "Payment Terms"; Language: Code[10])
GetDescriptionInCurrentLanguageFullLength(): Text[100]
UsePaymentDiscount(): Boolean
GetDueDateCalculation(var DueDateCalculation: DateFormula)

Plus 1 local procedures.

Triggers

OnDelete, OnInsert, OnModify, OnRename

Relations

lookup page Page 4 “Payment Terms”

Referenced by

61 fields in 45 objects relate to this table (TableRelation or CalcFormula).

Table 18 “Customer”: Cash Flow Payment Terms Code, Payment Terms Code, Payment Terms Id
Table 23 “Vendor”: Cash Flow Payment Terms Code, Payment Terms Code, Payment Terms Id
Table 1381 “Customer Templ.”: Cash Flow Payment Terms Code, Payment Terms Code
Table 1383 “Vendor Templ.”: Cash Flow Payment Terms Code, Payment Terms Code
Table 36 “Sales Header”: Payment Terms Code, Prepmt. Payment Terms Code
Table 38 “Purchase Header”: Payment Terms Code, Prepmt. Payment Terms Code
Table 5107 “Sales Header Archive”: Payment Terms Code, Prepmt. Payment Terms Code
Table 5109 “Purchase Header Archive”: Payment Terms Code, Prepmt. Payment Terms Code
Table 5475 “Sales Invoice Entity Aggregate”: Payment Terms Code, Payment Terms Id
Table 5495 “Sales Order Entity Buffer”: Payment Terms Code, Payment Terms Id
Table 5496 “Purchase Order Entity Buffer”: Payment Terms Code, Payment Terms Id
Table 5505 “Sales Quote Entity Buffer”: Payment Terms Code, Payment Terms Id
Table 5507 “Sales Cr. Memo Entity Buffer”: Payment Terms Code, Payment Terms Id
Table 5508 “Purch. Cr. Memo Entity Buffer”: Payment Terms Code, Payment Terms Id
Table 1001 “Job Task”: Payment Terms Code
Table 110 “Sales Shipment Header”: Payment Terms Code
Table 112 “Sales Invoice Header”: Payment Terms Code
Table 114 “Sales Cr.Memo Header”: Payment Terms Code
Table 120 “Purch. Rcpt. Header”: Payment Terms Code
Table 122 “Purch. Inv. Header”: Payment Terms Code
Table 124 “Purch. Cr. Memo Hdr.”: Payment Terms Code
Table 167 “Job”: Payment Terms Code
Table 172 “Standard Customer Sales Code”: Payment Terms Code
Table 181 “Posted Gen. Journal Line”: Payment Terms Code
Table 289 “Payment Method”: Direct Debit Pmt. Terms Code
Table 30158 “Shpfy Payment Terms”: Payment Terms Code
Table 462 “Payment Term Translation”: Payment Term
Table 5135 “Job Archive”: Payment Terms Code
Table 5136 “Job Task Archive”: Payment Terms Code
Table 5477 “Purch. Inv. Entity Aggregate”: Payment Terms Code
Table 5900 “Service Header”: Payment Terms Code
Table 5965 “Service Contract Header”: Payment Terms Code
Table 5970 “Filed Service Contract Header”: Payment Terms Code
Table 5990 “Service Shipment Header”: Payment Terms Code
Table 5992 “Service Invoice Header”: Payment Terms Code
Table 5994 “Service Cr.Memo Header”: Payment Terms Code
Table 6010 “Service Header Archive”: Payment Terms Code
Table 6650 “Return Shipment Header”: Payment Terms Code
Table 6660 “Return Receipt Header”: Payment Terms Code
Table 751 “Standard General Journal Line”: Payment Terms Code
Table 8010 “Imported Cust. Sub. Contract”: Payment Terms Code
Table 8052 “Customer Subscription Contract”: Payment Terms Code
Table 8063 “Vendor Subscription Contract”: Payment Terms Code
Table 81 “Gen. Journal Line”: Payment Terms Code
Table 846 “Cash Flow Worksheet Line”: Payment Terms Code

Pages and codeunits on this table

Page 20023 “APIV1 - Payment Terms” (source table)
Page 30023 “APIV2 - Payment Terms” (source table)
Page 4 “Payment Terms” (source table)

Calls

From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.

Codeunit 43 “Language” (1 call: GetDescriptionInCurrentLanguageFullLength → GetUserLanguageCode)
Codeunit 5342 “CRM Synch. Helper” (1 call: OnRename → UpdateCDSOptionMapping)

Countries that replace it

CA, ES, FI, IT, MX, US

Deprecations

field Coupled to CRM: Removed 26.0 (#if not CLEANSCHEMA26), “Replaced by page control Coupled to Dataverse”

Source: AL metadata extracted from the code (names, ids, signatures, properties); no code bodies (D10).

Ask your agent

Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. 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 Terms"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Across versions

Neighbourhood 56 connected objects and pages