About reimbursements (Public sector)

Applies To: Microsoft Dynamics AX 2012 R3, Microsoft Dynamics AX 2012 R2, Microsoft Dynamics AX 2012 Feature Pack, Microsoft Dynamics AX 2012

Reimbursements are issued to customers who have overpaid, or customers who have been issued a credit and have an outstanding credit balance. (This can be accomplished by using a general ledger credit voucher or a credit note.) When customer credit transactions are processed for reimbursement, a reimbursement transaction is created for each unique customer balance posting type entry across the vouchers of the transactions. This process can create several reimbursement transactions for a single credit transaction. If you select to create a separate reimbursement transaction for each billing classification, reimbursement transactions will be grouped by the unique customer balance posting type entry and billing classification. The resulting reimbursement transactions will be assigned a classification value.

Reimbursement transactions contain a debit entry for each unique customer balance posting entry type. This value equals the total of the credit transaction balances for the customer and can be separated by billing classification if the option is enabled. This is offset by a credit entry to the vendor summary account by using the financial dimensions defaulted from the debit entry. Once created, the reimbursement transactions are automatically settled against their source accounts receivables credit transactions to bring their balance to zero.

Reimbursements are always issued for the full outstanding credit amounts on selected credit transactions, even if outstanding debit transactions exist for the customer. Reimbursements are not processed for any customer who has pending settlements that have not been posted to the journal. Reimbursement settlements cannot be reversed using the Closed transaction editing. To generate a reimbursement check, you can select the reimbursement transactions for settlement against a vendor payment in the Journals.

Example 1: Do not separate reimbursements by billing classification

In this example, the customer has overpaid, there are two credit notes from different billing classifications, and Create a separate reimbursement for each billing classification is not selected.

Accounts receivables – payment voucher (Overpayment)

Accounts receivables – Credit note voucher (Billing classification PARKS)

Accounts receivables – Credit note voucher (Billing classification UTL)

Generated reimbursement transactions for the customer against these credit transactions

Reimbursement transaction 1 voucher (billing classification value is blank)

Reimbursement transaction 2 voucher (billing classification value is blank)

Reimbursement transaction 3 voucher (billing classification value is blank)

Reimbursement transaction 4 voucher (billing classification value is blank)

Example 2: Separate reimbursements by billing classification

In this example, the customer has overpaid, there are two credit notes from different billing classifications, and Create a separate reimbursement for each billing classification is selected.

Accounts receivables – payment voucher (Overpayment)

Accounts receivables – Credit note voucher (Billing classification PARKS)

Accounts receivables – Credit note voucher (Billing classification UTL)

Generated reimbursement transactions for the customer against these credit transactions

Reimbursement transaction 1 voucher (billing classification value is blank)

Reimbursement transaction 2 voucher (billing classification value is PARKS)

Reimbursement transaction 3 voucher (billing classification value is UTL)

Reimbursement transaction 4 voucher (billing classification value is UTL)

Reimbursement transaction 5 voucher (billing classification value is UTL)

See also

Reimbursement (class form)