Choose itemised sales
Export individual service and retail lines for the relevant invoice dates. A daily total cannot explain a staff-level difference. You need a reference, date, staff member, item, category and amount for each line.
Keep your original export
Trimsum retains the uploaded column names and original values beside each imported row. Keep the original file too. It is useful when checking a source report or discussing a correction.
Check dates and staff attribution
Select the correct day/month format during import. Use the staff member who earned the commission, which may differ from the person who processed the payment. Rows outside the selected pay period remain in the draft.
Separate service and retail
Map each line to Service or Retail. Unknown categories are held for review until corrected. Keep refunds negative and supply explicit tax values where your export contains them; otherwise check the tax setting before finalising.
Avoid importing the same sale twice
Replacing a draft and appending a file have different effects. Appending overlapping exports can introduce duplicates. Trimsum flags matching source fingerprints and separately checks whether a line was already included in a finalised run. Review the underlying rows before excluding either.
Use the mapping preview
Files can be comma-, tab- or semicolon-delimited. Preview the detected fields and sample rows before accepting the import. A malformed row stops the import, rather than silently losing a sale. The current limit is 8 MB and 15,000 rows per draft.
See it in a real workflow.
Use the illustrative sample workspace to try a review and export a statement.
Open the sample run