Page 10868 "Payment Slip" (FR)
FR country layer · Microsoft.Bank.Payment
Across versionsobsolete pending since 28.0
- BC23-28not present
- BC29-30present
FR country layer · Microsoft.Bank.Payment · BC29-30 · source at ea08af5e · facts from BC29
An object of the FR localization, not part of W1.
Properties
| Property | Value |
|---|---|
| Caption | Payment Slip |
| SourceTable | Payment Header |
| PageType | Document |
| ObsoleteState | Pending |
| ObsoleteTag | 28.0 |
| ObsoleteReason | Moved to the Payment Management FR first-party app |
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. | Rec."No." |
Specifies the number of the payment header. |
| Payment Class | Rec."Payment Class" |
Specifies the payment class used when creating this payment slip. | |
| Payment Class Name | Rec."Payment Class Name" |
Specifies the name of the payment class used. | |
| Status Name | Rec."Status Name" |
Specifies the status the payment is in. | |
| Currency Code | Rec."Currency Code" |
Specifies the currency code to be used on the payment lines. | |
| Posting Date | Rec."Posting Date" |
Specifies the date when the payment slip should be posted. | |
| Document Date | Rec."Document Date" |
Specifies the date when you create the payment slip. | |
| Amount (LCY) | Rec."Amount (LCY)" |
Specifies the sum of the amounts in the Amount (LCY) fields on the associated lines. | |
| Partner Type | Rec."Partner Type" |
Specifies if the payment slip is a person or company. | |
| Content | Lines | part Payment Slip Subform | — |
| Posting | Source Code | Rec."Source Code" |
Specifies the source of the payment slip. |
| Shortcut Dimension 1 Code | Rec."Shortcut Dimension 1 Code" |
Specifies the dimension value code that the payment header will be associated with. | |
| Shortcut Dimension 2 Code | Rec."Shortcut Dimension 2 Code" |
Specifies the dimension value code associated with the payment header. | |
| Account Type | Rec."Account Type" |
Specifies the type of account that payments will be transferred to/from. | |
| Account No. | Rec."Account No." |
Specifies the number of the account that the payments will be transferred to/from. | |
| FactBoxes | File Export Errors | part Page 1228 “Payment Journal Errors Part” | — |
Actions
| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Header | Dimensions | View or change the dimension settings for this payment slip. If you change the dimension, you can update all lines on the payment slip. | |
| Header RIB | View the RIB key that is associated with the bank account. | Page “Payment Bank” | |
| Navigate | Header | View general information about payments or collections, for example, to and from customers and vendors. A payment header has one or more payment lines assigned to it. The lines contain information such as the amount, the bank details, and the due date. | |
| Line | Create a new payment line for the payment slip. | ||
| Functions | Suggest Vendor Payments | Process open vendor ledger entries (entries that result from posting invoices, finance charge memos, credit memos, and payments) to create a payment suggestion as lines in a payment slip. | |
| Suggest Customer Payments | Process open customer ledger entries (entries that result from posting invoices, finance charge memos, credit memos, and payments) to create a payment suggestion as lines in a payment slip. | ||
| Archive | Archive the payment slip to separate it from active entries. | ||
| Posting | Generate file | Generate an XML or an XMLport file that you can send to your bank. This requires that File is chosen in the Action Type field for the payment slip setup. | |
| Post | Post the payment. | ||
| Print the payment slip. |
Procedures
1 local procedures, no public ones.
Triggers
OnAfterGetRecord
Deprecations
- object: Pending 28.0 (#if not CLEAN28), “Moved to the Payment Management FR first-party app”
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). 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 Slip"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.
A FR country object, not part of W1: the default corpus does not have it; bcatlas_list_countries shows which countries the atlas has.