# Approvals

> Approval templates (document type, condition, stage, decision rule, escalation), approval round, Awaiting My Approval, approval and rejection, delegation, document statuses and notifications.

URL: https://erpdocs.corexlogic.com/en/ayarlar/onaylar

- **Type:** Guide
- **Module:** Administration
- **Menu path:** Yönetim › Onay Süreci › Onay Şablonları · Onayımı Bekleyenler · Onay Vekaletleri (Administration › Approval Process › Approval Templates · Awaiting My Approval · Approval Delegations)
- **Screen route:** `/erp/approvals/templates`
- **Required permission:** `erp-approval-templates.view (şablonları görme) · .create · .edit · .delete`, `Karar: belge türünün onay izni — erp-sales-quotations.approve, erp-procurement-orders.approve, erp-procurement-requisitions.approve, erp-accounting-journal-entries.approve; mühendislik değişikliği talebinde erp-manufacturing-engineering-changes.edit`

The approval process ensures that a document is signed off by authorized people before it moves to the next step:
for example, a purchase order above 50,000 TRY goes to the purchasing manager, and a quotation with a high discount
goes to the sales manager. Approval is **not a mandatory step but a configured one**: if there is no active
template for a document type, documents of that type proceed without approval.

End-to-end example: [Approval flow process](https://erpdocs.corexlogic.com/en/surecler/onay-akisi).

## Concepts

| Concept | Meaning |
|---|---|
| **Approval template** | Which document type goes through which stages under which condition (amount range, discount threshold). |
| **Stage** | A step of the template: who approves (a role or specific people), how many approvals are required, how many rejections reject the document, and to whom it escalates if left unanswered. Stages are asked **in sequence**. |
| **Approval round** | One submission of the document for approval. On submission, the stages of the matching templates are **copied** into the round; even if the template changes later, a running round does not change. A document that is rejected and resubmitted opens a **new round**; the trail of the old round remains as it is. |
| **Approver** | A user who holds the stage's role or is named in the stage, and who has the approval permission for the document type. |
| **Delegate** | A user who votes **on behalf of** an approver within a date range. |
| **Segregation of duties** | **The person who submits the document for approval cannot approve it** (even if their role and permission match). For a sales quotation, the quotation's **sales representative** cannot approve it either. Rejecting is always allowed. |

## Documents that can require approval

| Document type | Condition terms | Permission that enables approval | Status after submission | On final approval | On rejection |
|---|---|---|---|---|---|
| **Satış Teklifi** (Sales Quotation) | Amount and discount | `erp-sales-quotations.approve` | Onay Bekliyor (Pending Approval; locked, not sent to the customer) | Gönderildi (Sent) | Taslak (Draft) |
| **Satın Alma Siparişi** (Purchase Order) | Amount | `erp-procurement-orders.approve` | Onay Bekliyor (Pending Approval; locked, no goods receipt possible) | Sipariş Verildi (Ordered) | Taslak (Draft) |
| **Satın Alma Talebi** (Purchase Requisition) | None (every requisition) | `erp-procurement-requisitions.approve` | Onay Bekliyor (Pending Approval) | Talep Edildi (Requested; on purchasing's agenda) | Taslak (Draft) |
| **Yevmiye Fişi** (Journal Entry) | Amount | `erp-accounting-journal-entries.approve` | Awaits approval | The entry's own flow | The entry's own flow |
| **Mühendislik Değişikliği Talebi** (Engineering Change Request) | None (every request) | `erp-manufacturing-engineering-changes.edit` | Awaits approval | A change number is opened | The request's own flow |

"Amount" is the document's **grand total** — including VAT, after discounts, including additional charges, in the
document's currency. "Discount" is the **highest effective discount** on the document: because line and header
discounts are applied together, the actual reduction of a line is calculated as `1 − (1 − satır%) × (1 − genel%)`;
if only the header discount were considered, the approval could be bypassed with a line discount.

## Approval Templates screen

**Yönetim › Onay Süreci › Onay Şablonları** (Administration › Approval Process › Approval Templates) — "Hangi
belge, hangi koşulda, hangi aşamalardan geçerek onaylanır" (Which document is approved, under which condition,
through which stages).

![Approval Templates — coverage cards and template table](https://erpdocs.corexlogic.com/en/en/img/screens/ayarlar/onay-sablonlari.png)
1. New Template
2. Document type card — does the type go through approval
3. Condition — amount range / discount threshold
4. Stages are asked in order
5. Active / Inactive

At the top there is a **scope card** for each document type: "N etkin şablon — onaydan geçer" (N active templates
— goes through approval), "Şablonlar pasif — onaysız ilerler" (Templates inactive — proceeds without approval) or
"Şablon yok — onaysız ilerler" (No template — proceeds without approval). **Şablon Ekle** (Add Template) on the card
opens the dialog with that type.

| Column | Description |
|---|---|
| **Belge Türü** (Document Type) | The document the template applies to. |
| **Şablon** (Template) | Template name. |
| **Koşul** (Condition) | The readable condition: "50.000,00 TRY ve üzeri" (50,000.00 TRY and above), "… – …", "… ve altı" (… and below), "iskonto %10 ve üzeri" (discount 10% and above); without a condition, **Her zaman** (Always). |
| **Aşamalar (sırayla)** (Stages, in sequence) | The approvers of the stages in order; with escalation, "24 saat sonra 'Yönetici' rolüne yükselir" (escalates to the 'Yönetici' role after 24 hours). |
| **Durum** (Status) | Active or inactive. |
| **İşlem** (Action) | Düzenle (Edit) · Sil (Delete) (depending on permission). |

The table is not paginated: to understand tiered approval, all templates are displayed together. The delete
confirmation reads "Şablon silinsin mi?" (Delete the template?): "Bu şablon bundan sonra onay turu doğurmaz. Geçmiş
turlar şablonu kendi içinde sakladığı için etkilenmez." (This template will no longer create approval rounds. Past
rounds are not affected because they store the template within themselves.) To pause a template temporarily, turn
off the **Etkin** (Active) switch instead of deleting it.

### Template dialog

**Yeni Şablon** (New Template) (or **Düzenle** (Edit) on a row) opens a wide dialog: the form on the left, and on
the right the **Özet** (Summary, a one-sentence reading of the rule) and a **Akış** (Flow) preview.

![New Approval Template — condition, stages, summary and flow](https://erpdocs.corexlogic.com/en/en/img/screens/ayarlar/onay-sablonu-yeni.png)
1. Document Type — fixed after creation
2. Condition — discount threshold
3. Stage 1 — role or named users, decision rule
4. If unanswered — hours and escalation role
5. Add Stage (max 10)
6. Summary — the rule as a sentence
7. Flow preview

#### General

| Field | Required | Description |
|---|---|---|
| **Belge Türü** (Document Type) | Yes | Satış Teklifi (Sales Quotation), Satın Alma Siparişi (Purchase Order), Satın Alma Talebi (Purchase Requisition), Yevmiye Fişi (Journal Entry), Mühendislik Değişikliği Talebi (Engineering Change Request). The selection determines the condition terms and approver lists. **It cannot be changed when editing** (another type has a different permission and condition); to change the type, create a new template. When the document type changes, conditions and stages are reset. |
| **Şablon Adı** (Template Name) | Yes | At most 128 characters. Example: "50.000 TRY üstü sipariş onayı" (Order approval above 50,000 TRY). Shown in the approval history and in Onayımı Bekleyenler (Awaiting My Approval). |
| **Etkin** (Active) | — | Only when editing. On: "Yeni belgeler bu şablona uyar" (New documents follow this template). Off: "Pasif — yeni belgeler bu şablona uymaz" (Inactive — new documents do not follow this template). An inactive template does not start new approval rounds; running rounds are not affected. A new template is created active. |

#### Which documents (condition)

A condition the document type does not offer is not drawn in the dialog. For a type without conditions
(requisition, engineering change), the dialog reads "Bu belge türünde koşul yok — şablon onaya gönderilen **her**
belgeye uygulanır." (This document type has no condition — the template applies to **every** document submitted for
approval.)

| Field | Values | Description |
|---|---|---|
| **Tutar** (Amount) | **Tutarı ne olursa olsun** (Whatever the amount) · **Genel toplam aralıktaysa** (If the grand total is within a range) | Default is "whatever the amount". Selecting a range opens the two fields below. |
| **Para Birimi** (Currency) | The installation's currencies (the default currency is preselected) | **No currency conversion**: the template applies only to documents in this currency. TRY and EUR orders require two separate templates. |
| **Genel toplam** … **ile** … **arası** (Grand total between … and …) | Lower limit (empty = 0) · Upper limit (empty = unlimited) | Including VAT, after discounts; it also matches when **equal** to the limits. For "50,000 and above", leave the upper limit empty. At least one limit must be entered, limits must be zero or positive, and the lower limit cannot be greater than the upper limit. |
| **İskonto** (Discount) | Checkbox: "Yalnız iskontosu belirli bir oranı aşan belgeler" (Only documents whose discount exceeds a given rate) | Sales quotation only. |
| **İskonto eşiği (%)** (Discount threshold, %) | Greater than 0, at most 100 | "Satırlardaki en yüksek iskonto bu orana eşit ya da üstündeyse uyar." (Matches if the highest discount on the lines is equal to or above this rate.) |

If both amount and discount are selected, both must hold.

#### Approval stages — asked in sequence

Each stage is a separate box; its number is its order ("İlk sorulan" (Asked first), "1. aşama kapanınca sorulur"
(Asked when stage 1 closes)). To the right of the box there are **Yukarı taşı** (Move up), **Aşağı taşı** (Move
down) and a button to remove the stage (a single stage cannot be removed). **Aşama Ekle** (Add Stage) adds a new
stage; a template can have at most **10** stages.

| Field | Required | Description |
|---|---|---|
| Stage name | No | "1. aşamanın adı (örn. Bölüm onayı)" (Name of stage 1, e.g. Department approval). At most 128 characters; if empty, "1. aşama" (Stage 1) is written. Shown in the approval history and in Onayımı Bekleyenler (Awaiting My Approval). |
| **Kim onaylar** (Who approves) | Yes | **Bir rol** (A role): "Rol seçin — rolü taşıyan herkes onaylayabilir" (Select a role — anyone holding the role can approve). A role that does not hold the document type's approval permission is marked "— onay izni yok" (— no approval permission) in the list, and if selected the template is not saved ("Bu rol bu belgeyi onaylama iznine sahip değil — aşama hiç kapatılamazdı, şablon kaydedilmez." — This role does not have permission to approve this document — the stage could never be closed, the template is not saved). **Belirli kişiler** (Specific people): only users who hold the document type's approval permission are listed, searchable by name or email; at most 10 people ("daha kalabalık liste bir roldür" — a longer list is a role). Roles and people cannot be mixed in the same stage. |
| **Karar kuralı** (Decision rule) | Yes | "**N** onay gerekli, **M** ret belgeyi reddeder" (**N** approvals required, **M** rejections reject the document) — each 1–10. The sentence below reads the rule: "Biri onaylarsa geçer, biri reddederse belge reddedilir." (Passes if one person approves; the document is rejected if one person rejects.) In a people stage, the number of approvals cannot exceed the number of selected people, and so that the stage does not deadlock when votes are split, approvals + rejections ≤ number of people + 1. |
| **Cevapsız kalırsa** (If unanswered) | No | "**S** saat sonra **[Üst onaycı rolü]** de karar verebilir" (After **S** hours, **[Higher approver role]** can also decide). Duration 1–720 hours; duration and role are entered **together**; the higher approver role cannot be the stage's own role and must hold the approval permission. If left empty ("kimseye aktarılmaz" — not passed to anyone), the stage waits until a decision is made; the "Onay bekleyen hatırlatması" (Pending approval reminder) alert reminds the approvers. |

A person votes **once** in a stage; the same person's vote is not counted twice (a "two of three managers" rule
cannot be passed by a single person).

