Visual designer
Build the workflow as a node diagram: steps, connections and rules, without touching code.
Approval workflows
Every approval reaches the right person, on time.
Draw the path a document such as a purchase order follows: who approves, under what condition and within how many hours. MKA builds each approver’s inbox, tracks the SLA and keeps the history attached to the document.
Without MKA
- Approvals are requested over chat and nobody knows whose desk the order is on.
- A small purchase goes through the same five sign-offs as a big one.
- When auditors ask who approved, you dig through old emails.
What you’ll measure
Average approval time
9,5 h−14 h
from submission to final approval
Approvals within SLA
92,6 %+11 pts
Pending tasks
14−23
across all inboxes
Failed jobs
0,4 %−1,1 pts
background jobs
Sample indicators with illustrative data. In MKA they are computed live from your operation.
Try it right here
The buyer submits a purchase order and the manager approves it from his phone.
On the left, the buyer in the back-office; on the right, the general manager’s phone. Add the management step "only if amount > Bs 50,000", submit PO OC-2231 and watch it reach the phone with its SLA running: reject with a comment, reopen and approve it while the buyer’s timeline updates. With OC-2232 (Bs 12,300) the step is skipped automatically. Click "Watch it run" to see it play.
Example flow
A purchase order that routes itself… down the right path
Step 1/5
The purchase is entered
The requester creates the purchase order and submits it for approval.
Purchasing & suppliersBenefits
Why Approval workflows in MKA
Roles and permissions per step
Each step requires a specific role or permission; only people who have it see the task.
Smart conditions
A step can apply only when a condition is met, such as an amount above a threshold.
SLA in hours
Each step has its deadline, and the inbox shows how much time each task has left.
History on the document
A timeline with every approval, rejection and reopening, visible from the document itself.
Scheduled and background jobs
Cron-scheduled tasks and a process center to watch, retry or cancel heavy jobs.
In detail
Everything included
Workflow design
- Visual workflow editor as a node diagram
- Steps that require a role or a permission
- Per-step condition so it only applies when relevant
- SLA in hours per step
- Field-validation rules before moving on
Approval
- "My pending tasks" inbox for every approver
- Document timeline and approval history
- Reopening a rejected workflow
Scheduled tasks
- Cron-based tasks that can be enabled or disabled
- "Run now" button
- Log of every run
Process center
- Status of every background job
- Retry or cancel jobs
- Error details when something fails
- Result download when finished
All-in-One
Connects with
Data flows between modules on its own: no integrations, no exporting or importing.
Purchasing & suppliersFrom request to payment, with partial receptions and lots.Petty CashFixed funds and expense reports without paper envelopes.Orders & shipmentsOrders, partial shipments and consolidated invoicing, all linked.Notifications & collaborationFollow documents, mention your team and know instantly.Audit & securityTamper-evident audit trail, fine-grained permissions and 2FA.
FAQ
Do I need a developer to change a workflow?
No. Steps, roles, conditions and SLAs are configured in the visual editor by an administrator.
What happens if someone rejects?
The rejection is recorded in the document history. The requester can fix it and reopen the workflow, and the new round is recorded too.
More in Platform
See Approval workflows with your data.
In 30 minutes we walk through your real flow: from sale to invoice, from stock to journal entry.