Channeltally

Service businesses may accept card payments, peer-to-peer transfers, bank transfers, cash and checks while invoicing in a separate system. The same payment can appear in an email, bank feed and processor export, or arrive with no usable invoice reference. Channeltally brings those observations into one reconciliation queue.

The product never turns an observation into cash truth automatically. A processor event can be pending or reversed; a bank line can aggregate transactions; an email receipt can be spoofed; cash and checks require operator evidence. Matching produces a candidate with reasons and uncertainty. A finance owner approves the link and any ledger posting. Observed, authorized, settled, matched, posted, refunded and disputed remain separate states.

The supplied research confirms limited direct access for some peer-to-peer rails and suggests authorized linked-bank reads or receipt parsing as fallbacks. Those fallbacks cannot impersonate a provider interface or prove payer identity. The first release supports exports and one verified bank or processor source, with explicit unmatched and duplicate queues.

An owner, bookkeeper or finance operator at a service business that invoices customers centrally but receives payment through several disconnected channels.