#### Multiple templates

"Aynı belgeye uyan birden çok şablon varsa hepsinin aşamaları sırayla eklenir." (If several templates match the same
document, the stages of all of them are added in sequence.) Matching templates are ordered by lower amount limit,
smallest to largest. Tiered approval can be set up in two ways:

- **Two templates:** "0 TRY and above → Purchasing Manager" and "50,000 TRY and above → General Manager". For a
  60,000 TRY order both templates match; the round has two stages.
- **One template, two stages:** in the "50,000 TRY and above" template, stage 1 is the Purchasing Manager and stage 2
  is the Administrator.

#### Validation messages

When a template is saved, the screen and the server apply the same rules: "Belge türünü seçin." (Select the document
type.), "Şablon adı zorunlu." (Template name is required.), "Tutar koşulunda en az bir sınır yazın (alt sınır 0
olabilir)." (Enter at least one limit in the amount condition (the lower limit can be 0).), "Alt tutar sınırı üst
sınırdan büyük olamaz." (The lower amount limit cannot be greater than the upper limit.), "İskonto eşiği 0'dan büyük
ve en fazla 100 olmalı." (The discount threshold must be greater than 0 and at most 100.), "Onaylayacak rolü
seçin." (Select the approving role.), "En az bir onaycı kullanıcı seçin." (Select at least one approver user.),
"Eskalasyon için süre ve üst onaycı rolünü birlikte girin." (Enter the duration and the higher approver role together
for escalation.), "Üst onaycı rolü aşamanın kendi rolüyle aynı olamaz." (The higher approver role cannot be the same
as the stage's own role.). In a multi-stage template, the message carries the stage number ("2. aşama: …" — Stage
2: …).

