About Quan Pham

Quan Pham · ‎04-03-2025

Hi, I'm encountering an error when trying to create a journal transaction with the JSON below. The same JSON works in another company but fails in this one. If I remove the "exchangeRate" field, it works, but it should be possible to send a value of 0 since it works for another company. Could you help me understand why this is happening and how to fix it? Thank you! { "ledger": { "Value": "1" }, "transactionCode": { "Value": "GLNE" }, "journalTransactionLines": [{ "accountNumber": { "Value": "9001" }, "transactionDescription": { "Value": "Datum: 2025-01-07" }, "quantity": { "Value": -8.5 }, "debitAmountInCurrency": { "Value": -3910.0 }, "subaccount": [{ "segmentId": 1, "segmentValue": "120230001" }, { "segmentId": 2, "segmentValue": "00" }, { "segmentId": 3, "segmentValue": "4300" } ], "creditAmountInCurrency": { "Value": 0.0 }, "lineNumber": { "Value": 0 }, "operation": "Insert" }, { "accountNumber": { "Value": "9009" }, "transactionDescription": { "Value": "Datum: 2025-01-07" }, "quantity": { "Value": -8.5 }, "creditAmountInCurrency": { "Value": -3910.0 }, "subaccount": [{ "segmentId": 1, "segmentValue": "110120001" }, { "segmentId": 2, "segmentValue": "00" }, { "segmentId": 3, "segmentValue": "0000" } ], "debitAmountInCurrency": { "Value": 0.0 }, "lineNumber": { "Value": 0 }, "operation": "Insert" }, { "accountNumber": { "Value": "9001" }, "transactionDescription": { "Value": "Datum: 2025-01-07" }, "quantity": { "Value": -8.5 }, "debitAmountInCurrency": { "Value": -3910.0 }, "subaccount": [{ "segmentId": 1, "segmentValue": "120230001" }, { "segmentId": 2, "segmentValue": "00" }, { "segmentId": 3, "segmentValue": "4300" } ], "creditAmountInCurrency": { "Value": 0.0 }, "lineNumber": { "Value": 0 }, "operation": "Insert" }, { "accountNumber": { "Value": "9009" }, "transactionDescription": { "Value": "Datum: 2025-01-07" }, "quantity": { "Value": -8.5 }, "creditAmountInCurrency": { "Value": -3910.0 }, "subaccount": [{ "segmentId": 1, "segmentValue": "110120001" }, { "segmentId": 2, "segmentValue": "00" }, { "segmentId": 3, "segmentValue": "0000" } ], "debitAmountInCurrency": { "Value": 0.0 }, "lineNumber": { "Value": 0 }, "operation": "Insert" }, { "accountNumber": { "Value": "9001" }, "transactionDescription": { "Value": "Datum: 2025-01-07" }, "quantity": { "Value": 8.5 }, "debitAmountInCurrency": { "Value": 5355.0 }, "subaccount": [{ "segmentId": 1, "segmentValue": "110120001" }, { "segmentId": 2, "segmentValue": "00" }, { "segmentId": 3, "segmentValue": "4100" } ], "creditAmountInCurrency": { "Value": 0.0 }, "lineNumber": { "Value": 0 }, "operation": "Insert" }, { "accountNumber": { "Value": "9009" }, "transactionDescription": { "Value": "Datum: 2025-01-07" }, "quantity": { "Value": 8.5 }, "creditAmountInCurrency": { "Value": 5355.0 }, "subaccount": [{ "segmentId": 1, "segmentValue": "110140001" }, { "segmentId": 2, "segmentValue": "00" }, { "segmentId": 3, "segmentValue": "0000" } ], "debitAmountInCurrency": { "Value": 0.0 }, "lineNumber": { "Value": 0 }, "operation": "Insert" } ], "transactionDate": { "Value": "2025-02-01T00:00:00.000Z" }, "description": { "Value": "Text." }, "financialPeriod": { "Value": "202502" }, "postPeriod": { "Value": "022025" }, "controlTotalInCurrency": { "Value": 0.0 }, "exchangeRate": { "Value": 0.0 } }

Quan Pham · ‎12-02-2025

Hi, It is disabled because we don't want to post to closed periods. Is it possible to post to an open period but with a transaction date from a closed one? I tried to use overrideNumberSeries=true but I receive the same error message.

Oskar Jansson · ‎23-09-2024

Henrik Lilleør · ‎03-09-2024

Exsitec Denmark has a customer with the same issue today. Were there ever found a solution for this problem? To be fare, it is old news for Visma now.

Quan Pham · ‎19-06-2024

Hi, I'm experiencing the same issue when trying to create a inventory with type ComponentPartItem. It works if i use FinishedGoodItem. Json: { "inventoryNumber": { "Value": "test5" }, "status": { "Value": "NoRequest" }, "description": { "Value": "TEST5" }, "itemClass": { "Value": "410" }, "type": { "Value": "ComponentPartItem" }, "kitItem": { "Value": false }, "vatCode": { "Value": "02" }, "postingClass": { "Value": "P4100" }, "packaging": { "baseItemWeight": { "Value": 0.0 }, "baseItemVolume": { "Value": 0.0 } } } Response: { "message": "Error creating inventory. Error: Inserting 'Item' record raised at least one error. Please review the errors.\r\nThe class you have selected cannot be assigned to a non-stock item, because the Stock item check box is selected for this class in the Item classes window. Select another item class which is designated to group non-stock items.\r\nError: VAT category '02' cannot be found in the system.\r\nError: 'Base unit' cannot be empty.\r\nError: 'Sales unit' cannot be empty.\r\nError: 'Purchase unit' cannot be empty.\r\n" }

