Glossary

Abbreviations and key terms that recur across these pages, each with a pointer to the page that explains it in full.

Abbreviations

Term	Meaning	Explained in
BAL	Business-logic layer — the B* classes (for example BPurchaseRequest) that hold the business rules between the controllers and data access.	Architecture
CBA	The bid comparison an RFQ produces: the quotations are compared and scored and the supplier is chosen. It is exported from the RFQ as CBA-<PR number>.	Procurement Cycle
DI	Dependency injection — how services are registered in Startup and handed to controllers and classes.	Services & DI
EF	Entity Framework Core 6, the ORM behind both databases.	Database
ERD	Entity–relationship diagram.	Context ERD
EUR / TL / USD	Euro, Turkish lira and US dollar — the currencies amounts are entered in. Approval tiers are judged on the USD value.	Procurement Cycle
FK / PK	Foreign key / primary key.	Database
FO	Finance Officer — the Finance step that signs a Purchase Request (the FOSign flag). Also part of setting names such as Timesheet FO.	Procurement Cycle
GD order	Good Delivery Order — the application's name for a Stock Release Request (SRR).	Logistics
GM	General Manager — the position the code looks up as the Country Director; the last approver in some chains, such as exceptional paid leave.	Leave Management
GRN	Goods Received Note — confirms that ordered goods arrived; it is the document that passes them to the warehouse.	Procurement Cycle
LOE	Level of effort — the share (%) of an employee's time and salary charged to a budget line. Used in salary allocations, project posts and grant budget lines.	Payroll
NKO	Nasaem Khair Organization, which runs the ERP.	Home
PIN	The approver's e-signature PIN, checked before Advance, Overtime and Leave approvals (VerifyPin).	Security & Permissions
PO	Purchase Order — the order to the chosen supplier, created from the approved RFQ.	Procurement Cycle
PR	Purchase Request — the request that starts a purchase.	Procurement Cycle
PTO	The Payment Order's document code: its numbers read PTO-…, and budget reports show PTO and PTO-paid totals.	Procurement Cycle
RFQ	Request for Quotation — suppliers are invited to quote; it ends in the CBA.	Procurement Cycle
RTL	Right-to-left text direction, which Arabic needs.	Recommendations
SC	Supply Chain — the department and the approval step (WaitingForSC) that takes an approved request into purchasing.	Procurement Cycle
SOD, SOD1–SOD4	Segregation of duties — the sign-off tiers a Purchase Request passes after Finance; how many depends on its USD value.	Procurement Cycle
SRF	Staff Requisition Form — the request to open a post; hiring starts here.	Recruitment
SRR	Stock Release Request — a request to release items from a warehouse, shown in the application as a Good Delivery Order.	Logistics

Key terms

Term	Meaning	Explained in
Advance / Loan	The two salary-backed requests in Payroll. An advance is limited to half the net salary (up to all of it with a justification) and is deducted in that month's payroll; a loan is repaid in monthly instalments. Loans are paid out of the ordinary cash box; the emergency box covers the part of an emergency loan the ordinary box cannot.	Payroll
Allocation / Allocator	An allocation splits an employee's monthly salary across budget lines by LOE %. The Allocator signs the allocations — the first step of the payroll chain (Allocator → Finance Manager → Country Director) — and cannot sign until every shared employee is fully allocated.	Payroll
Budget Holder	The approver for spending against a project's budget; the code routes this step to the project's program manager (Project.ProgramManager). Signs Purchase Orders, Payment Orders and Jobs — but never a Purchase Request (R6-11).	Procurement Cycle
Budget line	A line of a project's grant budget that spending and salaries are charged to.	Grant
ContextActions	The single endpoint each document uses to move to its next status — sign, approve, refuse.	Procurement Cycle
Core / Warehouse database	The two SQL Server databases: core (NKO_DB, context NKO_DBEntities1) and warehouse (NKO_DB_Warehouse, context WarehouseDBContext). No foreign key joins them; the GRN hands goods over in application code.	Context ERD
Data scope	Which records a user sees in a list — All, Location, Custom (chosen branches) or Default — set per area in SharedPermissions.	Permissions
Destruction	The approval workflow for disposing of (writing off) warehouse assets.	Logistics
Draft employee	An employee record HR has created but not yet approved — Status becomes Approved only at the last onboarding step. Draft and deleted employees are hidden from every query that does not explicitly bypass the AppUser global query filter.	HR Onboarding
E-signature	A user's uploaded signature (AppUserSign). It starts as Pending and HR approves it; until then most workflow steps refuse the user with "Please upload your E-signature." Separate from the PIN.	Security & Permissions
Exchange rate (global / donor)	The global rate (ExchangeRates) values TL and EUR purchase requests in USD and so decides their SOD sign-offs; the application has no way to update it (R7-1). Donor rates (DonorExchangeRate), entered under Administration → Donors, convert salary allocations and purchase-order lines.	External Services
Finding IDs (e.g. R1-9)	Entries in the Recommendations register. Other pages cite the ID next to the problem it describes.	Recommendations
General Settings	The admin screen (/Admin/GeneralSettings) for system-wide settings stored as CommonSetting rows — the allocator, procurement manager, HR and director approvers, timesheet officers, cash boxes, whether e-mail is sent. On a new database it crashes until its 21 rows exist.	First Run
Global query filter	An EF Core filter applied automatically to every query on an entity. Only four have one — AppUser, AppUserSign, Project, BudgetLine — hiding deleted rows and, for AppUser, draft employees.	Database
Justification	A written reason the system asks for when a request leaves the normal path: a provider justification is the other way to create a Purchase Order besides the RFQ's winning provider, an advance above half the net salary needs one, and attendance has its own justification queue.	Procurement
Next user (NextUserId)	The person whose turn it is to act on a document. Together with the integer StatusId it drives every approval workflow; anyone else's action is refused.	Architecture
Permission key	The name of a permission, such as HumanResourceFamilyManagement, checked on an action by [ClaimRequirement("Key")]. Keys are attached to groups and users get them through group membership; there are 219.	Security & Permissions
Position	An employee's job title. Several approvers are found by an exact position name — "Finance Manager", "General Manager" and others — so renaming a position can stall approvals (R6-10).	Recommendations
Ungated	An action with no authorization attribute at all — 44 of the 947. Some are public by design; see R3-2. The API pages give the count per controller.	API
Waybill	The shipping document that goes with released stock; each waybill belongs to a Stock Release Request (Good Delivery Order).	Logistics