### Sample templates

| Purpose | Document Type | Condition | Stages |
|---|---|---|---|
| High-value purchasing | Satın Alma Siparişi (Purchase Order) | TRY, grand total between 50,000 and (empty) | 1. Purchasing Manager (unanswered for 24 hours → Administrator) · 2. Administrator |
| Discounted quotation | Satış Teklifi (Sales Quotation) | Discount threshold 10% | 1. Sales Manager |
| Every requisition | Satın Alma Talebi (Purchase Requisition) | — (every requisition) | 1. Purchasing Manager |
| Two signatures | Satın Alma Siparişi (Purchase Order) | TRY, 250,000 and above | 1. Specific people (3 managers), 2 approvals required, 2 rejections reject |

Two templates are defined in the demo installation: **Satış teklifi — iskonto %10 ve üzeri** (Sales quotation —
discount 10% and above; active, single stage: Yönetim onayı (Management approval) · Yönetici (Administrator)) and
**Satın alma siparişi — 50.000 TRY ve üzeri (örnek)** (Purchase order — 50,000 TRY and above (sample); inactive, two
stages).

## How a document goes to approval

On the document's detail page, the submit button learns about the template match **from the server**: if an active
template matches, the button is named **Onaya Gönder** (Submit for Approval) (for a sales quotation: "Bu teklif onay
şablonuna takılıyor (tutar ya da iskonto). **Onaya Gönder** teklifi kilitler; son onayda kendiliğinden gönderildi
olur." — This quotation is caught by an approval template (amount or discount). **Onaya Gönder** locks the quotation;
on final approval it automatically becomes sent).

