Table 980 "Payment Registration Setup"

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

Properties

Property	Value
Caption	Payment Registration Setup
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	User ID	Code[50]	—	DataClassification EndUserIdentifiableInformation
2	Journal Template Name Δ BC28	Code[10]	Specifies the name of the journal template that the Payment Registration window is based on.	TableRelation Table 80 “Gen. Journal Template” (Gen. Journal Template)
3	Journal Batch Name Δ BC28	Code[10]	Specifies the name of the journal batch that the Payment Registration window is based on.	TableRelation Table 232 “Gen. Journal Batch” (“Gen. Journal Batch”.Name where(“Journal Template Name” = field(“Journal Template Name”)))
4	Bal. Account Type Δ BC28	Option	Specifies the type of account that is used as the balancing account for payments. The field is filled according to the selection in the Journal Batch Name field.	OptionCaption: ,G/L Account,Bank Account
5	Bal. Account No. Δ BC28	Code[20]	Specifies the account number that is used as the balancing account for payments.	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	Use this Account as Def. Δ BC28	Boolean	Specifies if the Date Received and the Amount Received fields are automatically filled when you select the Payment Made check box.
7	Auto Fill Date Received Δ BC28	Boolean	Specifies if the Date Received and the Amount Received fields are automatically filled when you select the Payment Made check box.

Keys

Key1: User ID (clustered)

Events published

OnBeforeValidateMandatoryFields(var PaymentRegistrationSetup: Record "Payment Registration Setup"; ShowError: Boolean; var Result: Boolean; var IsHandled: Boolean) + BC26 (integration): Integration event that fires before validating mandatory fields in payment registration setup. Subscribers can handle the validation process themselves and set IsHandled to true to skip the standard validation.

Procedures

GetGLBalAccountType(): Integer: Retrieves the corresponding general journal line balance account type for the setup. Converts the setup’s balance account type to the format used in general journal lines.
ValidateMandatoryFields(ShowError: Boolean): Boolean: Validates that all mandatory fields for payment registration setup are populated. Ensures the setup is complete and ready for use in payment registration operations.

Triggers

OnModify

Relations

Bal. Account No.: TableRelation Table 15 “G/L Account” (conditional)
Journal Batch Name: TableRelation Table 232 “Gen. Journal Batch”
Bal. Account No.: TableRelation Table 270 “Bank Account” (conditional)
Journal Template Name: TableRelation Table 80 “Gen. Journal Template”

Pages and codeunits on this table

Page 980 “Balancing Account Setup” (source table)
Page 982 “Payment Registration Setup” (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 Registration Setup"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.