Q360 is great at sales. It's not an AR automation platform.
Solutions360's Q360 is the ERP that system integrators live in — project management, inventory, service tickets, CRM. It's exceptional at everything that happens before the invoice goes out. What it's not exceptional at is everything that happens after: chasing payments, reconciling card-on-file, handling customer self-service, automating the dunning emails that nobody wants to write.
Most Q360 shops we work with end up doing AR manually — exporting an aging report to Excel, writing follow-up emails by hand, taking credit card payments over the phone, and re-keying the same payment data into both the gateway and Q360. It works. It also consumes 8-15 hours a week of AR staff time per billing cycle.
Manual AR on Q360 means slower cash collection, more keying errors, and a customer experience that feels like 2005. Your sales team closed the deal in a modern CRM — why is the customer getting a PDF invoice in a plain-text email?
Rubi Pay for Q360 — two editions, same goal.
Rubi Pay closes the AR gap on Q360 with two deployment options depending on how much automation you want and how ready your processes are for a full portal experience.
Automate the boring parts of AR. Keep Q360 as the source of truth. Let customers pay the way they already pay everyone else.
Edition 1 — Portal (full AR automation).
The Portal edition connects Q360 to Invoiced, a dedicated AR automation platform Rubi has deep expertise with. Invoices sync from Q360 to Invoiced automatically. Customers get a branded payment portal where they can view open balances, pay online, set up auto-pay, download statements, and manage their account.
What the Portal edition gives you:
- 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 — customers view their open balances, pay invoices, download statements, update card on file without calling your office
- Payment write-back to Q360 — once a payment clears, Rubi Pay posts it to the right invoice in Q360 so your AR aging is always accurate
Edition 2 — Links (embedded pay-links, simpler deployment).
Not every Q360 shop is ready for a full portal. Some just want their customers to be able to click a link and pay — no account creation, no portal login, no Invoiced subscription. The Links edition does exactly that.
Every Q360 invoice gets a secure payment link embedded in the PDF and the email. When a customer clicks, they land on a Cognito Forms–backed page wired to your Stripe account. They enter their card. The payment processes. The result writes back to Q360 via the API — same invoice, marked paid.
Portal vs Links — which edition fits?
Links — 1 week if your Stripe account is already set up.
What Q360 shops typically save.
Agencies we've deployed Rubi Pay for typically see:
- 30-50% faster payment cycles — customers paying within days instead of weeks because the pay button is one click away
- 8-15 hours per week back on the AR team's calendar — no more manual dunning emails or phone-call payments
- Fewer reconciliation errors — payments land in Q360 against the right invoice automatically, no transposed digits
- Happier customers — self-service access to invoices, statements, and payment history without having to call your office
A 40-person AV integrator we worked with was running 8 hours a week on AR follow-up before Rubi Pay. After the Portal edition went live, that dropped to under 1 hour/week, and their average days-to-pay dropped from 38 to 19.
Frequently asked questions.
Only for the Portal edition. The Links edition uses Cognito Forms + Stripe and doesn't require Invoiced at all.
Yes — many shops do exactly that. Links gives you the immediate pay-now functionality; once you see the value, we migrate you to the full Portal edition when AR volume or team size justifies it.
Both editions support partial payments. Customer can pay a portion of the invoice and the remaining balance stays in Q360's AR. Great for project milestones or "pay this much today, the rest next month" situations.
Portal edition: yes, via Invoiced's ACH rails. Links edition: ACH depends on your Stripe account configuration — if Stripe ACH is enabled for your account, we can wire it into the Cognito form.