Concepts

How Rhythm works out how much of a credit is still available to spend, where staff see a customer's open credit balance, and why a credit's status badge does not tell you whether it has been fully used.

What appears on a customer balance statement, how Rhythm groups open invoices by how overdue they are, which template it uses, and how a billing run can send statements automatically.

How Rhythm spreads a payment across an invoice's lines, what happens to money left over after everything owed is paid, how existing credit can be spent inside a payment, and why a payment that looks correct can still be refused.

How Rhythm chooses a payment's business unit, cash or merchant account, and payment processor when nobody names one, what a debug-mode merchant account is for, and why a card charge can fail for reasons that have nothing to do with the card.

How Rhythm turns a checked-out order into an installment schedule, why the amounts and dates land where they do, what happens to the saved payment method, and how a cancellation or return shrinks or removes the schedule.

How Rhythm assigns a batch to a new invoice, payment, refund, credit, or write-off when nobody names one, how a refund or cancellation follows the batch of the money it reverses, and what to do when a transaction is refused because of its batch.

Why an electronic check payment starts out pending, how Rhythm later learns that its funds settled or that the check was returned, and what that clearing outcome does and does not change on the payment.

What a billing run's planning stage looks for before anything is charged or sent, why a particular customer did or did not end up in the plan, and what the review report you get once a plan is ready actually tells you.

What happens to an installment schedule after each entry's charge or repeat order finishes, why a schedule shows as payment declined instead of error, and when a schedule closes as completed on its own.

What closing a fiscal period does beyond marking it final, why a revenue recognition schedule can close on its own, what reopening actually undoes, and what to check if a close or reopen fails partway through.

What ledger entries posting writes for invoices, payments, refunds, credits, write-offs, and memos, and the rules every entry has to follow.

What happens after you submit a refund or payment credit — why it can take a moment to finish, which batch it lands in, and what to do if a background refund or credit fails.

How Rhythm spreads a product's revenue out over the months it's earned instead of recognizing it all at once, and what happens to that schedule when the sale is credited, written off, or refunded.

How Rhythm adds your organization's card processing fee to an invoice before charging a card, why some invoices can't be paid by card, and how the fee still reaches an invoice whose batch already posted.

What an invoice is in Rhythm, how its number, due date, batch, and balance stay correct as it's created and worked with, and why records used on an invoice can't be deleted.

What happens once a billing run starts carrying out its plan — charging due installment schedules, notifying customers, cancelling declined schedules, sending statements — and what the finished report tells you.