---
id: object/page/4
type: object
title: Page 4 "Payment Terms"
summary: Page 4 "Payment Terms" in Base Application (Microsoft.Foundation.PaymentTerms). Present since at least BC23, still in BC30.
tier: official
language: en
tags:
  - page
  - base application
versions:
  introduced: null
  last_changed: null
  deprecated: null
review:
  state: derived
  by: null
  at: null
  flags: []
generated:
  at: "2026-10-11T00:31:51.816Z"
  pipeline: 0.2.0
  prompts: {}
  input_hash: 91e8851501e682b53cbd3f4b5f2c64840126d1e3c7a733f5a1c96cdefa1c7355
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Foundation/PaymentTerms/PaymentTerms.Page.al
    title: src/Layers/W1/BaseApp/Foundation/PaymentTerms/PaymentTerms.Page.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
  - kind: learn
    url: https://learn.microsoft.com/dynamics365/business-central/finance-payment-terms
    title: Set up payment terms
    date: null
    commit: null
    t: null
    quote: null
links:
  learn:
    - https://learn.microsoft.com/dynamics365/business-central/finance-payment-terms
  objects: []
  features: []
  topics:
    - topic/business-central/business-functionality/set-up-business-central/set-up-finance
  localizations: []
  videos: []
  posts: []
  guidelines: []
object_type: page
object_id: 4
name: Payment Terms
namespace: Microsoft.Foundation.PaymentTerms
app: Base Application
extends: null
first_version: "23"
last_version: "30"
present_in:
  - "23"
  - "24"
  - "25"
  - "26"
  - "27"
  - "28"
  - "29"
  - "30"
changed_in: []
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids:
  - docs/learn-smb-docs/business-central/finance-payment-terms.md
counts:
  fields: 0
  procedures: 0
  events: 0
  subscribers: 0
  controls: 7
  actions: 6
relations:
  out: 1
  referenced_by: 0
  pages: 1
  extended_by: 0
  event_subscribers: 0
  calls: 1
  called_by: 0
  implements: 0
---

# Page 4 "Payment Terms"

> Page 4 "Payment Terms" in Base Application (Microsoft.Foundation.PaymentTerms). Present since at least BC23, still in BC30.

Base Application · Microsoft.Foundation.PaymentTerms · BC23-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/W1/BaseApp/Foundation/PaymentTerms/PaymentTerms.Page.al) · facts from BC29

## Properties

| Property | Value |
|---|---|
| Caption | Payment Terms |
| SourceTable | Payment Terms |
| PageType | List |
| UsageCategory | Administration |
| ApplicationArea | Basic, Suite |

## 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 |
|---|---|---|---|
| Control1 | Code | [Code](../table/3.md#fields) | Specifies a code to identify this set of payment terms. <small>from the table field</small> |
|  | Due Date Calculation | [Due Date Calculation](../table/3.md#fields) | Specifies a formula that determines how to calculate the due date, for example, when you create an invoice. <small>from the table field</small> |
|  | Discount Date Calculation | [Discount Date Calculation](../table/3.md#fields) | Specifies the date formula if the payment terms include a possible payment discount. <small>from the table field</small> |
|  | Discount % | [Discount %](../table/3.md#fields) | Specifies the percentage of the invoice amount (amount including VAT is the default setting) that will constitute a possible payment discount. <small>from the table field</small> |
|  | Calc. Pmt. Disc. on Cr. Memos | [Calc. Pmt. Disc. on Cr. Memos](../table/3.md#fields) | Specifies that a payment discount, cash discount, cash discount date, and due date are calculated on credit memos with these payment terms. <small>from the table field</small> |
|  | Description | [Description](../table/3.md#fields) | Specifies an explanation of the payment terms. <small>from the table field</small> |
|  | Coupled to Dataverse | `CDSIsCoupledToRecord` | Specifies that the payment term is coupled to a payment term in Dataverse. |

## Actions

| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Processing | Translation | View or edit descriptions for each payment method in different languages. | [Page 756 "Payment Term Translations"](../page/756.md) |
| Dataverse | Synchronize | Send or get updated data to or from Dataverse. |  |
| Coupling | Set Up Coupling | Create or modify the coupling to a Dataverse Payment Terms. |  |
|  | Match-Based Coupling | Couple payment terms in Dataverse based on criteria. |  |
|  | Delete Coupling | Delete the coupling to a Dataverse Payment Terms. |  |
| Dataverse | Synchronization Log | View integration synchronization jobs for the payment terms table. |  |

## Triggers

OnAfterGetRecord, OnOpenPage

## Relations

- source table [Table 3 "Payment Terms"](../table/3.md)

## Pages and codeunits on this table

- [Table 3 "Payment Terms"](../table/3.md) (lookup page)

## 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 5330 "CRM Integration Management"](../codeunit/5330.md) (1 call: `OnOpenPage → IsCDSIntegrationEnabled`)

## Across versions

- Present in: BC23-30
- Changed (declaration) in: none

## Documented on Microsoft Learn

- [Set up payment terms](https://learn.microsoft.com/dynamics365/business-central/finance-payment-terms)

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