For accountants & bookkeepers

Stop emailing Excel templates to clients.

Collect bank transactions, expenses, customer lists and month-end figures from clients in the columns Xero and QuickBooks import, checked before they reach you.

Start free. No credit card required.

The spreadsheet way
The Excel template you send today
1
Create or find the right Excel template
2
Email it to your client
3
Wait for them to fill it in
4
Check and clean up the returned file
5
Import or transfer the data
With Import Builder
A structured version of the same workflow
1
Define the columns you need
2
Send your client the workflow
3
They enter or upload their data
4
Validation catches problems
5
Download a clean CSV

THE PROBLEM

Your clients have the information.
Getting it back in the right format takes work.

An Excel template gives clients control over the structure. By the time the file comes back, someone often needs to check it, correct it, and prepare it for the next step.

Dates both ways

03/04 is March in QuickBooks US and April in Xero UK and Australia, and one client file can mix both.

Amounts with extras

Currency symbols, CR and DR, and commas used as decimals all need fixing before a bank import accepts the file.

Columns that move

Clients add, rename and reorder columns, so every file needs mapping again.

Month-end chasing

Missing references and blank amounts turn up at month-end, when there's least time to chase them.

THE ALTERNATIVE

Define the structure once.
Let your client provide the data.

Import Builder gives you a spreadsheet-style workflow built around the exact information you need to collect.

01

Define

Create the columns your client needs to complete.

02

Send

Give your client a link or embed the workflow into your existing application.

03

Validate

Catch missing, invalid, or duplicate values before export.

04

Download

Download a clean CSV ready for your existing workflow.

Turn your client spreadsheet into a workflow.

If you send clients an Excel template for transactions, expenses or month-end figures, define the same columns here.

Clients enter rows directly, or upload a CSV and map its headers to yours.

Define the exact expense columns you need
Make important fields required
Add validation rules
Control the column order
Allow existing CSV files to be uploaded
Map client headers to your structure
Bank Statement
In Xero's import columns
CSV
Date
Amount
Payee
Description
05/08/2026
-84.50
Officeworks
Printer paper
06/08/2026
-129.00
Telstra
Phone and internet
07/08/2026
2400.00
Acme Pty Ltd
Invoice 1043
08/08/2026
-31.99
Adobe
Software
312 transactions
Map a bank export
Their bank's headers, matched to Xero's
Transaction DateDate
ValueAmount
MerchantPayee
NarrativeDescription
RefReference
Columns mapped successfully

Client already has the bank export?
Let them upload it.

Clients can upload the CSV their bank or old software exports. Its headers are matched to Xero's columns, and dates or amounts Xero would reject are highlighted before the file reaches you.

Their bank's export

Transaction Date, Value, Merchant, Narrative...

Date, Amount, Payee, Description, Reference

LESS CLEANUP

Catch problems before the data reaches your team.

Put your requirements into the workflow instead of relying on instructions hidden in an Excel template.

Required fields

Every transaction needs a date, an amount and a description.

Unique values

Mark account codes or invoice numbers unique, and repeats are flagged.

Dates and amounts

One date format per column, and amounts without currency symbols or comma decimals.

Dropdowns

Categories, tax codes or account types limited to the values your ledger uses.

EMBED IT

Put the workflow where your clients already work.

Send clients a link, or embed the form in your client portal. This is the Xero bank statement template, live: try typing $84.50 into Amount.

Link or embed

Share a link, or add the form to your own site with an iframe.

Your branding

Your logo and brand colour on the form.

Row limits

Set how many rows each form accepts, up to 1,000.

CSV processing happens in the browser.

Import Builder processes CSV data locally in the user's browser. Spreadsheet contents don't need to be uploaded to Import Builder simply to provide the editing and validation experience.

Browser-based CSV processing
Spreadsheet contents aren't stored as project data
Validation before export
Clean CSV output

Replace your next client spreadsheet.

Define the columns, add your validation rules, and give clients a structured way to provide the information you need.