Quan Pham · ‎08-04-2024

This is now solved. I removed "segments".

Quan Pham · ‎21-03-2024

Thank you!

Suzdar Ibrahim · ‎15-02-2024

Hi Quam! We need to investigate this further, and because it seems really client sensitive, I advise you to seek country specific support. Please take a look at the following on how to get support. Refer to this post in your initial contact. https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/td-p/633804

Joni Wolff · ‎29-01-2024

Hi! Just wanted to let you know that this has now been fixed

Quan Pham · ‎22-11-2023

Hi, we would also like this. Is it possible for you to add notes to the lines aswell?

Quan Pham · ‎07-11-2023

Hi, Is it possible to add the fields below to the SupplierInvoice endpoint?

Quan Pham · ‎17-10-2023

Hi, I'm getting the same error with this body and i can't see anything wrong with the customer number sequence. It is possible to create the payment in the UI. "message": "VismaId: 7e72a23f-5cb7-4853-895c-51c08010bc2b. Error creating payment Error: Inserting 'Customer payment' record raised at least one error. Please review the errors.\r\nLast reference number customers\r\n" { "branch": { "Value": "1" }, "currency": { "Value": "SEK" }, "customer": { "Value": "10089" }, "type": { "Value": "Payment" }, "paymentRef": { "Value": "Reglering" }, "cashAccount": { "Value": "1973" }, "paymentMethod": { "Value": "03" }, "applicationDate": { "Value": "2023-10-13T00:00:00.000Z" }, "paymentAmount": { "Value": 87603.75 }, "paymentLines": [{ "refNbr": { "Value": "1902396" }, "documentType": { "Value": "Invoice" }, "amountPaid": { "Value": 87603.75 }, "crossRate": { "Value": 1.000000 }, "operation": "Insert" } ] }

Anders_Traventus · ‎06-10-2023

Hi Actually it seams to have been solved now. Its working. /Anders

Yıldırım · ‎30-06-2023

This can be related to the SO, status, in your company since we're able to modify these values without any problem. Please check it out via the Financials ERP UI.

Quan Pham · ‎29-06-2023

Hi, we also have a customer that is in need for POST and PUT pending cost. Will this be available anytime soon?

Magnus Johnsen · ‎26-06-2023

Alright, please do. Thank you.

Yıldırım · ‎13-03-2023

Hello, you can try sending the payload without cash account to see what default value it gets.

Quan Pham · ‎26-01-2023

Quan Pham · ‎10-01-2023

Magnus Johnsen · ‎05-12-2022

Yıldırım · ‎15-11-2022

Hello, the Cash Account ID "6891" shown in the error message is the Account ID of the cash account you've used in the payload "cashAccount": { "Value": "0123" }, This can be found at Chart of accounts(ScreenId=GL202500) When it comes to the error, apparently you don't have access to that account via the "branch": { "Value": "23" }, In order to be able to Create a Customer Payment with specific PaymentMethod and Cash Account, Cash Account/s that you'd like to use with "CustomerPaymentMethod" should be defined under the Payment methods:"Allowed Cash Accounts" in Financials ERP ScreenId=CA204000 regardless of what branch is in use. then this cash account can be selected when creating a customerPaymentMethod. Regarding having multiple branches in your company and if those accounts are defined as branch-specific, Please make sure that "Multi-branch" and "Inter-branch transactions" are active in your licence and enabled in the Financials ERP company. Afterward, go to desired "Cash Account" screenID:CA2020PL and set "restrict visibility with branch : false"

Quan Pham · ‎25-10-2022

Hi again, Yes, it is possible to create a payment in the UI without any problem.

Error creating journal transaction. Customer curre...

Re: Error creating journal transaction

Re: Expose Deferal Schedule in the API - Status ch...

Sv: Webhook received multiple times

Svar: The class you have selected cannot be assign...

Svar: Problem updating salesSubaccount on Customer

Sv: Inventory - Description

Re: Inventory averageCost

Re: Salesorder API v3 creating orderLines without ...

Svar: Note is missing on PurchaseReceipt

Expose new fields to SupplierInvoice

Svar: Error creating payment - Last reference numb...

Re: POST CustomerInvoice. Error: 'RevisionID' cann...

Re: Problem patching salesorder line with V3

Svar: Inventory - POST and PUT pending cost and pe...

Re: Problem creating supplier payment

Re: Issue creating a supplier payment with branch

Expose revoke for (PUT) CustomerInvoice

Delete contact via API

Re: SupplierPayment in a specific branch - Status ...

Re: Create customerPayment error

Re: POST supplierPayment : "Error creating payment...

Useful pages

About Visma

Contact us

Follow us