Extract as CSV/Excel

View as Markdown

Turn table-heavy PDFs (receipts, invoices, bank statements, expense sheets, GST filings) into spreadsheet-ready CSV, Excel (XLSX), or structured JSON.

You’ll need an Extract Config that describes the tabular fields you want. If you don’t have one yet, see How to Create a Config, then come back here.

Step 1: Run the project

1

Open Extract

Click Extract under Products in the sidebar.

2

Kick off a new project

Click Extract next to your Config, or click Upload documents and pick your file.

3

Give the project a name

Something like Bank Statement May-Q2 to make it easy to spot in the Projects list.

4

Start Extract

Click Extract. Status progresses Draft → Processing → Completed (or Failed if something goes wrong).

Step 2: Review in the editor pane

Once the project shows Completed, click it to jump straight into the editor pane. The source document sits on the left and the extracted tables appear as a hierarchical Output panel on the right. Every row expands to show its fields, and every field carries a per-field confidence score and a source-page reference.

Extract results view for a credit card statement showing the source PDF on the left and a Transactions Output panel on the right with expanded transaction items (date, description, amount, type) and per-field confidence scores.
Credit-card statement extraction: source PDF on the left, expandable Transactions with per-field confidence on the right.

For a bank statement, you might see something like:

DateDescriptionAmountType
02/04/2020UPI Payment Received100000credit
26/03/2020LOGIN AND PAY WITH AMA BANGALORE IN4923.98debit
18/03/2020AMAZON PURCHASE IN2347.98debit

Low-confidence values (e.g. 48%) are highlighted so you can spot-review them quickly.

Edit tables in the Table Editor

Double-click any table in the results to open the dedicated Table Editor. It puts the source-table image on the left and an editable grid on the right, so you can fix cells without losing the surrounding page context.

Table editor showing a source-table image on the left and an editable grid of extracted bank transaction rows on the right, with Image Zoom, Close, and Save Changes controls.
The Table Editor: source-table preview on the left, editable grid on the right.

Inside the Table Editor you can zoom the source preview with the Image Zoom dropdown, click any cell to edit its value, add or delete rows with the + and trash icons, then click Save Changes to commit (or Close to discard).

Step 3: Download as CSV, Excel, or JSON

Click Download to open the export dialog and pick your Format from the dropdown.

Extract Download dialog with the Format dropdown open showing JSON, CSV, and Excel (XLSX) options; Excel (XLSX) is currently selected.
Extract Download dialog: pick JSON, CSV, or Excel (XLSX) from the Format dropdown.
CSV

Single-file, one-row-per-transaction. Best for pandas, SQL loading, or a spreadsheet tool.

Excel (XLSX)

Native Excel format with headers and cell formatting preserved.

JSON

Structured JSON, preserving nested groups and arrays. Best for feeding another system natively.

Confirm to save the file.

Handling tricky tables

Ask the Extract description to un-merge them:

When a cell spans multiple rows, repeat the value across the child rows.

Sarvam normalises the output for you.

Bank-statement descriptions often wrap. Sarvam consolidates wrapped lines into a single row by default. To keep them split, add:

Preserve each line of the description as a separate row.

Sarvam detects each distinct table. In Excel output, each becomes its own sheet. In CSV, tables are separated by a blank row. Split on blank rows in your loader.

Currency symbols and thousands separators are kept as-is unless you ask otherwise. Add:

Return amounts as plain numbers without currency symbols or commas.

Batch processing many documents

Two approaches, depending on how many similar documents you have:

Run one project per document

Best when you want each document’s rows in its own file. Every project shows up in Workspace → Projects for easy tracking.

Consolidate manually after download

Download CSVs or JSON from multiple projects and concatenate them. One paste per project works because column layouts are identical across runs of the same Config.