Masraff for Healthcare

In a single month a hospital might process a same-day consumables order from the ER, a card-paid training booking from the admin team, and a courier dispatch from a polyclinic. Each has a different approver, cost centre and document type. The clinical-adjacent complexity — multiple departments, shift work, multi-location operations, e-Invoice / e-Archive flow — makes spreadsheet-based tracking untenable past a certain size. Masraff standardises the flow by mapping department and organisational hierarchy directly into the expense form.

For consumables, non-pharmaceutical materials and outsourced services, budget-vs-actual tracking is non-negotiable. Masraff's budget module lets you set per-department limits and matches each expense against the limit in real time. Supplier name, invoice number, VAT and non-deductible-expense classifications are captured through custom fields tailored to your organisation.

• Per-department budget with live consumption indicator
• Custom fields for supplier name, invoice number, VAT and KKEG split
• Vendor data flows into ERP supplier accounts — not stored as a parallel master

Note: Vendor master sync and purchase-order push remain on the ERP side; Masraff handles the spend layer, not procurement orchestration.

Masraff is an operating-expense tool. It does not touch patient files, diagnostic records or any clinical data stream — directly or indirectly. That boundary intentionally shrinks the KVKK risk surface. What the system stores is limited to expense, receipt, approval, corporate-card and supplier-account data. Every action — form creation, approval, rejection, card reconciliation — is written to an audit log retrievable at period close or during a financial audit. No patient data is processed; only operational spend.

Role-based access (SuperAdmin, Admin, Accounting, User) lets finance see the whole hospital while a department head sees only their unit. SSO and 2FA align with your existing IT policy.

ER, outpatient, administration, surgery — each department carries its own approval matrix. Masraff's policy module encodes this through role-based rules, threshold-based approval and organisational-hierarchy support. Above a defined amount on non-pharmaceutical orders, an automatic step to the chief physician or administrative director kicks in; a second finance approval can follow. A manager on leave can hand approvals to a peer via temporary delegation.

• Rules by department, grade and title
• Automatic upper-tier approval on threshold breach
• Mobile approval — shift hours don't interrupt the flow

Healthcare groups in Turkey commonly run Logo, Mikro, Netsis, Luca or Orka on the local side, or SAP Business One, SAP ERP, Oracle EBS, Oracle Fusion and NetSuite on the global side. Masraff integrates with these at the expense, invoice, GL-code, supplier-account and KKEG-account mapping level. Closing entries replace manual re-keying. Full breakdown on the ERP integration page.

For the hospital CFO the outcome is visibility — which department spent how much, with which supplier, against which budget, answered in minutes not days. For the chief physician the outcome is control: define a rule once, the system enforces it every shift.