How the Tabs <> Rillet Integration Works

Last updated: October 27, 2026

Overview

The Tabs <> Rillet integration keeps customers, invoices, payments, and accounting data aligned between the two systems.

Tabs pulls reference data from Rillet on a schedule (and when you Sync from the dashboard). As you work in Tabs, invoices, credit memos, customer updates, and month-end journal entries push to Rillet. Payments that are matched or applied in Rillet sync back into Tabs.

Tabs does not receive Rillet webhooks. Payment and reference-data updates arrive through scheduled sync and any manual sync you run from Tabs.

What Syncs from Rillet to Tabs

During initial setup, Tabs imports existing supported records from Rillet. After setup is complete, Tabs continues to sync supported records on an ongoing basis.

Tabs imports the following objects from Rillet:

  • Customers

  • Products / Items

  • Chart of Accounts

  • Bank Accounts (included as part of the Chart of Accounts import)

  • Payments (onto invoices that already exist in Tabs and are linked to Rillet)

Tabs does not import invoices from Rillet. There is no historical or Rillet-originated invoice import. For invoices you send from Tabs, Tabs is the source of truth, and edits made only in Rillet do not flow back.

Tabs does not import credit memos from Rillet. Credit memos sync Tabs → Rillet only.

What Syncs from Tabs to Rillet

Tabs pushes the following objects to Rillet:

  • Customers (new records and updates)

  • Invoices (after they are sent)

  • Credit memos

  • Journal entries (month-end close, when Close Management is enabled)

Source of Truth

Tabs is generally considered the source of truth for:

  • Invoices

  • Journal entries

Rillet is generally considered the source of truth for:

  • Payments

  • Products

  • Chart of Accounts

Customer Sync

Customer sync is bi-directional.

Rillet → Tabs

Existing customers in Rillet are imported into Tabs during initial setup and ongoing syncs.

Tabs → Rillet

New customers and customer updates created in Tabs sync to Rillet automatically.

Customer Requirements

Before invoices can be sent:

  • Customer name must exist

  • Billing address should be populated

  • Primary email should be populated

Invoice Sync

When an invoice is sent in Tabs:

  • The invoice syncs to Rillet automatically

  • The invoice is marked as sent in Rillet

  • Tabs remains responsible for invoice delivery and numbering

Draft Invoices

Draft invoices do not sync to Rillet.

Invoices are only synced after they are sent.

Invoice Changes

Tabs is the source of truth for invoices.

Changes made directly in Rillet do not sync back to Tabs.

Invoice Reset Behavior

If a sent invoice is reset back to draft in Tabs:

  • The corresponding invoice is removed from Rillet

  • Re-sending the invoice recreates it in Rillet

Credit Memo Sync

Applying a credit memo in Tabs automatically syncs the credit memo to Rillet.

Supported workflows include:

  • Invoice-level credit memos

  • Customer-level credit memos

  • Invoice write-off credit memos

Payment Sync

Payment Sync

Payments sync from Rillet into Tabs. Apply or match cash in Rillet; Tabs then picks those payments up on the next sync for eligible invoices.

  • Payments matched or applied in Rillet sync to Tabs to eligible invoices

  • Payments you record only in Tabs do not automatically create matching payments in Rillet. Resolve cash application in Rillet so the two systems stay aligned.

  • If Tabs shows an invoice as paid before the payment is matched in Rillet, finish the match in Rillet, then let sync catch up.

  • Cancelling or deleting a payment in one system does not automatically cancel it in the other today. Ask Tabs Support if you need help cleaning up a mismatch.

  • Any reconciliation discrepancies should be resolved within Rillet.

ACH Credit Notify and Pending invoices:

This is the workflow that most often surprises teams.

  1. A customer pays with ACH Credit and chooses Notify in the portal. Tabs creates an Open payment, and the invoice moves to Pending.

  2. While the invoice is Pending, Rillet payment sync skips it. You will not see a special “blocked” message in Tabs. Apply the cash in Rillet as usual; Tabs will not pull that payment until the invoice leaves Pending.

  3. When you are ready for Tabs to pick up the Rillet payment: move the invoice out of Pending (for example, back to Sent); remove or cancel the Open (Notify) payment row on the invoice in Tabs; then run Sync (or wait for the next scheduled sync).

  4. Sync can then create a Completed payment from Rillet and update the invoice toward Paid.

Linking alone is not enough. If you leave the Open Notify payment in place, sync may attach Rillet’s payment ID to that Open row, but it will not flip the payment to Completed or mark the invoice Paid. Clear the Open/Pending Notify payment first, then sync.

Stripe Payments

Stripe payments can reconcile across both systems using the shared Stripe transaction ID.

Journal Entry Sync

Journal Entries sync from Tabs to Rillet through a user-triggered workflow during month-end close.

Key Details

  • Journal Entries do not sync automatically

  • Close Management must be enabled

  • Entries are pushed in batches (one Rillet journal entry per customer per period)

Products and Chart of Accounts

Tabs imports:

  • Products / Items

  • GL Accounts

  • Bank Accounts (included as part of the Chart of Accounts import)

Create products in Rillet before you use them on Tabs invoices. Tabs owns the revenue-account mapping used for month-end journal entries, so set those accounts on the items page in Tabs after products are imported.

Currency Handling

If multi-currency is enabled in Rillet:

  • Tabs uses the customer currency configured in Rillet

  • Exchange rates are provided by Rillet

Tax Handling

Tabs supports tax providers integrated with the Rillet workflow.

Tax amounts are included when invoices and credit memos sync to Rillet.

Additional Considerations

Write-Off Product Configuration

Rillet does not currently allow Tabs to dynamically create write-off products through the API.

If write-off workflows will be used, any required write-off products should first be created in Rillet.

Practical Tips

  • Connect with a Rillet API key from your Tabs integrations settings. Sandbox keys use Rillet’s sandbox environment; production keys use production.

  • Use dashboard Sync after you apply cash in Rillet, or after you clear a Notify payment and move an invoice out of Pending.

  • Keep products and write-off products current in Rillet so invoice and credit memo pushes succeed.

  • Treat Rillet as the place you match payments, and Tabs as the place you send invoices and run month-end close.

If something looks out of sync after following the steps above, contact Tabs Support with the customer name, invoice number, and what you already tried in Rillet and Tabs.