Contact

Calligra Sheets · Templates · Beginner

Create and Reuse an Expense-Sheet Template in Calligra Sheets

Create a clean Calligra expense template, register it, instantiate two months and validate a revised master without overwriting prior work.

Official 26.08.2 source and KDE handbook reviewed; native application verification pending · Editorial standards

Turn a clean expense model into a template that starts every month with blank inputs and intact formulas. Then create two separate workbooks to prove that entering one month’s spending does not contaminate the next.

Scope and preparation

Calligra Sheets 26.08.2 desktop source, English interface, with KDE handbook cross-checks; instructions and expected results are documentation-backed and have not been executed in the native application. Linux-oriented file recovery; Windows, macOS and distribution-specific builds require separate verification.

Use a local, disposable folder. The KDE handbook describes the template command, but its old .kst extension and KDE4 storage path are obsolete for this workflow. The 26.08.2 source creates .ots templates and registers them through the application’s template resource system. Use the template chooser rather than manually copying files into an old hidden folder. No native screenshots are available for this version.

Build the reusable master

Create a blank workbook with File → New. On the first worksheet enter the following cells individually; leave cells marked blank genuinely empty, rather than typing the word blank.

Cell Entry
A1 Expense template v1
A2 Month
B2 blank
A4 Category
B4 Budget
C4 Actual
D4 Remaining
A5 Food
B5 240
C5 blank
D5 =B5-C5
A6 Travel
B6 90
C6 blank
D6 =B6-C6
A7 Supplies
B7 70
C7 blank
D7 =B7-C7
A9 Total
B9 =SUM(B5:B7)
C9 =SUM(C5:C7)
D9 =B9-C9

Expected clean totals are 400 budget, 0 actual and 400 remaining. Widen columns if headers are clipped. Use File → Save As…, choose OpenDocument SpreadSheet, and save as expense-master-v1.ods. This saved workbook is a separate, inspectable master; it is not yet a registered template.

Check formula inputs before registration: D5:D7 must contain formulas, not their displayed numbers. B2 and C5:C7 must be empty. A formula accidentally replaced with a number would be reproduced in every new instance.

Register and discover the template

  1. With the clean master open, choose File → Create Template From Document….
  2. In the Create Template dialog, enter the unique name Expense practice v1. Select an existing template group or use Add Group… to create a practice group, then select that group. Keep the default preview picture. Explicitly uncheck Use the new template as default before choosing OK; the reviewed source initializes this checkbox as checked.
  3. Confirm with OK. If asked to overwrite an existing template, cancel and choose a different name so this exercise cannot replace someone else’s master.
  4. Choose File → New and locate Expense practice v1 in the group you selected. Open a new document from it. If the chooser does not appear or the template is absent, stop and resolve that installation’s template discovery before continuing. Opening the saved .ods directly is not this test.
  5. Immediately use File → Save As… to name the new instance expenses-october.ods in the disposable folder. Confirm that its filename is different from expense-master-v1.ods.

Enter a month and verify independence

In the October instance, put October practice in B2 and enter C5=215, C6=60 and C7=45. D5:D7 should become 25, 30 and 25. C9 should be 320, and D9 80. Save, close and reopen expenses-october.ods; inspect both the results and formulas.

Next choose File → New and create another instance from Expense practice v1. Before typing anything, verify B2 and C5:C7 are blank, B9 is 400, C9 is 0 and D9 is 400. Save this as expenses-november.ods. Enter November practice in B2 and 230, 80, 50 in C5:C7. Expected actual is 360, with 40 remaining. Save and reopen this file as well. Reopen October and verify that its actual remains 320. Finally open the saved master and verify its actual is still zero.

These are expected checkpoints to run locally, not reported native observations. A populated November instance indicates that the registered template contained October’s inputs or that the October file was reopened instead of creating a new document.

Grow the model without changing v1

For a revision, open the saved clean master and immediately Save As… expense-master-v2.ods. Keep the existing three categories. In row 8 enter A8=Equipment, B8=100, leave C8 empty, and enter D8==B8-C8. Change B9 to =SUM(B5:B8) and C9 to =SUM(C5:C8); D9 remains =B9-C9. Change A1 to Expense template v2.

The revised clean budget and remaining should both be 500. Save this intended final master before registering Expense practice v2 under a new name. In this registration dialog, explicitly uncheck Use the new template as default again before choosing OK. Make a new v2 instance, save it as expenses-v2-check.ods, and enter 215, 60, 45, 80 in C5:C8. Expected actual is 400, with 100 remaining. A newly created v1 instance must still have three categories and a 400 budget. Do not assume that editing a master updates previously registered templates or already-created workbooks.

Repair a bad instance

If only the month’s inputs are wrong, correct those inputs and save that instance. If formulas or template structure are wrong, retain the affected instance under a separate filename, rebuild a clean master, and register a uniquely named revision. Recreate a fresh instance and transfer only the intended input values. Do not use Undo after closing and reopening as a recovery plan, and do not overwrite the clean master with a populated instance.

For the initial budgeting concepts, see your first expense tracker. For format choices, see file compatibility.

Sources and verification boundary

The KDE saving and templates handbook supplies the user workflow. The official Calligra 26.08.2 source archive, sheets/part/View.cpp, Part.cpp, calligrasheets.rc and libs/main/KoTemplateCreateDia.cpp, confirms the current command, .ots creation and separate registered template storage. This is source review, not a guarantee that every packaged build presents the same chooser. Native template discovery, persistence and screenshots remain to be verified.