Skip to content
English
  • There are no suggestions because the search field is empty.

Release Notes 4/13/26

Changes made to Fidesic as of 4/13/26

What's New

Vendor Management

  • Per-Vendor Reject Statements Toggle: You can now configure the "Reject Statements" behavior independently for each vendor rather than applying a single global setting. This gives AP teams more precise control when vendors send a mix of invoices and account statements in the same email.

Invoice Workflows

  • Email Metadata Now Visible on Attachments: When viewing email content for an invoice attachment, the popup now displays the original email's Subject, CC, and Reply-To fields alongside the message body. This makes it easier to trace the source of an invoice without leaving Fidesic.

Bug Fixes

  • Approvers Can Now View Deleted Attachments Without Errors: Agents with approver-only roles were receiving 401 authorization errors when trying to view the previously mentioned deleted attachments on an invoice. The permission check on that endpoint has been corrected — any authenticated agent can now read the deleted attachments for invoices they have access to.

For Microsoft Dynamics GP Users

  • Next Month and After End of Month Payment Terms Now Supported: Fidesic now correctly handles GP native payment term types “Next Month” and “After End of Month / AEOM”. Both due date and discount date logic are now calculated correctly for these term types, and they are available in the term dropdowns.

For Microsoft Business Central Users

  • Configurable Posting Dates Now Supported: Posting dates in Business Central now support Invoice Date, Current Date, and the Posting Date on the invoice.

Behind the Scenes

  • Improved Email Attachment Processing: The invoice email grabber now applies additional heuristics to identify and reject email signature images, logos, and banners before they are treated as invoice attachments. This reduces noise in the attachment list for invoices delivered via email.

API Performance and Reliability Improvements: Resolved database lock contention that was causing API key authenticated requests to time out under concurrent load. Several stored procedures were updated to reduce lock hold times, and redundant database calls on authenticated requests have been eliminated.