Overview
The Document Information page provides a comprehensive view of a single AR Remittances document, supporting full review and processing from intake through write to the System of Record (SoR). The page is divided into four main areas:
Remittance Viewer – Preview of the attached remittance file (for example, CSV) so you can verify extracted values.
Document Header & Payment Record – Summary of customer details, classification, status, and key payment‑level fields.
Line Items – Table of invoices and references included in the remittance.
Email Threads – Original customer email, including message and attachments, for audit and context.
Each area provides specific information and actions to help AR and cash‑application teams ensure accuracy, completeness, and readiness for downstream posting.
Figure 1. Document Information Page
Special Actions
The top of the Document Information page contains navigation and action controls used to manage the current AR remittance record. These controls let you move between documents, edit extracted data, upload supporting files, write the remittance to the SoR, or dismiss records that should not remain in your processing queue.
Figure 2. Navigation and action controls – AR Remittances Document Information page
Table 1. Document Information Page – Navigation and Action Controls (AR Remittances)
| Field / Control | Description |
|---|---|
| Previous / Next | Buttons at the top‑right of the page. Move to the previous or next remittance record in your current Documents view for fast, sequential review. |
| Edit | Enables editing mode for editable header fields, payment record details, and line items so you can correct or supplement system‑extracted data. Some fields may be read‑only based on configuration or permissions. |
| Write to SoR | Finalizes the remittance, sending validated data to your System of Record. The document then appears in the Written to SoR tab after a successful write. Validation warnings or errors may appear before write completes. |
| Dismiss | Removes the record from active AR Remittances processing when it is not valid or not needed. A dismissal dialog prompts you to provide a reason for audit tracking. |
Using the page‑level actions
Using Previous/Next navigation
Click Previous or Next in the upper‑right corner.
Review each remittance in sequence without returning to the Documents list, which is especially helpful for high‑volume review.
Editing records
Click Edit to unlock editable header, payment, and line‑item fields.
Make the required changes (for example, update Customer, Payment Number, or line‑item invoice references).
Click Save to apply your updates.
Writing to SoR
After validating all data, click Write to SoR.
Review any validation messages that appear (soft warnings or blocking errors).
If everything is correct, confirm the action to write the remittance to the SoR. The record will then appear in the Written to SoR tab.
Dismissing a record
Click Dismiss for records that should not continue through AR Remittances (for example, test files or non‑payment communications).
In the dismissal dialog, enter a meaningful Reason for audit purposes.
Click Continue to dismiss the record, or Cancel to keep it active.
Tip: Use Write to SoR for remittances that are ready for downstream posting, and Dismiss for items that should be removed from the AR Remittances workflow (for example, mis‑sent or informational files).
Note: The availability of Edit, Write to SoR, and Dismiss depends on your AR Remittances configuration and your user permissions.
Document Header & Payment Record
The Document Header area on the right side of the page summarizes the remittance, customer, and payment‑level information. Use this section to confirm which customer the remittance belongs to, review classification and status, and verify key payment fields.
Figure 3. Document Header and Payment Record – AR Remittances
Table 2. Remittance Record Actions and Status Fields
| Field | Description |
|---|---|
| Customer | The customer associated with this remittance (for example, Access Consulting (C‑0229)). If the customer is not recognized, you can use Match with a Customer to manually link the record to a known customer. |
| Match with a Customer | Button used to search and select the correct customer when the record is not yet matched or needs correction. Matching improves automation and reporting accuracy. |
| Classification | System‑classified document type, typically Remittance. |
| Customer Match Status | Indicates whether the customer could be matched to a record in your system (for example, Known or Unknown). Known customers support stronger automation and posting. |
| Document Status | The current workflow state for this remittance (for example, Edited, Failed to Reconcile, Large File Please Review, Multi Tab File Please Review, New, Record is not a Customer Remittance, Record updated). Use this to understand whether the record needs attention or has been updated. |
1. Match with a Customer
Purpose
Displays the extracted customer for the remittance and lets you correct or confirm the match against a known customer record.
What you see
If the customer is not matched, you see an Unknown Customer value and a Match with a Customer button.
If matched, you see the customer’s name, often including both the description and code/ID (for example,
Access Consulting (C‑0229)).
Figure 4. Customer field with Match with a Customer
When you click Match with a Customer, a searchable list of customers opens:
A search bar at the top to quickly filter by name or code.
Each row shows the Customer Name (Code), an Enrolled / Unenrolled status badge, and an Update Customer Hints button on the right.
Figure 5. Match with a Customer dialog – search, enrollment status, and Update Customer Hints
User actions
Click Match with a Customer to open the customer list.
In the search bar, start typing to filter and locate the correct customer.
Review the Enrolled / Unenrolled badge for each candidate:
Enrolled – the customer is already enabled for AR Remittances.
Unenrolled – the customer exists but is not yet enabled for AR Remittances.
Click a row to select the appropriate customer and update the match on the remittance.
Update Customer Hints
You can also click Update Customer Hints for any row in the list to help the system better identify this customer in future remittances.
When you click Update Customer Hints, the Update Customer Hints dialog opens.
Figure 6. Update Customer Hints dialog
In this dialog:
The header shows the Customer Name, Customer ID, and Entity you are updating hints for.
The left side (Customer Payment) shows a preview of the remittance source file (for example, CSV or spreadsheet), including fields such as Customer Name, Payment Date, Payment Number, Currency, Total Amount, Entity, Payment Type, and Transaction Reference.
The right side (Verify and Choose Customer Hints) lists potential hint fields such as Customer Name and Email From, each with:
A Hint checkbox.
A Select… dropdown to define how that value should be used as a hint.
How to update hints:
Review the Customer Payment preview on the left to understand how this customer appears in the remittance.
On the right, under Verify and Choose Customer Hints:
Select the Hint checkbox for each value you want to treat as a hint (for example, Customer Name or Email From).
Use the Select… dropdown next to each checked field to choose the appropriate hint type or mapping.
Click Update to save the hints, or Cancel to close the dialog without saving.
Maintaining accurate hints helps the system improve future customer identification and auto‑matching, reducing manual work.
If you choose a customer that is not enrolled for AR Remittances, a confirmation dialog appears:
“The customer you chose to match is not enrolled in the AR Remittances.
Would you like to enroll <Customer Name> now?”
Click Enroll Now to enroll the customer for AR Remittances.
Click Cancel to close the dialog without enrolling.
Figure 7. Enroll customer in AR Remittances – confirmation dialog
Best practice
Always confirm that the customer is correct and enrolled for AR Remittances, and keep customer hints up to date. This improves automation, reduces manual matching, and helps prevent posting or reconciliation issues later in the process.
2. Classification
Purpose
Indicates the document type that the system has identified for AR Remittances—typically Remittance or another supported type.
What you see
A Classification field on the remittance showing the current type (for example, Remittance).
In some configurations, an option to click and change the classification if the document has been misclassified.
User actions
Click the Classification value to update it if necessary.
If you change the classification from Remittance to a non‑remittance type, a confirmation dialog appears:
“Would you like to continue with updating the document classification from remittance to other document type? This will dismiss the record.”
A Reason to Dismiss field appears; adding a reason is optional. Click Dismiss to proceed or Cancel to keep the current classification.
This ensures all classification changes are captured for audit purposes.
Figure 8. Classification change confirmation – Reason to Dismiss dialog
Table 3. Payment Record Fields
| Field | Description |
|---|---|
| Entity | Legal entity or business unit associated with the payment (for example, a specific company or subsidiary). |
| Payment Date | Date of the payment or remittance, as extracted from the file. |
| Payment Type | Method or type of payment, such as ACH, wire, or other supported methods. |
| Payment Currency | Currency of the remittance as received from the customer (for example, EUR). |
| Invoice Currency | Currency used for invoices associated with this remittance, when available (for example, USD). |
| Total Amount | Total amount of the remittance represented in the record. |
| Statement Number / Batch Number | Identifier used by the customer or bank to group payments in a statement or batch, when present. |
| RPA Reference ID | Reference used by any RPA or integration layer, when applicable. |
| Deposit Reference | Identifier linking this remittance to a deposit record or bank deposit, when available. |
| Ready to Auto Apply | Indicates whether this remittance is ready for automatic application to open invoices (for example, Yes). |
| Transaction Reference | Additional transaction or banking reference that supports reconciliation and audit. |
Use the Document Header and Payment Record to validate that the remittance is correctly identified, associated with the right customer and entity, and ready for reconciliation or posting.
Remittance Viewer
On the left side of the Document Information page, the Remittance Viewer displays the primary file used to create the remittance record (for example, Payment Items.CSV). This grid‑style viewer lets you:
See the raw rows and columns extracted from the remittance file.
Confirm that amounts, dates, and references match what appears in the header and line‑item sections.
Scroll horizontally and vertically to review all items in the file.
Common viewer controls (icons above the grid) include:
Zoom In / Zoom Out (for example, 150%, plus and minus icons) – Adjust how large the file content appears.
Download – Download the original remittance file (for example, the CSV) as it was received for offline review or retention.
Use the viewer to cross‑check extracted data and troubleshoot exceptions (for example, when line items are flagged as Failed to Reconcile).
Figure 4. Remittance Viewer
Line Items
The Line Items section appears below the viewer and header. It lists invoice‑level details that are part of the remittance and is useful for reconciliation, exception handling, and audit.
Figure 5. Line Items section – AR Remittances
Table 4. Line Item Fields
| Field | Description |
|---|---|
| Bill To Customer | Customer or sub‑customer the invoice is billed to, where available. |
| Invoice Amount | Amount associated with the invoice in the remittance. |
| Invoice Number | Invoice identifier provided by the customer for each line in the remittance. |
| Bill Number | Internal bill or reference number associated with the invoice (when available). |
| Reference Number | Additional reference used for matching or reconciliation. |
| Sum | Summary row at the bottom that totals numeric columns such as Invoice Amount, providing a quick check against the remittance total. |
Line‑item filters
A filter (funnel) icon in the Line Items header opens filtering controls for this table. You can:
Filter by specific invoice numbers, amounts, or references.
Combine multiple conditions to focus on only the lines that need attention.
Filters apply only to the Line Items table and do not affect the rest of the page.
Email Threads (Customer Inbox)
The Email Threads section at the bottom of the page provides full context for the remittance by displaying the original customer email and any attachments.
Figure 6. Email Threads – Customer Inbox view
Table 5. Email Thread Features
| Feature / Field | Description / Functionality |
|---|---|
| Customer Inbox link | Opens the integrated AR mailbox (Customer Inbox) in a new view so you can see all emails received from customers. |
| Email header and body | Shows sender, recipients, date/time, and the email message exactly as received (for example, “Hi please find the attachments”). |
| Attachments list | Displays all files attached to the email (for example, Payment Items.CSV). Each attachment name is clickable and can be viewed or downloaded. |
Use the Email Threads area to:
Review email details – Confirm who sent the remittance, when it was received, and any instructions or comments in the body.
Download or view attachments – Open the original remittance file or supporting documents directly from the email record.
Support audit and traceability – Demonstrate the complete chain from source email and attachment through to the remittance record and its final posting in the SoR.
Best practice: When investigating exceptions or unusual remittances, always review the original customer email and attachments in the Email Threads section. This helps you verify intent, clarify ambiguous references, and maintain a complete audit trail from mailbox to AR processing.