Dooap Standard Product Description

 

1 General Overview

1.1 Executive summary

Dooap is a mobile-first, cloud-native Accounts Payable (AP) automation solution built exclusively for Microsoft Dynamics 365 Finance & Operations and Dynamics AX2012 (CU12 and CU13). Running natively on Microsoft Azure, Dooap automates the entire invoice lifecycle — capture, coding, matching, approval, posting, and payment — while keeping master data, controls, and the audit trail anchored in Dynamics.

This document sets out the product standards of Dooap in detail and serves as a reference to the features it offers and the benefits they deliver.

It is written for the owner of the end-to-end Accounts Payable process — the person accountable for its efficiency, functionality, and compliance. In most organizations, AP combines business requirements owned by Finance with technical capabilities delivered by IT or a solution partner.

1.2 Why Dooap

Dooap replaces manual keying and rule maintenance with AI-driven automation — shortening invoice handling time, strengthening compliance, and giving Finance real-time visibility across the entire AP process.

1.3 Functionalities

Core capabilities at a glance:

• Invoice capture
  • Dooap Capture — built-in, LLM-based invoice data capture
  • Integration with any third-party scan-and-capture solution (add-on)
  • Support for any e-invoice or EDI format, or vendor-portal integration (add-on)
• Approval workflows
  • Approval workflows driven by signing limits, dimensions, or position hierarchy
• Non-PO coding aligned to your Dynamics account structures
• Automated 2- and 3-way purchase order matching
• Zero-configuration automation powered by AI (possible add-ons)
• Native mobile apps for iPhone and Android
• Dooap Analytics — dashboards for compliance, process performance, and key KPIs, powered by Microsoft Power BI
• Secure invoice archiving in Azure

 

2 Example Process

From arrival to payment, Dooap moves every invoice along a consistent, automated path. The steps below outline a typical end-to-end flow; each stage can run automatically or pause for a manual checkpoint, depending on your controls.

• Invoice Capture
  • Paper invoices are scanned in house and emailed to Dooap Capture.
  • Email invoices are forwarded to Dooap capture.
• Invoice Arrival
  • Invoices arrive in Dooap with all data captured.
  • AP can adjust any captured value — purchase order number, invoice type, vendor, receiving company, or dates.
  • AP can accept or adjust the automated coding and matching suggestions, or process the invoice manually.
  • Invoices with no validation errors can skip the AP check and route straight to approval.
• Workflow
  • Invoice type determines how an invoice is processed:
    • PO invoices are matched against the purchase order(s) and, where required, product receipt(s) in Dynamics (2- or 3-way matching).
    • Non-PO invoices are coded to ledger accounts or project numbers.
  • Matching and coding can be handled by AP or, during the workflow, by reviewers and approvers.
  • PO invoices that match within tolerance can be approved automatically under the 2- or 3-way matching policy.
• Approved Invoices
  • Approved invoices are transferred and posted to Dynamics 365 Finance automatically.
  • If preferred, AP can switch to manual transfer for a final check before posting, and send invoices back to approvers for correction.
• Transfer to Dynamics
  • Non-PO invoices are transferred to invoice journals, which post automatically.
  • PO invoices are posted automatically through the Pending vendor invoices form.
  • Dynamics workflows are not required – the full approval trail is documented in Dooap.
• Payment
  • Invoices are paid using standard or third-party Dynamics payment functionality.

3 Features and Functions

3.1 Master data from Microsoft D365FO/AX2012

Master data stays authoritative in Microsoft D365FO/AX2012 and syncs to Dooap through the Change Entity Framework, so updates made in Dynamics reach Dooap within minutes. Selected data is validated in real time at the moment it is used — account structures when coding invoices, and product receipt information during matching.

Synced information:

• Dynamics version information
• Users
• Companies/Legal Entities
• Vendors
• Vendor bank accounts
• Vendors default dimensions
• Tax codes
• Ledger accrual identification codes
• Payment Methods
• Payment Terms
• Cash discounts
• Charge codes
• Currencies
• Purchase order details
• Produce receipt details
• Miscellaneous charge codes
• Accounts payable parameters
• Main Accounts
• Dimensions
• Projects including activities, categories, resources and line properties

