Describe the issue
Subject: Subcontracting Extension – Missing "Get Receipt Lines" Functionality on Purchase Invoices Causes Invoice Mismatch and Compliance Issues
Product/Extension: Manufacturing – Subcontracting (Microsoft first-party extension)
Environment: Production database
Severity: High – Recurring business process issue, not an edge case
Summary
Since installing the Subcontracting extension, users are no longer able to use the "Get Receipt Lines" function on a Purchase Invoice when the underlying Purchase Orders were created via the Subcontracting Worksheet. This regression forces users to create one Purchase Invoice per Purchase Order instead of a single consolidated invoice, which does not reflect how vendors actually invoice and creates downstream financial, operational, and legal reporting issues.
Business Scenario
This is a routine, recurring scenario, not an exception:
Our customer issues multiple subcontracting Purchase Orders to the same Vendor throughout a month (via the Subcontracting Worksheet), each with different order dates.
The Subcontractor delivers partial quantities against several of these orders and issues a single combined invoice covering lines from multiple Purchase Orders.
The Vendor's invoice may also show a small VAT rounding difference (e.g., 0.02) from the system-calculated amount, which falls within the configured tolerance.
Previous (Expected) Behavior
Prior to installing the Subcontracting extension, users handled this correctly and efficiently:
Created a single Purchase Invoice.
Used "Get Receipt Lines" to pull in receipt lines from all relevant Purchase Orders.
Verified the total against the Vendor's invoice.
Adjusted the VAT Amount on the Purchase Invoice Statistics page if within tolerance.
Current (Actual) Behavior
With the Subcontracting extension installed, "Get Receipt Lines" is not available on Purchase Invoices for subcontracting orders. As a result:
Users must create a separate Purchase Invoice for each Purchase Order, even though the vendor issued one combined invoice.
There is no mechanism in the system to reconcile the combined total or VAT amount across these multiple invoices against the single vendor invoice, increasing the risk of posting errors.
Because "Vendor Invoice No." must be unique per invoice, users are forced to artificially modify/append to the actual vendor invoice number for each additional Purchase Invoice, so the recorded number no longer matches the document received from the vendor.
Business/Compliance Impact
Increased error risk: No consolidated total or VAT check across multiple invoices representing one physical vendor invoice.
Data integrity issue: Vendor Invoice No. no longer matches the source document exactly, since it must be artificially altered to remain unique across multiple system invoices.
Regulatory impact (Romania): Romanian legislation requires companies to report the number of invoices received per vendor and issued per customer (SAF-T , D394). Under the current behavior, the Subcontractor will report 1 invoice issued, while our customer will report multiple invoices received for the same document — creating a mismatch in statutory reporting between the two parties.
Why This Is a Bug
This is a regression, not a missing enhancement: a functionality that worked correctly and reliably (consolidated invoicing via Get Receipt Lines) has been made unavailable by the new extension, with no equivalent replacement. The new behavior introduces financial reconciliation risk, data accuracy issues, and regulatory reporting discrepancies that did not exist before.
Requested Resolution
Please restore "Get Receipt Lines" functionality (or an equivalent consolidation mechanism) for Purchase Invoices linked to subcontracting Purchase Orders, allowing multiple orders/receipts from the same vendor to be combined into a single Purchase Invoice, consistent with prior behavior.
Expected behavior
Users should be able to create a single Purchase Invoice that consolidates receipt lines from multiple subcontracting Purchase Orders issued to the same Vendor, using the "Get Receipt Lines" function — consistent with standard (non-subcontracting) Purchase Invoice behavior.
Specifically:
"Get Receipt Lines" should be available and functional on Purchase Invoices tied to subcontracting Purchase Orders, allowing selection of receipt lines across multiple orders for the same Vendor.
The resulting single Purchase Invoice should allow the user to verify the total invoice amount and VAT Amount against the Vendor's actual invoice, and adjust the VAT Amount on the Purchase Invoice Statistics page when the difference is within the configured tolerance — exactly as it worked before the extension was installed.
The "Vendor Invoice No." entered on this single Purchase Invoice should be able to match the Vendor's actual invoice number exactly, without needing to be artificially modified to satisfy uniqueness constraints, since only one system invoice should correspond to one physical vendor invoice.
The number of Purchase Invoices posted in the system for a given period should correspond 1:1 with the number of physical invoices received from the Vendor, ensuring accurate statutory reporting (e.g., the Romanian informative statement on invoices received/issued).
In short, the subcontracting-specific Purchase Order/Receipt process should not change or restrict how invoicing is consolidated at the Purchase Invoice level — subcontracting orders should be invoiced with the same flexibility as standard Purchase Orders.
Steps to reproduce
All steps were described in the Description
Additional context
No screenshots because the Get Receipt line has a filter with SetRange("Prod. Order No.",''). The fix I can provide is only removing the filters and the error, but might be other implications regarding costs of the production for the subcontracting operation.
Describe the issue
Subject: Subcontracting Extension – Missing "Get Receipt Lines" Functionality on Purchase Invoices Causes Invoice Mismatch and Compliance Issues
Product/Extension: Manufacturing – Subcontracting (Microsoft first-party extension)
Environment: Production database
Severity: High – Recurring business process issue, not an edge case
Summary
Since installing the Subcontracting extension, users are no longer able to use the "Get Receipt Lines" function on a Purchase Invoice when the underlying Purchase Orders were created via the Subcontracting Worksheet. This regression forces users to create one Purchase Invoice per Purchase Order instead of a single consolidated invoice, which does not reflect how vendors actually invoice and creates downstream financial, operational, and legal reporting issues.
Business Scenario
This is a routine, recurring scenario, not an exception:
Our customer issues multiple subcontracting Purchase Orders to the same Vendor throughout a month (via the Subcontracting Worksheet), each with different order dates.
The Subcontractor delivers partial quantities against several of these orders and issues a single combined invoice covering lines from multiple Purchase Orders.
The Vendor's invoice may also show a small VAT rounding difference (e.g., 0.02) from the system-calculated amount, which falls within the configured tolerance.
Previous (Expected) Behavior
Prior to installing the Subcontracting extension, users handled this correctly and efficiently:
Created a single Purchase Invoice.
Used "Get Receipt Lines" to pull in receipt lines from all relevant Purchase Orders.
Verified the total against the Vendor's invoice.
Adjusted the VAT Amount on the Purchase Invoice Statistics page if within tolerance.
Current (Actual) Behavior
With the Subcontracting extension installed, "Get Receipt Lines" is not available on Purchase Invoices for subcontracting orders. As a result:
Users must create a separate Purchase Invoice for each Purchase Order, even though the vendor issued one combined invoice.
There is no mechanism in the system to reconcile the combined total or VAT amount across these multiple invoices against the single vendor invoice, increasing the risk of posting errors.
Because "Vendor Invoice No." must be unique per invoice, users are forced to artificially modify/append to the actual vendor invoice number for each additional Purchase Invoice, so the recorded number no longer matches the document received from the vendor.
Business/Compliance Impact
Increased error risk: No consolidated total or VAT check across multiple invoices representing one physical vendor invoice.
Data integrity issue: Vendor Invoice No. no longer matches the source document exactly, since it must be artificially altered to remain unique across multiple system invoices.
Regulatory impact (Romania): Romanian legislation requires companies to report the number of invoices received per vendor and issued per customer (SAF-T , D394). Under the current behavior, the Subcontractor will report 1 invoice issued, while our customer will report multiple invoices received for the same document — creating a mismatch in statutory reporting between the two parties.
Why This Is a Bug
This is a regression, not a missing enhancement: a functionality that worked correctly and reliably (consolidated invoicing via Get Receipt Lines) has been made unavailable by the new extension, with no equivalent replacement. The new behavior introduces financial reconciliation risk, data accuracy issues, and regulatory reporting discrepancies that did not exist before.
Requested Resolution
Please restore "Get Receipt Lines" functionality (or an equivalent consolidation mechanism) for Purchase Invoices linked to subcontracting Purchase Orders, allowing multiple orders/receipts from the same vendor to be combined into a single Purchase Invoice, consistent with prior behavior.
Expected behavior
Users should be able to create a single Purchase Invoice that consolidates receipt lines from multiple subcontracting Purchase Orders issued to the same Vendor, using the "Get Receipt Lines" function — consistent with standard (non-subcontracting) Purchase Invoice behavior.
Specifically:
"Get Receipt Lines" should be available and functional on Purchase Invoices tied to subcontracting Purchase Orders, allowing selection of receipt lines across multiple orders for the same Vendor.
The resulting single Purchase Invoice should allow the user to verify the total invoice amount and VAT Amount against the Vendor's actual invoice, and adjust the VAT Amount on the Purchase Invoice Statistics page when the difference is within the configured tolerance — exactly as it worked before the extension was installed.
The "Vendor Invoice No." entered on this single Purchase Invoice should be able to match the Vendor's actual invoice number exactly, without needing to be artificially modified to satisfy uniqueness constraints, since only one system invoice should correspond to one physical vendor invoice.
The number of Purchase Invoices posted in the system for a given period should correspond 1:1 with the number of physical invoices received from the Vendor, ensuring accurate statutory reporting (e.g., the Romanian informative statement on invoices received/issued).
In short, the subcontracting-specific Purchase Order/Receipt process should not change or restrict how invoicing is consolidated at the Purchase Invoice level — subcontracting orders should be invoiced with the same flexibility as standard Purchase Orders.
Steps to reproduce
All steps were described in the Description
Additional context
No screenshots because the Get Receipt line has a filter with SetRange("Prod. Order No.",''). The fix I can provide is only removing the filters and the error, but might be other implications regarding costs of the production for the subcontracting operation.