The AR platform built for enterprise finance teams
Invite-only evening at The Times Center on October 21 will convene 150 CFOs, operators, founders and researchers
Four realistic routes to connect QuickBooks to Claude, what each can and cannot do, OAuth scopes and security, and the AR questions a ledger cannot answer.
One wire, nineteen invoices and the buyer's own voucher numbers. How to use subset sum matching, payer behaviour and on-account balances the right way.
A complete guide to automating collections in 2026: invoice delivery, portal acceptance, follow-up, reply handling, cash application and what to keep manual.
Most annoyance comes from repeating a question the customer already answered. Segment by why an invoice is late, match the channel, and stop when they reply.
A dispute is a claim with an owner and a deadline rather than a refusal. Split the contested line from the balance, send evidence, reach who can release it.
A customer paid less than the invoice. How to classify the gap, apply the cash, choose a credit memo or a residual, and keep your aging report honest.
Money arrived with no invoice reference and an unfamiliar payer name. Work the identification hierarchy: amount, name, history, bank, then the customer.
Eight groups of questions to ask an AR automation vendor, with what a good answer sounds like, what a vague answer tells you, and how to test every claim.
Most late payment is process failure rather than unwillingness to pay. The six real causes, how to tell them apart, and why one dunning cadence fails.
