<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Payments on Vio</title>
		<link>https://hellovio.app/tags/payments/</link>
		<description>Recent content in Payments on Vio</description>
		<generator>Hugo</generator>
		<language>en-US</language>
		
		
		
		
			<lastBuildDate>Wed, 21 Oct 2026 00:00:00 +0000</lastBuildDate>
		
			<atom:link href="https://hellovio.app/tags/payments/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Send invoices &amp; mark them paid without leaving chat</title>
				<link>https://hellovio.app/blog/sending-invoices-and-tracking-payments/</link>
				<pubDate>Wed, 21 Oct 2026 00:00:00 +0000</pubDate>
				<guid>https://hellovio.app/blog/sending-invoices-and-tracking-payments/</guid>
				<description>&lt;p&gt;The order was packed, the goods went out, the invoice landed in the customer&amp;rsquo;s chat. Two weeks later they ask for a copy, and you start scrolling — was their version before or after you fixed the shipping cost? The actual question — &lt;em&gt;has this customer paid?&lt;/em&gt; — still lives in your head, alongside eleven other orders you&amp;rsquo;re waiting on.&lt;/p&gt;&#xA;&lt;p&gt;The gap between &amp;ldquo;sent&amp;rdquo; and &amp;ldquo;known to be paid&amp;rdquo; is where invoices quietly rot in a lot of small businesses. In Vio, both sides of that gap are records: the invoice is generated from the order and stays linked to it, and payment is a set of fields you update on the order itself. This tutorial walks the full loop — invoice, send, mark paid — and shows which steps you can run by chat with your assistant instead of on the screens.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
