Project60 / Project60/org.project60.banking
SEPA-matcher and CiviSEPA 1.0+
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 22
- Forks
- 45
- Avg merge
- 3d 15h
- Merged PRs (30d)
- 7
Description
If you use CiviBanking's SEPA matcher, be aware of this potential issue:
The matcher adjusts the receive_date of the contribution to the value date as stated in the bank statement. This, however, might confuse CiviSEPA's batcher. Be sure to set the grace period in CiviSEPA to a lower value than the notice period.
This problem should become obsolete in the future, when we adjust the SEPA batcher to be better in identifying the contributions associated with a mandate.
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
The issue names the SEPA matcher and CiviSEPA batcher but no files or tests. Start by tracing how the matcher sets a contribution's receive_date and how the batcher identifies mandate-linked contributions. Done means the batcher handles the value-date change reliably, making the grace-period workaround unnecessary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- payments
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100