Skip to main content

Get accounting data accountingledger.nv

Resource: accountingledger.nv

HTTP-method: GET

The resource cannot be called without parameters; one of the following parameters is required: netvisorkey, netvisorkeylist, startdate + enddate, changedsince, lastmodifiedstart or lastmodifiedend

Notes on date parameters

  • When using changedsince or lastmodifiedstart parameters, ensure the date covers all vouchers that may have changed before the desired date range. For example, if a voucher is edited before the start of the range, it may not be included in the dataset even if the voucher date is within the range.

  • If vouchers are missing from the dataset, check the latest modification date and extend the search backward if necessary.

  • A separate targeted query may return a missing voucher if it was absent from the query results.

Parameters used in the request:

Parameter

Occurs

Description

Example

netvisorkey

0...1

Fetches a single voucher. The voucher identifier in Netvisor. Only the 'showgenerator' parameter is allowed with this.

1

netvisorkeylist

0...1

Fetches multiple vouchers at once. Only the 'showgenerator' parameter is allowed with this. Maximum of 500 Netvisor keys.

1,2,3

startdate

1

Fetches vouchers added after the given date. Requires parameter enddate.

2024-01-01

enddate

1

Fetches vouchers added before the given date. Requires parameter startdate.

2024-01-01

accountnumberstart

0...1

Filters vouchers based on account number. Returns vouchers with account numbers equal to or greater than the given value.

3000

accountnumberend

0...1

Filters vouchers based on account number. Returns vouchers with account numbers equal to or less than the given value.

3500

changedsince

0...1

Fetches new and modified vouchers after the given date (does not require startdate and enddate).

2024-01-01

lastmodifiedstart

0...1

Fetches vouchers modified after the given date.

2024-01-01

lastmodifiedend

0...1

Fetches vouchers modified before the given date.

2024-01-01

showgenerator

0...1

Returns information about who generated the voucher.

0 = Do not add generator (default)

1 = Add generator

1

voucherstatus

0...1

Filters vouchers based on voucher status.

1 = all

2 = valid (default)

3 = invalidated and deleted

1

vouchertype

0...1

Filters vouchers according to the voucher type. Uses the value of the voucher type's Netvisokey, which can be obtained from the vouchertypelist.nv resource. Requires the parameter startdate + enddate, lastmodifiedstart or lastmodifiedend

1

includetransactionhistory

0...1

Returns the voucher processing history

0 = Do not return voucher processing history (default)

1 = Return voucher processing history

If the voucher count are more than 500 in the request, then the response would have an error: When fetching multiple transactions at once, the page can have a maximum of 500 transactions

1

includeattachmentsmetadata

0...1

Returns the attachment metadata of the voucher. Exact attachment data can be fetch with getvoucherattachments.nv

0 = Do not return attachment metadata (default)

1 = Return attachment metadata

If the voucher count are more than 500 in the request, then the response would have an error: When fetching multiple transactions at once, the page can have a maximum of 500 transactions

1

includetransactionallocations

0...1

Returns transaction allocation information for voucher lines. Transaction allocations can be set and edited using settransactionallocation.nv

0 = Do not return transaction allocation information for voucher lines (default)

1 = Return transaction allocation information for voucher lines

Response:

Level

Element

Type

Occurs

Description

Example

root

Root

Aggregate

1

1

Vouchers

Aggregate

1

2

Voucher

Aggregate

0...n

Attr.

status

Text

0...1

Status of the voucher

"valid", "invalidated" or "deleted"

3

NetvisorKey

Numeric

1

Netvisor key of the voucher

5

3

NetvisorGuid

Text

1

Voucher GUID

2f251125-bea1-4862-ada7-0196ea0028d9

3

VoucherDate

Date

1

Date of the voucher

31.12.2023

3

VoucherNumber

Numeric

1

Voucher number

515144

3

VoucherDescription

Text

1

Description of the voucher

3

VoucherClass

Text

1

Class of voucher

ML Sales invoice

Attr.

netvisorkey

Numeric

1

Voucher type's netvisorkey

