Feature: Add "amount type" configuration column for CSV imports #1947
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Many banks export transactions with an "amount type" column that indicates whether the transaction is an "income" or "expense" (inflow/outflow).
This PR adds a configurable "amount type" column so users can choose between using the signage (e.g. positive/negative amounts) to control the income/expense designation OR use an "amount type" column with a configurable value that designates what is an "income" or "expense" in the import.
This should save users significant time as they won't have to prepare their imports prior to uploading to the Maybe app.
CleanShot.2025-03-04.at.19.09.46.mp4
Other changes
This PR also cleans up some of the import designs to match the latest Figma spec.