Bkper Sheets Add-on: Unified Output & Batch Editing

Jacob van den Berg | December 8, 2025

We’ve made two significant improvements to the Bkper Add-on for Google Sheets: unified output formats for all fetch functions, and the ability to save edits to Transactions back to Bkper directly from your spreadsheet.




Unified output formats

Previously, when fetching Transactions, the output format varied depending on your query. If you queried a permanent account (Asset or Liability), you’d get a single-entry format with Debit, Credit, and Balance columns. Otherwise, you’d get a double-entry format with From and To accounts. Combined with optional properties, this meant the output structure was far from standard—making it difficult to build reliable processes on top of it.

Now, the output is always the same. Whether you fetch transactions, accounts, or groups, each output starts with an ID column and always includes properties. One format. No variables.

This consistency matters because many teams already have processes built in Google Sheets—checks, analysis, approvals. When a bank statement is uploaded to Bkper, a financial team might want to review that data in their existing workflow, consolidate or maybe apporve it. With a unified output format, you can build your process once and trust that the data structure won’t change based on what you’re querying.



Save edits back to Bkper

With unified output comes the second major update: you can now save edits from Google Sheets back to Bkper.

Fetch your transactions, modify descriptions, correct accounts, update amounts or properties—then press Save. Your changes are applied directly to the existing transactions in your book.

How it works:

The unique Transaction ID from your book, garantees that the modifications made outside of your book for example in a Google Sheet always correspond to the same record in your book. This is also the main reason why properties are no longer optional. If you saved a transaction without its property columns, those properties would be lost. By always including properties in the output, your data remains complete through the round-trip.




The Bkper Agent learns from your edits

When you upload a bank statement to Bkper, the Agent reads the document and records transactions based on your history—completing the From and To accounts for each row. When you later correct an account, the Agent notices the edit, analyzes why it categorized differently, and adjusts its own understanding for next time.

Previously, many users had to export transactions to a spreadsheet, make batch corrections there, re-import them as new transactions, and then delete the originals. This workflow broke the Agent’s learning cycle, since there was no link between the initial categorization and the corrected version.

Now, when you edit transactions in Google Sheets and save them back, the Agent recognizes these changes and learns from them, steadily improving its categorization accuracy over time.




Version control for prompts

With the introduction of the Bkper Agent, Accounts and Groups now have the possibility to carry an agent_prompt property. These instructions guide the Bkper Agent on what to do with new input related to a specific Account or Group—for example, how to categorize transactions or what details to extract.

When you want to refine or experiment with these prompts, you can edit them in the edit popup in Bkper itself. But here’s the real advantage of editing agent_prompt properties in Google Sheets: Google Sheets maintains version history of all your changes.

This means you can experiment freely with different prompt instructions. If a new version doesn’t perform as well as the previous one, you simply go back to an earlier version in Sheets’ version history and save it—your book is updated with that working version. No need to remember what the old prompt said or try to recreate it from memory.

Note: Saving Account and Group edits from Google Sheets is coming soon—see “What’s next” below.




What’s next

For the moment, accounts and groups fetch in a unified format but cannot yet be updated from Sheets. We plan to make these editable as well in a future release.




A note on compatibility

If you had reports built on the previous output formats, you may need to adjust column references. We appreciate your patience and count on your understanding as this change unlocks batch editing and expands what’s possible with Bkper and Google Sheets together.

Learn more: Bkper Add-on for Google Sheets Help




Share on

and