Check a Dynamics GP customer statement before sending

Before sending a Dynamics GP receivables statement, verify the customer, statement date, and the invoices, payments and credits behind the balance.
Upload a case

Key facts

Save the final statement with the cutoff and the list of transactions that explain any difference the customer raised.

Choose the customer and statement scope

Confirm the billing entity and customer record. Review the statement setup for that account. Microsoft distinguishes open-item customers, whose activity can be tracked by transaction, from balance-forward customers, where older activity may be consolidated.

Review the transactions behind the amount

Compare the statement with the customer’s receivables records. Check large recent payments, unapplied credits and any new charges. If the customer says an invoice was settled, match the payment date and reference and explain any timing difference using the statement cutoff.

Give accounts payable a balance it can trace

Send the statement to the verified accounts payable contact. For a disputed line, include its invoice number, amount and the remittance or credit reference needed to resolve it. Microsoft documents the Keep Statement History option for reprinting, if it is enabled in your setup.

RELATED ARTICLES

Illustration of a free e-book representing the 'Free International Debt Collection Guide.' This guide offers proven debt collection techniques. Get your free copy now.
FREE GUIDE

Download our free debt collection guide

Practical steps to get unpaid invoices paid, at home and abroad. Download our debt collection guide for free.

Thank you! The guide will land in your inbox shortly
Oops! Something went wrong while submitting the form.