Skip to content
Showcase

Rubi Pay for Q360

Automates accounts receivable (AR) and integrates payment processing with Q360.

◆ View product documentation →

Q360 collections

System integrators use Solutions360's Q360 for project management, inventory, service tickets, and CRM. Once an invoice goes out, accounts receivable teams often handle reminders, card payments, and reconciliation by hand.

Rubi Pay for Q360 Portal Edition demo Open on Loom
Rubi Pay for Q360 Links Edition demo Open on Loom

Staff may export an aging report to Excel, write follow-up emails, take payments over the phone, and post the same payment in the gateway and Q360. Each handoff takes time, can introduce errors, and gives customers fewer ways to pay.

Payment options

Both editions post cleared payments to the correct Q360 invoice automatically. Choose customer self-service and collections automation with Portal, or add a pay link to each invoice with Links.

Portal edition

Portal connects Q360 to Invoiced to run automated collections and a branded payment portal.

Process diagram 1
Fig 01 · Portal edition: two-way sync between Q360 and Invoiced
  • Invoice + customer sync: new invoices in Q360 flow to Invoiced within minutes, with line-level detail and customer account mapping
  • Automated delivery: email or physical mail, configurable per customer
  • Multiple payment methods: credit card, ACH, wire, PayPal, auto-pay on file
  • Collections automation: dunning email sequences fire automatically based on aging buckets (30/60/90 days)
  • Customer self-service: View open balances, pay invoices, set up auto-pay, download statements, and update cards on file.

Each Q360 invoice PDF and email includes a secure payment link. It opens a Cognito Forms page connected to your Stripe account, where customers can pay by card without creating an account.

Process diagram 2
Fig 02 · Links edition: lightweight pay-now flow
Portal edition Best for teams with 200+ active AR customers, multi-invoice billing, or recurring collections work. Requires an Invoiced subscription and a Rubi integration fee.
Links edition Best for smaller AR teams or one-off project billing. Requires Stripe transaction fees and Rubi setup.
Time to deploy Portal: 3 to 5 weeks depending on Invoiced config complexity.
Links: 1 week if your Stripe account is already set up.
Write-back to Q360 Q360 remains the source of truth for AR aging in both editions.
PCI scope Both editions use tokenized card capture (Stripe Elements or Invoiced's vault). Your Q360 database never sees a card number.

Payment results

In prior deployments, teams reported 30–50% faster payment cycles and 8–15 hours per week back from manual reminders and phone payments. Posting to the correct invoice also cuts reconciliation errors.

Real-world example

After adopting Portal, a 40-person AV integrator cut weekly AR follow-up from eight hours to under one and average days to pay from 38 to 19.

FAQs

Do we need an Invoiced subscription?

Portal requires Invoiced. Links uses Cognito Forms and Stripe.

Can we start with Links and upgrade later?

Yes. Start with pay links and move to Portal as AR volume or team size grows.

What about partial payments?

Yes. Both editions support partial payments, such as project milestones. Q360 retains the remaining balance.

Is ACH supported?

Portal supports ACH through Invoiced. Links supports it when your Stripe account has ACH enabled.

Let's put this to work for your team.

Book a 30-minute call. We'll walk through your current stack and show you exactly how we'd approach your situation.