The "Visma.net AutoInvoice mapping
tool" is an application that can be used to configure mapping for some fields
not included in the default mapping and override some of the default
mapping. The application is run independent of Visma Business.
Files included in the package
Visma.Net.AutoInvoice.MappingTool.exe
Visma.Net.AutoInvoice.MappingColumns.xml
Visma.Net.AutoInvoice.MappingTool.exe.config
Visma.UI.WPF.dll
These files are in the "Visma.net AutoInvoice mapping
tool" folder, which is a sub-folder of Tools, found
in the installation ISO and in the Visma Business program folder after installation.
How to use the Visma.net AutoInvoice mapping
tool
Start the application with Visma.Net.AutoInvoice.MappingTool.exe. When opened, it opens an
existing mapping files in the default path, which is
\Business\Plugins. This location can be changed
with Select folder and browsing using the file
explorer. If a mapping file is saved, the changed path is remembered the
next time the application is started.
Select folder
This opens a dropdown that contains favourite paths if any have been used. Use
Browse… to navigate in the explorer to find a
suitable folder for the mapping file or to open an existing mapping file.
Note that you will only be able to select folder, the application will look
for a file with the default file name (AutoInvoiceMapping.xml) in the
selected path and display the result if found.
Visma UBL section
The box contains available high level tags which themselves do not have any content. When
you select one of the fields in this box, you will see content tags appear
in the Visma UBL content field and Visma Business columns boxes.
Visma UBL content field
These are the format fields actually used for mapping from Visma Business.
Visma Business
columns
The Visma Business columns made available for the Visma UBL content
field.
Configured mappings
The box contains mappings already created, both saved to file and those selected in the
current session.
How to set a mapping
From left to right, select Visma UBL section tag, Visma UBL
content field to map to, and Visma Business column for output. The selected mapping will appear in
Configured mappings. You may select as many Visma Business columns as you want for a single Visma UBL content
field and use the same column for more than one
Visma UBL content field. Columns already used for
the Visma UBL content field will be shown in the list
as selected. If you wish to remove a mapping, either click on it again in
Visma Business columns to unselect, or click on the trash can in
Configured mappings.
Save mappings
When clicking on Save mappings, the file AutoInvoiceMapping.xml is
created in the path defined in Select folder. If it
already exists, the contents will be replaced.
Closing the application
The application may be closed either by clicking Cancel or clicking
the X in the upper right corner. If there are unsaved mappings in
Configured mappings, a message will be displayed
asking if the application should be closed.
How to use the created mapping file
By default, Visma Business will look for AutoInvoiceMapping.xml in \Business\Plugins of the running
instance. This will be used for all companies in this instance. The
alternative is to select the file in the Företagsuppgifter column
AutoInvoice mappnings fil in Visma Business. When set in this field, the file will be used for this specific company.
Any file set in this column will be used regardless of file name, as long as
the contents are valid. Note that this only overrides the mapping for this
company. All other companies will still use the file in \Business\Plugins if
one exists. Visma Business will now look for the mapping file when sending invoices and either
replace default mapping for the configured fields or add new that are not in
the default mapping.
Use of configured mapping and incoming orders from AutoInvoice
If a sales order has been created from the Incoming document table, ie received from
customer through AutoInvoice, any configured invoice mapping done in the Visma.net AutoInvoice mapping
tool for the following elements will be replaced by the default mapping when
invoiced:
Note
AccountingCustomerParty (whole section)
DeliveryLocation (whole section)
InvoiceLine->Note
This is to make sure that the customer's information on the incoming order
is kept in the document throughout the flow.
Important to consider when mapping LineInvoicePeriod
Be aware of that if mapping the LineInvoicePeriod start and end period to
the order line fields From and To, these fields must have been set up
as date fields. If they contain data in any other format, the invoice
sending will fail and cause an error message to appear on screen.
Important to consider when mapping AdditionalItemProperty
Be aware of that while AdditionalItemProperty is optional, both fields in
the section (Name, Value) must be mapped to avoid validation error.
Vi uppskattar din feedback. Skicka feedback om detta ämne till Visma.