About CharlotteJB1

CharlotteJB1 · ‎13-12-2024

{ "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" } } ]}

CharlotteJB1 · ‎09-12-2024

In a program, we are trying to update customer invoice lines by assigning a deferral key, start date for deferral, and end date for deferral. We use the endpoint [PUT] https://integration.visma.net/API/controller/api/v1/customerinvoice/{invoiceNumber} and send a JSON payload as shown below. Bug: When we attempt to update more than 5 lines, only the first lines are assigned the deferral key, while all lines are assigned the start and end dates for deferral. The issue has been reproduced in the demo environment (see attachment). This applies to deferral keys with the accounting method "Flexible by periods, proportional over days."

CharlotteJB1 · ‎03-02-2023

{{ "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" } }}

CharlotteJB1 · ‎26-01-2023

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.

CharlotteJB1 · ‎20-01-2023

CharlotteJB1 · ‎20-01-2023

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

CharlotteJB1 · ‎19-01-2023

CharlotteJB1 · ‎18-01-2023

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" } }}

CharlotteJB1 · ‎16-01-2023

Hi, Our customer (ID: 4228921) receives the following error message in Medius AP A from the API when supplier invoices are to be sent over; Felmeddelande från ERP: 'requestUri: controller/api/v1/supplierinvoice / method: post / headers: Content: application/json Authorization: <******> ipp-application-type: Visma.net Financials ipp-company-id: ****** / response content: {"message":"VismaId: 71451f44-0405-4e30-b8a5-ec08cdc2ef8c. Error creating supplierInvoice. Error: Inserting 'Supplier transactions' record raised at least one error. Please review the errors.\r\nAn error in processing of field Subaccount: Error: Projekt + AO/ÄTA of Subaccount do not exist."} / json response {"Version": We have tried creating the invoice manually in Visma, but get no error. We see no error in the subaccount or the segment value.

CharlotteJB1 · ‎07-07-2022

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.

CharlotteJB1 · ‎01-07-2022

Thank you 🙂

CharlotteJB1 · ‎01-07-2022

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

CharlotteJB1 · ‎01-07-2022

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.

CharlotteJB1 · ‎10-06-2022

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

CharlotteJB1 · ‎10-06-2022

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?

CharlotteJB1 · ‎17-05-2022

Hej, Jag har fått frågan om att koppla 6 Upsales konton till samma visma.net bolag. Finns det någon begränsning från Vismas sida ?

CharlotteJB1 · ‎11-04-2022

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

CharlotteJB1 · ‎08-04-2022

POST/controller/api/v1/supplierInvoice When creating supplierInvoice we get an error "the documen t is out of balance". See attachment. We tested different scenarios, and it seems that we get the error when we send three decimals. This is something we have been able to do prior. - has there been a change in the API?

CharlotteJB1 · ‎04-04-2022

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

CharlotteJB1 · ‎02-03-2022

All imports from Visma.Net to Tracked stopped this morning. The endpoint /controller/api/v1/dimension/subaccount and parameter lastModifiedDateTime gives the correct answer if there is something changed since “lastModifiedDateTime” but if there is no change of data the endpoint answers with 404, see below. url = "https://integration.visma.net/API/controller/api/v1/dimension/subaccount?lastModifiedDateTime=2022-03-01T05:00:00&lastModifiedDateTimeCondition=%3E%3D" HTTPClient::BadResponseError (unexpected response: #<HTTP::Message::Headers:0x0000563e7405bf00 @http_version="1.1", @body_size=0, @chunked=false, @request_method="GET", @request_uri=#<Addressable::URI:0x2b1f3a02a830 URI:https://integration.visma.net/API/controller/api/v1/dimension/subaccount?lastModifiedDateTime=2022-03-01T05:00:00&lastModifiedDateTimeCondition=%3E%3D>, @request_query=nil, @request_absolute_uri=nil, @status_code=404, @reason_phrase="Not Found", @body_type=nil, @body_charset=nil, @body_date=nil, @body_encoding=#<Encoding:UTF-8>, @is_request=false, @header_item=[["Date", "Wed, 02 Mar 2022 06:18:25 GMT"], ["Server", "Nginx"], ["Strict-Transport-Security", "max-age=31536000; includeSubDomains"], ["Content-Type", "application/json; charset=utf-8"], ["ipp-request-id", "579fbcb9-664a-414a-90ff-bf1b03db9ddf"], ["X-Content-Type-Options", "application/json"], ["Pragma", "no-cache"], ["X-Handled-By", "Acumatica-PX.Export/AuthenticationManagerModule"], ["Referrer-Policy", "origin-when-cross-origin"], ["VnfInstanceId", "ERP_SE_REAL_0019"], ["Strict-Transport-Security", "max-age=31536000; includeSubDomains"], ["Cache-Control", "no-cache,no-cache"], ["Feature-Policy", "geolocation 'none'; vr 'none'; payment 'none'; midi 'none'; microphone 'none'; fullscreen 'none'; encrypted-media 'none'; camera 'none'; autoplay 'none';"], ["Expires", "-1"], ["X-XSS-Protection", "1;mode=block"], ["Set-Cookie", "UserDisplayName=; expires=Tue, 01-Mar-2022 06:18:25 GMT; path=/; secure; HttpOnly"], ["Transfer-Encoding", "chunked"]], @dumped=false>) Previously, status = 200 was returned with empty data, as expected. Nothing in the documentation https://integration.visma.net/API-index/ indicates otherwise. The release note about performance improvement in this endpoint yesterday maybe cause this problem? https://community.visma.com/t5/News-in-Developers-Visma-net/Release-Notes-Visma-Net-API-8-86-0-01-03-2022/ba-p/479925

Re: Assigning a deferral key - Put customerinvoice

Assigning a deferral key - Put customerinvoice

Re: Error: Projekt + AO/ÄTA of Subaccount do not e...

Re: Error: Projekt + AO/ÄTA of Subaccount do not e...

Re: Error: Projekt + AO/ÄTA of Subaccount do not e...

Re: Error: Projekt + AO/ÄTA of Subaccount do not e...

Re: Error: Projekt + AO/ÄTA of Subaccount do not e...

Re: Error: Projekt + AO/ÄTA of Subaccount do not e...

Error: Projekt + AO/ÄTA of Subaccount do not exist...

Re: Problem creating ‘Invoice separately’ See tick...

Re: Problem creating ‘Invoice separately’ See tick...

Re: Problem creating ‘Invoice separately’ See tick...

Re: Problem creating ‘Invoice separately’ See tick...

Re: Problem creating ‘Invoice separately’ See tick...

Problem creating ‘Invoice separately’ See ticket 0...

Flera kopplingar från Upsales till Visma.net

Re: Error message from API creating supplierInvoi...

Error message from API creating supplierInvoice "...

Re: All imports from Visma.Net to Tracked stopped ...

All imports from Visma.Net to Tracked stopped this...

Useful pages

About Visma

Contact us

Follow us