Endpoints for Supplier Ledger

<page>
<metadata>
<title>Endpoints for Supplier Ledger</title>
<path>/vismanetapi/setting-up-your-integration/how-tos/supplierledgerendpoint</path>
<kind>section</kind>
<description>In this article, you will find guidelines on how to use Visma Net API endpoints connected to the Supplier Ledger.</description>
<lastmod>2025-11-28T09:30:17+01:00</lastmod>
</metadata>
<content>
# Endpoints for Supplier Ledger

In this article, you will find guidelines on how to use Visma Net API endpoints connected to the Supplier Ledger.


For more information regarding the endpoints, query parameters, and other endpoints for all areas, please read the [Swagger Documentation](https://finance.visma.net/swaggerui/index.html).</content>
</page><page>
<metadata>
<title>Supplier</title>
<path>/vismanetapi/setting-up-your-integration/how-tos/supplierledgerendpoint/supplier</path>
<kind>section</kind>
<description>Common usage example for Supplier(ScreenId=AP303000)</description>
<lastmod>2025-11-28T09:30:17+01:00</lastmod>
</metadata>
<content>
# Supplier

Common usage example for Supplier(ScreenId=AP303000)


URL: `https://api.finance.visma.net/v1/supplier`

For information about the ERP logic behind Suppliers, please refer to the [ERP Manual Help: Suppliers](https://help.content.visma.net/Sweden/SE_EN/online-help/p2p/AP/AP303000-ref.html)

## Methods

---

### GET All Suppliers

URL: `https://api.finance.visma.net/v1/supplier`

#### Query Parameters

- `lastModifiedDateTime=YYYY-MM-DD`  

As of today Filtering Parameters does not accept certain characters such as W-Z

These are the formats for Filtering

- `2001-01-01`
- `2001-01-01 13:13:13`
- `2001-01-01 13:13:13.133`

#### Compare Operators for lastModifiedDateTimeCondition

- `>` - Greater than
- `<` - Less than
- `<=` - Less than or equal to
- `>=` - Greater than or equal to

#### Usage Example

This query will return suppliers updated on 2025-01-14 or later:

**GET** `https://api.finance.visma.net/v1/supplier?lastModifiedDateTime=2025-01-14&lastModifiedDateTimeCondition=>=`

---

### POST Supplier

URL: `https://api.finance.visma.net/v1/supplier`

This example shows the minimum fields you should send to be able to post a new Supplier, if you are using automatic numbering you can omit the “number” field.

#### JSON Request body

```json
{
    "number": {
        "value": "50002"
    },
    "name": {
        "value": "NewSupplier"
    },
    "mainAddress": {
        "addressId": 3001,
        "addressLine1": "Testroad 5",
        "postalCode": "0110",
        "city": "OSLO",
        "country": {
            "id": "NO",
            "name": "NORGE"
        },
        "county": {
            "id": "0301",
            "name": "OSLO"
        }
    },
    "supplierClassId": {
        "value": "1"
    }
}
```

If sent successfully, the API will return:

![Created](201created2.png)

---</content>
</page><page>
<metadata>
<title>Supplier Invoice</title>
<path>/vismanetapi/setting-up-your-integration/how-tos/supplierledgerendpoint/supplierinvoice</path>
<kind>section</kind>
<description>Common usage example for Supplier Invoice(ScreenId=AP301000)</description>
<lastmod>2025-11-28T09:30:17+01:00</lastmod>
</metadata>
<content>
# Supplier Invoice

Common usage example for Supplier Invoice(ScreenId=AP301000)


URL: `https://api.finance.visma.net/v1/supplierInvoice`

For information about the ERP logic behind Supplier Invoices, please refer to the [ERP Manual Help: Purchase invoices](https://help.content.visma.net/Sweden/SE_EN/online-help/p2p/AP/AP301000-ref.html)

## Methods

---

### GET All Supplier Invoices

URL: `https://api.finance.visma.net/v1/supplierInvoice`

#### Query Parameters

- Project=String  

Will limit response to documents with the specified project

#### Usage Example

This will return Supplier Invoices with projectID 20.

**GET** `https://api.finance.visma.net/v1/supplierInvoice?project=20`

---

### POST SupplierInvoice

URL: `https://api.finance.visma.net/v1/supplierInvoice`

This example shows the minimum fields you should send to be able to post a new Supplier Invoice, if you are using automatic numbering you can omit the “referenceNumber” field.

#### JSON Request body

```json
{
    "date": {
        "value": "2025-11-08T00:00:00"
    },
    "documentType": {
        "value": "Invoice"
    },
    "referenceNumber": {
        "value": "000357"
    },
    "invoiceLines": [
        {
            "inventoryNumber": {
                "value": "test*test"
            },
            "lineNumber": {
                "value": "1"
            },
            "operation": "Insert",
            "projectId": {
                "value": "X"
            },
            "quantity": {
                "value": 1
            },
            "subaccount": [
                {
                    "segmentId": 1,
                    "segmentValue": "00"
                }
            ],
            "unitCostInCurrency": {
                "value": "1.60"
            },
            "vatCodeId": {
                "value": "1"
            }
        }
    ],
    "paymentRefNo": {
        "value": "test"
    },
    "postPeriod": {
        "value": "112025"
    },
    "supplierNumber": {
        "value": "50000"
    },
    "supplierReference": {
        "value": "test"
    }
}
```

If sent successfully, the API will return:

![Created](201created3.png)

---

### PUT SupplierInvoice

URL: `https://api.finance.visma.net/v1/supplierInvoice/{invoiceNumber}`

When using PUT, you only send the fields you want to update. In the below example, we update the first line of the invoice:

URL
PUT `https://api.finance.visma.net/v1/supplierInvoice/000050`'

#### JSON Request body

```json
{
    "invoiceLines": [
        {
            "operation": "Update",
            "lineNumber": {
                "value": 1
            },
            "inventoryNumber": {
                "value": "6"
            },
            "quantity": {
                "value": 1
            }
        }
    ]
}
```

If successful, the API will return:

![No Content](nocontent2.png)

---</content>
</page><page>
<metadata>
<title>Purchase Order</title>
<path>/vismanetapi/setting-up-your-integration/how-tos/supplierledgerendpoint/purchaseorder</path>
<kind>section</kind>
<description>Common usage example for Endpoint(ScreenId=PO301000)</description>
<lastmod>2025-11-28T09:30:17+01:00</lastmod>
</metadata>
<content>
# Purchase Order

Common usage example for Endpoint(ScreenId=PO301000)


URL: `https://api.finance.visma.net/v1/PurchaseOrder`

For information about the ERP logic behind Purchase Orders, please refer to the [ERP Manual Help: Purchase orders](https://help.content.visma.net/Sweden/SE_EN/online-help/o2c/PO/PO301000-ref.html)

## Methods

---

### GET ALL Purchase Orders

URL: `https://api.finance.visma.net/v1/PurchaseOrder`

#### Query Parameters

##### Supplier=string
  
Lets you search for Purchase Orders registered to one supplier

##### orderStatus=string

Lets you define what orderStatuses to return, these are the Statuses of Purchase Order:

- On hold - The purchase order is a draft and can be edited manually.
- Open - The order was processed in accordance but has not been completed yet.
- Pending approval - The purchase order has not been approved by all the assigned persons.
- Rejected - The order was rejected by one of the persons assigned to approve it.
- Pending printing - Printing is required for the document but has not been performed yet.
- Pending e-mail - E-mailing is required for this document, but it has not been performed yet.
- Closed - All the ordered goods were received.
- Cancelled - The order was cancelled through the “ Cancel order” action - An order with this - status cannot be edited, and purchase receipts cannot be based on it.

#### Usage Example

This will return Purchase Orders registered on supplier “50000” that are in status OPEN.

**GET** `https://api.finance.visma.net/v1/purchaseorder?Supplier=50000&status=open`

---

### POST Purchase Order

URL: `https://api.finance.visma.net/v1/purchaseorder`

This example shows the minimum fields you should send to be able to post a new Purchase Order, if you are using automatic numbering you can omit the “referenceNumber” field.

#### JSON Request body

```json
{
    "orderType": {
        "value": "RegularOrder"
    },
    "date": {
        "value": "2019-12-27T09:46:11.202Z"
    },
    "supplier": {
        "value": "50000"
    },
    "lines": [
        {
            "operation": "Insert",
            "inventory": {
                "value": "teststock"
            },
            "lineType": {
                "value": "GoodsForInventory"
            },
            "warehouse": {
                "value": "2"
            },
            "uom": {
                "value": "PALL"
            },
            "orderQty": {
                "value": 2
            },
            "unitCost": {
                "value": 2000
            }
        }
    ]
}
```

If sent successfully, the API will return:

![Created](201created4.png)

---

### PUT Purchase Order

URL: `https://api.finance.visma.net/v1/purchaseorder/{purchaseOrder}`

When using PUT, you only send the fields you want to update. In the below example, we update the first line of the Credit Note:

URL
PUT `https://api.finance.visma.net/v1/supplierInvoice/000050`'

#### JSON Request body

```json
{
    "lines": [
        {
            "operation": "Update",
            "lineNumber": {
                "value": 1
            },
            "inventory": {
                "value": "6"
            },
            "orderQty": {
                "value": 1
            }
        }
    ]
}
```

If successful, the API will return:

![No Content](nocontent3.png)

---</content>
</page><page>
<metadata>
<title>Supplier Payment</title>
<path>/vismanetapi/setting-up-your-integration/how-tos/supplierledgerendpoint/supplierpayment</path>
<kind>section</kind>
<description>Common usage example for Endpoint(ScreenId=AP302000)</description>
<lastmod>2025-11-28T09:30:17+01:00</lastmod>
</metadata>
<content>
# Supplier Payment

Common usage example for Endpoint(ScreenId=AP302000)


URL: `https://api.finance.visma.net/v1/supplierPayment`

For information about the ERP logic behind Supplier Payment, please refer to the [ERP Manual Help: Supplier payments](https://help.content.visma.net/Sweden/SE_EN/online-help/p2p/AP/AP302000-ref.html)

## Methods

---

### GET All Supplier Payments

URL: `https://api.finance.visma.net/v1/supplierPayment`

#### Query Parameters

- SupplierId=String

This will limit the response to the provided SupplierId

#### Usage Example

This will return Supplier Payments registered on supplier “50000”

**GET** `https://api.finance.visma.net/v1/supplierPayment?supplier=50000`

---</content>
</page>