Account structures are validated in real time whenever coding is applied to Non-PO invoices, and re-checked for changes at every step of the workflow.

Purchase order and product receipt data is refreshed in real time during matching, and any PO changes are validated before the invoice is posted.

3.2 Invoice arrival

Dooap Capture

Dooap Capture is Dooap’s proprietary invoice data capture, built on a large language model (LLM). Invoices are sent to the cloud for capture, with results available in Dooap within minutes. AP users can correct captured values or fill in anything missing. Capture learns globally across all invoices, so there are no per-vendor templates to train.

Key fields selected by Dooap Capture include the following:

• Invoice Number
• Invoice Amount
• Vendor
• Invoiced Company (Mapped to your dynamics legal entity)
• Invoice Date
• Due Date
• Purchase Order Number
• Currency

Invoices can be delivered to Dooap Capture by email or on paper. Supported formats: .pdf, .jpg, .tiff, .doc/.docx, and .xls/.xlsx.

Different policies are available for processing the files:

• Multiple invoices in one email
  • Invoices include attachments within the same file.
  • Multiple invoices can be sent simultaneously in one email.
• One invoice per email
  • All documents in one email are scanned into one invoice.
  • The email body can also be included as a scanned page.

Once scanned and validated for mandatory fields, invoices appear in Dooap for AP pre-processing, where users can adjust captured information if needed.

Priority invoices: users can flag an individual invoice — or an entire vendor — as priority, moving those invoices to the top of the processing queue.

Invoice linking: related invoices can be linked together, for example a credit note to its original invoice.

Other formats for invoice arrival

Invoices can also be

• scanned by in-house personnel,
• scanned by other external service provider or
• delivered as an e-Invoice from a service provider.

In these cases, invoice documents are delivered to Dooap over secure file transfer (SFTP).

Scanning produces two files for the invoice import: the data in XML or CSV format and the invoice image in PDF format. These two files must be named similarly to link the data to the image.

Dooap supports any e-invoice or EDI format you need. The formats below are available out of the box; any other format can be added as a customer-specific integration, for which a build fee may apply.

• UBL 2.3
• TEAPPS 2.7/3.0

Manual import

PDF invoice images can be imported into Dooap directly from the interface. Vendor and company defaults populate automatically; remaining details are keyed in.

It is also possible to copy a previously processed invoice to a new invoice.

Payment request

Authorized users can create self-billing invoices, which then run through the standard approval workflow.

3.3 Duplicate Invoices

Duplicate invoice numbers are flagged in red for the same vendor and accounting period. Dooap follows the Dynamics Accounts Payable duplicate-number setup per legal entity.

Cross-company duplicate detection: Dooap can also detect duplicate invoices across companies within the same fiscal year, and administrators can configure whether a duplicate raises a warning or a hard error.

VAT number validation: Dooap can compare the vendor’s VAT registration number on the invoice against the vendor master data and warns users when the two do not match.

3.4 Users and authentication

Dooap uses single sign-on (SSO) for streamlined access management, with Microsoft Entra ID as the identity provider. Entra ID verifies users and applications in your organization’s directory and issues security tokens on successful authentication.

To access Dooap, users need a Microsoft Entra ID account linked to the D365FO/AX2012 user table.

Users do not need Dynamics access rights — they only need to appear in the user table. New Dynamics users import into Dooap at the next master-data sync. A Team Member license is recommended for users who access Dooap only (see Microsoft multiplexing rules, which apply to all AP automation solutions).

Users disabled in Entra ID can no longer sign in to Dooap. Users can also be disabled directly in Dooap, which affects only their Dooap access.

3.5 User rights

The default user roles are listed below. Roles can be customized in Dooap, and a user can hold multiple roles.

User role	Description
Reviewer/Approver	Has access to Dooap through web browser and mobile app. Can review, code and match invoices that are assigned to them, add attachments, set their own substitute, or send an invoice back in workflow. Can only approve invoices if approval limit is granted.
Accounts Payable	In addition to previous, has access to all company invoices, can import or archive invoices, edit header data, manage approved invoice transfer to Dynamics and define/start/recall an approval workflow.
Admin	Can adjust dooap configuration, set default values, and edit roles and approval limits. Can impersonate a user (activities are logged).

