1. Identification
| Parameter | Value |
|---|---|
| Object Type | Document (Documents) |
| Name | PaymentOrderWithdrawalOfFunds |
| Full Name | Document.PaymentOrderWithdrawalOfFunds |
| Synonym | “Payment order (withdrawal of funds)” |
| Configuration | Accounting for Kazakhstan, edition 3.0 (3.0.74.2) |
| Interface Section | “Cash” (in some releases — “Bank and cash”) |
| Navigation Link | e1cib/list/Document.PaymentOrderWithdrawalOfFunds |
Purpose. The document registers cashless outgoing payments from the organization's bank accounts: payments to suppliers, refunds to customers, loan repayments, salary payments, tax payments, contributions, and other fees, as well as other withdrawals. It generates accounting (BU) and tax (NU) entries, manages settlements with counterparties, and records cash flow. It supports multi-currency calculations with automatic exchange rate conversion (all amounts in examples are in tenge, ₸), accounts for bank commissions, and details payments by contracts and primary documents.
The document is used by accountants and cashiers daily. It can be entered manually or automatically based on invoices and supplier documents.
2. Attributes of Header and Table Parts
2.1 Mandatory Attributes of Header
| Attribute | Purpose |
|---|---|
Organization |
The payer organization on behalf of which the withdrawal is made. |
OperationType |
Determines the logic of filling and the composition of entries (payment to supplier, refund to customer, salary payment, other withdrawal, etc.). |
DocumentCurrency |
The currency of the payment. By default — tenge (₸); if another currency is used, the exchange rate and multiplicity apply. |
DocumentAmount |
The total amount of withdrawal in the currency of the document. |
Counterparty |
The recipient of the payment (supplier, customer, budget, etc.). |
CounterpartyAccount |
The bank account of the recipient counterparty. |
BankAccount |
The bank account of the organization from which funds are withdrawn. |
OrganizationAccount |
The settlement account of the organization (analytics for account 1030), subaccount for cash flow movements. |
TaxAccountingType |
Manages the formation of parallel entries for tax accounting. |
BUAccountForSettlementsWithCounterparty |
Account for settlements with the counterparty in BU (default 3310 / 1210). |
NUAccountForSettlementsWithCounterparty |
Account for settlements in NU (tax accounting plan). |
Other functional attributes (used in checks and entries): Paid (indicator of actual payment — mandatory for processing), IncludeBankCommission, CommissionAmount, ConsiderCIT, attributes of the sending structural unit (StructuralUnitOrganizationSender) when support for structural units is enabled.
2.2 Table Part “PaymentDetails”
Line-by-line detail of the payment by contracts/documents. Mandatory columns:
| Column | Purpose |
|---|---|
CounterpartyContract |
The contract under which the settlement is made. |
PaymentAmount |
The amount of the line in the currency of the document. |
SettlementExchangeRate |
The exchange rate of the currency of the settlement contract. |
SettlementMultiplicity |
The multiplicity of the rate. |
SettlementAmount |
The amount in the currency of the settlement. |
BUAccountForSettlementsWithCounterparty |
Account for settlements in BU for the line. |
NUAccountForSettlementsWithCounterparty |
Account for settlements in NU for the line. |
The sum of all lines in PaymentDetails must match DocumentAmount.
2.3 Table Part “SalaryPayment”
Used for the operation type “Salary Payment”. Mandatory columns:
| Column | Purpose |
|---|---|
Individual |
Employee — recipient of the salary. |
PaymentAmount |
The amount to be paid to the employee. |
The total of PaymentAmount must match DocumentAmount.
If a mandatory field is not filled — the platform will not process the document and will display the message “Field ... is not filled”.
3. Forms
| Form | Purpose |
|---|---|
DocumentForm |
Main form for input and editing. Manages the visibility of attributes and table parts depending on OperationType, contains client-server handlers (including OrganizationOnChangeOnServer). |
ListForm |
List of documents in the “Cash” section, selection and group operations. |
SelectForm |
Selection of a document when entering based on and in selections from other objects. |
4. Key Module Procedures
From evidence, checks in the object module and form handler are confirmed (the texts of messages are quoted verbatim, release 3.0.68.1; in 3.0.74.2, the formulations are generally identical).
ObjectModule → CheckFillingProcessing — control of correctness before processing:
| 1C Message | Trigger Condition |
|---|---|
| “The payment order can only be processed if it is paid (flag "Paid"). Until the payment indicator is set, the document can only be saved.” | NOT Paid |
| “None of the amounts (document amount, commission amount) is specified! For processing the document, one of the amounts must be filled” | DocumentAmount + CommissionAmount = 0 |
| “The document amount and the salary payment amounts do not match!” | NOT SalaryPayment.Total("PaymentAmount") = DocumentAmount |
| “The document amount and its breakdown do not match.” | NOT PaymentDetails.Total("PaymentAmount") = DocumentAmount |
Form.FormDocument → OrganizationOnChangeOnServer — when changing the organization, checks the compliance of the sending structural unit. Message: “The value in the field "Structural unit (sender)" does not match the selected organization and has been changed” (condition: support for working with structural units is enabled and StructuralUnitOrganizationSender is filled).
Standard handlers of this type of document (general logic of 1C):
ProcessingPosting— formation of movements in BU/NU and cash registers.ProcessingFilling— filling in attributes when entering based on.BeforeSaving— recalculation of settlement amounts by rate and multiplicity.
5. Processing and Movements
The document generates accounting entries according to the standard chart of accounts of the RK depending on OperationType. The credit in all cases is the cash account 1030 (money in current bank accounts) with analytics OrganizationAccount.
Payment to Supplier
Dr 3310 (KZ to suppliers) / Counterparty, Contract
Cr 1030 (Money in current accounts) / OrganizationAccount
If there is a breakdown — for each line in PaymentDetails.
Refund to Customer
Dr 1210 (Short-term receivables from customers) / Counterparty, Contract
Cr 1030 / OrganizationAccount
Salary Payment
Dr 3350 (Settlements for wages) / Individual
Cr 1030 / OrganizationAccount
For each line in SalaryPayment.
Other Withdrawal (taxes, contributions, fees)
Dr <AccountingAccount> / <Subaccount1, Subaccount2, Subaccount3>
Cr 1030 / OrganizationAccount
Accounts and subaccounts are filled manually or automatically by payment type. Example: payment of CIT, OIW 10%, OIW 3.5%, VOSMS 2%, OSMS 3%, CO 5%, social tax 6% is reflected as a withdrawal from 1030 in correspondence with the corresponding tax and contribution liability accounts.
Bank Commission (when IncludeBankCommission = True)
Dr 7210 (Bank services) / Organization
Cr 1030 / OrganizationAccount for the amount of CommissionAmount
NU Entries (when ConsiderCIT = True) are formed in parallel with BU according to the “Tax” chart of accounts:
Dr <NUAccountForSettlementsWithCounterparty> / <SubaccountDrNU1..3>
Cr <BankAccountNU> / OrganizationAccount
Registers. In addition to accounting registers, the document writes movements to cash accounting registers (balances and turnovers on bank accounts) and registers of settlements with counterparties; for the operation type “salary” — registers of settlements for wage payments.
The VAT rate in the RK from 2026 is 16%. The payment order itself does not accrue VAT (this is a cash document), but when paying to the supplier and subsequent offsetting of VAT advances, it is accounted for by related documents at the rate of 16%.
6. Related Objects and Input Based On
Basis Documents (input “based on”):
Document.InvoiceToSupplier— payment based on the issued invoice (scenario 3.2).- Incoming documents (acts, invoices, customs declarations) — payment of debt.
Input based on the payment order / related documents:
Document.ReceivedInvoiceand ESF (IS ESF) — when confirming VAT calculations.- Electronic documents: ESF (electronic invoice) and SNT (accompanying invoice for goods) — generated on related documents of goods movement, not the order itself.
Analytics/Directories: Directory.Counterparties, Directory.CounterpartyContracts, Directory.BankAccounts, Directory.Individuals, ChartOfAccounts.Business, ChartOfAccounts.Tax.
Typical Application Scenarios:
- Payment to supplier manually — registration of payment not yet processed through the bank.
- Payment based on an invoice.
- Accounting for bank commission as an expense (7210).
- Salary payment to employees' card accounts.
- Other withdrawal — taxes, fees, fines not related to settlements with counterparties.
7. Extension Points
- Configuration Extension: overriding/adding handlers
CheckFillingProcessing,ProcessingPosting,ProcessingFillingof the object module; adding attributes and columns of table parts. - Event Subscriptions (
OnSaving,OnPosting) — for integrations with bank clients and external accounting systems. - Common Bank Logic Modules — overriding algorithms for substituting settlement accounts and payment types.
- Forms: extending
DocumentFormfor additional fields and handlers (e.g.,OrganizationOnChangeOnServer). - Exchange Rules / EDI Formats — for exporting to the bank and exchanging ESF/SNT.
- Settings: indicators
IncludeBankCommission,ConsiderCITand the parameter “support for working with structural units” control the composition of movements and checks — to be considered in modifications.
Requires verification for 3.0.74.2: exact names of cash accounting registers and formulations of service messages may differ from release 3.0.68.1, from which the verbatim texts of errors are taken.