# Resolve Payments

When subscriber payments are imported into Circulation from a lockbox file, some subscribers in the file might not have valid subscription IDs. When this happens, the batch can still be accepted and valid payments processed. Payments associated with invalid subscription IDs are assigned a subscription ID of zero and are not processed.

{% hint style="info" %}
**Note:**

*Subscriber lockbox payments with an invalid subscriber ID will appear on the* [*Subscriber Payment Journal*](/circulation-user-manual/accounting/subscriber-payments-menu/payment-journal.md) *with a subscriber ID of zero and a name of “Unassigned Payment”. The bank totals will also contain a separate total for unresolved payments.*
{% endhint %}

Select **Resolve Payments** to resolve payments by assigning them to a valid subscriber.

There is also a **Resolve Payments** report to aid in balancing the GL in cases where payments were made in a prior fiscal period but resolved in the current period (see [Resolve Journal](/circulation-user-manual/accounting/subscriber-payments-menu/resolve-journal.md)).

In order to view or edit payments in **Resolve Payments**, the lockbox payment batch must first be accepted.

Pre-authorized **Credit Card** payments created through **Subscriber Lockbox Processing** that are not assigned to a subscription (Subscription ID = zero) can be modified in **Resolve Payments**. These payments may be assigned to a valid subscription and updated as required before processing.

#### To assign valid subscriber IDs to unresolved payments:

* Select `Subscriber Payments | Resolve Payments` to display the Resolve Payments screen.<br>

  <figure><img src="/files/tRSi9xlPwrb8BlzAzPjI" alt=""><figcaption></figcaption></figure>
* Complete the following fields.<br>

  <table><thead><tr><th width="176">Field</th><th width="89">Type</th><th>What to enter</th></tr></thead><tbody><tr><td>ALL RESOLVED</td><td>yes/no</td><td>Indicate whether to list all unresolved payments, or only payments made in a specific lockbox batch.</td></tr><tr><td>BATCH</td><td>setup</td><td>If resolving payments for a specific lockbox batch, enter the batch name here.</td></tr><tr><td>BANK</td><td>setup</td><td>Enter the bank for which to resolve lockbox payments, or enter “*” to multi-select banks.</td></tr><tr><td>CUTOFF DATE</td><td>date</td><td>If All Resolved is set to “y”, enter a cutoff date for resolving payments. Only unresolved payments interfaced on or before this publishing date will be listed.</td></tr></tbody></table>
* The unresolved payments that meet the criteria entered are displayed. Select Modify and enter the subscription ID on one or more payments. You can also modify the term and length for these payments.<br>

  <figure><img src="/files/yBCCJeu2Zjx6l2vOl2MQ" alt=""><figcaption></figcaption></figure>
* When finished, press F4 and select Exit to exit to the main menu.


---

# 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:

```
GET https://docs.navigaglobal.com/circulation-user-manual/accounting/subscriber-payments-menu/resolve-payments.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.