> For the complete documentation index, see [llms.txt](https://docs.navigaglobal.com/circulation-user-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.navigaglobal.com/circulation-user-manual/accounting/subscriber-payments-menu/payment-processing.md).

# Payment Processing

This option takes all subscriber payments that have been entered into the system (on or before the specified date) and applies them to subscriber accounts. This usually results in an extended expiration date for the subscriber. Payments in suspended batches are not processed. Payment processing should be run daily, before transaction processing is run.

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

*You must update Unearned Revenue at the end of each fiscal period, before processing subscription payments belonging in the next fiscal period. See* [Unearned Revenue](/circulation-user-manual/reporting/management-menu/unearned-revenue.md) *for more information. Also note that fiscal periods should be defined before payments are be processed—we recommend defining fiscal periods for at least one year in the future.*
{% endhint %}

#### To process subscriber payments:

1. Select Payment Processing from the Subscriber Payments menu to display the Subscriber Payment Processing window.<br>

   ![](https://1417315899-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1ToZXx8io0JJXNBRcPOt%2Fuploads%2FZnoeDJjuLDMHqDLbya8h%2FSubscriber%20Payment%20Processing.png?alt=media\&token=7ecd528a-5268-4bda-8ac0-904dfddd0bf9)

2. Click Add.

3. Enter the product and date for processing the payments.<br>

   <table><thead><tr><th width="150">Field</th><th width="150">Type</th><th width="371.2">What to enter</th></tr></thead><tbody><tr><td>PRODUCT</td><td>setup</td><td>Enter the product for which to process payments.</td></tr><tr><td>SELECTION DATE</td><td>date</td><td>Enter the selection date for which to process payments. All unsuspended payments entered on or before this date will be processed (including lockbox and auto renew payments). When subscriber payments are processed, they are posted to general ledger accounts. Make sure that all payments entered for a month are processed with a process date within the same month so the GL Interface Journal matches the Payment Journal.</td></tr></tbody></table>

4. Click OK and then Continue to begin payment processing. All unsuspended payments and/or canceled payments entered on or before the transaction date are processed, and the new expiration date is assigned to the subscription. If a subscriber is changing from carrier collect to office pay, a billing change transaction is created. The new expiration date is created and, if applicable, appropriate back credits are given to the carrier/dealer when the billing change transaction is processed.
   * During Payment Processing, Circulation attempts to process payments for the date entered, along with any payments from earlier dates. Therefore, Circulation tries to process any problem payments every time Payment Processing is selected, until the payment processes successfully or is deleted.

5. After the processing is completed, a report is displayed listing general information about the processing and any errors that occurred. Any payments with errors should be corrected, and then this option should be run again to process them.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.