Collect payments
Tabs collects payments from your customers and matches them against open invoices. This section covers connecting a payment processor, recording payments that arrive outside one, matching bank deposits, and chasing what’s overdue.
How the money reaches you depends on which processor you use. What happens on the invoice is the same either way.
How collection works
Tabs sends an invoice to your customer carrying a payment link. The customer pays—through the payment portal by card or bank account, through recurring “Autocharge” payments set by you, or outside Tabs entirely by check or wire. Tabs records a payment against the invoice and updates the invoice status. If you’ve connected your bank, Tabs matches the deposit to that payment once the cash lands. Either way, Tabs writes the journal entry to your ERP.
The part worth knowing up front is that an invoice can be settled before the cash arrives, and that the status you see depends on whether you run cash application.
With cash application enabled, an invoice paid through a processor moves to “pending” rather than “paid”, and stays there until Tabs confirms the matching bank deposit (or your payout lands). This is when the payment syncs to your ERP. Dunning pauses while an invoice is pending. Without cash application, the invoice moves straight to “paid” instead.
Choose how you collect
You run one payment processor at a time—Tabs Pay and Stripe aren’t used side by side. Plaid is separate and works alongside whichever processor you use, since it reads your bank feed rather than collecting payments.