Release Notes

Fidesic Release Notes: October 23rd, 2026

Written by Fidesic | Oct 23, 2026, 4:55:29 PM

Release Notes

Heads Up: Things That Will Look Different


  • Edits to POs in Business Central and GP now reach Fidesic. When a PO changes in Business Central, or in GP with the Fidesic Dynamics GP sync service, after it first syncs, Fidesic now updates its lines, quantities and prices to match. Before, every edit after the first sync was ignored, so a PO created in Business Central often arrived with no lines at all. A line an invoice has already billed is kept at no less than the quantity billed, and can't be changed to a different item or account. Business Central customers need extension version 2.0.4.0, described below.
  • PO lines show your own item number under No. On a PO's detail page, the No. column now shows your item number first, then the vendor's, and the G/L account on G/L account lines. Business Central item lines, which showed a blank No., fill in once they sync from extension 2.0.4.0. If you use the Fidesic add-in for GP, PO lines that carry a vendor item number now show your GP Item Number there instead of the vendor's.
  • The Master Services Agreement has been updated. A new section 4.5 says fees can change on 30 days' notice, by email or on the Fidesic website, starting the first of the following month, and that you can end the agreement under section 7.2 if you don't accept a change. Section 18 now names Michigan law, matching its Michigan courts. Agreements accepted from now on record the new wording.

Invoice Entry & Coding

  • Import a Bank of America card statement as one invoice. Choose Bank of America Card Statement on the Import page, pick the card's vendor and upload the export from Bank of America's portal. It becomes one draft invoice for the statement total, with a line for each transaction, coded to a GL account by AI with the reason shown. Lines the AI was unsure about are flagged, and you can recode any line before you confirm. A receipt must be attached before the statement can be confirmed, and Discard throws away a statement you don't want.
  • One invoice can bill several POs. Each invoice line can now carry its own PO, and the PO in the invoice header is optional. Import Lines from PO lets you go back and add lines from another of the vendor's POs, the invoice page lists every PO the invoice bills as a link, and the PO line picker can switch to any of the vendor's open POs. PO match checks quantities against each PO separately.
  • Import Lines from PO opens beside the invoice. The Import Lines from PO panel and the PO line picker now open over the form, with no dark backdrop, so you can still read, scroll and click the invoice PDF while you match. Move right and Move left put the panel on the other side.
  • Find any of a vendor's POs in Import Lines from PO. A search box finds a PO by part of its number or its location, including POs older than the 50 newest the list shows, and ignores leading zeros. Paste captured PO searches for the PO number MagiCapture read off the invoice, so "PO# 35301" or "JM 35301" finds PO 35301.
  • Match to invoice picks the right PO lines. In Import Lines from PO, Match to invoice uses AI to pair the lines MagiCapture read off the invoice with the PO's lines. It ticks only the PO lines the invoice bills, fills in the invoice's quantities and amounts (72 rolls of 300 feet becomes 21,600 feet on a PO counted in feet), and lists the invoice lines that aren't on the PO. Before, every open PO line was ticked at its remaining quantity. It needs Match PO Numbers Flexibly turned on. Learn more

MagiCapture

  • New Premium Feature: PO numbers match through buyer initials and prefixes. With the new Match PO Numbers Flexibly setting under Capture PO Numbers, a PO printed as "JM 35301", "PO# 35301" or "35301 H" links to your PO 35301. When no number fits, AI suggests a PO from the vendor's open POs: a confident match is linked with a warning to check it, and a less certain one leaves a note naming the possible PO. The setting is off by default. 
  • Invoice lines match PO lines by the product, not only the item code. When a vendor prints its own part numbers and your PO has only yours, MagiCapture now pairs the lines by description, size, unit cost and quantity, and gives each line your item number. When you pair such a line by hand, it takes the PO line's item number, and unlinking gives it back.
  • Spreadsheets go through MagiCapture. Send to MagiCapture in the Invoice Inbox now works on CSV, XLS and XLSX files, and a spreadsheet holding several invoices comes in as one. MagiCapture now remembers a vendor you correct even on a document with no address, such as a card statement.
  • New vendors are coded from your whole chart of accounts. When a vendor has no history or default GL codes of its own, MagiCapture's suggested coding now draws on your full chart, preferring the accounts you use most, instead of only accounts you have used before.
  • Emailed invoices no longer get stuck on a read error. An emailed invoice that failed with "Sequence contains no elements" while we were updating MagiCapture used to sit in your queue until someone keyed it by hand. It is now tried again automatically, up to three times over the next two hours.

