10.3 Payment Journals, Cash Receipts & Payment Registration Setup

10.3 Payment Journals, Cash Receipts & Payment Registration Setup

Quick Summary: In Microsoft Dynamics 365 Business Central, cash disbursements and receivables settlements are processed across three specialized workspaces: the Payment Journal (Page 256), the Cash Receipt Journal (Page 255), and the Register Customer Payments page (Page 980). Payment Journals execute automated vendor disbursements via the Suggest Vendor Payments batch job (Report 393), optimizing liquidity using Available Amount (LCY), Vendor Priority, cash discount deadlines, and Summarize per Vendor options for computer checks and electronic EFT/SEPA exports. Cash Receipt Journals manage incoming customer collections with flexible document application and payment discount tolerance. For high-volume, simplified receivables processing, Payment Registration Setup (Page 983) enables cashiers to mark invoices as paid, adjust received dates, and record partial or lump-sum settlements directly from a streamlined list without entering journal lines.

---

The Payment Journal & The "Suggest Vendor Payments" Engine

The Payment Journal (Page 256 / Table 81 Gen. Journal Line) is the primary accounting workspace for generating, approving, exporting, and posting outbound payments to suppliers, employees, and creditors.

UI Navigation Path:
Tell Me (Alt+Q) -> Payment Journals (opens Page 256)

1. The "Suggest Vendor Payments" Batch Job (Report 393)

Rather than manually keying hundreds of vendor payment lines, treasury teams execute the Suggest Vendor Payments batch job (Action: Prepare -> Suggest Vendor Payments). This intelligent routine analyzes open vendor ledger entries across the organization, evaluates available cash reserves, and automatically constructs balanced journal lines:

UI Navigation Path:
Payment Journal -> Action Bar: Prepare -> Suggest Vendor Payments (opens Report 393 Request Page)

Suggest Vendor Payments Calculation Architecture:

[Open Vendor Ledger Entries]
              │
              ├──► Filter: Last Payment Date / Due Date
              ├──► Filter: Find Payment Discounts (captures early discount dates)
              ├──► Evaluation: Use Vendor Priority (1, 2, 3...)
              ├──► Constraint: Available Amount LCY (caps total disbursement run)
              └──► Layout: Summarize per Vendor (Single line vs Line-per-invoice)
                            │
                            ▼
               [Populates Payment Journal Lines]

Key Request Page Parameters:

• Last Payment Date / Calculation Date: The cutoff date evaluated against open vendor invoices. Any invoice with a Due Date on or before this date is proposed for payment.
• Find Payment Discounts: When checked (Yes), Business Central evaluates the Pmt. Discount Date on open invoices. If the discount cutoff date falls on or after the calculation date, the invoice is included in the payment run even if its final net due date is weeks in the future, maximizing captured discounts.
• Use Vendor Priority: When enabled, Business Central evaluates the Priority integer on Vendor Cards (where 1 is highest priority, 2 is second, etc.). If cash constraints prevent paying all due invoices, higher-priority vendors receive payments first.
• Available Amount (LCY): Establishes an absolute financial ceiling on the payment proposal (e.g., maximum $50,000 disbursement). When combined with Use Vendor Priority, Business Central sequentially funds invoices from highest-priority vendors until the available cash ceiling is exhausted, preventing overdrafts.
• Summarize per Vendor:
  • When Checked (Yes - Standard Practice): Business Central aggregates all open invoices for each vendor into a single consolidated payment journal line. This minimizes banking transaction fees and produces a single check or EFT transfer per vendor. The individual invoice applications are preserved behind the scenes in Table 241 Apply Entries.
  • When Unchecked (No): Business Central generates a separate journal line for every individual open invoice, providing line-by-line transparency in the journal grid.
• Posting Date & Starting Document No.: Specifies the ledger date and sequential check/payment document number stamped on resulting entries.
• Bank Payment Type: Defines disbursement mechanics: Manual Check (handwritten check), Computer Check (printed from BC), or Electronic Payment (EFT/SEPA export).

2. Electronic Payment Export & Remittance Advice

To disburse funds electronically via SEPA Credit Transfer (ISO 20022 pain.001), US NACHA ACH, or Canadian EFT:

1. Prerequisites:
   • The General Journal Batch must have Allow Payment Export set to Yes.
   • The balancing Bank Account Card must have a valid Payment Export Format assigned (linked to a Data Exchange Definition).
   • The vendor must have a Preferred Bank Account Code populated with valid transit and account/IBAN coordinates.
2. Export Workflow:
   • In the Payment Journal, select Export Payments to File (or Generate EFT Files).
   • Business Central validates banking coordinates, exports the structured file, and updates the journal lines' status to Exported.
3. Remittance Advice (Report 211):
   • Treasury staff execute Print Remittance Advice or Send Remittance Advice to transmit an itemized electronic breakdown of all settled invoices to the vendor via email.
4. Correcting Exported Lines (Exam Trap):
   • Once payment lines have been exported, Business Central locks the lines against editing or deletion to prevent variances between bank files and ledger entries.
   • If a line must be altered or removed, the user must select the line and execute Cancel Exported Payments (or Void Electronic Payment), unlocking the line for modification.

---

Cash Receipt Journals: Direct & Applied Receipts

The Cash Receipt Journal (Page 255 / Table 81) processes incoming customer payments, wire deposits, credit card settlements, and manual checks.

UI Navigation Path:
Tell Me (Alt+Q) -> Cash Receipt Journals (opens Page 255)

