Faster Expense Type Loading

We have improved how expense type lists are loaded throughout the application. Previously, the system retrieved all expense type data at once, which could cause slower load times - especially for organisations with a large number of expense types and cost centres. Now, expense type information is fetched more efficiently, loading only the data relevant to your current selection. You should notice faster response times when selecting expense types across expenses, items and reports.

BSB Number Sync Fix for Business Central Supplier Integration

Resolved an issue where BSB numbers were not syncing from Business Central into ProSpend for newly created suppliers. Following a recent Business Central update, vendor bank account fields were merged, causing clients to populate the Bank Branch No field instead of the EFT BSB No field. As our integration was mapped exclusively to the EFT BSB No field, BSB numbers were no longer being captured for affected suppliers.

The integration has been updated to use EFT BSB No as the primary field, with an automatic fallback to the Bank Branch No field when EFT BSB No is blank. This ensures BSB numbers sync correctly into ProSpend regardless of which field is populated in Business Central, preventing any disruption to supplier invoice processing.

Open API – Transaction Creation Endpoint

A new POST /beta/company/{id}/transaction endpoint is now available in the Open API, allowing integrated card providers to create card transactions directly in ProSpend. The endpoint supports key transaction fields including transaction date, posting date, merchant name, MCC, amount with multi-currency support (foreign currency amount and code), cardholder details (name, card suffix, external card ID), and transaction status. Duplicate transactions are detected using a combination of transaction ID and card program code to ensure accuracy across multiple card providers. All required fields are validated with descriptive error responses for invalid input.

Please refer to our Open API documentation for more information on this.