About Pryme AP Automation

• 1: Setup and configuration
• 1.1: Assisted setup
• 1.2: Basic Setup
• 1.3: Approvals and workflow setup
• 2: Stack Icons in Role Center
• 3: Process
• 3.1: Receive and Review
• 3.2: Correct data
• 3.3: Approvals
• 3.4: Post and Pay
• 4: Features
• 5: Pryme AP Automation Release Notes
• 6:

1 - Setup and configuration

Get started

1.1 - Assisted setup

When Pryme AP Automation app is installed, the Assisted Setup will start automatically. If the Assisted Setup doesn’t start automatically, or to run the Assisted Setup at later point after installation, click the 🔎 icon, search for “Assisted Setup,” and select the related link. In the “install extensions to add features and integrations” section, click Setup Pryme AP Automation.

The Assisted Setup will guide through the following steps:

1. Company and Contact Information
   Confirm or input company details and contact information. The details are retrieved from the Company Information page in Business Central.

2. Password Setup
   Click on the link to create a password for your account. The password must meet the following criteria:

   • At least 8 characters long.
   • At least one lowercase letter.
   • At least one special character.
   • The same password must be entered in all three fields.

3. Complete the Setup
   Click Next to process the information and finalize the registration. Once this step is done, your OCR email address will be shown and sent to the contact person via email. You will also be prompted to test the connection to ensure it was successful.

1.2 - Basic Setup

After the Assisted Setup process is completed, additional configuration options is available on the Pryme AP Automation Setup page.

Choose the 🔎 icon, enter Pryme AP Automation Setup, and select the related link.

Enable Posting Date Change

To automatically set the Posting Date to match the Document Date when creating a Purchase Document:

• Turn On to synchronize the Posting Date with the Document Date.

• If turned Off, the Posting Date will default to the work date or be left blank, following the configuration on the Default Posting Date field in the Purchases & Payables setup page.

Bank Details Validation

Enable validation of bank details on the Vendor Card against incoming documents. If a mismatch is detected, purchase document creation will be blocked, displaying a warning that allows for manual correction or proceeding with document creation.

The following fields can be validated:

• IBAN

• SWIFT

• Bank Account No

• Bank Branch No

Set up Notifications

There are different types of notifications that can be managed through the Notifications setup, found under the Approval User Setup page. These are standard Business central style notifications, learn more Setting up approval workflow notifications - Business Central | Microsoft Learn

Notification type/trigger:

• New Record – notification for a new record, for example a new incoming document.

• Approval - notification for a new approval record, for example an approval of a purchase document.

• Overdue – notification of overdue entries. When an entry is considered overdue is configured under each workflow, see section Workflows.

Notification method:

• Email – an email is sent out to the user that should be notified.

• Note – no email is sent out, only a notification in Business Central is created for the user.

• Schedule/Occurrence settings - Notifications can be configured to be sent out immediately when a new record is triggering a notification. However, to limit the amounts of notifications sent, the notification schedule for a user can be set to send out a summary of the notifications created in different intervals. This must be configured on a user-by-user basis, the default value is immediate distribution of the notifications. For more details on the setup of notifications, see Setting up approval workflow notifications - Business Central | Microsoft Learn.

Simplified Approval Pages for Purchase Documents

Simplified approval pages for both purchase invoices and purchase credit memos. These pages display only the essential fields required for approvals, include a larger PDF preview for better document visibility, and now allow users to perform approval actions directly on the simplified pages, similar to the standard pages.

Permissions

To ensure efficient usage and access control, there are two distinct permission sets: Approver and Superuser.

Approver has targeted privileges, including the ability to handle approvals for purchase documents and access related Pryme AP Automation features out of the box.

Superuser has elevated privileges, including full access to all Pryme AP Automation features and comprehensive control over the system’s automation capabilities.

1.3 - Approvals and workflow setup

Before configuring workflows, approvers must be set up. A user must be designated as an approver in each step of the approval process.
Access the Approval User Settings through selecting the 🔎 icon, enter Approval User Settings, and select the related link.

Information on the Approval User setup, and how to test the flow, please see: Set up approval users - Business Central | Microsoft Learn

Workflows

