Verified on release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).
The customer asks for a deferral: "50% now, the rest in 30 days." You agree verbally, and then in the receivables report you see that the entire amount is "overdue" already on the second day. The reason is simple — the contract or order doesn't specify a payment schedule, and the program assumes the payment was due immediately. The "Payment Schedules" reference list is exactly the place where you describe the installment rule once (advance, stages, deadlines), and then 1C automatically splits the document amount by dates and reminds you of each payment.
1. Purpose
"Payment Schedules" is a reference list of installment templates. In it, you specify in what shares and by what deadlines the counterparty must pay (or you must pay the supplier): prepayment, payment on fact, credit with deferral, several stages. The schedule is linked to a contract, agreement, or order and determines the planned payment dates and overdue control.
2. Where to find it
- Section:
Master data and administration→Master data→Sales/Purchases settings→ in the agreement or contract card, field "Payment Schedule" → selection button →Show all. - The reference list also opens from the Customer Order / Supplier Order card, tab "Main", field "Payment Schedule".
- Direct access via 1C navigation link: menu
Service(or link icon) → "Go to navigation link" → insert:
e1cib/list/Справочник.ГрафикиОплаты
This will open the full list of schedules, even if the field is hidden in the form.
If the "Payment Schedule" field is not visible — enable the functional option:
Master data and administration→Sales→ "Detailed control of settlements and receivables" (or "Payment stages").
2a. How to find out your release
Help → "About the program" (or the "?" icon in the top right corner). In the window that opens, you will see the platform version (e.g., 8.3.24) and the configuration release — a line like "Trade Management for Kazakhstan, edition 3.4 (3.4.5.21)." Rely on this exact number: field locations change from release to release.
3. How to fill it in
Open the reference list → button "Create". Fill in the header and the stages table.
Header
| Field | Required | Why and what happens if wrong |
|---|---|---|
| Name | Yes | The name by which you will select the schedule in contracts. Write it meaningfully: "50% advance + 50% in 30 days." An empty name cannot be saved. |
| Deadline calculation method | Yes | How to calculate the payment date: "By calendar days" or "By business days." If set incorrectly, deadlines will shift to weekends and overdue control will be wrong. |
| Currency | No | Usually not specified — the schedule takes the currency from the document. Fill in only if the schedule is strictly currency-bound. |
Payment stages table
Use the "Add" button to add rows. Each row is one payment.
| Row field | Why and what happens if wrong |
|---|---|
| Payment option | Advance (before shipment), Prepayment (before fulfillment), Credit (after shipment). This determines whether the payment counts as an advance or post-payment. Mix it up, and the goods will ship without the prepayment you planned to receive in advance. |
| Percent | The stage's share of the document amount. The sum of all rows must equal exactly 100%. If it comes to 90% or 110%, the program won't let you post the document or will distribute the debt incorrectly. |
| Deadline (days) | How many days from the reference point the payment is due. For an advance, "0" means payment on the day of registration; for credit, "30" means 30 days after shipment. Set it too low, and the payment will become "overdue" ahead of time. |
| Payment method | Cash / Non-cash / Payment card — a planned attribute for the payment calendar. Not critical for postings, but useful for cash planning. |
Check that the total in the "Percent" column equals 100 and click "Save and close."
4. Worked example with postings
Condition. You sell goods to "Astana-Trade" LLP for 1,160,000 ₸ including VAT 16%. Agreed: 30% advance, the remaining 70% in 20 calendar days after shipment.
Schedule "30% advance + 70% in 20 days":
| Stage | Option | Percent | Deadline |
|---|---|---|---|
| 1 | Advance (before shipment) | 30% | 0 days |
| 2 | Credit (after shipment) | 70% | 20 days |
Breakdown of 1,160,000 ₸:
- Cost excluding VAT: 1,160,000 / 1.16 = 1,000,000 ₸
- VAT 16%: 160,000 ₸
- Advance 30%: 348,000 ₸ (to receive before shipment)
- Remainder 70%: 812,000 ₸ (to receive no later than +20 days)
Postings for this transaction (standard Kazakhstan chart of accounts):
- Advance of 30% received — 348,000 ₸ (document "Receipt of Non-Cash Funds"):
| Dr | Cr | Amount |
|---|---|---|
| 1030 "Cash on current accounts" | 1210 "AP to customers" (advance) | 348,000 ₸ |
- Shipment of goods (document "Sale of Goods and Services"), cost of goods 700,000 ₸:
| Dr | Cr | Amount |
|---|---|---|
| 1210 "Accounts receivable" | 6010 "Sales income" | 1,000,000 ₸ |
| 1210 "Accounts receivable" | 3130 "VAT payable" (16%) | 160,000 ₸ |
| 7010 "Cost of sales" | 1330 "Goods" | 700,000 ₸ |
- Advance offset and receipt of the remaining 812,000 ₸ within +20 days:
| Dr | Cr | Amount |
|---|---|---|
| 1030 "Cash on current accounts" | 1210 "Accounts receivable" | 812,000 ₸ |
It is precisely the payment schedule that ensured that after shipment 348,000 ₸ is already recorded as an advance, and 812,000 ₸ received the status "payment due by day 20" — and until that date the debt in reports is not marked as overdue.
5. Types of operations (what the reference list provides)
The reference list itself does not post any operations — it sets the rule that documents follow. Possible schemes:
- Full prepayment — 100% advance, deadline 0.
- Payment on fact — 100% credit, deadline 0 (on the day of shipment).
- Deferral (credit) — 100% credit, deadline N days.
- Partial advance + remainder — 2 stages (as in the example).
- Multi-stage installment — 3 or more rows (e.g., 20% / 30% / 50% with different deadlines).
6. What is generated when used
The reference list item itself does not create register movements when saved. The effect appears in the documents where the schedule is linked:
- "Settlements with customers/suppliers" register — planned dates and amounts of payment stages.
- Payment calendar — forecast of receipts/payments by stage deadlines.
- Debt control — status "on time / overdue" for each stage.
- Postings are generated not by the schedule, but by sales/receipt and payment documents (see example above).
- ESF (Electronic Invoice Information System) and SNT (Goods Consignment Note) are issued from sales/transfer documents independent of the schedule; the schedule only determines cash settlement deadlines, not the issuance of electronic documents.
7. Printed forms
The "Payment Schedules" reference list itself has no separate printed form — it's a master data template. The schedule is reflected in the printed forms of documents where it is applied:
- Invoice for payment — payment terms and deadlines.
- Contract / Agreement — "Settlement procedure" section.
- Customer Order / Supplier Order — "Payment Schedule" block.
- Reconciliation act — accounting for planned deadlines.
8. Common errors
"The sum of payment stage percentages must equal 100%." You entered stages of 30% and 60% (total 90%) or more than 100%. Open the schedule, recalculate the "Percent" column, and get exactly 100. Fractional shares (33.33 / 33.33 / 33.34) are allowed — the total is what matters.
"Payment schedule not filled in" when posting an order. Stage control is enabled in the agreement/order, but the field is empty. Select an existing schedule or create a new one directly from the field using the "Create" button.
Debt is immediately "overdue." The credit stage in the schedule has a deadline of "0." Set the actual number of deferral days (e.g., 20) and reselect the schedule in the document — the planned date will be recalculated.
Advance did not register as an advance. The stage is marked as "Credit," even though the payment occurs before shipment. Change the option to "Advance (before shipment)."
The schedule cannot be deleted — "Object is in use…"
It is linked to contracts/orders. Mark it for deletion and run Administration → "Delete marked objects," having first removed the references.
9. FAQ
1. How does a payment schedule differ from a payment method? Payment method is "how" (cash, non-cash, card). Schedule is "when and in what shares." The method can be part of a schedule row, but it's the schedule that controls the deadlines.
2. Where do I link a schedule to a customer? In the standard agreement with the client or in the contract — the "Payment Schedule" field. Then it will automatically apply to all orders for that client.
3. Can I set an installment plan for 3 or more payments? Yes. Add as many rows as needed, with different percentages and deadlines. The main thing is that the sum of percentages equals 100%.
4. From what date is the stage deadline calculated? For an advance — from the date the order/invoice is issued; for credit — from the shipment (sale) date. The calculation method (calendar/business days) is set in the schedule header.
5. Does the schedule affect the VAT rate? No. VAT (in Kazakhstan in 2026 — 16%) is charged in the sales document based on the goods' cost and does not depend on the schedule. The schedule only splits the cash flows by deadlines.
6. What happens if I leave the schedule field empty? The program assumes payment is due immediately (deadline 0). Any deferral will immediately become "overdue," and the payment calendar will be incorrect.
7. Can one schedule be used for both sales and purchases? Yes, the reference list is shared. The same "50/50 in 30 days" template can be used for both a customer order and a supplier order.
8. How do I set up "payment upon shipment"? One stage: option "Credit (after shipment)," percent 100, deadline 0. The debt arises on the day of shipment and becomes due on the same day.
9. Why weren't old orders recalculated after changing the schedule? Changes to the reference list apply to new documents. In already posted orders, reselect the schedule so the planned dates are updated.
10. Do I need a separate contract for each schedule? No. One default schedule is linked to the contract, but in a specific order you can select a different one — this is a one-time exception without editing the contract.
10. Related documents
- Basis for use: the reference list item is applied in the Customer/Supplier Agreement, Contract, Customer Order, Supplier Order, Invoice for Payment.
- What is generated next: based on the schedule deadlines, Receipt/Write-off of Non-Cash Funds, Cash Receipt/Payment Order are planned, Sale of Goods and Services and the issuance of ESF/SNT are reflected, and a Payment Calendar and Reconciliation Act are built.
How to find out your release
Help → "About the program": it shows the 1C:Enterprise platform version and the configuration release. This guide was compiled for "Trade Management for Kazakhstan," edition 3.4, release 3.4.5.21. If you have a different release, the location of individual fields may differ, but the logic of the "Payment Schedules" reference list remains the same.
Prepared for release 3.4.5.21 "Trade Management for Kazakhstan" (edition 3.4).