3.6 Approval rights and invoice visibility

Only a user with sufficient approval limits can complete the workflow and approve an invoice for posting and payment. Approval rights are set in the Admin section, or signing limits from D365 Finance can update them automatically — this requires the user ID and employee record to be linked in D365.

For PO invoices, automated 2- or 3-way matching can bypass manual approval; auto-approved invoices still appear in the approver’s previous invoices.

By default, users can access only their D365 default legal entity. This governs invoice visibility and keeps processing separated across multiple legal entities; access to additional entities is granted in Dooap Admin.

By default, invoice visibility is limited to the AP team, users in that invoice’s workflow, and users with special search permissions. Viewing an invoice image is a logged action.

Invoice image visibility can be further restricted to workflow participants only, preventing non-essential access to sensitive information. Classification can be manual or automated from incoming invoice data.

3.7 Approval Workflows

The approval workflow ensures no invoice is paid without validation by authorized people. By default, only authorized users can change a workflow, and additional review steps can be added as needed.

The following workflow automation features are available; some combinations have limitations.

• Manual workflow selection
• Split workflow for simultaneous approval
• Additional consecutive approval
• Default approver based on vendor
• Preset workflows, company specific. Defaulted from company, invoice type or vendor
• Purchase order requestor / orderer imported from Dynamics based on invoice data
• Conditional approval for invoices above threshold
• D365 position hierarchy additional approval for invoices above threshold
• ML predictions based on invoice data and history
• Dimension based approval based on invoice coding
• Changing approval step to another user
• Returning invoice to AP or previous user
• Group approval, with shared invoice visibility and approval right
• Auto-send to workflow, when invoice data passes system validation rules
• Auto-approval for PO invoices matched within tolerance
• Substitution, where approval rights and invoice visibility are shared
• Mobile approval on the go
• Email reminder when invoices wait approval

3.7.1 Workflows powered by Machine learning

Rather than maintaining complex rule-based automation, Dooap uses ML to automate both workflow routing and coding.

A self-learning algorithm runs in the background, finding correlations across invoice data, coding, and workflow history to surface the most likely options — in real time, as you process each invoice.

Custom AI Actions: beyond the built-in AI, Dooap can run custom AI Actions at the invoice-header level — for example, calculating due dates or cash-discount dates that differ from the vendor master, or performing more advanced invoice-number validation and data enrichment. AI Actions are designed and enabled together with Dooap Support, and are composed, governed, and audited in Dooap Studio — Dooap’s AI trust layer (see section 4).

Every manual correction feeds back into the model, continuously improving prediction accuracy as your process evolves.

3.7.2 Dimension based approval

Dimension-based approval shapes the approval matrix from the invoice’s coding. Each distinct dimension value creates a mandatory approval step, and only authorized users can approve their respective coding lines. The controlling dimension is configurable per legal entity.

It is activated per invoice type, allowing separate approval processes for PO, project, and more complex ledger invoices.

A default approver per dimension can be set via the dimension-value “Owner” in D365 Finance, improving automatic approver selection while still allowing manual changes.

3.8 Coding

Invoices can be coded at any point in the workflow. Validation rules can require coding to be completed before the AP step is closed or during approval.

Coding follows the account structure defined in Microsoft D365FO/AX2012 and can be entered as a gross or net amount (Non-PO).

Coding can be done to:

• Main Dimension + Dimensions based on Account structure, including advanced rules
• Projects + Categories based on Dynamics Project setups

Sales tax and item sales tax groups are supported as defined in D365.

For US market Vertex Tax integration is also available as an option.

Supported functions in coding:

• Quick search of input value or description, using partial match
• Account structure validation and sales tax calculation per D365/AX2012 setup
• Account structure advanced rules
• Intercompany ledger journals (posting a coding line to another legal entity)
• Accrual schemes (automatically splitting a coding line to multiple open ledger periods)
• Copying coding from previous/current invoice
• Copying coding from Excel spreadsheet (multi-line or by column)
• Coding lines generated automatically from the e-invoice/XML data file (activation via Dooap support)
• Modifiable transaction text/description, posted to general ledger
• Coding predictions by Machine learning
• Vendor main account and dimension defaults from D365/AX2012
• Support for up to 250 coding lines per invoice
• Main account limitation per user role
• D365 Finance Derived Dimensions (Currently 08/2022, D365 overrides selections done in Dooap if the setups of derived dimensions is set to prefer override even though it would not be mandatory)