Workflows are used with Pryme AP Automation to automate document creation and set up document approvals. For detailed information on how to set up workflows in Microsoft Dynamics 365 Business Central, please see: Create approval workflows to connect tasks - Business Central | Microsoft Learn.

To set up workflows, select 🔎 and search for Workflows:

A new workflow can be created by the user or based on Workflow Templates. To create new workflows from a template, select New Workflow from Template in the menu.

Below follows documentation on the Pryme AP Automation workflows setup, Set up workflows for creation of incoming documents.

To set up workflows for automatic creation of Purchase documents from successfully read incoming documents, select the template Incoming Document OCR Workflow. Select if and which user should be notified about failed incoming documents and activate the workflow by clicking Enabled.

Set up workflows for document approvals

For document approvals the following workflows are available from the Workflow Templates:

Added Approver types to approval workflows in Pryme AP Automation

In addition to the standard Approver and Workflow user groups types Salesperson/Purchaser, Pryme AP Automation adds two more Approver Types: Dimension Code and Project Manager. Below follows an explanation of how you can set up approvals based on Dimensions and Project Manager.

• Dimension code: Select this option to set the approver based on dimension values. In the Dimension Code field, select which dimension code this workflow applies to.

  • To define approvers: select 🔎 and search for Dimensions, select the Dimension Code entered in your workflow and select Dimension -> Dimension Values from the menu. In the list that opens, an approver can be selected for each Dimension Value. This user will now be the first in an approval flow for this Dimension Value.

• Project Manager: Select this option to set the approver based on selected Project Manager on a project. For this option to work, it will be required that your invoice (lines) have a Project No. assigned, and that the *Project selected has a Project Manager assigned.

Header-Level Approval 

When approval is at the header level, all lines share the same status as the header. This means: 

• If the header is sent for approval, all lines are Pending Approval. 
• If the header is Approved or Rejected, all lines follow that status. 
• If the header is Open, all lines are also Open.

If the Purchaser Code is changed in the header, a prompt appears asking whether to update the Purchaser Code for all lines.

Line Approval for Purchase Documents

When approval is at the line level, users have the ability to approve individual purchase lines within documents. Each line can have its own status (Open, Pending Approval, Approved, or Rejected), providing more flexibility when handling approvals. Rejected lines can be modified and resubmitted.

This feature works alongside the existing workflow for approving the entire document, but only one workflow can be active at a time. For example, if lines are sent for approval, the header cannot be sent for approval, and vice versa.

With line-level approval, each line has its own approver. If there are multiple approvers, the header will show “Multiple Approvers.”

With header-level approval, all lines share the same approver.

2 - Stack Icons in Role Center

Standard Stack Icons in Business Central used for approvals

Approval Tiles

When a document is sent out for approval, it can be accessed though standard Business Central Tiles or through the Request to Approve page. Learn More about Approve or reject approval requests - Business Central | Microsoft Learn

Added Stack Icons when installing Pryme AP Automation

Stack icons are available in the Role Centers for Accountant, Business Manager, and Accounts Payable Coordinator. These icons provide quick access to key document statuses.

Incoming Documents

When an invoice is sent to the designated email address for purchase documents, the system automatically processes the document and generates a corresponding Incoming Document.

If the document cannot be processed successfully, it is shown to the Failed Incoming Documents tile, where it remains available for manual review and necessary corrections.

Successfully processed Incoming documents, that have not been created as Purchase invoice or Purchase Credit memo yet is shown in the New Incoming Documents tile.

New Purchase Documents

For documents that are successfully processed, the system can automatically generate a corresponding Purchase Invoice or Credit Memo if the Workflow is enabled. The newly created document is then shown in the appropriate tile within the Role Center, providing clear visibility and easy access for further review, approval, or processing.

Purchase Documents Pending Approval

Once the document has been sent for approval, it is shown in the Purchase Documents Pending Approval tile. In this tile, the document awaits action from the designated approver, who can then take the necessary steps to either approve or reject the document. This stage ensures that all documents are properly vetted before they move forward in the approval workflow.

Purchase Documents Rejected

A document will show under Purchase Documents Rejected tile when it is rejected through the approval workflow. Rejected documents can still be modified and resubmitted for approval, following the standard Business Central process for documents with an “Open” status. This feature enhances visibility and control over documents that were not approved, ensuring that they can be adjusted as needed before being resubmitted for further approval.

