The goal was to update invoicerows by polling GET on already existing invoice rows which had article, description, amount, unit, price, account, and subaccounts on them. We extract the dates from the description and assign them to the accrual dates along with an accrual key in a mapped update dto. If the invoice had more then five rows, only the first five rows would receive the updated accrual key, but all would receive the dates. Meaning we would have updated all rows but missing accrual keys on n-5 rows. This was also tested in a demo company so it has to be a bug. The workaround is currently to post (n = rows) n/5 customer invoices (same invoice head) with 5 rows of update dto each. ... View more

{ "ReferenceNumber": null, "Note": { "Value": "" }, "DocumentDate": null, "CurrencyId": null, "CreditTermsId": null, "Hold": null, "BranchNumber": null, "ExternalReference": null, "CustomerRefNumber": null, "InvoiceText": null, "ExchangeRate": null, "CustomerNumber": null, "SalesPerson": null, "LocationId": null, "InvoiceLines": [ { "InventoryNumber": null, "Description": null, "Quantity": null, "UnitPriceInCurrency": null, "Note": null, "Subaccount": null, "VatCodeId": null, "AccountNumber": null, "Operation": "Update", "LineNumber": { "Value": 1 }, "ManualDiscount": null, "DiscountPercent": null, "DiscountAmountInCurrency": null, "DeferralCode": { "Value": "06I1" }, "TermStartDate": { "Value": "2025-01-01T00:00:00" }, "TermEndDate": { "Value": "2025-12-31T00:00:00" } }, { "InventoryNumber": null, "Description": null, "Quantity": null, "UnitPriceInCurrency": null, "Note": null, "Subaccount": null, "VatCodeId": null, "AccountNumber": null, "Operation": "Update", "LineNumber": { "Value": 2 }, "ManualDiscount": null, "DiscountPercent": null, "DiscountAmountInCurrency": null, "DeferralCode": { "Value": "06I1" }, "TermStartDate": { "Value": "2025-01-01T00:00:00" }, "TermEndDate": { "Value": "2025-12-31T00:00:00" } }, { "InventoryNumber": null, "Description": null, "Quantity": null, "UnitPriceInCurrency": null, "Note": null, "Subaccount": null, "VatCodeId": null, "AccountNumber": null, "Operation": "Update", "LineNumber": { "Value": 3 }, "ManualDiscount": null, "DiscountPercent": null, "DiscountAmountInCurrency": null, "DeferralCode": { "Value": "06I1" }, "TermStartDate": { "Value": "2025-01-01T00:00:00" }, "TermEndDate": { "Value": "2025-12-31T00:00:00" } }, { "InventoryNumber": null, "Description": null, "Quantity": null, "UnitPriceInCurrency": null, "Note": null, "Subaccount": null, "VatCodeId": null, "AccountNumber": null, "Operation": "Update", "LineNumber": { "Value": 4 }, "ManualDiscount": null, "DiscountPercent": null, "DiscountAmountInCurrency": null, "DeferralCode": { "Value": "06I1" }, "TermStartDate": { "Value": "2025-01-01T00:00:00" }, "TermEndDate": { "Value": "2025-12-31T00:00:00" } }, { "InventoryNumber": null, "Description": null, "Quantity": null, "UnitPriceInCurrency": null, "Note": null, "Subaccount": null, "VatCodeId": null, "AccountNumber": null, "Operation": "Update", "LineNumber": { "Value": 5 }, "ManualDiscount": null, "DiscountPercent": null, "DiscountAmountInCurrency": null, "DeferralCode": { "Value": "06I1" }, "TermStartDate": { "Value": "2025-01-01T00:00:00" }, "TermEndDate": { "Value": "2025-12-31T00:00:00" } }, { "InventoryNumber": null, "Description": null, "Quantity": null, "UnitPriceInCurrency": null, "Note": null, "Subaccount": null, "VatCodeId": null, "AccountNumber": null, "Operation": "Update", "LineNumber": { "Value": 6 }, "ManualDiscount": null, "DiscountPercent": null, "DiscountAmountInCurrency": null, "DeferralCode": { "Value": "06I1" }, "TermStartDate": { "Value": "2025-01-01T00:00:00" }, "TermEndDate": { "Value": "2025-12-31T00:00:00" } }, { "InventoryNumber": null, "Description": null, "Quantity": null, "UnitPriceInCurrency": null, "Note": null, "Subaccount": null, "VatCodeId": null, "AccountNumber": null, "Operation": "Update", "LineNumber": { "Value": 7 }, "ManualDiscount": null, "DiscountPercent": null, "DiscountAmountInCurrency": null, "DeferralCode": { "Value": "06I1" }, "TermStartDate": { "Value": "2025-01-01T00:00:00" }, "TermEndDate": { "Value": "2025-12-31T00:00:00" } } ]} ... View more

