This article explains about the issues of missing data in Basware accrual reports since 26.3.1 release and solution/workaround to these issues.

Issue Start: April 08, 2026

Solution:
We have implemented the fix for this issue in Basware release 26.4.3 and 26.5.

You can find the exact deployment date under Service Status > Extended Release Schedule in our Customer Service Portal.

In the release notes, the reference for this issue is the Support System Id BWPB0048786.

Issue:
We identified two scenarios where data is missing in Accrual reports:

Scenario 1: Coding rows exist.
Still data is missing when there is a coding difference at the time of accrual report generation.
This behaviour is as per design.

Solution: Enable the checkbox “Apply coding for invoices with coding difference” when generating the accrual report.

Handling of partly coded invoices

• • By default: 
    • Partly coded invoices are shown as a single line without coding details.
  • Optional configuration: 
    • When the option “Apply coding for invoices with coding difference” is enabled:
      • The report includes one line per existing coding row
      • In addition, a balance line is added to represent the portion of the invoice amount that is not yet coded. For this line, all coding dimensions are intentionally empty, indicating missing coding values.

For example:
1. Invoice with two coding rows but have coding difference. By default in Accrual report: Partly coded invoices are shown as a single line without coding details.

Invoice with two coding rows but have coding difference:

 

Default Accrual report:

Generated Report:

Solution: Enable the checkbox “Apply coding for invoices with coding difference” when generating the accrual report.

Generated report after solution:

• When the option “Apply coding for invoices with coding difference” is enabled:
  • The report includes one line per existing coding row
  • In addition, a balance line is added to represent the portion of the invoice amount that is not yet coded. For this line, all coding dimensions are intentionally empty, indicating missing coding values.

Scenario 2: No coding rows are present
As per bug fix in 26.3.1 release: AP-3014: In accrual reports coding fields show header data when invoice has no coding row 
Support system id: BWPB0048485 

Problem: When the user requested an accrual report and an invoice contained no coding rows, the coding fields incorrectly displayed values taken from the invoice header.
After bug fix impact to the customer: The coding fields remain empty when an invoice has no coding rows. However, if invoice fields are configured for the coding rows, those values are populated in the export (for example fields starting with "InvoiceHeader." or "Invoice."). 

But some customer expects data to be populated in Accrual report from the invoice header. 
This is a known issue reported to R&D with Major priority. In the release notes, the reference for this issue is the Support System Id BWPB0048786.

Workaround: Mapping invoice header fields in accrual report.
Navigate to Configuration Tool → Entities and Screens → All Screens → Invoice List PRO → Search → Coding Rows, and map the required field (e.g., Invoice.GrossSum) so that the value is retrieved from the invoice header when coding rows are absent.

Configuration: Both GrossSum and Invoice.GrossSum

GrossSum field will have value from the coding rows, and Invoice.GrossSum field will have value from invoice header in Accrual report.

Similarly, if additional fields need to be populated in accrual reports from the invoice header when coding rows are absent, they can be configured in the same way as described above. 



Example: Invoice with no coding rows


Accrual report:

Solution

We have implemented the fix for this issue in Basware releases 26.4.3 and 26.5

You can find the exact deployment date under Service Status > Extended Release Schedule in our Customer Service Portal.

In the release notes, the reference for this issue is the Support System Id BWPB0048786.
It is also placed as a candidate to next possible MR release. 

After the fix: NetSum, GrossSum, and TaxSum are correctly populated from the invoice header.
Values in both company and organization currency are also included. So, after the bug fix following fields will be auto populated in the accrual report in case of NO coding:
NetSum
NetSumOrg
NetSumComp
GrossSum
GrossSumOrg
GrossSumComp
TaxSum
TaxSumOrg
TaxSumComp

Workaround can be reverted for above fields after the fix is in place unless customer wishes to keep the fields visible in the report.

**NOTE**
if additional fields [other than mentioned above] need to be populated in accrual reports from the invoice header when coding rows are absent, they can be configured in the same way as workaround mentioned above to map invoice header fields in accrual report.

Further Support

If you would like to raise a case regarding this issue, please use this link: Support case

 

What Happened?

After a bug fix in Basware release 26.3.1 (AP-3014), Coding-related information was not being displayed in accrual reports for invoices that did not contain coding rows. Some report fields that were expected to obtain their values from the invoice header were not populated correctly, resulting in missing data in the report output.

Root Cause Analysis:

Why and How did it Happen?

A previously reported issue (AP-3014) identified that header-level data was being copied into coding-row fields when both fields shared the same binding path, even when coding rows were not present.

To address that issue, the application logic was modified to prevent header data from being copied to coding-row fields when coding rows did not exist. As a side effect of this change, certain accrual report fields that relied on header-level values were no longer populated, causing the missing data observed in accrual reports.

Impact Analysis:

How are customers Impacted?

• Approximately 50+ customers were affected.
• Accrual reports may have displayed incomplete coding-related information.
• No service outage, downtime, or rollback was required.
• As a temporary workaround, customers were advised to include the required header-level fields directly in their reports (for example, NetSum, GrossSum, and TaxSum) to ensure the necessary data was available.

Timeline of Events:

Event Start: April 8, 2026

Event End: May 21, 2026

Corrective Measure

What are our Corrective Actions planned/completed to restore services for this incident? 

The application logic has been updated so that NetSum, GrossSum, and TaxSum are always sourced directly from the invoice header, regardless of the presence or absence of coding rows.

This change restores the expected behavior and ensures these values are consistently available in accrual reports.

Preventative Measures

What are our Preventative actions planned/completed to prevent the recurrence of this incident?

To reduce the likelihood of similar issues in the future, the following measures have been implemented:

1. Enhanced impact analysis will be performed before implementing defect fixes to identify potential effects on existing functionality.
2. Cross-functional design reviews will be conducted for changes affecting shared reporting components and customer-facing behavior.
3. Additional regression testing has been added to validate report behavior for invoices both with and without coding rows.
4. Broader customer scenarios will be considered during the defect assessment and remediation process to ensure changes do not introduce unintended side effects.