Small business guide
How to review a voice-drafted money record before saving it
Voice input can turn a spoken description into a draft, but the draft still needs review. Describe one completed event, check the transcript and fields, then confirm that it should be saved. This general method can be used with recordings, transcription or spreadsheets; it is not a product tutorial, accounting or tax advice, or a substitute for an actual payment.
Describe one event with enough context
First decide whether you are asking about existing records or adding a new one. Asking how much you spent today is not the same as asking to save an expense. For a new entry, state the date, event, incoming or outgoing direction, amount and actual status. Avoid descriptions such as “that one” or “same as before” when their meaning depends on missing context.
Example: “Today I bought wrapping paper, paid 48 yuan, and the payment is complete.” If it is only a planned purchase, say that it is a reminder rather than money already paid. When one recording contains several events, separate them into individual drafts and review each. Do not divide a combined amount between items by guesswork.
Check the fields that change the meaning
Check incoming versus outgoing first, followed by the amount, decimal point, date and person or business involved. Similar-sounding numbers can be confused, and relative dates can be interpreted incorrectly. Read the transcript or replay the recording. Replace “yesterday” with a specific date, and leave missing information unresolved instead of silently treating it as today.
Review suggested categories and linked records as well. A correct amount may still be attached to the wrong purchase or customer. If names repeat, amounts match several events, or a category is unfamiliar, look up the source before proceeding. Include only the information needed for the task, and avoid speaking sensitive personal details where other people can hear them.
Confirm the specific draft you have just reviewed
After reviewing, say something specific such as “Confirm this 48-yuan payment for wrapping paper,” or use the confirmation control for that draft. Acknowledgments such as “I heard you” should not stand in for permission to save. If you change the amount or date, review the complete revised draft and confirm that version rather than relying on an earlier approval.
Review batch drafts individually, particularly when some events have happened and others are only plans. After saving, look for an explicit result and a record reference. Producing a draft and successfully saving it are different states. Leave uncertain items for review instead of confirming the whole batch just to clear the list.
Check an uncertain save before repeating it
If the connection drops or a page stops responding, look in recent records for the date, amount and event you just submitted. Retry only after establishing that it was not saved. This reduces accidental duplicates. When correcting an error, retain the reason; do not hide a transcription mistake by adding an unrelated entry in the opposite direction.
Practice the review sequence with one simple event; OpsSense is in development with separate voice-query and write-draft paths, keeping explicit confirmation as the boundary for changes.