Purchase Documents Approved

Once the document has been reviewed and approved, is shown in the Purchase Documents Approved tile, indicating that it is now ready for posting.

3 - Process

Process introduction

Pryme AP Automation is an AI-powered solution that simplifies purchase document management. By utilizing AI technology, Pryme AP Automation captures incoming invoices from PDF or image formats, automatically converting them into structured, digital documents on a line level. Streamlining the process from incoming document to approval and posting of the invoice.

Pryme AP Automation can be configured to automatically create Purchase documents directly in Business Central. Businesses can fully automate the workflow and approval processes of purchase documents, from capture to posting.

3.1 - Receive and Review

Receive and create Purchase Document

When a document is sent to the designated email address, it is processed and interpreted by the AI engine. The information is then converted into an Incoming Document, ready to be created as a Purchase Document. The new incoming document will appear in Business Central within a maximum of five minutes.

When issues arise, such as data discrepancies or vendor mismatches, they must be resolved before the Purchase Document can be created. Learn how under the section Correct Data. These documents will be shown under the Failed Incoming Documents tile.

Review the created document

In this step you can complete the creation of the document, adding possible additional information before approvals and posting:

Do so by navigating to New Purchase Documents tile, select the document. Add or change the necessary information, for example dimensions, projects or other information not specified from the Incoming Document.

To make the Review step easier, there is a few provided productivity features implemented:

Map text to account available from additional pages

From the vendor or the purchase invoice you have quick access to the Map-text-to account page, enabling use of suggested lines on the Purchase documents based on recognized vendors and/or texts on the documents

PDF Viewer

There is a dynamic PDF viewer accessible in the Fact box pane from any page handling Purchase documents within Business Central. You can also zoom for better visuals, and it is possible to open and view the full-scale PDF in a separate window.

Create New Vendor from Incoming Document Details

If incoming documents contain vendor details not found in the current vendor list, the incoming document will fail to be created. Users can now create or select a vendor directly from the document, or the Correct OCR Data page, using the information from the incoming document. In combination, users can also use existing vendor templates for quick setup of new vendors

When the document is finalized, use the function “Approve-> Send Approval Request/Send Line Approval Request” to send the Document for Approval, or if no approval in enabled, go directly to Post to post the document directly.

3.2 - Correct data

Correct data from Incoming Document Details

If the document contains errors or missing details that prevent processing, the document is shown in the Failed Incoming Documents tile. To correct failed incoming documents, follow this guide:

1. Click on Failed incoming Document tile.

2. If data needs to be corrected from the AI Engine result, select Correct OCR Data (under OCR -> Correct OCR Data) and correct the information.

3. Click on Send OCR Feedback (to further train the AI engine).

4. If the document is from a new Vendor, or if information on existing vendor cards is missing, either a new Vendor can be created based on the information on the incoming document or an already existing vendor can be assigned to the document.

   • In case of a new vendor, see section Create New Vendor from Incoming Document Details.
   • In case of missing details on an already existing vendor, such as a missing VAT number that prevents the matching, the vendor can be selected in the Vendor No. field in the Financial information section on the Incoming document. From the drop down, existing vendors can easily be accessed and edited if necessary.

5. When the document information is corrected and/or matched to a vendor, the document can proceed and be used to create a new Purchase Document by selecting Create Document (under Home -> Create Document)

A correct purchase document will now be created and automatically sorted in the appropriate tile.

Create New Vendor from Incoming Document Details

If Incoming Document contains vendor details not found in the current vendor list, the Incoming Document will fail to be created. Users can create or select a vendor directly from the document, or the Correct OCR Data page, using the information from the Incoming Document. In combination, users can also use existing vendor templates for quick setup of new vendors.

To update existing vendor information or to create a New Vendor follow one of these guides:

1. Click on Failed incoming Document tile.

2. Select New and Create New Vendor (from template if applicable).

3. Complete the changes by selecting Create Document (under Home-> Create Document).

3.3 - Approvals

Approvals

Approvals are an optional step in Pryme AP Automation. If you choose to use an approval workflow, you must configure and enable it beforehand, as described in Approvals and Workflow Setup. If an approval workflow is not configured, the approval function remains disabled, and the document can only be posted.

