Skip to content
Product

One loop, four modules.

Observe, match, flag, close. Tessel runs the loop on every line of every account, and leaves the evidence for each step where your team can read it.

AReconcile

Every line, paired with its entry.

Tessel reads the bank and card feeds as they land and pairs each line with the ledger entry it belongs to. It handles the awkward ones too: one payment against three invoices, a transfer split across two days, a fee taken off the top.

  1. 01One-to-one, one-to-many and partial matches
  2. 02Fees and FX differences booked to their own accounts
  3. 03Every match names the rule that made it
Operating account · March 2026Operating account
Four ledger lines in the Reconcile view
#DateDescriptionBankLedgerStatus
0101 MarNorthfold Freight01 Mar4,200.004,200.00Matched
0202 MarLarkspur Hosting02 Mar1,180.401,180.40Matched
0304 MarCard · Quayside Café04 Mar42.6042.60Matched
0708 MarPayroll run 0508 Mar28,400.00—Open
Suggested matchExact reference
Bank
04 Mar · Card · Quayside Café
42.60
Ledger
JE-1043 · Meals and entertainment
42.60

Reference, amount and date agree. Below your auto-match threshold of 500.00, so Tessel matched it and logged the evidence.

ApproveUnmatch

BFlag

One reason, and the evidence.

Some lines shouldn’t be matched. Tessel holds them and says why in one sentence, with the documents that made it suspicious attached.

  1. 01Duplicates, missing receipts, unusual amounts, new vendors
  2. 02One plain reason per flag, with the evidence attached
  3. 03Held lines never auto-match until a person decides

Flag · Line 05

Possible duplicate

Paperline Studio billed 640.00 on 06 Mar and again on 02 Feb, with the same reference. Held until someone decides.

Evidence · 2 bank lines · 1 invoice

HoldMatch anyway

Flag · Line 11

Missing receipt

A 312.00 card payment to Harbour Water has no receipt, and receipts are required above 75.00. Held until one is attached.

Evidence · 1 card line · 0 receipts

Request receiptMatch anyway

CClose

A checklist that fills itself in.

The month-end checklist updates as the work gets done. Tessel suggests accruals, explains movements against last month, and waits for the people who own each task to sign off.

  1. 01Accrual suggestions from open orders and recurring bills
  2. 02Flux against last month for every balance-sheet account
  3. 03Sign-offs by the people who own each task
  • Bank reconciliationsReconcile · 6 of 6Done
  • Card spend reviewReconcile · 214 of 214Done
  • Accrual suggestionsClose · 3 of 560%
  • Flux against FebruaryClose · 41 of 66 accounts62%
  • Controller sign-offClose · waiting on 2 tasks—

DEvidence

A trail an auditor can follow.

Every action Tessel takes is logged with its source documents. Any number on the balance sheet can be followed back, line by line, to the bank.

  1. 01Every action logged with its source documents
  2. 02Read-only access: Tessel never moves money
  3. 03An auditor view that starts from any number
Evidence · line 03Export PDF
  1. 04 Mar 09:12Bank line receivedOperating account · 42.60
  2. 04 Mar 09:12Matched to JE-1043Rule · exact reference under 500.00
  3. 04 Mar 09:12Receipt attachedreceipt_0304.pdf
  4. 05 Mar 10:02Reviewed by the controllerNo change
  5. 31 Mar 17:40Period closedMarch 2026 · signed off
Control

Tessel proposes. You approve.

Set the thresholds once. Below them Tessel acts and logs why. Above them, every line waits for a person.

Approval rules3 active
  • Auto-match when the reference is exactUnder 500.00
  • Hold every vendor seen for the first timeAny amount
  • Ask for two approversOver 25,000.00
  • Auto-book processor feesUnder 5.00
Waiting for you2 lines
  • Tidewater Leasing · fleet renewalOver 25,000.00 · 1 of 2 approvals31,200.00Approve
  • Brightmoor Supplies · first invoiceFirst-time vendor1,845.00Approve
What Tessel reads

Reads everything. Moves nothing.

Read-only connections to the systems your close already runs on. Tessel never initiates a payment.

  • ERP and general ledger

    • Chart of accounts
    • Journal entries
    • Open periods
  • Bank feeds

    • Statement lines
    • Balances
    • Remittance details
  • Card programmes

    • Card transactions
    • Receipts
    • Cardholders
  • Payroll

    • Pay runs
    • Employer taxes
    • Accrued wages
  • Billing

    • Invoices
    • Payouts
    • Fees and refunds
  • Data warehouse

    • Custom tables
    • Entity mapping
    • FX rates
Security and audit

Read-only, by design.

Tessel reads. It never initiates a payment, never edits a bank record and never deletes a ledger entry.

  • Read-only bank access

    Bank and card connections are read-only tokens. There is no permission to move money, so there is nothing to misuse.

  • Role permissions

    Preparers, reviewers and controllers see and approve different things. Every role is set per entity.

  • The evidence log

    Every action is written once and never edited: who, what, when, and the documents behind it.

  • Data residency

    Each workspace lives in one region, EU or US, chosen when it is created.

Close next month with nothing left to tick.