3.8.1 Coding powered by Machine learning

ML offers coding predictions automatically, comparing the current invoice data against your processing history.

Manual corrections are fed back into the model to sharpen future predictions. Users can pick from up to three suggestions or let the system auto-select the best one, and high-confidence predictions can be applied automatically at import.

ML can also predict sales tax groups from coding-line input.

3.9 Recurring Invoices

Recurring invoices are generally used for two different purposes:

• Self-billing or Contract related invoices (e.g. rents, subscriptions without a physical document)
• Recurring Invoice matching (e.g. insurance, electricity) (Released on a future date)

Self-billing templates create invoices automatically on a preset schedule — ideal when you pay against an agreement (for example, an annual contract) without receiving a physical invoice each month.

3.9.1 General settings

Recurring invoices are Non-PO invoices (base type in settings). User can fill the default values for the invoice template like header information, coding, invoice picture and scheduling. These values will be used for every created invoice.

Invoice date will be defaulted with the date of creation. This will also be the posting date. Invoice number is formed from the set base value and a sequence number. The sequence number is added as a continuous number. The "next" value of the sequence can be defined. e.g. invoice base number in recurring entry is "Rent Unit 1, 2023". The next sequence number is set to "2". The next created invoice will thus receive the invoice number of "Rent Unit 1, 2023-2".

Attachment is mandatory as it is used for invoice picture for the created invoices. Invoice picture will be created only from PDF and from first PDF which is found from database. Attachments are not picked automatically, if attachment needed for the invoice it needs to be attached for created invoice afterward.

3.9.2 Scheduling

Schedule is maintained for each recurring invoice. This means the timeline how often a selfbilling invoice is created from the template. Contract number is defaulted to contract field for created invoice. Schedule needs to be applied to the recurring invoice. When schedule is applied you can see what is your currently selected schedule. NOTE! Scheduling uses UTC timezone
When recurring invoice template status is changed to active, it will generate new invoices from the template according to the schedule.

3.10 Matching of Purchase Order Invoices

3.10.1 Matching Policy

Dooap supports 2- and 3-way matching of purchase order invoices, based on the PO line setup in D365/AX2012. Both policies can apply on the same invoice.

Three-way matching lines require a product receipt to be posted in Dynamics.
Two-way matching invoices can be matched without a product receipt.

During matching, invoice totals are compared against PO line-level data in D365/AX2012, with invoice lines drawn from the purchase order and product receipt. By default, Dooap matches automatically to a product receipt with the same total; otherwise, all PO lines are offered for matching.

One invoice can be matched to:

• One or multiple purchase orders
• One or multiple product receipts
• Specific lines on a PO/PR
• Specific quantity on any of the available PO lines

Matching invoices can be set to pass approval automatically under the 2- or 3-way policy on the PO line in D365 Finance. In that case, an invoice stops for approval only if it fails to match or the unit price has changed.

The last product-receipt date for the selected PO is shown on the invoice header, helping users spot and sort invoices with recent changes that may now be matchable.

Newly arrived PO invoices can be placed in a “waiting” mode, where Dooap keeps attempting an automatic match for a set period before escalating to AP for manual matching.

3.10.2 Adjustments to Unmatching Invoices

If an invoice falls outside the specified tolerance, the user adjusts the matching details. In Dooap you can change:

• Allocated purchase order(s) or product receipt(s)
• Matching quantity
• Unit Prices
• Sales taxes
• Miscellaneous Charges (Freight, Hazmat fees, etc.)

Miscellaneous charge codes are pulled from Microsoft D365FO/AX2012 or added manually. Dooap supports fixed and percentage charges allocated by net amount, covering both charges paid to the vendor and internal cost reallocations.

