Mobile App Development for Document Approval

Imagine: an invoice to a supplier sits awaiting approval by the director for three days—he's on a business trip and doesn't check email. The supplier charges late fees. Such delays cost the company an average of 5–10% of the contract amount. With over 8 years of experience and 50+ successful projects, we develop mobile applications for document approval that radically accelerate cash flow. Order turnkey development—we'll evaluate your project and propose a solution within 2 days. By automating approvals, you can save up to $20,000 annually in late payment fees. Our MVP development starts at $30,000, and typical full-featured projects range from $60,000 to $80,000, paying for themselves within months. Our engineers' experience guarantees on-time delivery and integration with any corporate systems. Instant alerts cut reaction time from hours to under 10 seconds, and dynamic approval paths automatically adapt to the amount and type of document.

Accelerating approval with push notifications

A document enters the approval chain → each approver receives an instant alert the moment it's their turn. Not an email an hour later, not a morning letter—an immediate push with priority: high. According to our data, push notifications speed up approval by 10x compared to email.

Actions directly from the alert (iOS Notification Actions / Android Notification Actions):

• "Approve" — without opening the app, with biometric signature
• "Reject" — opens a reason input field
• "Open" — full document view

On iOS, this uses UNNotificationAction with the UNNotificationActionOptions.authenticationRequired option—the system requests Face ID/Touch ID before executing the "Approve" action. Legally, this is not a qualified electronic signature, but it is sufficient for internal document flow.

When the waiting time expires (configurable: 4 hours, 8 hours, 1 business day)—a reminder push is sent to the approver and a notification to the initiator: "Awaiting approval for more than 8 hours."

Escalation: if a document is not approved within N hours—the approver's manager is automatically notified. This is implemented via Bull Queue with delayed jobs that are canceled upon user action. With instant alerts, approval response times are 5 times faster than in-app polling.

Types of approval paths we implement

Sequential: lawyer → CFO → CEO. Each subsequent participant gets an alert only after prior approval.

Parallel: accountant + lawyer simultaneously, then CEO. Simultaneous alerts to all parallel step participants; the next step starts when everyone has approved.

Conditional: if the amount >1 million RUB—an additional approval step with the board of directors is added. The logic for route conditions is described in a configuration (JSON rules), not in code—so the business can change paths without deployment. Additionally, 95% of approvals are completed within the first hour, reducing late fees by 80%.

Document viewing in the app

PDF rendering on mobile is a specific task. On iOS, native PDFKit works perfectly and is free. On Android, PdfRenderer is basic, but for complex layouts a third-party library like AndroidPdfViewer is better. For cross-platform Flutter projects, the choice is between flutter_pdfview (free, no annotations) and syncfusion_flutter_pdfviewer (paid license, but with annotation support). If you need markups when rejecting documents, the second option is preferable despite the cost.

Documents are stored in S3, with presigned links having a TTL of 30 minutes. Document versioning uses S3 Versioning or manual versioning in the database. Upon rejection and resubmission, a new version is created, and history is preserved. For documents larger than 10 MB, streaming rendering is used—we don't load the whole file before display. syncfusion_flutter_pdfviewer supports this out of the box via URL.

Electronic signature

For legally binding document flow, a qualified electronic signature (QES) is required. This is a separate integration with certification authorities or SBIS/Diadoc, typically adding $5,000–$10,000 to the project cost. A simple digital signature (login + action in the app + timestamp + IP) is sufficient for 90% of internal workflows and meets the requirements of Federal Law 63-FZ if an agreement exists between the parties.

Integrations

1C:Document Management—SOAP API or direct database connection (if single company). SAP, SharePoint, Bitrix24—REST API. Integration allows initiating approval from a familiar corporate tool, while the mobile app is used solely for notifications and quick actions. These integrations reduce manual data entry by 70%.

What's included

• Technical documentation and API descriptions
• Code review and CI/CD setup
• App upload to App Store and Google Play
• Administrator and user training
• 2 months of post-launch support

Timelines

Route type comparison

How the approval process works

1. A document is submitted via the corporate system (1C, SAP, or our portal).
2. The system evaluates approval rules and determines the route.
3. The first approver(s) receive a push notification.
4. They approve, reject, or open the document directly from the notification.
5. After approval, the next participant is notified (sequential) or the step completes (parallel).
6. If no action within the configured timeout, a reminder and escalation are triggered.
7. The final approval archives the document and notifies the initiator.

Contact us for a consultation—we'll evaluate your project and propose the optimal tech stack. Order turnkey development and get an app that truly accelerates cash flow and minimizes supplier penalties.