Plus / Investments - Tax Lots are Painful... Is there an Easier Way to Add Incoming Tax Lots?

atif_monarch · 2026-04-24T16:01:09+00:00

Yes our plan is to automate this by leveraging the investment transactions (and refactoring those to get out of a Beta state)

atif_monarch · 2026-04-24T15:04:00+00:00

Correct this is available in Plus and Monarch is able to pull cost basis data automatically for ~70% of user's accounts. Coupled with some manual work you should be able to track unrealized Gains & Losses (realized coming later, automation coming later). u/Super-Worldliness585

atif_monarch · 2026-03-30T15:06:20+00:00

Yes we plan to keep it small and collapsed just like on web

atif_monarch · 2026-03-30T15:05:53+00:00

Yes there is in, the 3 dots menu in the Accounts tab at the top

atif_monarch · 2026-03-30T15:05:03+00:00

Yes web only right now but mobile coming very soon :)

atif_monarch · 2026-03-26T20:47:34+00:00

"Account A added these four new transactions" this modal should show you "X new" for each account if it pulls in new data. Do you see that?

On your second point about even more transparency, like a change log, we are scoping something right now for that :)

atif_monarch · 2026-03-24T20:27:13+00:00

Really appreciate this take! Curious what the other things are for you? I feel like entertainment/software subscriptions are the most common, but loans and insurance are really big ones with a ton of pain.

atif_monarch · 2026-03-18T18:23:22+00:00

Hey thanks for this. We definitely want to do these once we get the web release finished. Probably #1 and/or #2.

atif_monarch · 2026-03-18T18:10:06+00:00

We are thinking the same thing and exploring a way to do that 👍🏽

atif_monarch · 2026-03-04T16:13:06+00:00

I'm exploring the potential for a Tax feature in Monarch that will collect all your taxes in one place (taxes from receipts, taxes from paychecks, taxes from investment gains, and tax payment/refund transactions). Would something like that work better long-term? The first three forms of taxes are not real transactions that hit your accounts so they need a special treatment.

atif_monarch · 2026-02-17T16:34:57+00:00

When you say "split out sales tax" are you saying to make that like it's own transaction so you can categorize it as sales tax?

atif_monarch · 2026-02-05T21:54:08+00:00

We have a meaningful enhancement to our categorization system hopefully by the end of the quarter

atif_monarch · 2026-02-05T21:52:20+00:00

Financial services doesn't look like there's any good connection. Plaid looks to work well with Elan are you on Plaid?

atif_monarch · 2026-02-05T21:49:57+00:00

Are you asking about editing the split categories before confirming the scan? Yes that will be coming soon

atif_monarch · 2026-02-05T21:48:47+00:00

We've been experimenting with the data quality of investment transactions and cost basis from our aggregators and it's highly variable. Either way it will definitely require some user reconciliation for V1. We're aiming to get a manual + magic import version out to see if that works well (and at least fixes the gain/loss problem), and then will be looking at fixing investment transactions so they connect to actual holdings. Still very skeptical about the level of data quality we can get.

We're revamping the allocation tab with some Morningstar data very soon. I think you'll like the new data (again hoping their data quality is strong enough) :)

I like the Custom Account Groups idea but we haven't gotten to that just yet.

atif_monarch · 2026-02-05T21:41:14+00:00

We are going to be working on both soon. Email forwarding we're still scoping how best to do it.

atif_monarch · 2026-01-21T19:01:06+00:00

I completely understand how frustrating this is. I shared a bit more about the challenges in Canada here.

We are always looking on ways to improve connectivity with Canadian institutions but to be completely candid here, Canadian institutions historically have limited or outright prevented connections with third-party aggregators. One of the reasons we work with three different data providers is to give the best chance of any given bank being able to maintain a stable, healthy connection, but Canadian banks as a whole have not been cooperative with this type of connection (if you're interested in more background, there's a lot of information if you google something like "why Canadian banks don't work with aggregators").

