How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Visma Customer Overdue Charge API

The CustomerOverdueCharge API from Visma — 5 operation(s) for customeroverduecharge.

Visma Customer Overdue Charge API is one of 193 APIs that Visma publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include CustomerOverdueCharge. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, rate-limit docs, and a support channel.

This API exposes 6 operations across 5 paths, and defines 45 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://api.finance.visma.net.

6 operations 5 paths 45 schemas 2 GET3 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://api.finance.visma.net
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

Visma Customer Overdue Charge API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (interactiveapi) using the authorizationCode flow, exposing 5 scopes.

Paths & Operations 6

Across 5 paths, the API surfaces 6 operations — 2 GET, 3 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

CustomerOverdueCharge 6
GET
/v1/customerOverdueCharge/{overdueChargeNumber}
Get a specific Customer Overdue Charge
CustomerOverdueCharge_GetByoverdueChargeNumber 2 params → 200202
PUT
/v1/customerOverdueCharge/{overdueChargeNumber}
Update a specific Overdue Charge
CustomerOverdueCharge_UpdateByoverdueChargeNumber 3 params body → 204412202
GET
/v1/customerOverdueCharge
Get a range of Customer Overdue Charges - ScreenId=AR301000 Request page size…
CustomerOverdueCharge_GetAll 33 params → 200202
POST
/v1/customerOverdueCharge/{overdueChargeNumber}/action/release
Release overdue charge operation
CustomerOverdueCharge_ReleaseDocumentByoverdueChargeNumber 3 params → 412200202
POST
/v1/customerOverdueCharge/{overdueChargeNumber}/attachment
Creates an attachment and associates it with an overdue charge.
CustomerOverdueCharge_CreateHeaderAttachmentByoverdueChargeNumber 3 params → 201412202
POST
/v1/customerOverdueCharge/{overdueChargeNumber}/{lineNumber}/attachment
Creates an attachment and associates it with a certain overdue charge line.
CustomerOverdueCharge_CreateLineAttachmentByoverdueChargeNumberlineNumber 4 params → 201412202

Schemas 45

The contract defines 45 schemas that model the data the API accepts and returns. The most detailed are CustomerOverdueChargeDto (66 properties), CustomerOverdueChargeUpdateDto (30 properties), CustomerOverdueChargeLineDto (28 properties), CustomerOverdueChargeLineUpdateDto (25 properties). Each schema is shown below with its type and property counts.

creditTermsInCustomerOverdueChargeDto
object
Mandatory field: The top part Terms The credit terms used in relations with the customer.
2 properties
ArAdjustDto
object
16 properties
AttachmentDto
object
3 properties
salesPersonInCustomerOverdueChargeDto
object
The document details tab Salesperson ID The salesperson involved.
2 properties
invoiceContactInCustomerOverdueChargeDto
object
The Invoice address tab The Invoice contact section.
6 properties
financialPeriodInCustomerOverdueChargeUpdateDto
object
The financial period to which the transactions recorded in the document should be posted. Use the format YYYYMM.
1 property
ReleaseCustomerOverdueChargeActionResultDto
object
3 properties
DtoValueOfString
object
1 property
subaccountInCustomerOverdueChargeLineDto
object
Mandatory field: Subaccount The corresponding subaccount used for this transaction.
9 properties
paymentMethodInCustomerOverdueChargeDto
object
The Financial details tab The Payment information section Payment method The identifier for the payment method that the customer will use to pay the document.
2 properties
branchNumberInCustomerOverdueChargeLineDto
object
Mandatory field: Branch The branch that sells the line item or provides the service.
2 properties
accountInCustomerOverdueChargeDto
object
The Document details tab Account The sales account used for the transaction.
6 properties
branchNumberInCustomerOverdueChargeDto
object
The Financial details tab Branch The branch with which this invoice or memo is associated. The field is available if your company is set up with branches.
2 properties
TaxDetailDto
object
This class represents a VAT Detail Line. Used for getting data.
7 properties
customerVatZoneInCustomerOverdueChargeDto
object
The Financial details tab The VAT info section Dunning letter date
2 properties
SegmentUpdateDto
object
2 properties
CustomerOverdueChargeDto
object
This class represents a invoice in CustomerOverdueChargeController. Used by getting data.
66 properties
DtoValueOfDecimal
object
1 property
vatCodeInCustomerOverdueChargeLineDto
object
VAT category The VAT category (if applied) for the transaction. The category represents the type of goods or services.
2 properties
CustomerOverdueChargeLineDto
object
28 properties
contactInCustomerOverdueChargeDto
object
The top part Contact The contact associated with the customer.
2 properties
projectInCustomerOverdueChargeDto
object
The top part Project The identifier and description of the project with which this document is associated, or the code indicating that this document is not ass…
3 properties
locationInCustomerOverdueChargeDto
object
The top part Location The location of the customer related to the document. By default, it is the default location of the selected customer or, if the invoice…
3 properties
subaccountInCustomerOverdueChargeDto
object
The Document details tab Subaccount The corresponding subaccount used for this transaction.
9 properties
CustomerOverdueChargeLineUpdateDto
object
25 properties
BackgroundApiAcceptedDto
object
2 properties
SegmentDto
object
4 properties
accountInCustomerOverdueChargeLineDto
object
Mandatory field: Account The sales account used for the transaction.
6 properties
customerInCustomerOverdueChargeDto
object
The top part Customer The customer associated with the document.
2 properties
salespersonInCustomerOverdueChargeUpdateDto
object
The identifier of the salesperson involved.
1 property
DtoValueOfNullableOfBoolean
object
1 property
sellerInCustomerOverdueChargeLineDto
object
Salesperson ID The identifier of the salesperson involved.
2 properties
DtoValueOfDateTime
object
1 property
postPeriodInCustomerOverdueChargeUpdateDto
object
The financial period to which the transactions recorded in the document should be posted. Use the format MMYYYY.
1 property
DtoValueOfInt32
object
1 property
invoiceAddressInCustomerOverdueChargeDto
object
The Invoice address tab The Invoice address section.
9 properties
countyInCustomerDocumentAddressDto
object
County The county or province.
2 properties
DtoValueOfNullableOfInt32
object
1 property
MetadataDto
object
2 properties
CustomerOverdueChargeUpdateDto
object
30 properties
DtoValueOfNullableOfRutRotItemTypes
object
1 property
countryInCustomerDocumentAddressDto
object
Country The country.
4 properties
DtoValueOfBoolean
object
1 property
vatIdInTaxDetailDto
object
VAT ID The ID of the specific VAT applied.
2 properties
salesPersonIDInCustomerOverdueChargeUpdateDto
object
The field is deprecated for customer document endpoints, please use Salesperson instead
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

visma-customeroverduecharge-api-openapi.yml Raw ↑

Other APIs Visma publishes across the network.

Visma Business NXT GraphQL API
Visma Account API
Visma Accounts API
Visma Agreements API
Visma Allocation Periods API
Visma Approval API
Visma App Store Activation Status API
Visma Article Account Codings API
Visma Article Labels API
Visma Articles API
Visma Attachment API
Visma Attachment Links API
Where this information came from

This is an independent, third-party profile of Visma Customer Overdue Charge API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.