9/7/2026

Bug-Fixes

#1 Improved API matching logic for buyers and suppliers to prevent profile overwrites from duplicate BRNs.

1. Overview

Improved the buyer and supplier matching logic when creating invoices via API to prevent existing company profiles from being overwritten when different companies share the same Business Registration Number (BRN).

2. What Has Changed

Previous:
The system identified buyer/supplier profiles using BRN only.
If another company submitted an invoice with the same BRN, the existing profile could be reused and updated, resulting in incorrect company information.

Now:
The system now matches buyer/supplier profiles using a combination of:

• BRN

• TIN

• Company Name
  An existing profile will only be reused when all three values match.
  If any of these values differ, a new buyer/supplier profile will be created instead.

3. Impact

• Prevents accidental replacement of existing buyer and supplier information.

• Preserves the accuracy of company records.

• Reduces data inconsistency when integrating invoices through the API.

#2 Resolved an issue preventing company email settings from being disabled by prioritizing company-specific configurations over system defaults.

1. Overview
Fixed an issue where company email settings could not be disabled because the system continued using the default configuration instead of the company's own setting.

2. What Has Changed

Previous:
When a company turned an email setting OFF, the system ignored the company configuration if the default setting was ON.
As a result, email-related features remained enabled unexpectedly.

Now:
Company-specific settings now always take precedence over the default configuration.
When a company turns an email setting OFF, the system correctly respects that choice.

3. Impact

• Company preferences are now applied consistently.

• Prevents unintended email notifications or email-related actions.

• Improves reliability and predictability of system settings.

#3 Enhanced status tracking by separating Request Status and Invoice Status to provide clearer visibility into independent workflows.

1. Overview
Enhanced status tracking by introducing separate Request Status and Invoice Status fields, providing clearer visibility into both the request workflow and invoice lifecycle.

2. What Has Changed

Previous:
A single Status field was used to represent both request progress and invoice status.
Changes to one status could make it difficult to determine the actual state of the request or invoice.

Now:
The system now maintains two independent status fields:
Request Status – Tracks the progress of the request workflow.
Invoice Status – Tracks the current invoice lifecycle.
Each status is managed independently, ensuring updates to one do not affect the other.

3. Impact
Provides clearer tracking of requests and invoices.
Improves visibility for users and support teams.
Reduces confusion when monitoring request progress and invoice processing.