![Draft quotation matching a template — Send for Approval](https://erpdocs.corexlogic.com/en/en/img/screens/ayarlar/teklif-onaya-gonder.png)
1. Send for Approval instead of Send
2. Why it needs approval

```
Draft ──Submit for Approval──► Pending Approval ──(stage 1)──►(stage 2)──► final approval ──► next status (e.g. Sent)
  ▲                         │  document LOCKED: cannot be edited, converted, or goods-received
  │                         ├─ rejection threshold ───────────────► Draft (edited and resubmitted — new round)
  │                         └─ Cancel ────────────────────────────► Cancelled (open round closes)
  └───────────────────── if no template matches, Send advances it directly
```

- On submission, the stages of the matching templates are copied into the round, and a **"Onayınız bekleniyor"**
  (Your approval is awaited) notification is sent to the approvers of stage 1 ("ST-… numaralı satış teklifi 1. onay
  aşamasında sizi bekliyor." — Sales quotation ST-… is waiting for you at approval stage 1.).
- When a stage is approved, a notification is sent to the approvers of the next stage; the document remains locked.
- When the last stage is approved, the round becomes **Onaylandı** (Approved), the document proceeds, and a
  **"… onaylandı"** (… approved) notification is sent to the sender (for a quotation: "… numaralı teklif tüm
  onayları aldı ve gönderildi olarak işaretlendi." — Quotation … has received all approvals and was marked as sent.).
  Because approval may take days, the document's sending rules (item master, customer, validity) are re-evaluated
  at that moment.
- When a stage reaches the rejection threshold, the round becomes **Reddedildi** (Rejected), the remaining stages
  close as **Sorulmadı** (Not asked), the document returns to draft, and a **"… reddedildi"** (… rejected)
  notification is sent to the sender with the reason.
- If a document pending approval is cancelled, the open round becomes **İptal Edildi** (Cancelled).

### Approvals card on the document detail

Above a document pending approval it says whom it is waiting for ("Teklif onay bekliyor — sırada 1. aşama:
Yönetici. Onaylanınca gönderildi olur; reddedilirse taslağa döner." — Quotation pending approval — next is stage 1:
Administrator. When approved it becomes sent; if rejected it returns to draft.). The **Onaylar** (Approvals) card
lists the rounds with the newest on top: the round's status, sender, submission time and amount; for each stage the
approver, template and stage name, status (**Karar bekleniyor** (Decision pending) · **Onaylandı** (Approved) ·
**Reddedildi** (Rejected) · **Sorulmadı** (Not asked)), and the votes cast (name, "adına" (on behalf of) delegation
note, "(eskalasyonla)" (by escalation), Onayladı/Reddetti (Approved/Rejected), time, note). In a multi-vote stage
it says "Karar bekleniyor — 1/2 onay" (Decision pending — 1/2 approvals); in an escalated stage the escalation time
is shown.

![Quotation pending approval — current stage and rounds](https://erpdocs.corexlogic.com/en/en/img/screens/ayarlar/teklif-onay-bekliyor.png)
1. Decision buttons — server decides (submitter cannot approve)
2. Who it is waiting for
3. Current round — awaiting decision
4. Previous round — rejection and reason kept

## Approval and rejection

The decision is made **on the document's detail page**: the **Onayla** (Approve) and **Reddet** (Reject) buttons are
drawn if the server answers yes to the question "can this person vote on this stage right now". The rule: holding
the stage's role or being named in the stage (or a delegation valid today), having the document type's approval
permission, and not having voted in this stage yet; for approval, segregation of duties applies as well. The
sender sees only **Reddet** (Reject).

| Dialog | Content |
|---|---|
| **Onay verilsin mi?** (Approve?) | "Oyunuz sıradaki aşamaya yazılır. Aşama gereken onaya ulaşır ve başka aşama yoksa belge onaylanır." (Your vote is recorded in the current stage. If the stage reaches the required approvals and there is no other stage, the document is approved.) **Not (isteğe bağlı)** (Note, optional) — "Onay kaydına düşecek açıklama" (Comment to be recorded with the approval), at most 512 characters. If voting as a delegate, it states on whose behalf. Buttons **Vazgeç** (Cancel) · **Onayla** (Approve). |
| **Reddedilsin mi?** (Reject?) | "Aşama red eşiğine ulaşırsa belge taslağa döner ve yeniden düzenlenebilir." (If the stage reaches the rejection threshold, the document returns to draft and can be edited again.) **Red gerekçesi** (Rejection reason) is required — "Neyin düzeltilmesi gerekiyor?" (What needs to be corrected?); "Gerekçe belgeyi onaya gönderen kişiye bildirim olarak iletilir." (The reason is sent as a notification to the person who submitted the document.) Buttons **Vazgeç** (Cancel) · **Reddet** (Reject). |

![Reject confirmation — reason required](https://erpdocs.corexlogic.com/en/en/img/screens/ayarlar/onay-reddet.png)
1. Rejection reason — sent to the submitter
2. Reject — document returns to draft at the threshold

On the approver's screen (demo: **Demo Onaylayıcı**, ST-2026-000005), the **Onay verilsin mi?** (Approve?) dialog
also shows the document number and amount ("ST-2026-000005 · 50.476,80 TRY"); the note appears under the vote on the
**Onaylar** (Approvals) card.

![Approve confirmation — optional note](https://erpdocs.corexlogic.com/en/en/img/screens/ayarlar/onay-ver.png)
1. Document and amount being approved
2. Note — saved with the approval
3. Approve — last stage moves the document on

There is **no** bulk approval: an approval is a signature, and its justification lies in the content of the
document. On a phone, the same decision is made from the **Onaylarım** (My Approvals, mobile) screen.

### Decision messages

| Message | Reason |
|---|---|
| Onaya kendiniz gönderdiğiniz belgeyi onaylayamazsınız. Kararı başka bir onaycı vermeli. (You cannot approve a document you submitted for approval yourself. Another approver must decide.) | Segregation of duties. |
| Onaya kendiniz gönderdiğiniz ya da satış temsilcisi olduğunuz teklifi onaylayamazsınız. Kararı başka bir onaycı vermeli. (You cannot approve a quotation you submitted for approval or for which you are the sales representative. Another approver must decide.) | For a quotation, the sales representative cannot approve either. |
| Bu aşamada kararınızı zaten verdiniz — aşama diğer onaycıların oyunu bekliyor. (You have already made your decision in this stage — the stage is waiting for the other approvers' votes.) | One vote per person per stage. |
| Bu aşamayı yalnız '…' rolündeki kullanıcılar kapatabilir. (Only users in the '…' role can close this stage.) | You do not hold the stage's role. For an escalated stage, the time the duration expires is also stated. |
| Bu aşamada vekiliniz sizin adınıza oy verdi — aşama diğer onaycıların oyunu bekliyor. (Your delegate voted on your behalf in this stage — the stage is waiting for the other approvers' votes.) | Your delegate used your vote. |
| Red gerekçesi zorunludur. (A rejection reason is required.) | The reason is empty in the rejection dialog. |
| … onaylama yetkiniz yok. (You do not have permission to approve ….) | No approval permission for the document type. |
| Bu teklif onay beklemiyor. (This quotation is not pending approval.) | The document was approved, rejected or cancelled in the meantime — refresh the page. |

## Awaiting My Approval {#onayimi-bekleyenler}

**Yönetim › Onay Süreci › Onayımı Bekleyenler** (Administration › Approval Process › Awaiting My Approval) —
"Sırası gelmiş ve sizin (ya da vekili olduğunuz onaycının) kararını bekleyen belgeler" (Documents whose turn has
come and that are waiting for your decision, or that of the approver whose delegate you are). All document types are
in a single list, the longest-waiting first; documents you submitted yourself do not appear here. You make the
decision on the document's detail page, not on the row.

![Pending My Approval](https://erpdocs.corexlogic.com/en/en/img/screens/ayarlar/onayimi-bekleyenler.png)
1. Document type filter
2. Submitter and date
3. Stage position, template and stage name
4. How long the stage has waited
5. On behalf of

| Column | Description |
|---|---|
| **Belge** (Document) | Document number and type; click to open the document. |
| **Gönderen** (Sender) | The person who submitted it for approval and the submission time. |
| **Tutar** (Amount) | The grand total at the time of submission and the currency; "—" for a document without a condition (requisition). |
| **Aşama** (Stage) | "2. aşama / 3" (Stage 2 / 3) or "Tek aşama" (Single stage); in a multi-vote stage "1/2 onay" (1/2 approvals); below it, the template and stage name. |
| **Bekliyor** (Waiting) | How long the stage has been waiting ("1 saatten az" (less than 1 hour), "5 saat" (5 hours), "2 gün" (2 days)) — the same duration the reminder counts. |
| **Vekalet** (Delegation) | "… adına" (on behalf of …) if waiting as a delegate. |

The **Belge Türü** (Document Type) filter narrows the list to a single type. **Bekleyen İşlerim** (My Pending Tasks)
on the Home page also counts the approval queue.

A document waiting in an approver's list (demo: ST-2026-000005 in Demo Onaylayıcı's queue, "Tek aşama" (Single
stage), "Satış teklifi — iskonto %10 ve üzeri — Yönetim onayı"):

![Pending My Approval — the approver’s queue](https://erpdocs.corexlogic.com/en/en/img/screens/ayarlar/onay-kuyrugu.png)
1. Document — click to open
2. Submitter and date
3. Stage, template and stage name
4. How long the stage has waited

## Approval Delegations {#onay-vekaletleri}

**Yönetim › Onay Süreci › Onay Vekaletleri** (Administration › Approval Process › Approval Delegations) — "Onaycı
yokken (izin, hastalık) vekili tarih aralığında onun adına oy verir" (When an approver is absent (leave, illness),
the delegate votes on their behalf within a date range). The vote counts as the approver's; a person casts a single
vote in a stage; a document the approver cannot approve cannot be approved by the delegate either.

![Approval Delegations](https://erpdocs.corexlogic.com/en/en/img/screens/ayarlar/onay-vekaletleri.png)
1. New Delegation
2. Manager: everyone’s delegations
3. Show ended delegations
4. Validity — both days inclusive

By default the list shows **Vekaletlerim** (My Delegations: delegations I have given and that have been given to
me); an administrator sees all delegations with the **Herkesin vekaletleri** (Everyone's delegations) switch.
**Bitmişleri göster** (Show ended) also lists the expired ones. Columns: **Onaycı** (Approver), **Vekil**
(Delegate), **Tarih Aralığı** (Date Range), **Belge Türü** (Document Type; if empty, "Bütün belge türleri" — All
document types), **Durum** (Status: Geçerli (Valid) · Başlamadı (Not started) · Bitti (Ended)), **Not** (Note);
**Kaldır** (Remove) in the row's Actions menu.

![New Approval Delegation dialog](https://erpdocs.corexlogic.com/en/en/img/screens/ayarlar/onay-vekaleti-yeni.png)
1. Approver — myself or (manager) another approver
2. Document type or all types
3. Substitute — a user with approval permission
4. Date range — up to 366 days
5. Note

| Field | Required | Description |
|---|---|---|
| **Onaycı** (Approver) | Yes | Visible to administrators only: **Kendim** (Myself) or another approver. "Yönetici, sisteme giremeyen onaycının yerine de vekil atayabilir." (An administrator can also assign a delegate for an approver who cannot sign in.) Other users can assign a delegate only for themselves. |
| **Belge Türü** (Document Type) | Yes | A single type or **Bütün belge türleri** (All document types). "Bütün türlerde vekil, onaycının onayladığı her belgenin onay yetkisini taşımalı." (For all types, the delegate must hold the approval permission for every document the approver approves.) |
| **Vekil** (Delegate) | Yes | "Onay yetkisi olan bir kullanıcı seçin" (Select a user with approval permission). The delegate must hold the approval permission for the delegated document types themselves — a delegation does not grant permissions. |
| **Tarih aralığı** (Date range) | Yes | Start — end; "İki gün de dahil; en fazla 366 gün — daha uzunu rol değişikliğidir." (Both days inclusive; at most 366 days — anything longer is a role change.) A delegation that ended in the past cannot be created. |
| **Not** (Note) | No | "Örn. yıllık izin" (e.g. annual leave); at most 512 characters. |

Server messages: "Kişi kendisine vekil olamaz." (A person cannot be their own delegate.), "Bitiş tarihi
başlangıçtan önce olamaz." (The end date cannot be before the start date.), "Geçmişte biten bir vekalet
tanımlanamaz." (A delegation that ended in the past cannot be defined.), "… için … bu tarihlerde zaten vekil." (…
is already the delegate for … on these dates.), "… şu belgeleri onaylama yetkisine sahip değil: …" (… does not have
permission to approve these documents: …). When a delegation is removed ("Vekalet kaldırılsın mı?" — Remove the
delegation?), the delegate can no longer vote on the approver's behalf; votes already cast remain in the trail with
the "adına" (on behalf of) record.

## Notifications and reminders

| Notification | Recipient | When |
|---|---|---|
| **Onayınız bekleniyor** (Your approval is awaited) | Everyone who can approve the stage whose turn has come (delegates included) | On submission and at each stage transition |
| **Onay hatırlatması** (Approval reminder; alert: *Onay bekleyen hatırlatması* — Pending approval reminder) | The same people | If a stage waits longer than the threshold (default 24 hours), once a day until a decision is made — if the alert is enabled |
| *Onay eskalasyonu* (Approval escalation; alert) | The higher approver role in the template | Once, when the stage's escalation duration expires — if the alert is enabled; the decision authority takes effect even when the notification is disabled |
| **Onay tamamlandı** (Approval completed) | Sender | On final approval |
| **Onay reddedildi** (Approval rejected) | Sender | On rejection, with the reason |

The purchase order also has its own notification types: **Satın alma siparişi onay bekliyor** (Purchase order pending
approval), **… onaylandı** (… approved), **… reddedildi** (… rejected). The channel (application, email, daily
digest) is the person's preference: [Notifications](https://erpdocs.corexlogic.com/en/ayarlar/bildirimler).

## Tasks

- [Create an approval template](https://erpdocs.corexlogic.com/en/ayarlar/islemler/onay-sablonu-olusturma) — Document type, condition, stages.
  - [Make an approval decision](https://erpdocs.corexlogic.com/en/ayarlar/islemler/onay-karari-verme) — Approve, or reject with a reason.
  - [Define an approval delegation](https://erpdocs.corexlogic.com/en/ayarlar/islemler/onay-vekaleti-tanimlama) — A delegate for leave and absence.
  - [Approval flow (process)](https://erpdocs.corexlogic.com/en/surecler/onay-akisi) — End-to-end approval of a discounted quotation.