Skip to content
Use case

Card spend, coded on arrival.

Every card line is matched to its receipt and coded as it posts, and the ones without a receipt ask the cardholder for one, so the statement is reconciled the day it closes.

Book a demo
The problem

Receipts in inboxes, codes in someone’s head.

Card statements arrive with hundreds of small lines and no receipts. Finance chases cardholders for a week, then codes what’s left by guessing.

The lines that cause trouble are the same every month: missing receipts, personal spend on a company card, and subscriptions nobody remembers starting.

The workflow

Four steps, three of them Tessel’s.

  1. 01

    Connect the card programme

    Card transactions arrive as they post, with the cardholder and merchant on each line.

  2. 02

    Tessel matches receipts and codes

    Receipts forwarded by email are paired with their line, and the line is coded from its history.

  3. 03

    Missing receipts ask for themselves

    Lines above your threshold email the cardholder once, then wait in their list.

  4. 04

    Approve the statement

    Reconcile the statement against the card account in one sign-off.

In the product

The card spend view

Company cards · March 2026Company cardsDifferenceΔ 480.00
Card spend: the preset ledger
#DateDescriptionBankLedgerStatus
1202 MarLumen Office Supply02 Mar86.2086.20Matched
1303 MarQuayside Café03 Mar42.6042.60Matched
1403 MarTram pass · monthly03 Mar64.0064.00Matched
1504 MarHarbour Water04 Mar · Missing receipt312.00—Flag
1605 MarSoftware · annual seat05 Mar480.00480.00Open

Close next month with nothing left to tick.