To send a document for approval, click on Request Approval on the purchase invoice menu bar.

• Select Send Approval Request for documents requiring approval at the header level, or
• Select Send Line Approval Request for documents needing approval at the line level.

For the document to reach the correct approver, you must assign an approver. This assignment is determined by the workflow configuration setup during the Workflow and Approval User Setup. The configuration uses criteria such as salesperson/purchaser, dimensions, or project number.

The assigned approver will receive an email notification with a link to the Requests to Approve page. This page is accessible through Pending Approval Tile in Business Central.

When the document is awaiting approval, it is shown under the Documents Pending Approval tile.

When the document is approved it is shown under the Purchase Document Approved tile.

3.4 - Post and Pay

Post and pay

The Document is now ready for Posting. This can be done in 3 different ways:

1. Single posting Post singular documents.
2. Batch Posting Will post a batch of documents.
3. Workflow Will automate the Posting. When a document is approved, it will automatically post the document.

The Post function follows standard Business Central functionality, read more on Posting Documents and Journals - Business Central | Microsoft Learn.

There is a provided productivity features implemented to further help with posting:

Remaining amount to match here you have information about the remaining amount that needs to be allocated on the invoice lines, so the purchase invoice matches the incoming documents amount. Learn more here

4 - Features

Features in Pryme AP Automation

Overview

Detailed descriptions

Approvals in Pryme AP Automation with Progressus installed

If Progressus is installed, Pryme AP Automation shifts approval assignments from user IDs to resources and adjusts field visibility to match. Here’s how it works.

Assigning Approvals

Approvals are tied to resource codes instead of user IDs. These codes link to user IDs through the User Setup table. Delegation follows the same mapping, so approvals route to the right people automatically.

Changes to Field Visibility

• The Project No. field in Pryme AP Automation hides itself in purchase documents.
• In Dimension Values, approver fields switch from user-based to resource-based options.
• The system syncs changes between user-based and resource-based approvers seamlessly.

How Approvals Behave

Behind the scenes, the approval process stays the same. Approvals display as resources but still rely on user IDs to function. Pryme AP Automation detects Progressus and applies these changes for you.

PDF viewer

There is a dynamic PDF viewer accessible in the Fact box pane from any page handling Purchase documents within Business Central. You can also zoom for better visualisation, and it is possible to open and view the full-scale PDF in a separate window.

Remaining amount to match

In the Incoming document details fact box, you have information about the remaining amount that needs to be allocated on the invoice lines, so the purchase invoice matches the incoming documents amount. If the invoice total does not match the incoming document amounts, posting will be prevented. Therefore, if the sum of the lines is not matching the total from the Incoming document, a warning message will show before an approval flow is started.

Map text to account available from additional pages

From the vendor or the purchase invoice you have quick access to the Map-text-to account page, enabling use of suggested lines on the Purchase documents based on recognised vendors and/or texts on the documents.

Posting date set to document date on purchase documents

This features enables the possibiltiy to set the Posting date automatically to the document date, instead of today’s date or blank as possible in the standard Business Central functionality.

New Stack Icons in Role Centers

New stack icons have been added to the role centers for Accountant, Business Manager, and Accounts Payable Coordinators. These icons provide quick access to various document statuses, e.g. Invoices to approve, Failed Incoming Documents, New Incoming Documents, Purchase Invoices on Approval, Purchase Invoices Approved.

Create New Vendor from Incoming Document Details

If incoming documents contain vendor details not found in the current vendor list, the incoming document will fail to be created. Users can now create or select a vendor directly from the document, or the Correct OCR Data page, using the information from the incoming document. In combination, users can also use existing vendor templates for quick setup of new vendors.

Rejected Status for Purchase and Sales Documents

A new Rejected status has been added for both Purchase and Sales documents. This status is automatically applied when a document is rejected through the approval workflow. Rejected documents can still be modified and resubmitted for approval, following the standard Business Central process for the Open status. This provides better visibility and control over documents that were not approved and ensures that they can be adjusted as needed before being resubmitted for approval.

Bank account details validation

This functionality enables validation of IBAN, SWIFT, Bank Account No, and Bank Branch No on the Vendor Card against an incoming document. If there is a mismatch between the vendor’s saved details and the incoming document, automatic creation of purchase documents will be blocked, and a warning will prompt manual correction. Users can override this warning and enable or disable the feature globally or on a vendor-specific basis.