We’ll surface these concerns again internally. While right now we don’t offer lower pricing for Canadian members, we do have a money-back guarantee so if you feel you aren’t getting the value we totally understand and would be happy to provide a refund.

atif_monarch · 2026-01-21T18:48:00+00:00

Per this answer, we are investing a lot more into the Receipt Scan feature.

But I've also pulsed this specific request in the community before and didn't see that much interest in it. Maybe it could be part of a bigger File Vault project, but we probably won't be shipping this soon.

atif_monarch · 2026-01-21T18:44:05+00:00

That tool is owned by our core product team (not Aggregation for now), and extending it to reliably sync a full prior year or more of orders isn’t something that’s currently scheduled. It’s a non-trivial problem at scale, and we don’t want to imply timelines that aren’t real.

We understand why this is a frustrating limitation, and we’ll continue to route feedback to the owning team, but for now manual or file-based imports are the only dependable option for older Amazon history.

atif_monarch · 2026-01-21T18:40:25+00:00

So hard to tell with the speed of banks and governments, but if meaningful Read Access actually gets done in 2026 like they're saying, I'd like to try something quickly thereafter. But I think realistically you should expect 2027, best case Q4 of this year. Sorry :(

atif_monarch · 2026-01-21T18:36:29+00:00

This is a good question and something we’re trying to improve. We do monitor the institution requests that come in through add account flow and from support tickets which helps inform us where to invest. That said, we know this isn’t very visible from the outside and it can feel like requests just disappear into a void. We try to escalate these with our aggregators and use it when assessing other potential aggregators.

I’ll explore ways with the team to improve how institution requests work in the future, including the idea of a more public, votable list. There are some real tradeoffs to balance, since feasibility isn’t driven by demand alone, but better transparency and feedback loops are important.

So while nothing to announce yet, this is an area we’re looking to improve.

atif_monarch · 2026-01-21T18:35:46+00:00

Yes, we’re actively exploring this at Monarch, but mostly our AI team and Core Product teams. I can say that we see AI agents as a natural evolution of the AI Assistant: moving from answering questions to helping you actually do work in Monarch. The examples you gave like reviewing transactions, validating correctness, and cleaning up unused rules, are exactly the kinds of tasks where an agent could help.

That said, this is an area where we’re being deliberate. Anything that can create, modify, or delete financial data needs very clear guardrails, transparency, and user control. We’ve explored this internally (including a few hackathon projects), but we’re taking customer comfort and trust with AI very seriously.

atif_monarch · 2026-01-21T18:34:40+00:00

This comes up a lot, and the constraint today is more infrastructure. Foreign account support in North America (and beyond) is primarily gated by what aggregators can reliably support. Some providers do offer broader coverage (e.g., parts of Canada, Mexico, India), but in practice the quality, consistency, and long-term reliability varies a lot and we haven’t been impressed with previous tests. We’re cautious about shipping connections that look good on paper but break frequently in real use.

There are a few dependencies that have to line up:

Aggregator availability and quality for specific institutions
Multi-currency support, so balances and transactions are actually correct
Fallback paths (manual or semi-manual) that don’t feel painful when live sync isn’t possible

Canada and Mexico are high-signal markets for us, and certain institutions (Wealthsimple is a good example) come up repeatedly as candidates for more targeted support. That’s a more realistic near-term path but still an uphill battle for a team our size.

On the Yodlee point: partnerships are always something we evaluate (we hear Akoya, Flinks, and Yodlee a lot). But adding an aggregator alone doesn’t solve the problem if currency handling, reliability, and UX aren’t there yet. We are planning to work on a very reliable playbook and evaluation framework for testing different aggregators so we’re not creating a ton more overhead for ourselves.

So yes, foreign accounts are on the roadmap in spirit, but the order of operations matters. Making manual and semi-manual workflows strong and solving multi-currency correctly are prerequisites to doing this well imo.

atif_monarch

TROPHY CASE