Page 434 "Reminder"

Base Application · Microsoft.Sales.Reminder · BC23-30 · source at ea08af5e · facts from BC29

Properties

Property	Value
Caption	Reminder
SourceTable	Reminder Header
PageType	Document

Fields on this page

Layout controls in source order, grouped by the container they sit in. Shows: the table field a control is bound to (or its expression as written); ToolTip: the control’s own, else the bound field’s (marked).

Group	Control	Shows	ToolTip
General	No.	No.	Specifies the number of the involved entry or record, according to the specified number series. from the table field
	Customer No.	Customer No.	Specifies the number of the customer you want to post a reminder for. from the table field
	Name	Name	Specifies the name of the customer the reminder is for. from the table field
	Address	Address	Specifies the address of the customer the reminder is for. from the table field
	Address 2	Address 2	Specifies additional address information. from the table field
	Post Code	Post Code	Specifies the postal code. from the table field
	City	City	Specifies the city name of the customer the reminder is for. from the table field
	Contact	Contact	Specifies the name of the person you regularly contact when you communicate with the customer the reminder is for. from the table field
	Phone No.	`PrimaryContact."Phone No."`	Specifies the telephone number of the customer contact person the reminder is for.
	Mobile Phone No.	`PrimaryContact."Mobile Phone No."`	Specifies the mobile telephone number of the customer contact person the reminder is for.
	Email	`PrimaryContact."E-Mail"`	Specifies the email address of the customer contact person the reminder is for.
	Your Reference	Your Reference	Specifies the customer’s reference. The content will be printed on the related document. from the table field
	Posting Date	Posting Date	Specifies the date when the reminder should be issued. from the table field
	VAT Reporting Date	VAT Reporting Date	Specifies the date used to include entries on VAT reports in a VAT period. This is either the date that the document was created or posted, depending on your setting on the General Ledger Setup page. from the table field
	Document Date	Document Date	Specifies the date when the related document was created. from the table field
	Reminder Level	Reminder Level	Specifies the reminder’s level. from the table field
	Use Header Level	Use Header Level	Specifies that the condition of the level for the Reminder Level field is applied to all suggested reminder lines. from the table field
	Assigned User ID	Assigned User ID	Specifies the ID of the user who is responsible for the document. from the table field
Content	ReminderLines	part Page 435 “Reminder Lines”	—
Posting	Reminder Terms Code	Reminder Terms Code	Specifies how reminders about late payments are handled for this customer. from the table field
	Fin. Charge Terms Code	Fin. Charge Terms Code	Specifies the code for the involved finance charges in case of late payment. from the table field
	Due Date	Due Date	Specifies when payment of the amount on the reminder is due. from the table field
	Currency Code	Currency Code	Specifies the currency code of the reminder. from the table field
	Company Bank Account Code	Company Bank Account Code	Specifies the bank account to use for bank information when the document is printed. from the table field
	Shortcut Dimension 1 Code	Shortcut Dimension 1 Code	Specifies the code for Shortcut Dimension 1, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field
	Shortcut Dimension 2 Code	Shortcut Dimension 2 Code	Specifies the code for Shortcut Dimension 2, which is one of two global dimension codes that you set up in the General Ledger Setup window. from the table field
FactBoxes	Control9	part Page 9106 “Customer Ledger Entry FactBox”	—

Actions

Group	Action	ToolTip	Runs
Reminder	List	View all reminders that exist.
	Comments	View or add comments for the record.	Page 442 “Reminder Comment Sheet”
	Customer	Open the card of the customer that the reminder or finance charge applies to.	Page 21 “Customer Card”
	Dimensions	View or edit dimensions, such as area, project, or department, that you can assign to sales and purchase documents to distribute costs and analyze transaction history.
	Statistics	View statistical information, such as the value of posted entries, for the record.	Page 437 “Reminder Statistics”
Functions	Suggest Reminder Lines	Create reminder lines in existing reminders for any overdue payments based on information in the Reminder window.
	Update Reminder Text	Replace the beginning and ending text that has been defined for the related reminder level with those from a different level.
Issuing	Test Report	View a test report so that you can find and correct any errors before you perform the actual posting of the journal or document.
	Issue	Post the specified reminder entries according to your specifications in the Reminder Terms window. This specification determines whether interest and/or additional fees are posted to the customer’s account and the general ledger.
Customer	Statement	—	Report 153 “Customer Statement”
	Customer Detailed Aging	—	Report 106 “Customer Detailed Aging”
	Customer - Order Summary	—	Report 107 “Customer - Order Summary”
	Customer - Detail Trial Bal.	—	Report 104 “Customer - Detail Trial Bal.”
	Aged Accounts Receivable (Obsolete) obsolete Pending 28.0; #if not CLEAN28	View an overview of when customer payments are due or overdue, divided into four periods. You must specify the date you want aging calculated from and the length of the period that each column will contain data for.	Report 120 “Aged Accounts Receivable”
	Customer - Balance to Date	—	Report 121 “Customer - Balance to Date”
	Customer - Trial Balance	—	Report 129 “Customer - Trial Balance”
	Customer - Payment Receipt	—	Report 211 “Customer - Payment Receipt”

Procedures

1 local procedures, no public ones.

Triggers

OnDeleteRecord, OnNewRecord, OnOpenPage, OnAfterGetRecord

Relations

source table Table 295 “Reminder Header”

Pages and codeunits on this table

Page 436 “Reminder List” (card page)

Extended by

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 8703 “Feature Telemetry” (2 calls: OnOpenPage → LogUptake, OnOpenPage → LogUsage)
Codeunit 1400 “DocumentNoVisibility” (1 call: SetDocNoVisible → SalesDocumentNoIsVisible)
Codeunit 1630 “Office Management” (1 call: OnOpenPage → IsAvailable)
Codeunit 799 “VAT Reporting Date Mgt” (1 call: OnOpenPage → IsVATDateEnabled)

Called by

Codeunit 980 “Payment Registration Mgt.” (1 call: ShowRecords → (object))

Recent changes

2026-07-30 #9583 636017 Move Sales report action tooltips to report objects (main, BC30, refactor)

Documented on Microsoft Learn

Send Reminders of Outstanding Balances

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

Across versions

Neighbourhood 11 connected objects and pages