Credit Aging Control
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 0
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
What: On the Customers page, customer cards with overdue credit payments would be highlighted in red. On the Dashboard, the "Total Receivable" card could be divided into "Up to Date" and "Overdue."
How: The backend would require a configuration (CreditPaymentDue) and would use the customer's LastCreditPurchaseDate to calculate the status. The Customer entity could have a transient @Formula field to calculate this dynamically.
Value: Gives the user a powerful collections tool, directly improving cash flow.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Customers page and Dashboard entry points, then locate the Customer entity and the CreditPaymentDue configuration named in the issue. Trace how LastCreditPurchaseDate and Total Receivable are currently handled; done means overdue customers can be identified and receivables can be separated into up-to-date and overdue amounts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100