Approvals

  • Require a receipt before approving a card statement. A new toggle on the MagiCapture settings page, off by default, stops an invoice whose only attachments are spreadsheets from being approved until a receipt or other file is attached. Where a rule would approve it automatically, it is held for the person who submitted it.

Purchase Orders

  • Allow freight, misc or tax the PO doesn't carry. If your POs never include freight, every freight invoice was flagged Charges Not on PO. Under Settings, Company, Preferences, Charges not on PO now lets you choose, for freight, misc and tax separately: flag it (the default), allow up to an amount, allow up to a percentage of the subtotal, or always allow it. The invoice shows "Not on PO (within tolerance)" in green or "Not on PO" in amber. Turn on Freight Expected on PO for a vendor whose freight should always be on the PO. Learn more
  • POs with an unknown vendor now open. When your ERP sends a PO whose vendor isn't in Fidesic, the PO now opens and shows "Unknown vendor". Before, it wouldn't open, and the PO list showed Fidesic as its vendor.
  • PO lines list in order. PO lines numbered 10 and up no longer appear ahead of line 2.

Payments

  • Unvoiding a payment marks its invoices paid again. An unvoided payment's invoices stayed Unpaid. They now read Paid again. If you marked an invoice paid while the payment was voided, that Mark as Paid is replaced by the payment. If another payment paid the invoice in the meantime, the unvoid still goes through, with a warning naming the invoice now paid more than once.
  • Removing an invoice from an unapproved payment clears Payment Pending. An invoice taken off an unapproved payment, or losing an unapproved credit memo, kept reading Payment Pending. It now goes back to its earlier status.
  • Void a settled payment you received. When the card processor refuses to void a payment you received, usually because the ACH has already settled, the payment page now offers Void in Fidesic Only. It shows the processor's reason, and any refund has to be made outside Fidesic. Before, the void just stopped with the processor's error.

Reporting

  • Invoices Received links to POs. The PO Number column lists every PO an invoice bills, header PO first, and each one opens the PO for anyone who can view purchase orders. Searching by PO number finds an invoice by any of its POs, and the Excel export lists the same numbers.
  • See backups that are still being built. After you run an Invoice or Payment Backup, the Reports page lists it under Being generated, queued or in progress, until it finishes. The list updates on its own, so there is no need to click Run again. Learn more

Users & Account

  • Make a pending user an account owner. Make account owner now works on a user who hasn't finished signing up. They don't count as the account's remaining owner until they do. Learn more

Also Fixed

  • Adjusting an invoice keeps all its lines. Adjusting an invoice that had both catalog item lines and other lines could delete the other lines and their PO matches.
  • Removing a GL row shows the right values. On Enter and Adjust Invoice, removing a GL row could make the rows below it show another row's values.
  • Notification email checkbox works. The Notify checkbox for a notification email on the User Profile never changed anything. It now saves, and it goes back to how it was if you cancel or the save fails.

For Microsoft Dynamics GP Users

  • Credits applied in GP now sync correctly. With version 2.5.0 of the Fidesic Dynamics GP sync service, an invoice paid by a credit in GP shows as paid in Fidesic, and a credit split across several invoices is applied to each one. Before, those invoices stayed Unpaid, and credits from years back appeared dated the day they synced, many for invoices Fidesic never had. Credits now sync from your payment sync start date, at their GP amount and date. A payment that pays only part of an invoice is now applied to it, and checks from two checkbooks or vendors that share a number no longer have their remittance merged.
  • Freight, misc and trade discount import into GP. Version 18.6.3 of the Fidesic add-in for GP reads an invoice's freight, misc and trade discount amounts when it imports the invoice into GP, as long as they add up to the invoice total.

For Dynamics 365 Business Central Users

  • PO item numbers and edits sync with extension 2.0.4.0. Item lines now send their No., so it shows on the PO in Fidesic and helps match invoice lines, and the vendor's item number is sent too. Lines keep their Business Central line numbers, so an edited PO updates the right lines. A quote or invoice that shares a PO's number no longer adds its lines to that PO, and a blank row no longer stops the whole PO from syncing. Existing POs fill in the next time they sync: after an edit, a release, or the Initial Sync Purchase Order report. This applies to both the standard and multi-entity extensions.