Ason E-RP
From the first line of a quotation to the last day of a warranty — one system for the whole firm.
Ason E-RP was written for the small and mid-size company that works in the field and keeps a real commercial ledger behind that work. Eighteen screens run inside one application: every record from CRM to accounting sits in the same database, behind the same permission gate.
"What is installed at this customer?" has an answer
The invoice says one line: Camera System, qty 1. On site there are five cameras, one recorder and one switch. Ason E-RP keeps a separate customer equipment ledger: which device is at which customer, its serial number and MAC address, when it was installed, when the warranty ends. The service team arrives knowing what it will find.
A quotation is written once, and every revision keeps its own document
A proforma starts as a draft, is published, and is revised when needed. Each revision's own PDF is prepared on the server and stored: the third revision you sent the customer opens exactly the same six months later. The exchange rate comes daily from the Turkish central bank and is proposed on the document; you can change it, but the rate used and its date stay inside the document. Amounts are also printed in words, and footnotes print in red.
Work waiting for approval does not get lost on someone's desk
There is one shared workflow core: approvals from every module collect in a single "My Work" screen. You can delegate, put a timeout on a step, and approve similar items in bulk. Process definitions are versioned — work that started yesterday runs under yesterday's rules.
Accounting is its own ledger, not a by-product of sales
Double-entry bookkeeping, trial balance, income statement, receivables, journal and fiscal period close are built in. Modules talk through events, and the same event arriving twice does not create a second entry. Inventory runs on FIFO cost, and the product card carries customs code, origin and barcode — not fields bolted on later for a company that imports goods.
One calendar for every due date
Subscription renewals, digital asset expiries, purchasing due dates, project milestones, to-dos, agreement targets — all of it appears on one calendar as eight separate layers, each badged with the module it came from. What falls due this month is on one screen.
Permission is not hiding a menu item
Removing a screen from the menu does not protect it; in Ason E-RP the gate is on the server. A permission the system does not recognise is refused, not allowed. The audit log is append-only and its entries are hash-chained; fields such as national ID and IBAN are masked in the log. Two-factor authentication (TOTP) can be enabled, and the session key is never kept in browser storage.
No interface that lies
A capability Ason E-RP does not have is never drawn as though it does. On a channel that is not connected, no reply box appears — the screen says what is required instead. Viewing a record does not change it, an unrecognised permission is refused, and an unexpected error is met with its reason rather than a blank page. These are the code's own rules, not later additions.
18 modules, one application
CRM, sales, purchasing, inventory, accounting, projects, proformas, workflow and more; no separate licence, no separate install.
Equipment ledger
Serial number, MAC, installation date, warranty end: "who has this serial number" is an answerable question.
Tamper-evident audit trail
An append-only, hash-chained log with sensitive fields masked.
- Modules: Dashboard · My Work · To-dos · Calendar · Messaging · Map · CRM · Opportunities · Sales · Proformas · Agreements · Social Media · Purchasing · Inventory · Accounting · Projects · Administration · Plugins
- Identity: local password or single sign-on with Ason ID; two-factor authentication (TOTP)
- Authorisation: role-based permissions from a single source; unknown permission is refused
- Architecture: multi-tenant, every query scoped to its tenant
- Money: integer minor units — no accumulating rounding drift
- FX: daily central-bank rate proposed on the document; the rate used is stored with it
- Documents: server-side PDF, a separate document per revision; attachments up to 20 MB with the type verified from file content
- Data transfer: CSV export (Excel upload is deliberately refused)
- Interface: Turkish; desktop and mobile; light/dark theme with optional time-of-day switching
- Turkey-specific fields: tax number, national ID, customs code, origin; privacy-aware search and logging
Frequently asked questions
Do we buy the modules one by one?
No. All eighteen screens are part of the same application. A user's role decides which screens they see; there is no separate licence or install.
Can we issue e-invoices?
No. Ason E-RP keeps the sales invoice in its own ledger but does not connect to an e-document provider. You continue to use your existing solution for that.
Can we upload Excel files?
No — and this is a decision, not a gap. An Excel file carries compressed XML and brings formula and file-safety problems with it. Data transfer is done with CSV.
What happens if a user changes a record by mistake?
The audit log shows who changed what and when. The log is append-only and its entries are hash-chained, so nothing can be quietly corrected afterwards.
Is there an English interface?
Today, Turkish only.
Let's Talk About Your Project
Contact us for free technical consulting.