Liquidity planning in Seatable

Hi,
for my young company it is important to me to track the finances properly.
I have been using Seatable privately for some time now and am very enthusiastic.

My wish is to map a large part of the business processes with Seatable and to use it as a central hub for our data.

I would also like to create liquidity planning in Seatable. I imagine something similar to finban.

Unfortunately, I am reaching my limits with my current level of knowledge.

I’m currently failing because I want to track and categorize all transactions in a table. And in another table, results are calculated based on the data and broken down by month.

Is this even possible with Seatable and if so, can anyone give me a tip on the best way to go about it?

With enough effort this is possible. I am tracking my personal finances since 2017, exported from my bank account obviously.
I am tracking all bank account, cash, credit cards, paypal, etc.
The main table contains 11865 rows. There are additional tables for categories, invoices, bank imports and summary per month to track how much percent of yearly expenses are spend per month. Same for income.
When I pay with Apple Pay, expenses are tracked immediately via shortcuts and n8n.
Expenses are automatically processed via n8n. I am also using this for taxes.

Took me a years to have it up and running.

This is 100% possible. All you need to do is… start. Next step is to improve from there.

That sounds promising.
I have a similar approach with a main table in which the data is collected.

What I can’t manage is an extra table in which income and expenses are summarized per month.

Can you tell me how you managed to do this?

Hi @JordanBW, and welcome to the SeaTable forum!

There are (at least!) two ways of doing what you want:

  • if you just want to display the summarized amounts, you could just Group your entries in your first table, creating for example one first grouping rule by category, and a second grouping rule by date/monh
  • if you want to be able to store these amounts (which seems to fit better with what you describe), you’ll have to create links between tables and to use link formulas, particularly rollup formula to be able to calculate the sum of several linked records

Here are two ideas I can think of, depending of what you want (you can actually use both at the same time):
Grouping by category

  1. Create a Categories table2.
  2. Create a Category column in your first table (Link to other records type)
  3. In your Categories table, you can create on Global amount column (link formula/rollup/sum on first table’s amount) and monthly amounts in a similar way (presentation will look like one category per row, one monthly amount by column)

Grouping by month

  1. Create a Months table
  2. Create a Month column in your first table (Link to other records type)
  3. In your Months table, you can create on Global amount column (link formula/rollup/sum on first table’s amount) and category amounts in a similar way (presentation will look like one month per row, one category amount by column)

My preffered solution: Grouping both by category and by month

  1. Create a Categories table and a Months table
  2. Create a Monthly categories table where each row is linked to both a month (from Months table) and a category (from Categories table)
  3. Create a Monthly category column in your first table (Link to other records type)
  4. In your Monthly categories table, presentation will look like one month+category per row, one single amount column. You can then create for example one first grouping rule by category, and a second grouping rule by date/month

Bests,
Benjamin

What I do:

  • main tables with all details per expense
  • category table with parent and child categories, e.g. leasing for a car is the child category of “cars”, etc. you could also add subscriptions or contracts with parent categories as services.
    from main table you add the link to a specific category which will then populate the parent category too, if you add your link formulas correct.
  • there is a third table with months.
  • The recurring categories are linked to the months when they are usually due. This is very handy for insurances that are due once per year.

If you add all the expenses you are already aware of you will see exactly how much you spend at any given time in the future plus you will see how much of your expenses occur in which month. If you already know that an insurance is due in july 26, then add it.
Play around with formula and linked columns.
With this setup I can compare this current month with 12 month ago and what to expect in 12 months.

My category table contains 154 columns with all kinds of data I might need for aggregations and statistics, e.g. last 7 days, last 31 days, last 90 days, last 180 days, etc., sum for last 12 months, forcast 12 months, this month, last month, -2 months, +2 months, etc. and so on.

Thank you very much!
Your approaches have helped me a lot and I have already been able to implement a few things.

Is there a way to display different columns instead of several groups in a line chart?

You’re welcome. :slight_smile:

I don’t think there is way to display different columns in a single chart. And to be fair I think it doesn’t make any sense since every column could display different dimensions of data.
What I’d do is, create a third column with a formula to display either or. This new column is displayed in the chart.

In my case, that makes sense.

I have several columns next to each other that show sales trends in different scenarios.
Each row represents one month. I would like to see the possible scenarios in a chart and how they change in relation to each other.

Ok, fair enough, it makes sense in your case. I think this is just not working with how graphs are created. I can’t think of a chart where you could add multiple columns.

You could create a separate table with the scenarios and create multiple rows per month, but for the different scenarios. I think you could create a chart where you group per scenario and per month. I am not 100% sure though.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.