Line Approval for Purchase Documents

Introduces the ability to approve individual purchase lines within documents. Each line can have its own status (Open, Pending Approval, Approved, or Rejected), providing more flexibility when handling approvals. Rejected lines can be modified and resubmitted.

This feature works alongside the existing workflow for approving the entire document, but only one workflow can be active at a time. For example, if lines are sent for approval, the header cannot be sent for approval until the line workflow is completed, and vice versa.

Simplified Approval Pages for Purchase Documents

Simplified approval pages have been introduced for both purchase invoices and purchase credit memos. These pages display only the essential fields required for approvals, include a larger PDF preview for better document visibility, and now allow users to perform approval actions directly on the simplified pages, similar to the standard pages.

5 - Pryme AP Automation Release Notes

2.3.1 Hotfix (March 2025)

Fixes and Minor Adjustments

• #422 Require user to test connection after Assisted Setup.

2.3 (March 2025)

Application updates

Permission Sets for Superuser and Approver a

New permission sets have been added to manage access in Pryme AP Automation. The Superuser role grants full access to all features, while the Approver role allows approval and rejection of documents with access to the document log. Learn more.

Progressus Advanced Projects Compatibility

Pryme AP Automation now adapts when Progressus Advanced Projects is installed. Instead of using Pryme AP Automation’s project fields, the Progressus fields are used. Approvals reference resources linked to users instead of direct user assignments. Learn more.

Fixes and minor adjustments

• #408 Approval request error when sending lines for approval
• #391 Purchaser code line update confirmation
• #361 Fit ’n Finish
• #344 Stack icon Incoming documents - showing the incorrect value
• #365 Limit User Email Input to 32 Characters on Assisted Setup Page
• #326 Change error message when approving lines where the user is not the approver
• #204 Negative credit memos create negative purchase CM
• #128 Error when using an email address that creates a user ID from Procys longer than 50 characters
• #412 Fixed Typos in Pryme AP Automation
• #368 Skip job queue execution in Assisted Setup if the user lacks required permissions
• #362 Cannot run Assisted Setup with a partner account
• #352 Change approval email link to open the full document page for line approvals
• #366 Handle currency code on incoming documents when missing

2.2 (February 2025)

Application Updates

Enhanced Bank Detail Validation Button Functionality

The functionality of the Bank Detail Validation buttons in the Pryme AP Automation Setup page has been updated to improve usability. When the Default Bank Detail Validation is enabled, all fields (IBAN number, SWIFT Code, Bank Account No, Bank Branch No) will be toggled on by default. Users can toggle off individual fields to exclude them from validation, offering clearer and more intuitive control over which fields are validated.

Automatic Navigation to Next Purchase Document in Simplified Purchase Document Approval Page

The Simplified Purchase Document Approval Page now automatically moves to the next purchase document in the queue after a user approves, rejects, or delegates. This improves efficiency by eliminating the need for manual navigation.

Approval Actions Directly on Purchase Lines in Simplified Pages

Approval actions (approve, reject, or delegate) can now be accessed directly from each purchase line on simplified purchase pages. Users can trigger approval actions via a button or through the existing line options menu, making it easier to manage approvals at the line level.

Fixes and Minor Adjustments

• #294 Changed the captions for OCR actions to “AI Engine” in the Incoming Document Page.
• #330 Fixed an issue where the approver user was not updating correctly.
• #318 Fixed an issue where the purchaser code was empty on the purchase line.
• #328 Ensured that the purchase header updates when all purchase lines have the same status.
• #337 Enabled opening standard purchase document pages for purchase lines when simplified mode is disabled.
• #354 Restricted access to Simplified Purchase Documents via the Search Bar.

2.1 (January 2025)

Application Updates

Add Approval Logic to the Simplified Pages

Approval logic has been added to the simplified Purchase Invoice page and the simplified Purchase Credit Memo page. Users can now approve, reject, or delegate both headers and lines directly on these pages, aligning them with the existing functionality in the standard pages. Learn more about the invoice page.

Simplified Approval Page for Purchase Credit Memos

