# Posted Document Applications

`GET` _(Table: EONE Posted Doc Application)_

```
eOne/core/v1.0/postedDocApplications
```

The settlement breakdown of a posted payment or refund. Each row is one invoice/credit memo it settled, with the amount applied and that document's resulting balance. A **nested collection** addressed under a parent, not on its own.

## A nested collection

This collection is addressed under a parent payment/refund, e.g. `postedCustomerPayments({id})/postedDocApplications`. The same collection is reused by [postedCustomerPayments](https://eonesolutions.github.io/eone-bc-integration/core-postedCustomerPayments.md), [postedCustomerRefunds](https://eonesolutions.github.io/eone-bc-integration/core-postedCustomerRefunds.md), [postedVendorPayments](https://eonesolutions.github.io/eone-bc-integration/core-postedVendorPayments.md), and [postedVendorRefunds](https://eonesolutions.github.io/eone-bc-integration/core-postedVendorRefunds.md).

Each row carries `appliedDocumentNumber` and `appliedIntegrationId` (correlate back to the settled invoice/credit memo), `appliedAmount` (how much of the payment went to it), and, read live, `appliedRemainingAmount` and `appliedOpen`, the settled document's balance **after** this and every other application. `appliedRemainingAmount = 0` means paid in full.

## Posted Document Applications fields

_API column → BC field._

**Legend**

- _(req)_ required on create
- _(res)_ resolver
- _(cur)_ currency-translated
- _(ro)_ read-only
- _(ext)_ added to this endpoint by another extension (BC field name shown; its API column name is not known here)

| API | BC field | Notes |
| --- | --- | --- |
| `id` | SystemId | BC record GUID. _(ro)_ |
| `bcCompanyId` | bcCompanyId | The company this row belongs to - the same GUID that appears in the request URL. Present on every endpoint so a store pooling several companies can keep them apart without relying on which URL it called. _(ro)_ |
| `bcCompanyName` | bcCompanyName | The name of the company this row belongs to. _(ro)_ |
| `appliedDocumentType` | Applied Document Type | Type of the settled document (usually Invoice or Credit Memo). _(ro)_ |
| `appliedDocumentNumber` | Applied Document No. | Number of the settled document. _(ro)_ |
| `appliedIntegrationId` | Applied Integration Id | The settled document's eOne integration key, so you can correlate back to the source order/invoice. _(ro)_ |
| `appliedAmount` | Applied Amount | How much of this payment/refund was applied to the settled document. _(ro)_ |
| `appliedRemainingAmount` | Applied Remaining Amount | The settled document's remaining balance after this and every other application. Zero means paid in full. _(ro)_ |
| `appliedOpen` | Applied Open | Whether the settled document is still open (has an outstanding balance). _(ro)_ |

## Related pages

Nested under [Customer Payments](https://eonesolutions.github.io/eone-bc-integration/core-postedCustomerPayments.md) and [Customer Refunds](https://eonesolutions.github.io/eone-bc-integration/core-postedCustomerRefunds.md) and [Vendor Payments](https://eonesolutions.github.io/eone-bc-integration/core-postedVendorPayments.md) and [Vendor Refunds](https://eonesolutions.github.io/eone-bc-integration/core-postedVendorRefunds.md) and [Employee Payments](https://eonesolutions.github.io/eone-bc-integration/core-postedEmployeePayments.md).
