Problem creating ‘Invoice separately’ See ticket 00150654

[CharlotteJB1]

Hi, 

When creating sales order the ‘Invoice separately’ is unchecked on order type, Visma still create invoices separately. See ticket 00150654. 

Visma creates invoices basted on Adress ID, in our case the address never chanced in Visma but it’s still creating invoices separately.  Visma is connected to Upsales. When we generate new invoices, we want the lates information from the customers, way use the Adress ID when the sales order was created? And witch settings can we use to makes sure the sale order will be invoices at once?

[Magnus Johnsen]

The issue has been reviewed and is currently in the backlog. 

[Magnus Johnsen]

Hi,

This seems to be related to the ERP itself and not the API, please contact your ERP support for help regarding this.

Contacting Visma Partner Service / Visma.net ERP Support

[CharlotteJB1]

The ERP support told us to contact you. The integration between Visma.net and Upsales create this problem.

[Magnus Johnsen]

Judging by the ticket, the issue is that one user has updated the address of the customer which creates a new adress ID even if the value is set to the same. This causes the automatic scheduling process to group them separately.

I'll send you the name if the user that updated the address in a PM, then you should check with the developers of Upsales and the user as to why this is being done.

Thank you. 

[Magnus Johnsen]

Could you please explain what the issue is and what the workflow is?

What do you do when generating the invoices? Are you using the automation in the ERP or are you posting to the customerInvoice endpoint?

[CharlotteJB1]

Hi Magnus, 

We are using the automation in the ERP. 

Step 1. Create a sales order manually

Step 2. Create Shipment

Sep 3. Prepare Invoice (routine)

When we generate new invoices from order in Visma.net the settings are made to have one invoice for each customer. But Visma.net generates multiple invoices for each customer. It’s seems like Visma.net generate one invoice for each address ID.  We would like to have one invoice per customer regardless address ID.

[Magnus Johnsen]

As they explained earlier in the case as well, the system sends these invoices in different batches because someone has updated the address of the customer. Have you been able to find out what happened in the cases where this happens?

When the customer address is updated, a new revision of the address in our system is saved, which is handled as a separate address.

[CharlotteJB1]

From Upsales: 
New information is added, changed or disappears. It does not have to be information needed to sync to Visma.NET. As soon as we feel that something is happening on the customer card, we sync everything to Visma.NET to be on the safe side that there is always correct information in both systems

[Magnus Johnsen]

Ok, thank you we'll have a look at it and report it to the development team. 

[CharlotteJB1]

Thank you 🙂 

[Magnus Johnsen]

This is in the backlog of the development team. They will investigate this to see if this is a bug or intended behavior.

For now, the best workaround would be to first check the customer card in Financials and the information that you need to update from Upsales, if the address is not changed, we recommend not sending it for now.

As soon as we have more information from the development team we will give you an update at the moment we are not able to provide an ETA. 

[CharlotteJB1]

As we said, it is not the address itself that changes, but whether Upsales has made a event on the customer. Which can be every other day. Even though we keep track of whether the customer has been updated, K3 still needs to invoice its customers. We need a workaround that makes it easy for the customer to make a collective invoice in Visma.net. It's a pity because the customer is happy with their way of working. If only the routine in Visma.net checked customer number instead of address id, this would not have been a problem.

[Magnus Johnsen]

Hi,

We'll have a look at the issue regarding the update via the API, if any update to the customer endpoint causes a new revisionID to be triggered. 

We've checked with the ERP support, and as far as we can tell there does not seem to be a workaround for the routine in the ERP UI.

Could you please provide us with some examples on what customer updates Upsales say they are sending that triggers a new address?

The collection invoice routine is not only going by address "revisionID", it's a combination of customerNumber and the address. 

[KonsultVn]

Hi, 

From Upsales: 
New information is added, changed or disappears. It does not have to be information needed to sync to Visma.NET. As soon as we feel that something is happening on the customer card, we sync everything to Visma.NET to be on the safe side that there is always correct information in both systems. 

Exempel: See Custumer 441025 in Visma.net. 

[Magnus Johnsen]

Hi,

Thank you, we'll forward this to the development team.

The issue is being prioritized.