1. Architectural Setup & Single-Line Entry

• Cash Receipt Journals are governed by a General Journal Template where Type = Cash Receipts and Page ID = 255.
• On the General Journal Batch, administrators pre-populate Bal. Account Type = Bank Account and Bal. Account No. = BNK-01. This enables cashiers to record receipts using single-line balanced entries:

  Posting Date: 09/15/2026 | Doc Type: Payment | Doc No: RCPT-1001 | Account Type: Customer
  Account No: C10010 | Amount: -1,200.00 | Bal. Account Type: Bank Account | Bal. Account No: BNK-01
  

  Result: Entering -1,200.00 credits the Customer account and automatically debits the balancing Bank Account for +1,200.00 upon posting.

2. Cash Application Mechanics

When customer payments arrive, cashiers link the cash receipt to outstanding sales invoices using one of two application workflows:

• Direct Line Application (Applies-to Doc. No.): On the journal line, the user enters or selects the specific sales invoice in the Applies-to Doc. No. field. This is ideal when a payment settles a single known invoice in full or in part.
• Multi-Document Application (Apply Entries - Page 232): When a customer remits a single payment covering multiple invoices:
  1. The user enters the customer receipt line in the journal grid.
  2. Selects Process -> Apply Entries (Page 232 Apply Customer Entries).
  3. Highlights each invoice being settled and executes Set Applies-to ID (Shift+F11). Business Central stamps the journal line's Document No. onto the selected invoice lines.
  4. The user can adjust the Amount to Apply on individual invoices for partial settlements.
  5. Clicks OK to return to the journal. The total applied sum populates the journal line Amount.

3. Payment Discounts & Payment Tolerance

• If the receipt Posting Date is on or before the invoice Pmt. Discount Date, Business Central automatically calculates and recognizes the early payment discount, posting the difference to the Sales Discounts Granted account.
• If enabled in General Ledger Setup, Payment Tolerance allows small discrepancies (e.g., up to $5.00 or 2%) to be automatically accepted as fully paid, writing off the minor discrepancy to a dedicated tolerance account.

---

Payment Registration: Streamlined Daily Collections Setup & Operation

While Cash Receipt Journals provide granular control over complex allocations and dimensional distributions, organizations frequently require an accelerated, simplified workspace for non-accountant staff, store cashiers, or customer support teams. Business Central satisfies this need through Payment Registration.

Payment Registration Workflow:

[Payment Registration Setup: Page 983]
  ├── Journal Template: CASHRCPT (Type = Cash Receipts)
  ├── Journal Batch: DEFAULT
  ├── Bal. Account Type: Bank Account / G/L Account
  ├── Bal. Account No.: BNK-01 (Operating Cash)
  └── Auto Fill Date Received: Yes
             │
             ▼
[Register Customer Payments: Page 980]
  ├── Displays live list of all open customer invoices
  ├── Cashier marks 'Payment Made' checkbox
  ├── Adjusts 'Date Received' or enters partial 'Amount Received'
  └── Action: Post Payments (or Post as Lump Payment)
             │
             ▼
[Background Journal Generation & Posting Committed to Ledger]

1. Payment Registration Setup (Page 983 / Table 980)

Before users can access the payment registration workspace, the feature must be initialized via Payment Registration Setup (Alt+Q -> Payment Registration Setup):

• Journal Template Name: Mandatory link to a General Journal Template configured with Type = Cash Receipts.
• Journal Batch Name: Mandatory link to a specific working batch under the selected template.
• Bal. Account Type: Identifies the offset account classification (Bank Account or G/L Account).
• Bal. Account No.: Identifies the specific checking or cash account (e.g., BNK-01 or G/L 10100) where incoming funds are deposited.
• Auto Fill Date Received: When checked (Yes), clicking the Payment Made checkbox on an open invoice automatically populates the Date Received field with the current system Work Date.

2. The Register Customer Payments Page (Page 980)

Users open the simplified collection window via Tell Me (Alt+Q) -> Register Customer Payments. Rather than presenting debit and credit columns, the page renders an intuitive, card-style list of all outstanding customer invoices:

UI Navigation Path:
Tell Me (Alt+Q) -> Register Customer Payments (opens Page 980)

Operational Features & Actions:

• Standard Full Settlement: The cashier locates the customer invoice and clicks the Payment Made checkbox. Business Central automatically sets Amount Received equal to Remaining Amount (less applicable early payment discounts) and defaults Date Received to the current Work Date.
• Partial Payments: If a customer pays less than the remaining balance, the cashier leaves Payment Made unchecked and manually enters the payment value into the Amount Received field. Business Central calculates the remaining unpaid balance automatically.
• Payment Discount Dates: The page displays the Pmt. Discount Date. If Date Received falls within the discount eligibility window, the system automatically suggests the discounted payment value.
• Post as Lump Payment: When a customer sends a single check or wire to settle multiple separate invoices:
  1. The user selects multiple invoice rows for that customer.
  2. Selects Process -> Post as Lump Payment.
  3. Business Central aggregates the selected invoices into a single cash receipt line in the underlying journal batch, applies the invoices, and posts the transaction in a single step.
• Preview Posting: Simulates the G/L Entries, Cust. Ledger Entries, and Bank Account Ledger Entries before posting.
• Post Payments: Executes immediate background posting, updating customer balances and cash accounts instantly.

---

Comparative Analysis: Payment Processing Workspaces

---

Common Implementation Pitfalls & Exam Traps