Accounts receivable: invoicing, collections, and customer portal.

Invoicing

Send a branded invoice. Track it through to paid.

Invoices carry your branding, PDF output, and email send. Recurring invoicing posts on the schedule you set via SmartGL. Customer portal access via tokenized URL lets customers view and download statements without a login.

• Custom branding, PDF generation, email send.
• Recurring invoices with auto-posting.
• Customer portal with tokenized URL.
• Credit notes and customer credits.
• Multi-currency invoicing.

Collections

AR aging and collections follow-up.

AR aging reports cover current, 1-30, 31-60, 61-90, and over 90 buckets. Collections centralizes follow-up: AI-drafted collection emails (single or bulk), a per-invoice activity log, and collection statuses driven by real aging. ASC 326 allowance for doubtful accounts uses the aging-bucket method.

• AR aging across standard buckets.
• AI-drafted collection emails, single or bulk.
• Bulk statement runs (open-item or activity).
• ASC 326 allowance, using the aging-bucket method.

Recognition

Ties to revenue recognition.

When an invoice line belongs to a revenue arrangement, the recognition schedule on Growth and Enterprise governs when revenue posts. See /features/revenue-recognition. Multi-invoice payment allocation handles early-pay discounts and write-offs.

Why Quoining

Invoicing, collections, and recognition in one motion.

When invoicing lives in one tool and accounting in another, deferred revenue and collections fall into the gap. Quoining's AR runs on the ledger: invoices, payments, credit memos, statements, collections, and ASC 606 recognition share one source of truth.

• Recurring invoices, customer portal, and statement runs included.
• Collections workflows driven by real aging, not exported lists.
• Revenue recognition attaches to the invoice line, not a side system.