We'd love to hear from you! Provide  feedback  to earn a badge today. Take our quick survey
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register

FAH - Transaction Number unique constraint does not allow tracking the transaction movement for cust

Received Response
19
Views
5
Comments
edited Apr 29, 2021 10:02AM in Subledger Accounting & Accounting Hub 5 comments

Summary

FAH - Transaction Number unique constraint does not allow tracking the transaction movement for customer payment application

Content

we are implementing FAH for an external customer billing system. The payment received from customer is first entered in the system as 'Unapplied Payment' . At this stage the payment number generated is say 'R-1234' and the accounting requirement is Debit Cash/Bank and Credit Unapplied Cash.

We are able to achieve the above ask in FAH

Subsequently the payment number 'R-1234' is applied to Invoice say 'INV-456' and the accounting requirement is Debit Unapplied Cash and Credit Receivables.

Tagged:

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!