---
id: object/page/12446-ru
type: object
title: Page 12446 "Outgoing Cash Order" (RU)
summary: Page 12446 "Outgoing Cash Order" (RU) in the RU country layer. 1 public procedures. Introduced in BC29, still in BC30.
tier: official
language: en
tags:
  - page
  - ru layer
versions:
  introduced: "29"
  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: ebe1b1d15cd2bee2877f2159c569799f338979547b7fc01c1f296f7ba5fce8a9
evidence:
  - kind: code
    url: https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/RU/BaseApp/Local/OutgoingCashOrder.Page.al
    title: src/Layers/RU/BaseApp/Local/OutgoingCashOrder.Page.al (releases/29.x)
    date: null
    commit: ea08af5ef2d6a9b5c5af4a029288abbe2c883220
    t: null
    quote: null
links:
  learn: []
  objects: []
  features: []
  topics: []
  localizations:
    - localization/ru
  videos: []
  posts: []
  guidelines: []
object_type: page
object_id: 12446
name: Outgoing Cash Order
namespace: null
app: Base Application
extends: null
first_version: "29"
last_version: "30"
present_in:
  - "29"
  - "30"
changed_in: []
source_major: "29"
obsolete: null
countries: []
ms_search_form_ids: []
country: RU
counts:
  fields: 0
  procedures: 5
  events: 0
  subscribers: 0
  controls: 25
  actions: 5
relations:
  out: 0
  referenced_by: 0
  pages: 0
  extended_by: 0
  event_subscribers: 0
---

# Page 12446 "Outgoing Cash Order" (RU)

> Page 12446 "Outgoing Cash Order" (RU) in the RU country layer. 1 public procedures. Introduced in BC29, still in BC30.

RU country layer · BC29-30 · [source at ea08af5e](https://github.com/microsoft/BCApps/blob/ea08af5ef2d6a9b5c5af4a029288abbe2c883220/src/Layers/RU/BaseApp/Local/OutgoingCashOrder.Page.al) · facts from BC29

An object of the [RU localization](../../localizations/ru.md), not part of W1.

## Properties

| Property | Value |
|---|---|
| Caption | Outgoing Cash Order |
| SourceTable | Gen. Journal Line |
| PageType | Card |

## 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 | Bal. Account No. | `Rec."Bal. Account No."` | Specifies the number of the general ledger, customer, vendor, or bank account to which a balancing entry will posted, such as a cash account for cash purchases. |
|  | Posting Date | `Rec."Posting Date"` | Specifies the entry's posting date. |
|  | Document Type | `Rec."Document Type"` | Specifies the type of the related document. |
|  | Prepayment | `Rec.Prepayment` | Specifies if the related payment is a prepayment. |
|  | Document No. | `Rec."Document No."` | Specifies the number of the related document. |
|  | Account Type | `Rec."Account Type"` | Specifies the purpose of the account. |
|  | Account Code | `Rec."Account No."` | — |
|  | Agreement No. | `Rec."Agreement No."` | Specifies the agreement number associated with the general journal line. |
|  | Currency Code | `Rec."Currency Code"` | Specifies the currency code for the record. |
|  | Amount | `Rec."Debit Amount"` | Specifies the amount. |
|  | Give to | `Rec.Description` | — |
|  | Reason | `Rec."Payment Purpose"` | Specifies the payment purpose associated with the general journal line. |
|  | Supplement | `Rec."Cash Order Supplement"` | Specifies the cash order supplement associated with the general journal line. |
|  | Per | `Rec."Cash Order Including"` | Specifies the cash order including a standard text code, such as travel expenses, associated with the general journal line. |
|  | Check Printed | `Rec."Check Printed"` | Specifies if a check has been printed for the amount on the document or journal line. |
|  | Debit Account | `CorrAccNo` | — |
|  | Credit Account | `BankAccNo` | — |
|  | Analytic Code | `Rec."Account No."` | — |
|  | Posting Group | `Rec."Posting Group"` | — |
|  | Reason Code | `Rec."Reason Code"` | Specifies the reason code, a supplementary source code that enables you to trace the entry. |
|  | Bank Payment Type | `Rec."Bank Payment Type"` | Specifies the code for the payment type to be used for the entry on the journal line. |
|  | Applies-to Doc. Type | `Rec."Applies-to Doc. Type"` | Specifies the type of the posted document that this document or journal line will be applied to when you post, for example to register payment. |
|  | Applies-to Doc. No. | `Rec."Applies-to Doc. No."` | Specifies the number of the posted document that this document or journal line will be applied to when you post, for example to register payment. |
|  | Shortcut Dimension 1 Code | `Rec."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. |
|  | Shortcut Dimension 2 Code | `Rec."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. |

## Actions

| Group | Action | ToolTip | Runs |
|---|---|---|---|
| Functions | Copy Document | — |  |
|  | Void Check Print | Change the status of the ingoing cash order from Check Printed to No. If there is a corresponding record in a check ledger entries table, the value in the Entry Status field in that record will be changed from Printed to Voided. |  |
| Processing | Print | Print the information in the window. A print request window opens where you can specify what to include on the print-out. |  |
| Posting | Post | Record the related transaction in your books. |  |
|  | Preview Posting | Review the different types of entries that will be created when you post the document or journal. |  |

## Procedures

- `CalcPayment()`

Plus 4 local procedures.

## Triggers

OnAfterGetRecord, OnInit

## Across versions

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

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

A RU country object, not part of W1: the default corpus does not have it; `bcatlas_list_countries` shows which countries the atlas has.