Fixed inconsistency in interest calculation between planned payment and
payment by accruing interest on the real amount rather than compounding
the calculated daily interest, then applying it for the planned payment.

This resulted in some misbehavior in planned payments around the interest
costcomponent since both accrual and incurral were being added to that
costcomponent.  To fix this I excluded accrued costcomponents from the
payment and changed the basis of journal entry creation from the
costcomponents to the balanceAdjustments in the payment builder.

This approach gives a more accurate result anyways because sometimes
when two identical charges were debitting the same account, one of them
was getting lost in the set.  It also makes it easier to filter out
entries which cancel each other producing a zero debit or credit.
26 files changed
tree: 8c58dc7b7066a6f2aee9a20f9d605762aaca0087
  1. api/
  2. component-test/
  3. gradle/
  4. service/
  5. .gitignore
  6. build.gradle
  7. gradlew
  8. gradlew.bat
  9. HEADER
  10. LICENSE
  11. README.md
  12. settings.gradle
  13. shared.gradle
README.md

Mifos I/O Portfolio

Join the chat at https://gitter.im/mifos-initiative/mifos.io

This project provides product and case management for Mifos I/O. Products are described and “instantiated” for customers as cases.

Abstract

Mifos I/O is an application framework for digital financial services, a system to support nationwide and cross-national financial transactions and help to level and speed the creation of an inclusive, interconnected digital economy for every nation in the world.

Versioning

The version numbers follow the Semantic Versioning scheme.

In addition to MAJOR.MINOR.PATCH the following postfixes are used to indicate the development state.

  • BUILD-SNAPSHOT - A release currently in development.
  • M - A milestone release include specific sets of functions and are released as soon as the functionality is complete.
  • RC - A release candidate is a version with potential to be a final product, considered code complete.
  • RELEASE - indicates that this release is the best available version and is recommended for all usage.

The versioning layout is {MAJOR}.{MINOR}.{PATCH}-{INDICATOR}[.{PATCH}]. Only milestones and release candidates can have patch versions. Some examples:

1.2.3-BUILD-SNAPSHOT 1.3.5-M.1 1.5.7-RC.2 2.0.0-RELEASE

License

See LICENSE file.