Customer invoice falsifier for D365 for Finance

In certain business scenarios, it may become necessary to update and reprint customer invoices in Dynamics 365 for Finance with corrected or intentionally adjusted figures. By selectively mapping only specific invoice header and invoice line fields for update, the ER configuration we are sharing here enables targeted adjustments without triggering recalculations of dependent totals. These electronic reporting configurations may also be used as a tutorial for the Excel imports in D365.

Check the above screenshot: assuming we’ve initially issued an invoice with 19% VAT instead of the reduced 7% VAT, the ratio between the SalesBalance (amount before VAT) and SumTax (total VAT amount) may be shifted while keeping the total invoice amount the same. Beware: to reflect the VAT manipulations in the tax books a separate [cumulative] GL journal must be posted manually. Please ensure any misaligned invoice reprints are clearly marked as adjusted copies to avoid confusion or compliance issues, though.

The underlying method uses the Electronic Reporting import configuration capabilities in Dynamics 365 for Finance. You may download the ER configurations here: CustInvoiceUpdater.zip. Unpack and import into the ER tree one by one, starting with the model. Use it at your own risk!

Key elements include:

Data Model – definition of the conceptual invoice structure (header amounts, line amounts, tax values, etc.).
Model Mapping for export and a model mapping To destination for the import (both in the same model mapping ER configuration) – links the data model fields to the relevant Dynamics 365 tables and columns.
Formats – define the export file structure (Excel) and the same import file structure and maps the file’s data to the model fields.

For a detailed description of the ER import concept and practical configuration guidance, check Electronic Reporting in Data Migration.

The process follows a three-step cycle:

Export: extract invoice data from Dynamics 365 into an Excel using the “CustInvoiceJourDump format” ER export configuration.
Adjust / Transform: modify the extracted data in Excel, changing selected amounts while leaving others untouched.
Import: re-import the adjusted file by selecting the “CustInvoiceJour mapping” in the ER tree, clicking Designer, then Run at the “To destination” mapping, and uploading the Excel file. If the file is well formed and there is a match for every RecId of the invoice headers/lines, it updates the records in Dynamics 365 and says “Operation completed“.

In our scenario, the import mapping is deliberately limited to only 3 or better to say 6 amounts, both in the transaction currency and the accounting currency (the “MST” amounts): Sales subtotal amount, Total charges, VAT amount. A built-in validation ensures these three values still sum to the original invoice total, maintaining internal consistency while allowing the reprint to reflect updated breakdowns.

The “CustInvoiceTrans mapping” for invoice lines does not have this safeguard, since the invoice lines to not hold grand totals in D365.

The total invoice amount field was intentionally excluded from the update, because this may lead to a mismatch between the general ledger and the AR subledger.

Electronic reporting blog series

Filling PDF Forms with Electronic Reporting in Dynamics 365 for Finance

Dynamics 365 Electronic Reporting (ER) supports output into Excel, Word, and PDF formats. Excel and Word templates are well-covered in documentation and practice, but PDFs remain obscure – there’s only a short article Design ER configurations to fill in PDF templates – Finance & Operations | Dynamics 365 | Microsoft Learn from Microsoft.

The PDF/File component in ER is usable, it fills out static PDF forms. For example, one may take the VAT return or another tax declaration form, import into the ER configuration designer and get it filled out.

Technically, this resembles the old Dynamics Axapta approach using XFDF to inject data into form fields. That still seems to happen under the hood: you map values to fields, and the form gets filled in and flattened into a non-editable PDF. However, PDFs don’t support repeatable ranges like Excel – everything is fixed on the page. If there are – let’s say – several lines, then the subtotals below won’t slide on the PDF page. They’ll remain on the same page as placed on the PDF form, and remain on the exact place on the form.

To simulate Excel-like ranges, Microsoft introduced a naming trick. You create form fields named, e.g., LineNo1, LineNo2, …, LineNo10. In ER, you create a Field group containing a single LineNo field. ER fills LineNo1 with the first record, LineNo2 with the second, and so on. If only two records are present, only LineNo1 and LineNo2 get filled—the rest stay blank. You must not exceed the number of fields available in the form: 11 records will crash the report.