A configurable tolerance can post rounding differences automatically to D365/AX2012 charge codes.

Price-unit changes, warehouse unit conversions, line discounts, and sales tax codes follow the Microsoft D365FO/AX2012 setup, and sales taxes are rounded automatically.

Locking a matching line: a purchase order invoice line can be locked so that automated matching or re-fetching PO lines will not overwrite manually adjusted quantities or prices.

3.10.3 Consideration with Purchase Order Invoices

By default, PO invoices post automatically to Dynamics through the Pending vendor invoices form. Using Dynamics workflows for a second approval is possible but not recommended.

As a thumb rule, PO invoices are posted as-is with the purchase order details. This includes

• Line item coding
• Project
• Fixed asset item

Certain PO fields can be modified in Dooap, including procurement category accounting distributions, method of payment, and cash discount code. Users can also add a procurement-category line that was not on the original purchase order — Dooap generates the accounting distributions automatically, and any invoice with a manually added line is routed for approval (activation via Dooap support).

Unique product receipt numbers are recommended, as duplicate product receipt numbers may cause problems with matching. Multiple, simultaneous invoices for the same PO are supported, and require quantity to be released from an invoice, before it can be allocated to another invoice.

During the transition from Dynamics standard AP, or a third party AP tool to Dooap, PO lines partially invoiced outside of Dooap are not counted towards invoiced matching quantity in Dooap and must be manually allocated. By default, Microsoft D365FO/AX2012 will prevent posting of over-invoiced quantities. Actual remaining quantity on PO is shown during matching.

3.11 Touchless invoice processing

Dooap offers automation at every major processing step. Combined, these settings enable fully touchless, end-to-end invoice processing — as illustrated below.

Each step has customizable validation rules per organization and vendor, so you can fine-tune the process to your needs.

• Header data is populated from the scanned/einvoice file at import.
• Based on invoice data, coding is added from vendor defaults, or from an AI suggestion. PO lines are automatically matched to a PO invoice.
• Workflow is selected using one of the automated methods available.
• Invoice is sent to workflow automatically, if validation is passed (Auto-AP)
• Non-PO invoice below a selected amount threshold and PO invoice passing 2-way or 3-way matching is auto-approved.
• Invoice is posted automatically and made available for payment. (Auto-transfer & Auto-post)

3.12 Email notifications

Email notifications go to users with at least one invoice awaiting approval, on a customizable schedule (for example, daily). The notification address can differ from the AD login email.

3.13 Delegation

When a user is away, a substitute from the same legal entity can be assigned to approve invoices on their behalf; main users can bypass the same-company restriction.

Substitutes gain temporary access to the user’s view, extending their own invoice visibility and approval rights for the task. They can process current and future invoices, and anything they approve stays in the original user’s history for review. All delegate actions are logged.

Restrictions prevent substituting for another person in the same invoice’s workflow. Delegation can be chained across multiple accounts, and a substitute must belong to the same company unless an admin authorizes otherwise.

3.14 Localization and language

The Dooap web and mobile applications are available in the following languages:

English, French, Spanish, German, Portuguese, Finnish, Swedish, Norwegian, Danish

Number and date formats are available in US, European, and Australian styles, configurable per user.

3.15 Audit trail and comments

Every invoice keeps a detailed history log. Key data changes and workflow actions — such as approvals — are recorded with a username and timestamp, and for selected fields (like a vendor account change) both the original and new values are stored.

Comments and replies can be added to an invoice at any time and appear below the invoice header.

3.16 Invoice picture and attachments

Attachments can be added in xls, xlsx, csv, tiff, tif, jpg, jpeg, and pdf formats, with US-ASCII file names. They are stored alongside the invoice image in Dooap’s Azure cloud storage.

A Dooap invoice can be opened directly from a link in vendor transactions (D365FO/AX2012). Accessing the invoice-image link requires the “Dooap” user group on the user, plus the appropriate viewing permissions in Dooap.

An entity called “DooapInvoiceLinks” is installed as part of the standard package. This table can be used for 3rd party reporting, in order to directly open Dooap invoice view from the report. Users also need permissions in Dooap to be able to view the invoice.

3.17 Document transfer to D365FO