A simplified Purchase Credit Memo approval page has been added. It displays only the essential fields required for approvals and includes a larger PDF preview for better document visibility. Learn more about the credit memo page.

Fixes and Minor Adjustments

• #274 Fixed an error that occurred when adding purchase lines for unsupported document types.
• #259 Updated Assisted Setup titles and descriptions to consistently use “Pryme AP Automation.”
• #269 Updated all references from “AI for AP” to “AP Automation” across the application.
• #278 Fixed validation issues causing duplicate workflows in the Workflow and Workflow Templates pages.
• #297 Resolved permissions issues in the Purchase Document Log PAYME table by adding scoped permissions.

2.0.2 Hotfix (January 2025)

Fixes and Minor Adjustments

• #274 Fixed an error that occurred when adding purchase lines for unsupported document types.

2.0.1 Hotfix (January 2025)

Fixes and Minor Adjustments

• #267 Fixed status validation error during posting, allowing modifications to purchase lines even when their status is not open or rejected.
• #271 Fixed an issue with the approver chain for purchase lines where approval entries were not being created.
• #272 Fixed line status logging to ensure accurate recording of status changes in the purchase document log.
• #273 Added a Project Manager field to the purchase header for project manager-based approvals.

2.0 (December 2024)

Application Updates

Purchase Line Approval Logic

Approval logic for individual purchase lines in documents has been introduced. This allows users to approve, reject, or delegate lines independently of the document header, providing greater flexibility in workflows and better control over approvals. Learn more.

Simplified Purchase Invoice Approval Page

The simplified approval page for purchase invoices now shows only the essential fields, with a larger PDF preview for better document review. Learn more.

Fixes and Minor Adjustments

• #232 Addressed currency code validation issues when creating new vendors to prevent errors during document creation.
• #176 Improved workflow logic for purchase line approvals, ensuring seamless status updates and event handling.
• #245 Enhanced functionality in the simplified invoice approval page for user-friendly approvals.
• #226 Updated purchase document logs to record changes to purchase lines, including status updates and approvers.

1.9 (December 2024)

New Features and Improvements

Bank Detail Validation Enhancements

• The SWIFT Code has been added to the bank detail validation process. It is now verified alongside other bank details to ensure consistency and accuracy.
• New toggles have been added in the Pryme AP Automation Setup page. These toggles allow users to control the default values for fields related to bank detail validation in the Vendor Card, providing greater customization for validation defaults based on specific needs.
• Additionally, new toggles have been added under the Invoicing group in the Vendor Card. These toggles enable users to control which fields should be included in the bank detail validation process, offering more control over the validation criteria.

App Name Change

• The name of the app has changed from Pryme AI for AP to Pryme AP Automation. This new name better reflects the expanded capabilities and scope of the application.

Fixes and Minor Adjustments

• #227 Fraud protection (Bank details check BIC/SWIFT).
• #205 Change app name to Pryme AP Automation.
• **#2

1.8.1 Hotfix (November 2024)

Fixes and Minor Adjustments

• #195 Added a toggle to control IBAN validation when validating bank details, allowing users to enable or disable this feature as needed.

1.8 (November 2024)

New Features and Improvements

Fraud Protection with Bank details Validation

• Added functionality to verify that the Bank details (Bank Account No., Bank Branch No. and IBAN) in incoming documents match any existing Vendor Bank Account card. If the details do not match, the document is flagged for review to prevent possible fraud. Learn more.

Fixes and Minor Adjustments

• #182 Enhanced the Purchase Document Log to ensure that comments are consistently recorded whenever there is a change in the status or approver.

1.7 (October 2024)

Pryme AI for AP Improvements

Purchase Document Log

A Purchase Document Log has been added to track changes in purchase documents, focusing on the approval status and the assigned user.

Reassign Approvers in the PowerApp

New functionality allows approvers to be reassigned for purchase invoices and credit memos directly from the PowerApp.

Handling of Rejected Status for Credit Memos

A Rejected status has been added for credit memos in the approval workflow. If a credit memo is rejected, its status will now be set to Rejected, similar to how the Open status functions, allowing for further processing or resubmission.

Fixes and Minor Adjustments

