AI and MCP

Getting a client's expense data into your own books, step by step

A beginner tutorial on how to pull client expense data into your own workflow without writing code: what an API is, why a file often does the job, and the steps.

Editorial illustration for Getting a client's expense data into your own books, step by step

An API is a way for one program to ask another for data without a person clicking buttons. You may never need one: if your client's expense app can export a file and you can import it into your accounts, you already have a working data pipeline. This tutorial is for the bookkeeper or finance person who is not technical and wants a clean, repeatable way to get client data each month.

What is the simplest thing that works?

A monthly export file, checked and then imported. In SpendixAI, the Export centre has templates for Tally, Zoho Books, QuickBooks, a standard all-transactions file, and a categories-and-tax-codes file, and reports can be downloaded as CSV. The owner of the workspace does the export. I am describing only what the product lists; if you need a technical interface beyond that, ask the vendor directly.

The steps

  1. Tell the client which month and which template you want.
  2. The client uploads that month's bank and card statements to their workspace, picking the account for each, and reviews rows before saving.
  3. The client exports the file and sends it to you.
  4. You open it and check the row count and the total, as in the example below.
  5. You import it into your books.
  6. You save the original file, unchanged, in the client's folder.

The check that saves trouble

Say three clients send their files. You note how many rows each contains before you do anything.

ClientRows in fileRows after importMatch?
Client A120120Yes
Client B8585Yes
Client C6462No, 2 missing

The total is 120 plus 85 plus 64, which is 269 rows expected. If your books show 267, two rows from Client C did not come through. Go back to the file, find which rows were rejected, and fix them. This takes five minutes and prevents a month-end surprise.

Why not just ask the client to forward the statements?

  • A statement PDF has to be typed or parsed again, which introduces mistakes.
  • An export already has the categories the client chose, which saves you sorting.
  • Bank statement layouts differ, and importing them may not parse perfectly every time, so the review step matters.

Making it safe

Client records are private. Ask for files through email or a shared folder that only you and the client can open. Never ask a client for a bank login, and never accept one. The app does not ask for net-banking logins, so an exported file is all you need. Delete working copies you no longer need once the books are closed, in line with your own retention rules.

What the product is not

Pro covers one personal workspace, so it is not a team or approvals tool, and it is not a practice-management system. Each client keeps their own workspace and you receive their exports. GST figures in reports are estimates to confirm with invoices and your own judgement.

A word on naming files

Boring habits make this work. Name each file with the client, the month and the template, for example clienta-2026-10-standard. Keep an untouched copy in a folder called original, and work only on a duplicate. If a client sends a second file for the same month because they added something late, mark the first as superseded rather than deleting it. When you later wonder why October looks different, the folder will tell you.

A one-page checklist

  1. Template chosen and written in the client's note.
  2. File received and original saved.
  3. Row count and totals checked.
  4. Imported, with the post-import count noted.
  5. Client told if anything was missing.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports