> For the complete documentation index, see [llms.txt](https://panduan-dms.simplidots.id/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://panduan-dms.simplidots.id/website-backoffice/dms-distribution-management-system/intelligence/bi-business-intelligence/account-report/account-payable-list.md).

# A/P List (Account Payable List)

**Step 1.** Buka menu **Intelligence**. \
**Step 2.** Pilih menu **BI**. \
**Step 3.** Pilih **Account Report**.

![](/files/-MklrhIgroL7tXKss1HU)

**Step 4.** Pilih tab paling bawah **A/P List.**

 Pada menu **Account Payable List**, terdapat beberapa tampilan yang dapat membantu Anda, seperti berikut ini:

<figure><img src="/files/Pgw8JOdwFacqvoI6w28E" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}

* **Supplier A/P Summary** merupakan daftar hutang pembelian yang belum dibayar secara keseluruhan berdasarkan supplier.\ <mark style="color:orange;">**Note :**</mark>
  * <mark style="color:orange;">**Supplier Code:**</mark> kode supplier
  * <mark style="color:orange;">**Supplier Name:**</mark> nama supplier
  * <mark style="color:orange;">**Sisa Bayar:**</mark> Sisa hutang yang belum dibayar.
  * <mark style="color:orange;">**Overdue:**</mark> Sisa hutang yang belum dibayar dan sudah jatuh tempo.
  * <mark style="color:orange;">**PurchaseInvoices:**</mark> Jumlah faktur pembelian yang belum dibayar.
* **Outstanding Purchases** merupakan daftar hutang berdasarkan nomor faktur pembelian yang belum dibayar.\ <mark style="color:orange;">**Note :**</mark>
  * <mark style="color:orange;">**Date :**</mark> tanggal faktur pembelian
  * <mark style="color:orange;">**Purchase Invoice No:**</mark> nomor dokumen faktur pembelian
  * <mark style="color:orange;">**Reference No:**</mark> nomor referensi faktur (opsional)
  * <mark style="color:orange;">**Supplier Code:**</mark> kode supplier
  * <mark style="color:orange;">**Name:**</mark> nama supplier
  * <mark style="color:orange;">**Total:**</mark> total hutang berdasarkan faktur pembelian.
  * <mark style="color:orange;">**Sisa Bayar:**</mark> selisih (sisa) hutang yang belum dibayar.
  * <mark style="color:orange;">**Late By:**</mark> Jumlah hari sebelum/sesudah waktu jatuh tempo. \
    Jika <mark style="color:green;">**Late By = minus (-)**</mark> maka faktur pembelian tersebut belum jatuh tempo.\
    Contoh : \ <mark style="color:green;">**Late By : -10**</mark> maka masih ada 10 hari lagi menuju jatuh tempo.\
    \
    Sebaliknya, jika <mark style="color:red;">**Late By = positive (+)**</mark> maka faktur pembelian tersebut telah jatuh tempo.\
    Contoh : \ <mark style="color:red;">**Late By : 10**</mark> maka invoice tersebut sudah lewat selama 10 hari dari tanggal jatuh tempo.&#x20;
  * <mark style="color:orange;">**Overdue :**</mark> jumlah hutang yang sudah jatuh tempo
    {% endhint %}

{% content-ref url="/pages/-Ml3E\_k14L7OsEWntwaE" %}
[Cara Export Excel Data BI](/website-backoffice/dms-distribution-management-system/intelligence/bi-business-intelligence/cara-export-excel-data-bi.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://panduan-dms.simplidots.id/website-backoffice/dms-distribution-management-system/intelligence/bi-business-intelligence/account-report/account-payable-list.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.