Table 289 "Payment Method"

Base Application · Microsoft.Bank.BankAccount · BC23-30 · source at ea08af5e · facts from BC29

Learn documents this table through its pages: Page 30020 “APIV2 - Payment Methods” (5 Learn pages), Page 427 “Payment Methods” (2).

Properties

Property	Value
Caption	Payment Method
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 Δ BC28	Code[10]	Specifies a code to identify this payment method.	NotBlank
2	Description Δ BC28	Text[100]	Specifies a text that describes the payment method.
3	Bal. Account Type Δ BC28	enum “Payment Balance Account Type”	Specifies the type of account that a balancing entry is posted to, such as BANK for a cash account.	enum Enum 96 “Payment Balance Account Type”
4	Bal. Account No. Δ BC28	Code[20]	Specifies the number of the general ledger, customer, vendor, or bank account that the balancing entry of a posted sales or purchase document is posted to, such as a cash account for cash purchases. Please note Payment Method is not considered when creating document entries through journals.	TableRelation Table 15 “G/L Account”, Table 270 “Bank Account” (if (“Bal. Account Type” = const(“G/L Account”)) “G/L Account” else if (“Bal. Account Type” = const(“Bank Account”)) “Bank Account”)
6	Direct Debit Δ BC28	Boolean	Specifies if the payment method is used for direct debit collection.
7	Direct Debit Pmt. Terms Code Δ BC28	Code[10]	Specifies the payment terms that will be used when the payment method is used for direct debit collection.	TableRelation Table 3 “Payment Terms” (Payment Terms)
8	Pmt. Export Line Definition Δ BC28	Code[20]	Specifies the data exchange definition in the Data Exchange Framework that is used to export payments.
11	Last Modified Date Time	DateTime	—	not editable

Keys

Key1: Code (clustered)

Events published

OnBeforeCheckGLAcc(var PaymentMethod: Record "Payment Method"; CurrFieldNo: Integer; AccNo: Code[20]; var IsHandled: Boolean) (integration): Integration event raised before validating G/L account for payment method. Enables custom validation logic for payment method account configuration.

Procedures

TranslateDescription(Language: Code[10]): Updates payment method description with translated text for specified language.
GetDescriptionInCurrentLanguage(): Text[100]: Retrieves payment method description in the current user’s language.

Plus 1 local procedures.

Triggers

OnDelete, OnInsert, OnModify, OnRename

Relations

drill-down page Page 427 “Payment Methods”
lookup page Page 427 “Payment Methods”
Bal. Account No.: TableRelation Table 15 “G/L Account” (conditional)
Bal. Account No.: TableRelation Table 270 “Bank Account” (conditional)
Direct Debit Pmt. Terms Code: TableRelation Table 3 “Payment Terms”

Referenced by

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

Table 18 “Customer”: Payment Method Code, Payment Method Id
Table 181 “Posted Gen. Journal Line”: Payment Method Code, Payment Method Id
Table 23 “Vendor”: Payment Method Code, Payment Method Id
Table 81 “Gen. Journal Line”: Payment Method Code, Payment Method Id
Table 1001 “Job Task”: Payment Method Code
Table 110 “Sales Shipment Header”: Payment Method Code
Table 112 “Sales Invoice Header”: Payment Method Code
Table 114 “Sales Cr.Memo Header”: Payment Method Code
Table 120 “Purch. Rcpt. Header”: Payment Method Code
Table 122 “Purch. Inv. Header”: Payment Method Code
Table 124 “Purch. Cr. Memo Hdr.”: Payment Method Code
Table 1381 “Customer Templ.”: Payment Method Code
Table 1383 “Vendor Templ.”: Payment Method Code
Table 167 “Job”: Payment Method Code
Table 172 “Standard Customer Sales Code”: Payment Method Code
Table 21 “Cust. Ledger Entry”: Payment Method Code
Table 25 “Vendor Ledger Entry”: Payment Method Code
Table 30118 “Shpfy Order Header”: Payment Method Code
Table 30134 “Shpfy Payment Method Mapping”: Payment Method Code
Table 36 “Sales Header”: Payment Method Code
Table 38 “Purchase Header”: Payment Method Code
Table 466 “Payment Method Translation”: Payment Method Code
Table 4812 “Intrastat Report Line”: Payment Method
Table 5107 “Sales Header Archive”: Payment Method Code
Table 5109 “Purchase Header Archive”: Payment Method Code
Table 5135 “Job Archive”: Payment Method Code
Table 5136 “Job Task Archive”: Payment Method Code
Table 5222 “Employee Ledger Entry”: Payment Method Code
Table 5900 “Service Header”: Payment Method Code
Table 5965 “Service Contract Header”: Payment Method Code
Table 5970 “Filed Service Contract Header”: Payment Method Code
Table 5990 “Service Shipment Header”: Payment Method Code
Table 5992 “Service Invoice Header”: Payment Method Code
Table 5994 “Service Cr.Memo Header”: Payment Method Code
Table 6010 “Service Header Archive”: Payment Method Code
Table 6650 “Return Shipment Header”: Payment Method Code
Table 6660 “Return Receipt Header”: Payment Method Code
Table 8010 “Imported Cust. Sub. Contract”: Payment Method Code
Table 8052 “Customer Subscription Contract”: Payment Method Code
Table 8063 “Vendor Subscription Contract”: Payment Method Code
Table extension 5283 “Audit File Export Setup SAF-T”: Default Payment Method Code

Pages and codeunits on this table

Page 20020 “APIV1 - Payment Methods” (source table)
Page 30020 “APIV2 - Payment Methods” (source table)
Page 427 “Payment Methods” (source table)

Extended by

Table extension 20104 “AMC Bank Paym. Method Ext”

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: GetDescriptionInCurrentLanguage → GetUserLanguageCode)

Recent changes

2026-10-02 #8429 E-Document DE: map Payment Method to PEPPOL payment means codes, add SEPA Direct Debit export support (main, BC30, feature)

Countries that replace it

CA, ES, IT, MX, US

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 Method"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.

Across versions

Neighbourhood 56 connected objects and pages