Back to resources

Close the period. Keep its working.

See what a completed Trimsum run preserves, how it differs from an editable draft and what remains available in summary and detailed audit exports.

A completed commission record should still make sense after rates change and the next export arrives. Trimsum saves the selected period, its source lines, calculation settings and review decisions together at finalisation. The record remains available in Archive while the draft moves on to the next set of sales.

The useful part

Finalisation creates a fixed application record of the reviewed calculation. It does not certify the source report, send a payment or replace a separate backup.

A draft is a working calculation

While a period is open, you can import sales, choose dates, correct staff or categories, change rates or dated agreements and reopen review decisions. The displayed commission responds to those changes. Missing rates or staff links, uncovered agreement dates, unresolved categories and held duplicates can keep amounts out of its total; other unresolved questions may still be reflected in the arithmetic. That makes the draft useful for investigation, but unsuitable as a completed record until its review is finished.

The close checks more than a checkbox

Every review item must be resolved, at least one eligible sale must remain and the run needs a non-empty name. For an account workspace, the local server recomputes finalisation from the saved draft and checks its current revision. A stale tab cannot silently replace a newer saved state. After a successful close, the server supplies the recorded identity and time. These checks protect the application workflow; they do not establish that the supplied business assumptions were correct.

Know exactly what is kept together

The run preserves period dates, calculation policy, reviewed rows, staff totals, overall commission and the review audit captured with the run. Legacy closes keep their staff rules; dated closes also snapshot the linked staff and agreements selected for their rows. Each saved row retains its source reference, source filename and row number, plus original-column values when the import captured them. Included-sale fingerprints support later repeat detection. Excluded rows also remain in the record, making the explanation for their zero contribution inspectable instead of removing them from the history.

Draft and completed record
ElementCurrent draftCompleted run
Staff ratesCan changeSaved rates retained
Review noteCan be reopenedSaved with its treatment
Period salesEditable working rowsSnapshot kept in Archive
New importCan add or replace draft rowsDoes not update the closed record

A rate change leaves the old result explainable

Suppose a fictional service used a $200.00 supplied basis and a 40% rate, giving $80.00 at close. The current draft rate later changes to 45%. The same basis would now calculate $90.00, but the archived run still shows its original 40% and $80.00. Comparing these two records reveals a $10.00 rate effect. Replacing the old percentage with today’s setting would erase the reason the earlier result differed.

Retrieve the right view for the next task

The detail export is a practical inspection file. It is not a digital signature or an independently certified audit. The app does not automatically deliver it to another person or submit it to payroll.

  1. Open Archive and identify the run by name and inclusive period dates.
  2. Download Summary CSV for staff totals and the saved basis.
  3. Open the run and choose Detailed audit CSV for line calculations, treatments and notes.
  4. Keep the original report reference and a workspace backup with your close records.

Preservation and recovery are separate jobs

Ordinary account saves cannot rewrite completed history. An explicit restore is a separate operation: the server keeps the prior workspace snapshot, retains previous closed runs as archived records and labels restored history as imported provenance. A restored file therefore should not be mistaken for a newly verified close. The database and exports still need appropriate storage. Files placed in an iCloud Drive location may sync through that service; the local application itself does not provide hosted backup or multi-user synchronisation.

Put it to work.

Follow the actual steps from a reviewed statement to its downloadable record.

See the close procedure

A record you can check.
A number you can explain.

Explore a sample run