openmasu
solutions · finance
Budgets, spend and payments in one base you can close the month on.
Compare each budget line with what was spent using formulas, take purchase requests through a form with an approval status, and read Stripe or SumUp payments synced every 15 minutes. Group by month and let the summary bar do the totals.
- Budget vs spend formulas on every line
- Purchase requests via form with approval status
- Stripe and SumUp payments synced every 15 min
| Line | Department | Budget | Spent | Remaining | Used |
|---|---|---|---|---|---|
| Cloud hosting | Engineering | $12,000 | $9,450 | $2,550 | 79% |
| Paid social | Marketing | $8,000 | $8,620 | -$620 | 108% |
| Trade shows | Sales | $15,000 | $4,200 | $10,800 | 28% |
| Office supplies | Operations | $2,400 | $1,310 | $1,090 | 55% |
| Training | People | $5,000 | $3,750 | $1,250 | 75% |
Everyday workflows
Budget against spend, line by line
Each budget line holds its department, budget and spent so far. Formulas `{Budget} - {Spent}` and `{Spent} / {Budget}` show what's left and how much is used, and `IF({Spent} > {Budget}, "Over", "")` flags overruns. A filter «Used is greater than 90%» gives the lines to talk about at the weekly review.
Purchase requests through a form
Anyone in the company submits a request from a public form: item, amount, vendor, department and a link to the quote. Each answer lands as a record with status Pending. Finance moves cards across a kanban by «Approval status» and uses comments with @mentions to ask the requester for details.
Payments and invoices synced from Stripe or SumUp
Connect Stripe and OpenMasu creates a base with Customers, Payments, Invoices, Subscriptions and Products, refreshed every 15 minutes. It's read-only: nothing is written back to Stripe. Add your own fields, like an «Account code» select or a «Reconciled» checkbox, and the sync never touches them. SumUp card and online sales plus payouts work the same way.
Month-end in a grouped grid
Add a formula `DATETIME_FORMAT({Date}, 'YYYY-MM')` to purchases and payments, then group the grid by month and by department. The summary bar re-totals the visible rows, so filtering to «Reconciled is unchecked» shows exactly what still needs checking before you close.
Views & structure
Key views
- Budget review Lines with remaining and used formulas, summary bar totals.
- Purchase request One public link for every request; each answer becomes a record.
- Approvals Requests stacked by approval status; drag to approve or reject.
- Month-end Grouped by month and department, filtered to unreconciled items.
Recommended fields
- Budget (Currency) Planned amount with your currency symbol and decimals.
- Remaining (Formula) {Budget} - {Spent}, recalculated on every change.
- Used (Formula) Spend as a share of budget, formatted as percent.
- Approval status (Single select) Pending, Approved, Rejected, Paid: drives the kanban.
- Quote (URL) Link to the quote or invoice PDF wherever it's stored.
- Reconciled (Checkbox) Your own mark on synced payments, never overwritten.
Your agent over MCP
Connect your own agent (Claude, ChatGPT, Codex or Cursor) over MCP and ask in plain words. It totals and groups records with aggregate_records, reads synced Stripe data, and only edits what your token allows, marked in history.
aggregate_records query_records create_view update_records
Close the month from one base
Set up budgets and requests, connect Stripe or SumUp, and let formulas do the arithmetic.