Hi, Does anyone know if it’s possible in IFS10 to import and Finvoice xml file with posting information to IFS. I have tested by adding these additional tags to the invoice file but IFS seems to be ignoring those. I get the invoice in but the posting iformation I included in the file is not to be found in IFS , expect to find it in external supplier Invoice Posting Information

Finvoice xml file with posting information on line level

Page 1 / 1

Yes, it is possible.

<RowNormalProposedAccountIdentifier> = Account

<RowAccountDimensionText>B;C;D;F;G;H</RowAccountDimensionText> = Code parts values

from CODE_B ... CODE_H

I don’t know the last xml tag you’ve posted.

Hi,

Is there some additional parameter to set in the application for this to work? I have tested but do not get the posting info in to IFS.

/Anna

Hi @atvanst

do you get any error messages?

How do you import the file?

Did you create a media code and assign it to the supplier?

And don’t forget the tax codes. You can’t import them from the xml file.

Make sure that this checkbox is set to false:

Hi,

Thank you :-)

The checkbox on message default ‘Exclude posting information’ did the trick, we had it checked.

Hi, is this solution in IFSAPP10 ? And what must we do so Pagero can send us XML-files with this tags?

HI,
this solution should work in Apps 10 and Cloud as well. The above mentioned tags need to be present in the XML:
<RowNormalProposedAccountIdentifier> = Account

<RowAccountDimensionText>B;C;D;F;G;H</RowAccountDimensionText> = Code parts values

from CODE_B ... CODE_H

That would mean that the account and codepart information must be already available in Pagero, else it cannot be in the XML to be created.

Also note: If Account and Codepart Information is in the XML File AND a PO Number is also present in the XMl File then the Account and Codepart information will not be considered when the File is imported

thanks ! :-)

Hi again :-)If we wanr to use CODE_B in the tag

<RowAccountDimensionText>B;C;D;F;G;H</RowAccountDimensionText> = Code parts values

from CODE_B ... CODE_H , how should the tag look like ?

Lets assume you have the value 1000 for Codepart B and ABC for Codepart D that you would like use in the posting

the it looks like this: <RowAccountDimensionText>1000;;ABC;;;</RowAccountDimensionText>

Thanks again, and one more question is there a tag for tax-code ?

And could you tell where in the XML-file we shall put the different tags mentioned above ?

Sorry overlooked your comment ‘ And don’t forget the tax codes. You can’t import them from the xml file’

Tax Code is not available as Tag in the xml. In the following you will find an explanation about the concept for the XML Import and finally the logic beeing used to fetch the tax code from a XML.

The functionality for the supplier invoice import (especially with the supplier invoice workflow) is designed to be “independed” from a service provider who reads the information from an invoice and creates the xml.
There is no need for an exchange of any basic data with the service provide. This approach supports the principles for data avoidance and data economy and reduces the risk for data theft because it is one party less keeping the supplier data.
Using Purchase Orders together with the Supplier Invoice Workflow will improve data quality and reduce additional workload in the 3-way-match of PurchaseOrder-Delivery(qty)-Invoice. Purchase orders can be created for inventory parts as well as for non inventory part. Using purchase orders with non inventory parts will make it obsolete to enter the account and codepart information already in the XML and no codepart-information needs to be shared with the service provider. When using already PurchseOrder-Approvals it is optional to validate the invoices in the supplier invoice workflow again. Invoices can be posted without any additional user involvement in case that there are no differences between Invoice-Delivery and Purchase Order.

When scanning or importing a E-Invoice the service provider can only work with the information on the invoice. That means for the tax code that the supplier will not know what ID you use for a specific tax code.
The tax code will be fetched based on the tax percentage that is written on the invoice and additional information (like supplier, Supply Country and Delivery Country) - if none of the condition matches the tax code from the supplier/invoice information will be used. Idf the tax % is <>0 the taxable tax code will be fetched if the tax % is 0 the non-taxable.