• #124 Fixed formatting issues in text and number alignment.
• #165 Restored the standard job queue for receiving OCR documents temporarily.
• #166 Added approval workflows for credit memos.
• #166 Fully supported the Rejected status for credit memos in approval workflows.
• #167 Prevented re-adding of the standard status field during customization.
• #168 Added new API pages for Document Attachment, User, and User Setup, and edited existing APIs to improve design.
• #169 Deprecated unused code related to the old rejected status logic.

1.6 (September 2024)

Pryme AI for AP Improvements

New API Page for Users

A new API page was created for accessing user information via external systems.

Rejected Status for Purchase and Sales Documents

A Rejected status was added to both Purchase and Sales documents. This status will work the approval workflow when a document is rejected, allowing the document to be resubmitted for approval after necessary changes.

Direct Editing in “Text-to-Account Mapping” Page

It is now possible to directly edit the Default Debit Account for Non-Item Lines and Default Credit Account for Non-Item Lines fields in the “Text-to-Account Mapping” page, eliminating the need to navigate to the “Purchases & Payables Setup” page.

Fixes and Minor Adjustments

• #126 Added APIs for Power Apps integration
• #134 Added new API page for users
• #144 Fixed error when copying companies
• #147 Enabled direct editing of default accounts in “Text-to-Account Mapping”
• #149 Added a new ‘Rejected’ status for Purchase and Sales documents with corresponding workflows

1.5 (August 2024)

Pryme AI for AP Improvements

Vendor Card Menu Enhancements

The “Mapping Text to Account” and “Item References” options have been moved to the Home tab on the Vendor Card and Vendor List pages, improving accessibility.

Fixes and Minor Adjustments

• #115 OCR Setup Duplication Prevention
• #117 Email Template Updates for Assisted Setup
• #118 Vendor Card Menu Enhancements

1.4 (July 2024)

Fixes and Minor Adjustments

• #108 Approval Not Triggering Correctly for Purchase Documents in Total Mismatches
• #109 Assisted Setup Password Not Saving Correctly
• #43 Fill in of Service Settings

1.3 (June 2024)

Pryme AI for AP Improvements

Synchronization with Procys for Data Exchange Definitions and Data Exchange Types

To improve the OCR service, the installation process now includes automatic synchronization of data exchange definitions and types with Procys. This automation ensures the necessary schemas are downloaded and integrated during setup.

Create New Vendor from Incoming Document Details

This new feature simplifies invoice processing. If incoming documents contain vendor details not found in the current vendor list, users can now create or select a vendor directly from the document. Users can also use existing vendor templates for quick setup.

PDF Viewer on Additional Pages

The PDF viewer is now available on additional pages such as Purchase Credit Memo (both list and document views), General Ledger Entries, and Vendor Ledger Entries. The viewer is visible only if an incoming document is attached, keeping the interface clean.

New Stack Icons in Role Centers

New stack icons have been added to the role centers for Accountants and Accounts Payable Coordinators. These icons provide quick access to various document statuses, including invoices to approve, failed incoming documents, new incoming documents, and purchase documents pending approval or rejection.

Registration Check for Pryme AI for AP

A new feature prompts users to complete app registration before starting the Pryme AI for AP Assisted Setup to ensures all necessary prerequisites are met.

Onboarding Wizard for Pryme AI for AP

A new onboarding wizard guides users through the setup and configuration of Pryme AI for AP. The goal of the wizard is to ensure the correct configuration and setup to process documents through OCR.

Synchronization with Procys for Data Exchange Definitions and Data Exchange Types

To improve the OCR service, the installation process now includes automatic synchronization of data exchange definitions and types with Procys. This ensures the necessary schemas are downloaded and integrated during setup.

Fixes and Minor Adjustments

• #74 Sales Invoice Error in Pryme AI for AP
• #77 Remove Set URLs to Default Menu Option
• #78 Factbox Reserved Space Issue
• #66 Remove Incoming Documents Details Factbox for Invoices Without Attached Documents
• #94 Error Verification for Mismatched Totals on Incoming Document Approval
• #3 Handle Auto Upload of Data Exchange Definitions
• #91 Vendor Names Shown Incorrectly
• #56 Fix Job Queue 881
• #54 Purchase Invoice with Non-PDF Document Attached Corrupts PDF Viewer
• #43 Fill in Service Settings

6 -