1

3

LinkedSourceNetvisorKey

Numeric

1

Netvisor key of the purchase or sales invoice (invoice Netvisor key)

123

Attr.

type

Text

1

Invoice type

purchaseinvoice or salesinvoice

3

VoucherNetvisorUri

Text

1

URI to the voucher in Netvisor

3

VoucherLine

Aggregate

0...n

Attr.

status

Text

0...1

Status of the voucher line

"valid" or "invalidated"

4

NetvisorKey

Numeric

1

Netvisor key of the voucher line

6

4

LineSum

Numeric

1

Sum of the voucher line

150,22

4

Description

Text

1

Description of the voucher line

4

AccountNumber

Numeric

1

Accounting account number

1701

4

VatPercent

Numeric

1

VAT percent

24

4

VatCode

Text

1

VAT code

4

AccountDimension

Text

0...1

Follow-up object

Follow-up object 1

Attr.

type

Numeric

1

Follow-up object's netvisorkey

2

4

TransactionFollowUpStatus

Text

1

Open/Closed

Open

4

TransactionAllocations

Aggregate

0...1

5

TransactionAllocation

Aggregate

0...1

Attr

type

Text

1

Voucher line allocation

allocatedby/allocatedto

6

VoucherLineNetvisorKey

Numeric

1

Voucher line Netvisor key

123

6

VoucherNetvisorKey

Numeric

1

Voucher Netvisor key

123

4

CorporationEventTarget

Aggregate

0...1

5

TargetCompany

Text

1

Target company of the corporation event

Test company

Attr.

organisationidentifier

Text

1

Business id of the target company

123456-7

5

EventStatus

Text

1

Status of the corporation event

New, Pending or Exported

4

Dimension

Aggregate

0...n

5

DimensionName

Text

1

Cost object header

5

DimensionItem

Text

1

Cost object

If the cost object has an identifier in Netvisor, the combined name identifier + name is returned, for example "P001 Website renewal".

5

DimensionItemName

Text

0...1

Name of the cost object

Website renewal

5

DimensionItemCode

Text

0...1

Identifier of the cost object

P001

3

VoucherAttachments

Aggregate

0...1

Attachment metadata of the voucher

For retrieving voucher attachments data use API endpoint getvoucherattachments.nv

4

VoucherAttachment

Aggregate

0...n

5

NetvisorKey

Numeric

1

Netvisor ID of the attachment

123

5

Name

Text

1

Name of the attachment file

Testattachment.pdf

5

Size

Numeric

1

File size in bytes

425229

3

TransactionHistory

Aggregate

1

4

Transaction

Aggregate

0...n

5

Comment

Text

1

Comments added to the voucher activity

Voucher created

5

TimeStamp

Date

1

Date of the activity

2025-06-08 12.53.18

Attr.

format

Text

1

Date type

ansi

5

Editor

Text

1

Name of the user who performed the activity

User

Change history

Date

Change

Description

New elements DimensionItemName and DimensionItemCode

Change in DimensionItem logic

New elements added according to Netvisor's new cost object handling. In future, if identifiers have been added to cost objects in Netvisor, the cost object identifier is returned in its own DimensionItemCode element. Correspondingly, the previous DimensionItem element then returns the combined name identifier + name.

30.10.2025

New elements in VoucherLine

New elements TransactionFollowUpStatus and TransactionAllocations, which add follow-up and allocation information

20.8.2025

New data in response

New aggregate VoucherAttachments, which returns the metadata of the voucher attachment

20.8.2025

New parameter includetransactionhistory

New parameter includetransactionhistory returns the voucher processing history

18.6.2025

New data in the response

New aggregate CorporationEventTarget, which returns possible corporation data of the voucher line

1.11.2024

New parameters

netvisorkey, netvisorkeylist and vouchertype

1.11.2024

New data in the response

New element NetvisorGuid and the existing VoucherClass element's netvisorkey attribute

```

This article has been translated using an AI-based translation tool. The contents or wording of these instructions may differ from those in other instructions or in the software.

Did this answer your question?