By default, invoice images and attachments are stored and backed up in Dooap’s Azure cloud storage. Optionally, a copy can be transferred to D365 blob storage, after which the files appear in D365 as attachments — on the vendor invoice journal’s vendor line (Non-PO) or on the vendor invoice (PO).

Document transfer requires the storage to have sufficient capacity and file size limit. Implementation of this feature requires setup and maintenance from Dooap development team, therefore activation is agreed during onboarding. The required key vault setup is maintained by Dooap, which requires system administrator permission in D365. Files exceeding 100Mb are not supported.

3.18 Dooap Capture - Additional details

Supported capture languages

• LLM based Capture supports basically all languages including but not limiting: Arabic, Chinese, Danish, Dutch, English, Filipino, Finnish, French, German, Greek, Hebrew, Hindi, Indonesian, Italian, Japanese, Korean, Portuguese, Russian, Spanish

• Data capture covers the first 10 pages of each invoice as most commonly necessary data is in the first few pages. Recapture can be triggered through Dooap Studio for larger invoices where all pages need to be read for example to line capture.

Supported file types

• File types: PDF, JPEG, TIFF, PNG, Word, Excel
• File size: Max. 50Mb

Attachment processing

Email content	Output	Note
One attachment file (Any supported format)	One invoice
Multiple attachment files (Ex: PDF + Excel + Word + JPEG)	One invoice (PDF) with attachments	PDF shown as main invoice and the rest as attachments.
Multiple PDF attachment files	Multiple individual invoices	System splits the batch-PDF to separate invoices
1 PDF attachment file incl. multiple invoices	One invoice	Auto separation coming in future release
No attachment files – Invoice data as body text	One invoice	Email body text as invoice image

4 Dooap Studio

Dooap Studio is a separate, optional product that layers on top of Core Dooap as an AI trust layer for finance. It lets teams compose AI Actions — multi-step workflows that read, code, match, and post invoices — while keeping every uncertain decision under human control. Work that falls below a confidence threshold you set stops automatically, routes to a person, and is recorded in a full per-decision audit trail, so automation can safely take on more of the queue over time. Dooap Studio is grounded in your own data, matching new invoices against years of your postings, and is enterprise-ready (SOC 2 Type II, GDPR, EU and US hosting).

• Composable AI Actions: build automation as small, named, typed steps — Agent, OCR, Code, Switch, Tool Call, and more — choosing the right model for each step.
• Confidence gates: results below your set threshold stop and route to a human for review instead of posting automatically.
• Full audit trail: every reason, tool call, parameter, and result is logged and inspectable, run by run.
• Governed tool perimeter: connect any OpenAPI or MCP-based service as reusable tools; agents can reach only what administrators authorize.
• Safe iteration: auto-versioning, draft-alongside-live, dry-runs on real data, and evaluations against datasets, with one-click promote and roll-back.
• Dooap Shepherd: describe an Action in plain language and Shepherd drafts it, previews it, and waits for your approval before anything changes.

5 Transfer to Microsoft D365FO/AX2012

Approved Non-PO invoices are transferred and posted automatically, one invoice per invoice journal, while approved PO invoices post through Pending vendor invoices. If posting hits an issue, users are alerted — unposted PO invoices appear in the pending invoices table and Non-PO invoices in an open invoice journal.

Automatic posting can be disabled when final adjustments are needed in Microsoft D365FO/AX2012. Prepayment invoices are held from posting automatically to allow prepayment allocation.

Dooap invoices post under a dedicated invoice journal type, created during onboarding in Microsoft D365FO/AX2012 as DOOAP. The voucher series matches your existing AP invoices.

5.1 Transfer to D365/AX2012 and Payment

Once approved in Dooap, invoices are transferred and posted to Dynamics automatically. Any invoice with a validation warning will wait for manual correction and transfer, and auto-transfer can be switched off if preferred.

For manual transfer, AP can validate invoices one by one for QA or batch several into a single transfer. The system runs a final validation before any transfer; if more information is needed, invoices can be sent back into workflow or corrected on the spot.

If the selected posting period is closed in Dynamics, the user is alerted and the posting date moves automatically to the next open period.

