Loading
How it works
See exactly how DPAS routes a payment through your approvers, captures every signature, and seals the result in a tamper-evident document — in English and Arabic.
Request form
Step 1
An accountant fills a versioned request form with the payment details and any supporting documents. The form version is recorded, so an approved request always reflects the exact form it was raised on.
Approval chain — configurable role stages
Step 2
The request moves through the approvers you configure — accountant, finance officer, executive, director, and any document authorizers. Each stage records a decision, a signature, and any comments. The chain is yours to define: reorder the roles, add stages, or require a director's approval on every payment.
Sealed voucher (hash-locked PDF)
Step 3
On final approval DPAS renders a PDF carrying every signature and stamp, then records a SHA-256 hash of it on the request and in the audit log. Re-hashing the file later reveals any change, so the record is tamper-evident. The signed document lands in the in-app inbox and is emailed to the parties.
Why DPAS
Every decision is recorded with who signed and when, alongside a hash-locked document — so answering an auditor takes minutes, not days.
Requests move through a defined chain instead of sitting in inboxes and paper trays, so approvals happen in hours.
The whole product and every generated document work in English and Arabic with full right-to-left layout.
Most organizations go live quickly: we configure your approval chain and request forms during onboarding, and our team walks the first requests through with you.
Yes. The approval chain is configurable — reorder roles, add stages, and choose whether a director's approval is required. Changes apply to future requests.
The chain is defined per organization, so it adapts to how you actually approve payments rather than forcing a fixed path.
Book a demo and our team will walk your approval workflow through DPAS end to end.