To prepare such a form, you need Adobe Acrobat (not the free Reader). Create a fillable form and assign field names. For repeated fields like headers or footers (e.g. Total_pages), it’s okay to copy-paste – Acrobat auto-numbers them visually (Total_pages#1, #2) but they’re still internally just one field, and ER will fill all copies identically. That is ideal for values repeated on every page.
For tables where every row must be unique, the fields must have unique names (LineNo1, LineNo2, etc.). Renaming manually gets tedious fast. A handy script Acrobat — Rename Duplicate Fields to Unique Fields | Try67 | Custom PDF tools (the script is commercial + Adobe Acrobat Pro is required) automates this: draw a rectangle over the fields, and it appends unique suffixes to overlapping fields across pages. You can prepare a single line of fields, copy-paste the line (do not shuffle but always keep adding them in the strict order from top to bottom: Acrobat keeps track of their numbers and sorts them internally), then start replicating blocks of lines until the page is full, copy-paste full pages in the Acrobat’s “Organize pages” tool, and then batch-rename everything.
Back in ER: in the Format mode, add a PDF/File object and point it to your PDF template. Use the button Import / Update from PDF once to pull in field definitions. Don’t use “Update from PDF” again – it can scramble your mapping. Grouping fields by suffix (e.g., LineNo1..10) doesn’t always work automatically, so you might have to manually create a field group and drop in the core field (LineNo) without suffix.
Apply ENUMERATE(Lines) to record lists to create a structure where @.Number gives you the index (1-based) and @.Value gives the record. Then, in the Mapping mode, set the Name property of the line field in the lower right corner to "LineNo"&TEXT(@.Number), then assign the value from @.Value.YourField as usual with the Bind button. By the way, the order of fields doesn’t matter – unlike Excel, where rows and columns are positional, the PDF is filled at once using a key-value approach (essentially, an FDF file).
Don’t exceed the number of fields in your form. There’s no pagination or overflow – ER won’t split lines across multiple copies of the form. You may limit the data source with the formula like WHERE(@.LinesEnumerated,@.LinesEnumerated.Number<=10) to harden the report. You may also design a custom warning if the number of lines exceeds a certain threshold: Validate Electronic Reporting on execution and show errors or warnings – Arcadi Burria.

In short, ER’s PDF support is usable and powerful enough but static. With proper naming and field repetition strategy, it’s good for things like tax forms, returns, invoices with known limits, etc. The main challenge is preparing the template, not the mapping itself.

E-invoice and configurable business documents blog series

Dynamics 365 Intercompany Cost+ pricing

As highlighted 10 years ago by M. Aamer in his article Inter-company goods trading (sales price equal to cost price) – Microsoft Dynamics AX 2012 – Microsoft Dynamics 365 Blog, there is a parameter Unit price equal to cost price in the intercompany settings in Dynamics 365 for SCM, which enforces the intercompany purchase price at the cost price in the intercompany selling company.

The system tries to update the Sales order – Purchase order pair on 3 occasions:

ICO sales order line creation;
reservation of the goods in the supplier company;
release (!) to the warehouse in that company i.e., just before picking.

The resulting sales price is the current moving average stock price. D365 traverses the inventory transactions, and if no price is known at the given inventory dimensions, it defaults to the price at the item master (this may be relevant in the engineer-to-order scenario, where the ultimate cost price becomes known just shortly before the shipping).

As noted many years ago by my humble self 😉 , the pure cost price is normally not allowed by accounting standards: the “arm’s length” principle must be respected in transfer pricing between companies within a group i.e., there must be a markup on top. The Intercompany percent charge was developed recently by Microsoft to comply: Set up charges on intercompany orders – Supply Chain Management | Dynamics 365 | Microsoft Learn.

At some locations, the misc. charge is not good enough, as the auditors favour an “opaque” sales price with an embedded markup percentage. This may in principle be achieved with a negative line discount to the sales price = cost price. Normally, negative discounts are frowned upon by D365: “Field 'Discount percentage 1'(= -15,00) can only contain positive numbers.“, but the trick described in the blog “Overwrite a read-only configuration in D365FO” will let you import such a trade agreement.

At the recipient’s side, at the ICO Purchase order, the accounting distribution will be split into the base price (= ICO cost) and the [negative] discount. To satisfy the request for one single SO revenue GL transaction and one single PO change-in-stocks GL transaction, a customization was made out of pure desperation. The markup percentage is stored in a custom field Intercompany percent at the seller’s Item group, and quietly added to the net sales price in the following routine (you may download the source code here: ICOCostPlus.axpp):

				
					[ExtensionOf(classStr(SalesLineType))]
final class SalesLineType_ICOCostPlus_Extension
{
    public CostPrice interCompanyCalcSalesPrice()
    {
        SalesPrice          salesPrice = next interCompanyCalcSalesPrice();

        if (! salesLine.InterCompanyInventTransId ||
            salesLine.SalesQty < 0 ||
            ! salesLine.isStocked())
        {
            return salesPrice;
        }
        if (! salesTable.interCompanyEndpointActionPolicy().UnitPriceEqualsCostPrice)
        {
            return salesPrice;
        }

        InventItemGroup itemGroup = InventItemGroupItem::findByItemIdLegalEntity(salesLine.ItemId, salesLine.DataAreaId).itemGroup();

        if (itemGroup.ICOSalesPercentMarkup != 0)
        {
            salesPrice += CurrencyExchangeHelper::price(salesPrice * itemGroup.ICOSalesPercentMarkup/100, salesLine.CurrencyCode);
        }

        return salesPrice;
    }

}

Yearly Archives: 2025

Customer invoice falsifier for D365 for Finance

Customer invoice falsifier for D365 for Finance

Electronic reporting blog series

Filling PDF Forms with Electronic Reporting in Dynamics 365 for Finance

Filling PDF Forms with Electronic Reporting in Dynamics 365 for Finance

E-invoice and configurable business documents blog series

Dynamics 365 Intercompany Cost+ pricing

Dynamics 365 Intercompany Cost+ pricing

Revenue recognition and deferred cost blog series