Financial Management - PSFT (MOSC)

MOSC Banner

Bank Recon: Recon Status = "DPI" (Duplicate Input Transactions)

in Financial Management - PSFT (MOSC) 1 commentQuestion

Looking for any customers that may have customized / modified the Bank Recon Process to eliminate "DPI" (Duplicate Input Transactions) Reconciliation Exceptions.

We receive numerous payments on the same day, for the same amount, and frequently they have either no Reference populated from Payor, or Payors use the same reference repeatedly, yet they are not duplicate payments. For example, we received 8 payments yesterday for $3,500 that all went to "DPI" - and though the amounts were the same, the payments were all ACHs from different customers.

The core problem is that we load these payments to Accounts Receivable, and when flagged as a "DPI", they are not eligible for loading to Accounts Receivable, causing our end users to "miss" payments from being loaded. We are wondering how others may have adjusted their business processes / bank services / reconciliation to address this issue?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

PSFT Financial Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center