Main account validity: Dooap validates the invoice posting date against main-account validity periods and alerts users when the date falls outside the allowed range. (Not supported on AX2012.)

Transferred invoices are paid through standard payment methods in Microsoft D365FO/AX2012. For bank connectivity, Dooap offers a Microsoft-certified payment automation module supporting 600 banks worldwide — contact Dooap sales to learn more.

Payment details flow back to Dooap once an invoice is settled by payment journal, settled manually, or reversed in D365 — updating the payment voucher, status, and payment date on the Dooap invoice. (Limitations: utilized cash discounts are not reported to Dooap; this feature is not available for AX2012.)

5.2 Customer specific fields

For customer-specific needs, up to three extra fields can be added at the invoice header level. Each can be mapped directly from invoice data (XML) or entered manually, and transferred to any available header field in the D365/AX invoice journal or Pending vendor invoices form.

 

6 Dooap Analytics

Dooap Analytics runs on Microsoft Power BI, with the data model connected directly to Dooap’s database so no information leaves the Azure cloud.

Alongside a broad set of ready-made KPIs and reports, users get Fast Close — an efficient way to accrue invoices still in workflow with a single journal.

The Power BI app is published by Dooap, with access granted per user. Each user viewing the reports needs a Power BI Pro license. Dooap maintains the data model and refreshes it against the production database eight times per day (a Microsoft limitation).

As an add-on, customers can request direct database access to build their own reports, controlling how often data is queried and which tools are used. Because queries run against a real-time replica, this does not affect production performance.

Dooap Analytics includes four dashboards, each with multiple KPIs and drill-through:

• AP Tools — daily and periodic Accounts Payable functions
• CPO — financial KPIs and AP process efficiency
• Vendor Analytics — vendor-related bottlenecks and discrepancies
• Process Automation — automation bottlenecks and performance levels’
• Procurement — procurement-cycle performance

7 Mobile Application

The Dooap mobile app is available on iOS from the App Store and on Android from Google Play. Authentication runs through Azure AD, which also secures real-time communication with Dooap and Microsoft D365FO/AX2012.

The app is localized in English, German, and Finnish.In the Dooap mobile app, invoices are presented as a stack of cards — flip through the deck to find one and dive in. Users can review header details next to a full-size, zoomable PDF of the invoice and its attachments.

Users can review and adjust the workflow, redirecting invoices for additional approval when needed. If an invoice needs a final touch from AP, they can add comments and send it back.

The app also lets users assign a delegate when they are away, or process invoices delegated to them.

With desktop-level, real-time coding validation from Dynamics, users can edit both ledger and project coding on mobile. Dimension values appear and are searchable in plain text, and for PO invoices the matching data can be reviewed before approval.

 

8 Technical Requirements

As a browser- and mobile-based SaaS platform, Dooap requires a stable internet connection. Performance also depends on the latency between Dooap’s Azure application server and the client’s D365/AX2012, and on D365/AX2012 performance overall.

Dooap does not support third-party or ISV customizations unless agreed separately. The customer or their Dynamics partner is responsible for the D365 setups and parameters governing any business process that affects vendor-invoice posting.

Dooap service status can be monitor in the following page: http://status.dooap.net/

Azure service status can be monitor in the following page: https://status.azure.com/

Dooap depends on Microsoft Azure services and the customer’s Dynamics environment, and is unavailable if either experiences a service interruption.

Supported Web browsers:

• Google Chrome (latest publicly available version)
• Microsoft Edge (latest Chromium-based publicly available version)

Supported Mobile platforms:

• Apple iOS, latest release
• Android 11 and up

 

9 AX2012 Limitations

The following limitations apply when integrating with AX2012:

• No support for Advance Rules or Derived Dimensions
• No support for transferring the invoice image (or attachments) over to AX2012
• No support for Position Hierarchy or Signing Limits
• No “Open PO on D365” link from PO invoice
• “Dooap Invoice Image” link only available on Vendor transactions page in AX2012
• Intercompany accounting can fail when group companies use different account structures

 

Links

Release Policy

D365 Technical tasks

AX2012 Technical tasks

AX2012 Model installation

Onboarding Service Description

Support Services Description