{{ "SupplierNumber": { "Value": "50063" }, "SupplierReference": { "Value": "097889152621" }, "Note": { "Value": "https://cloud.mediusflow.com/hevinghagglund/#Tasks/ShowDocument/475" }, "ReferenceNumber": null, "CurrencyId": { "Value": "SEK" }, "Description": null, "DueDate": { "Value": "2023-02-25T01:00:00+01:00" }, "Date": { "Value": "2023-01-11T01:00:00+01:00" }, "SupplierTaxZone": { "Value": "01" }, "PaymentRefNo": { "Value": "097889152621" }, "ExchangeRate": null, "CashDiscountDate": { "Value": "2023-02-25T01:00:00+01:00" }, "PostPeriod": null, "InvoiceLines": [ { "LineNumber": { "Value": 1 }, "TransactionDescription": null, "CostInCurrency": { "Value": 409.52 }, "AccountNumber": { "Value": "4099" }, "VatCodeId": { "Value": "01" }, "DeferralCode": { "Value": null }, "Operation": "Insert", "SplitHierarchy": null, "SplitLine": null, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "8755101" }, { "SegmentId": 2, "SegmentValue": "1406" }, { "SegmentId": 3, "SegmentValue": "30" } ] }, { "LineNumber": { "Value": 2 }, "TransactionDescription": null, "CostInCurrency": { "Value": 0.1 }, "AccountNumber": { "Value": "3740" }, "VatCodeId": { "Value": "12A" }, "DeferralCode": { "Value": null }, "Operation": "Insert", "SplitHierarchy": null, "SplitLine": null, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "1000100" }, { "SegmentId": 2, "SegmentValue": "0000" }, { "SegmentId": 3, "SegmentValue": "00" } ] } ], "TaxDetailLines": null, "DocumentType": { "Value": "Invoice" } }} ... View more

Thanks!    (ID: 4228921) is now up and running.  We have the same error with company ID:4481022, 1374141, we checked the length of segmentvalue and it's correct.    ... View more

We send your jason file, but get the same error.  ... View more

Hi,  There are no branch or user restriction for the Subaccount Segments in the Financials ERP company.      {{ "SupplierNumber": { "Value": "50048 " }, "SupplierReference": { "Value": "100006.1" }, "Note": { "Value": ";Administrationstjänster//;Omkostnader//" }, "ReferenceNumber": null, "CurrencyId": { "Value": "SEK" }, "Description": null, "DueDate": { "Value": "2023-02-16T01:00:00+01:00" }, "Date": { "Value": "2023-01-17T01:00:00+01:00" }, "SupplierTaxZone": { "Value": "01" }, "PaymentRefNo": { "Value": "100006" }, "ExchangeRate": null, "CashDiscountDate": { "Value": "2023-02-16T01:00:00+01:00" }, "PostPeriod": null, "InvoiceLines": [ { "LineNumber": { "Value": 1 }, "TransactionDescription": null, "CostInCurrency": { "Value": 34246.58 }, "AccountNumber": { "Value": "4990" }, "VatCodeId": { "Value": "01" }, "DeferralCode": { "Value": null }, "Operation": "Insert", "SplitHierarchy": null, "SplitLine": null, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "30098" }, { "SegmentId": 2, "SegmentValue": "30098A001" }, { "SegmentId": 3, "SegmentValue": "000" }, { "SegmentId": 4, "SegmentValue": "00" } ] }, { "LineNumber": { "Value": 3 }, "TransactionDescription": null, "CostInCurrency": { "Value": -0.23 }, "AccountNumber": { "Value": "3740" }, "VatCodeId": { "Value": "12A" }, "DeferralCode": { "Value": null }, "Operation": "Insert", "SplitHierarchy": null, "SplitLine": null, "Subaccount": [ { "SegmentId": 1, "SegmentValue": "00000" }, { "SegmentId": 2, "SegmentValue": "00000000" }, { "SegmentId": 3, "SegmentValue": "000" }, { "SegmentId": 4, "SegmentValue": "00" } ] } ], "TaxDetailLines": null, "DocumentType": { "Value": "Invoice" } }} ... View more

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. ... View more

Thank you 🙂  ... View more

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 ... View more

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. ... View more

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

Hi,  8.16.00? But our integration worked last week, and we sent three decimals. ... View more

Hi Magnus, Was there any changes or correction in the API before you had time to test? ... View more