General approvals
Any request that needs a decision — system access, policy exceptions, headcount, procurement. Describe it once and Mizan turns it into a formal memo.
Loading...
Approval workflows and electronic signature
Mizan turns any approval request into a formal memo, routes it through the people who need to say yes, then builds and sends the document for signature. One engine for every approval your organisation runs — not just the financial ones.
Single sign-on with your existing organisation account — no separate password to set up. Access is granted by your administrator.
Everything you would use a standalone e-signature tool for, except the paperwork arrives already written and already approved.
No one drafts the agreement by hand. The approved memo becomes the signature document, with the right fields in the right places.
Each party is emailed their own signing link in the order you set, and reminded automatically while the request sits unsigned.
Signature is captured through Documenso and the completed PDF is stored against the record it belongs to.
General approvals handle anything you can describe. The rest are purpose-built for the requests that come with their own paperwork.
Any request that needs a decision — system access, policy exceptions, headcount, procurement. Describe it once and Mizan turns it into a formal memo.
Vendors submit invoices through their own portal. The document is read automatically, matched to the vendor and raised as an approval.
Ask questions across your requests and documents, and get answers grounded in your own records.
The same four steps behind every approval, whether it started as an invoice, an investment deck or a sentence typed into a form.
Describe the request, or drop in the source document. Mizan reads it and pulls out the details that matter.
A formal approval memo is drafted for you — header, body, figures and justification. Edit anything before it moves.
Multi-level chains and approver groups send it to the right people, who decide from their inbox or straight from email.
Mizan builds the signature document, collects every signature in order, and files the signed PDF against the record.
Controls are part of the workflow rather than a report someone assembles afterwards.
Roles and permissions decide what each person can open, edit and approve — down to the individual module.
Every submission, edit, approval, rejection and signature is written to the audit log with who did it and when.
People are notified the moment something needs them, and reminded automatically while it sits unanswered.
Approver groups and multi-level chains mean a request never stalls because one person is away.
Built in-house
Mizan is designed, built and run by Unifrutti's own engineering team. That means the approval rules, the memo templates and the signing flow are shaped around how the business actually works — and when something needs to change, the people who can change it are in the building.
Visit Unifrutti-Techunifrutti.tech
Sign in to Mizan to see what's waiting on you.