Scope and supported business processes
Truvio ExFlow e-Invoicing for Poland exchanges invoices and corrective invoices through the Pagero integration with KSeF. ExFlow Document Integration sends the XML generated from posted Dynamics 365 Finance invoices, retrieves clearance responses and exposes the document status to the user. Incoming invoices are retrieved through Pagero and transferred to ExFlow AP for processing.
ExFlow e-Invoicing does not create or post accounts receivable invoices or extend the posting functionality of the Polish localization in D365 Finance. Support for a business process depends on both:
- D365 Finance being able to represent and post the transaction.
- The selected Electronic Reporting (ER) configuration generating the required invoice XML for that transaction.
A process that can be posted in D365 Finance is not automatically covered by the selected ER configuration. Review the invoice scenarios with your D365 partner before enabling them.
Components required for Polish flows
- D365 Finance: Polish legal entity and customer master data, NIP identifiers, tax codes and exemption reasons, and Electronic Reporting configured for the required document types.
- ExFlow Document Integration: Version 1.3.1 or newer, fully configured for Pagero, with CTC flow = Yes in ExFlow document integration | Setup | Parameters | General.
- ExFlow AP: Version 2.18.0 or newer for the incoming invoice process. Direct Posting is required for the incoming KSeF number to be stored in the correct standard D365 table.
- Pagero: An account configured with the data and certificates or tokens required to connect to KSeF.
See Setting up the Polish legal entity for the setup requirements.
Supported business processes
The table distinguishes the ExFlow integration scope from processes handled by D365 Finance or Pagero. Support assumes that the prerequisites and the appropriate ER configuration are in place.
| Business process | ExFlow scope | Conditions and responsibility |
|---|---|---|
| Send an invoice to a domestic Polish customer | Supported. | D365 Finance posts the invoice and generates the XML. ExFlow Document Integration sends it through Pagero to KSeF. After clearance, KSeF makes the invoice available to the recipient. |
| Send a corrective invoice | Supported for the documented sales order, free text and project invoice flows. | D365 Finance must represent the correction correctly, and the selected ER configuration must map the original and corrected invoice information. |
| Submit an invoice for a foreign customer to KSeF | Supported clearance process. | ExFlow sends the invoice through Pagero and retrieves the clearance response, including the KSeF number and validation URL. |
| Deliver the cleared invoice to a foreign customer | Handled outside ExFlow Document Integration. | KSeF does not deliver the invoice to the foreign buyer. Use D365 Finance printing or email functionality that includes the KSeF number and QR code generated from the validation URL. |
| Monitor acceptance or rejection | Supported. | Retrieve the response using Get status or the customer document batch job. Review the document status and substatus in Outgoing documents or the Document integration workspace. |
| Store the outgoing KSeF number and validation URL | Supported after approval. | ExFlow stores these values in standard fields on the Invoice Journal record so that D365 Finance can use them when printing the invoice. |
| Receive a KSeF-approved vendor invoice | Supported. | Retrieve the invoice through Pagero and import it into ExFlow AP using the configured import method and the standard AP process. |
| Preserve the incoming KSeF number | Supported with Direct Posting. | The number is extracted into the UUID field. ExFlow AP must use Direct Posting for storage in the correct standard D365 table. |
| Advance invoices | Not supported. | Outside the documented Polish ExFlow scope. |
| Offline invoices | Not supported. | Outside the documented Polish ExFlow scope. |
Supported invoice types and ER configurations
The documented Polish scope covers sales invoices and corrective invoices for sales orders, free text invoices and project invoices, together with the incoming AP invoice process.
| Outgoing document type | ER configuration coverage | Conditions |
|---|---|---|
| Sales order invoice | Microsoft Sales e-invoice (PL) generating FA3 XML accepted by Pagero, should be used for these scenarios. | The selected configuration must cover the posted invoice data and the required tax treatment. |
| Free text invoice | Microsoft Sales e-invoice (PL) generating FA3 XML accepted by Pagero should be used for these scenarios. | The selected configuration must cover the posted invoice data and the required tax treatment. |
| Sales order or free text corrective invoice (credit note) | Use applicable Microsoft Microsoft Sales e-invoice (PL) configuration. | Follow the corrective invoice line pattern described below and validate the generated XML. |
| Project invoice or project corrective invoice | Microsoft Project e-invoice (PL), generating FA3 XML accepted by Pagero. | Project documents require the Microsoft configurations. |
Corrective invoices
When creating a corrective invoice (credit note), use the D365 Finance pattern described in Sending AR invoices:
- An original line with negative values to reverse the previously submitted line.
- A corrected line.
For the Pagero integration, the Polish setup page strongly recommends setting Assign sequential line numbers when posting customer invoice lines = Yes in Accounts receivable | Setup | Accounts receivable parameters | Updates | Optimize batch and posting processing.
The ER configuration must support the correction scenario. Posting a credit note alone does not establish that the generated XML contains the required correction information.
Clearance responses and automation
An outgoing invoice remains in Sent status until the KSeF application response is retrieved. The document status and substatus then reflect the response.
Use Get status manually or configure ExFlow execute customer documents under ExFlow document integration | Periodic | Batches | Customer to automate the outgoing process and status retrieval.
After approval, ExFlow stores the KSeF number and validation URL. If KSeF rejects the invoice, review the returned error, correct the relevant data and resend the document.
Incoming invoices and KSeF number
Incoming invoices follow the standard ExFlow AP import and processing flow. The Polish integration additionally extracts the KSeF number embedded in the incoming invoice and stores it in the UUID field.
The Direct Posting requirement applies to storing this number in the correct standard D365 table. See Receiving AP invoices.
Limitations and implementation notes
- Advance and offline invoices are not supported. Do not infer support from the availability of such processes in D365 Finance.
- Project invoices require Microsoft ER configurations.
- Delivery after clearance to a foreign customer is outside ExFlow Document Integration. The customer must configure D365 Finance printing or email to include the KSeF number and the QR code.
- ER and tax setup determine scenario coverage. Review NIP identifiers, VAT treatment, exemption reasons and correction mapping for each business process.
- Incoming KSeF-number storage requires Direct Posting. Confirm this setting before relying on the number being available in the standard D365 tables.
- Validate the complete process before production. The Polish setup page recommends generating a test invoice with Microsoft Sales e-invoice (PL) and uploading the FA3 output to the KSeF test or pre-production environment to validate the data and tax coding. Also verify the Pagero integration and the applicable outgoing or incoming flow.
Planned capabilities
The Polish flow documentation does not specify release dates or planned support for additional business processes. Advance and offline invoices remain outside the scope described on this page.