Software & apps
What does “paid” mean in your finance software?
Follow an invoice through the product's actual states, distinguishing document changes from confirmed movement of money.
Capri Video · Updated · 1 min read
An invoice can be created, sent and marked with several payment-related states. Buyers need to know what each one means in your product. Follow a fictional transaction and show which action or information changes its status.
Keep the invoice and its status together
Show a sample invoice moving through confirmed steps. Distinguish manual changes from information received through an established connection. A moving payment icon should not imply completed funds movement when the screen only confirms a request or intermediate state. Keep the same transaction details across views so the meaning remains traceable.
Prepare a consistent demo
Prepare a demo transaction, the rules behind its statuses and details of the integrations being shown.
Use fictional demo data and record the screens and product version shown. Check who acts in each scene and what the screen actually confirms.
Try it before the next demo
Use it on the feature page or in onboarding. Ask what the status confirms and what's still unknown. If viewers confuse a document state with completed payment, fix the labels or transitions. Keep the clip about product behavior, with accounting, tax and financial advice outside its purpose.