Busy ERP to Google Sheets: CSV Import and Spreadsheet Reporting

For a finance or operations team, a checked export is often a useful first step: take one report, preserve the company and financial year, and reconcile it before building a dashboard. Ask your Busy provider which export fields your edition and report support. This guide does not verify a particular Busy installation or connector.

A spreadsheet is a reporting copy. Keep Busy as the accounting record and show when the copy was obtained. Changing a Sheet does not write a voucher back to Busy unless a separately designed and verified integration does so.

Choose a question first: outstanding by invoice, stock by warehouse, or sales by period. Export only the columns needed to answer it. Confirm the report’s filters, company, financial year, currency, opening balances and treatment of cancelled or reversed vouchers. Avoid putting payroll, full bank details or unrelated customer information into a shared dashboard.

Keep an unchanged export and a short import log with report name, extraction time, filters and operator. In Sheets, separate Raw data from Calculations and Dashboard tabs. Review who can view and edit the destination before importing financial data; do not publish a private ledger as a public CSV link.

On a computer, open the destination spreadsheet and choose File → Import. Select the CSV, choose an available import option such as inserting a new sheet, and use the correct separator, then import. For this example, use a comma separator and rename the imported tab Raw. Google lists the supported formats and import options in its file-import documentation.

The sample below is invented data for a two-invoice exercise. Save it as a UTF-8 .csv file if you want to try the documented steps in your own disposable spreadsheet. DEMO is not a real company. The quotation marks around the first customer preserve the comma inside that one cell.

Compare row count, unique invoice keys and totals with the original Busy report. If the totals differ, stop and inspect the export filters, duplicate rows, credit notes, blank amounts and date formats. A successful upload alone does not establish correct accounting data.

Evidence illustration

Validate the reporting copy against its source

A successful import is only a starting state. Compare the rows and totals before relying on a dashboard.

01

Source

Keep the original export, company and financial-year context available.

02

Match

Check row counts, dates, amounts and duplicates against that export.

03

Freshness

Record when the copy was produced and who reviews exceptions.

For the sample, columns G and H contain invoiced and paid amounts. In Calculations, =SUM(Raw!G2:G3)-SUM(Raw!H2:H3) gives 67000. Keep invoice references as text if leading zeros matter. Verify that dates were interpreted as intended for the spreadsheet’s locale rather than silently swapping day and month.

For an ageing exercise, put an explicit as-of date in Calculations!B1. With a recognised due date in Raw!E2, =MAX(0,$B$1-Raw!E2) gives days overdue. At 2026-04-30, the two sample invoices are 15 and 10 days overdue. Use outstanding amounts, not the original invoice totals, in ageing buckets. A changing current-date formula cannot make a stale export current.

If a second spreadsheet needs the checked Raw data, use its Google spreadsheet URL and range. Replace DEMO_SPREADSHEET_ID below with your source spreadsheet ID; this placeholder is not a working document. The source tab must be named Raw and contain A1:H3. Enter the formula into a clear area of the destination.

You need source access and must explicitly connect the spreadsheets. Google documents a first-use #REF! prompt to allow access. Review destination editors: once connected, any destination editor can pull other source ranges. A small selected range is not a permission boundary.

Google documents update delays and a 10 MB received-data limit per request. Keep ranges bounded and avoid chains and cycles. IMPORTRANGE does not refresh the CSV in Busy or upload a new export; an operator or separately verified process must update the source data.

A manual CSV import is a snapshot. Set an owner and a freshness threshold suitable for the report. If a refresh fails, keep the last checked snapshot clearly dated, flag the failure and do not label it live. Do not let a partial import overwrite the last reconciled dashboard.

IMPORTDATA is documented for CSV or TSV at a URL. A local file path is not such a URL, and the formula is not an authenticated Busy connector. For private financial data, keep the manual import path or evaluate an authenticated integration rather than exposing a ledger to make a formula work.

For automation, ask for the actual supported Busy interface, required permissions, field mapping, company/year isolation, scheduler, update semantics, failure log and recovery process. There is no verified universal refresh interval in this guide. Google’s Sheets API has per-minute quotas and documents bounded exponential backoff for quota errors; switching from push to pull does not remove those quotas.

For receivables, group outstanding amounts into due, 1–30, 31–60, 61–90 and over-90-day buckets at a stated as-of date. Reconcile their sum with the source report. Show disputed invoices separately so a dashboard does not turn a dispute into an automatic reminder.

For inventory, compare stock by warehouse and batch only when those fields exist in the export. Confirm units and stock valuation basis before combining companies or years. For sales, use a consistent net/gross basis and handle returns. A chart should state its filters and last successful refresh.

Forecasting is a separate modelling exercise. Historical sales alone do not establish forecast accuracy; test assumptions, seasonality and missing periods. Keep statutory reports and accounting approvals in their authorised workflow. A spreadsheet dashboard is not evidence of tax or legal compliance.

A checked Sheet can be a staging copy for a CRM migration: map customer keys and field types, preview the destination records, and prevent duplicate updates. Do not assume that Salesforce, Zoho or another ERP connector is installed or that every field can be transferred.

For document generation, agree a template, reference and storage permission before creating PDFs. Validate totals and recipients against the accounting record. A Google Sheet by itself does not create invoices or send WhatsApp messages.

A candidate messaging workflow is: checked record → permitted recipient → reviewed template/attachment → configured sending service → recorded result and failure handling. Balance and ledger replies need customer-to-ledger authorisation; a matching phone number alone should not disclose all financial data. Confirm platform/account conditions and supported trigger behavior before a pilot.

Use synthetic data first, then obtain approval for a limited real report. Separate who can import, edit calculations and view outputs. Decide retention, deletion and incident handling with the responsible owner; this guide makes no encryption, compliance, audit-log completeness or provider-security assurance.

Before expanding, demonstrate a repeat refresh, a duplicate row, a changed invoice, an unavailable source and a recovery to the last checked snapshot. Record what the operator should see at each failure. Automation is ready only when supported behavior and reconciliation are verified for the intended company and report.

The linked Google documentation was checked on 29 September 2026 for import syntax, file import options, access behavior and API limits. That check is not a live Busy or Google Sheets integration test, and does not change this article’s source-record publication date.