For Finance

Expenses & reimbursements

Reimbursements get lost in inboxes and nobody's sure who's owed what. Here's how a team turns expenses into one shared log just by describing it — where a bad entry simply can't get in.

  • Built by chatting
  • Bad entries refused
  • Totals in a sentence

01 The problem

Reimbursements get lost in inboxes

Receipts arrive as forwarded emails, chat screenshots, and photos. Some get paid twice, some never at all. By month end the team is scrolling three inboxes trying to remember who is still owed.

Nobody wants an expense platform. You just want the list to be right.

Ops lead Describes the problem
You

Expenses come in from everywhere and half of them get lost. I never know who still needs reimbursing.

TypeTable

Let's give the team one shared expense log. Tell me what you track on an expense and I'll build it.

02 Just describe it

Say it in a sentence

You type what an expense looks like in plain English. TypeTable suggests a table — which fields to include and what rules to apply — and waits for you to approve.

The category becomes a fixed list, so a random "Miscellaneous" can never creep in again.

Ops lead Creates the log
You

Track person, amount, category, status, whether there's a receipt, and the date.

TypeTable Expense log

Here's the table I'd create:

  • Person
  • Amount
  • Category
  • Status
  • Receipt
  • Date

Amount can't be negative · Category from a fixed list · Date can't be in the future

Approve Edit fields

03 It's ready

Live in minutes, not weeks

You hit approve and the expense log is real — a real table you can share with the whole team. No field design, no IT project.

Expense log Live
amountnumber categoryenum statusenum datedate
$240 Travel Submitted Jul 1
$89 Software Reimbursed Jun 24
$32 Meals Approved Jun 30
Rules checked on every entry

04 The team just types

The team submits by talking

No complicated forms. No training session. You set it up; teammates just say what they spent. TypeTable applies the rules and saves it clean, with the receipt flag set for them.

Set it up once
Ops lead Sets it up
You

New expenses start as Submitted until I approve them.

TypeTable

Done — status defaults to Submitted on every new entry.

Anyone adds records
Teammate Submits an expense
You

Add $240 flight to Jakarta, travel, I paid, receipt attached.

TypeTable

Saved — $240, Travel, receipt yes, Submitted, dated today.

05 Ask a question, get an answer

"How much did we spend on travel?"

No spreadsheet formulas. You ask in plain language and get the number back instantly — plus a chart of spend by category you can drop straight into the finance update.

Ops lead Asks a question
You

How much did we spend on travel this month?

TypeTable
$4,820 on travel

this month · 14 expenses

You

Break it down by category as a chart

Spend by category USD

06 Keep it trustworthy

Bad entries get politely refused

Every submission is checked. When a teammate mistypes a negative amount or invents a category, TypeTable won't save it — it says what's wrong and offers a fix.

Friendly, not scolding — and never silent.

Teammate Submits an expense
You

Add -50 dinner, category Miscellaneous

TypeTable

Couldn't save that one. The amount can't be negative, and Miscellaneous isn't one of the allowed categories. Want to log it as a positive amount under Meals?

Amount ≥ 0 · Category ∈ Travel, Meals, Software, Office, Other

You

$50 team dinner, Meals

TypeTable

Saved — $50, Meals, Submitted, dated today.

What does your team keep re-typing?

If your team keeps updating the same spreadsheet, TypeTable can replace it. Describe it once and let everyone add records in plain language.

See how it works Get started free