10
Actual: How to import data with proper readable payee? (lemmy.ml)
submitted 9 months ago by Atemu@lemmy.ml to c/selfhosted@lemmy.world
2 comments fedilink hide all child comments

cross-posted from: https://lemmy.ml/post/11150038

I'm trying out Actual and have imported my bank's (Sparkasse) data for my checking account via CSV. In the CSV import, I obviously had to set the correct fields and was a bit confused because Actual only has the "Payee" field while my CSVs have IBAN, BIC and a free text name (i.e. "Employer GmbH".)

IBAN is preferable because it's a unique ID while the free text name can be empty or possibly even change(?). (Don't know how that works.)
OTOH, the free text name is preferable because I (as a human) can use it to infer the actual payee while the IBANs are just a bunch of numbers.

Is it possible to use IBAN aswell as the free text name or have a mapping between IBAN and a display name?

How do you handle that?

top 2 comments
sorted by: hot top controversial new old
[-] Unsaved5831@lemm.ee 3 points 9 months ago

The tool is for budgeting so I would say use what is readable for you. Using IBAN for payee sounds like an overkill. You can still manage your payees and merge them later differently.

[-] Piatro@programming.dev 1 points 9 months ago

Personally I rename them to something meaningful and they get merged if there are no other references. PayPal is especially bad for completely meaningless rubbish in the payee field and they tend to be ad-hoc purchases so I don't fiddle with them much. The category is the most relevant bit for me.

this post was submitted on 28 Jan 2024
10 points (91.7% liked)

Selfhosted

40219 readers
1042 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
CannaVet@lemmy.world
Loki@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz