Feature Ideas

We're exploring ways to add existing cards to Precoro and record payments you make with them for better flexibility and spend control.

Payments made with Precoro Cards will automatically match approved invoices, reducing manual work in reconciliation and minimizing errors. AI will send exceptions for review, so you stay in control and ensure transactions are allocated correctly.

Soon, you’ll be able to add payments made with Precoro Cards to POs. You'll no longer have to create invoices in Precoro if they're not necessary for a particular vendor. Simply pay with a virtual card and have the payment allocated to a relevant order.

You'll be able to connect Precoro with Microsoft Teams to receive notifications and approve requests directly from your workspace 🚀. Here's what the integration will include: approving or rejecting documents and suppliers directly in MS Teams with adaptive cards;quick redirect to Precoro for thorough review; notifications when you're tagged in a comment; reminders and notifications about documents awaiting your action (matching, revision, or receipt creation).

We're planning to add a shopping list feature so you can save frequently requested items. When creating a purchase requisition, you’ll be able to select from that list instead of entering details manually each time.

Would it be possible to make the following fields on the PO optional for printing and controllable (visible vs invisible) by user? Status (PO approval status)Creation Date (date when PO was originally created)Approval Date (date when final approver approves the PO)Delivery Date (expected date for goods / services to be delivered by supplier) Thank you!

We're building an official, enterprise-ready, marketplace-grade connector for Microsoft Dynamics 365 Finance & Operations, providing a standardized, secure, and reliable Procure-to-Pay integration with Precoro. The scope covers synchronization of vendors, items, financial master data, purchase invoices, and credit memos.

For better clarity, we hope to see that 'Available Amount' can be changed to 'Available Amount after PO Approval' as users tend to get confused that the available amount is the amount balance before the current PO they are raising. Thank you.

Revising or editing an approved PR may trigger re-approval. Making changes and resubmitting for approval may easily raise questions from management, and we would like to avoid that, especially in cases POs already issued to vendors. It is recommended that Requestors raise a new PR instead of modifying an already approved one

Control which fields appear when creating an invoice from a purchase order. Customize the layout and required information to fit your process.

We’re planning to add support for local e-invoicing requirements in Romania to help you stay compliant and simplify electronic document exchange.

It helps to correctly track completed vs pending PRs. Reduces confusion for requesters whether their items have been ordered or not. And procurement team does not make mistake later of re ordering items. For example, requester puts 3 items in requisition, pencil, eraser, pencil sharpener. Procurement team finds a deal where all 3 are offered as a set, so PO will be different from requisition. Procurement team should be able to link this PO to the 3 items of the PR. Without this, items show as not ordered even though item has been ordered.

Allow approval thresholds to be set using two or more parameters (e.g., Department + Project) instead of only one. This would enable different threshold values for the same department across multiple projects or locations. Add a batch setting option so multiple departments/projects/locations can be selected and assigned a threshold at once, reducing repetitive data entry and setup time.

Currently there is a size limit of 25 MB on attachments to POs in Precoro. We need to include larger file sizes and spend time on dividing original files to make them fit with the limitation in Precoro. This causes additional manual work that can be omitted by increasing the size limit in Precoro.

The system currently does not check for duplicates among other incoming OCR attachments in the AP Inbox; it only checks against actual invoices that were already created. Proposing that the system checks incoming OCR attachments to against all documents in the system (including AP inbox items) to identify duplicates earlier.